Reputation
972
Top tag
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
5 12
Newest
 Yearling
Impact
~57k people reached

May
20
comment IPv6 Tunnel behind NAT
Have you tried sixxs.net?
Apr
1
comment Questions about building a native IPv6 router/firewall
A /80 will work fine as long as you manually configure every device. Autoconfiguration won't work though, so you won't be able to get e.g. an android device on that network on IPv6 because they require autoconfiguration. And because your ISP thinks your whole /64 is on the LAN their router provides you have to play tricks with proxy NDP to get routing working to your /80. Better to avoid such tricks and just use the /64 provided by your up as one big LAN until they get proper DHCPv6-PD running.
Apr
1
answered Questions about building a native IPv6 router/firewall
Nov
6
comment IPV6 Gives out multiple subnets
SLAAC (Stateless Address Autoconfig) only works on /64 subnets. Don't use /60 on a LAN.
Aug
13
awarded  Yearling
Jul
16
answered How to force IPv4 on Ubuntu Desktop 14.04
Jul
15
comment IPv6 network is unreachable. until reboot
dataskq is the DirectAdmin Task Queue runner. I never used DirectAdmin so I don't know which kind of tasks are executed by it. I think someone with more DA experience has to answer this...
Jul
15
comment IPv6 network is unreachable. until reboot
You should see default via 2001:xxxx:4300:xxxx::1 dev eth0 metric 1024 in your ip -6 route output. Something is removing it. You might want to see if there is any correlation between certain cronjobs running and this behaviour. Maybe run ping6 -a 2001:4860:4860::8888 while running tail -f /var/log/syslog in a different window and see what showed up in the logs the moment the beeps stop.
Jul
15
comment IPv6 network is unreachable. until reboot
You say the output was from when things are working fine, but without a default route that can't be. You don't have a route to reach i.e. 2001:4860:4860::8888.
Jul
15
comment IPv6 network is unreachable. until reboot
This is strange. Where do all those IPv6 addresses (...:8:: to ...:8::69) come from? Also your routing table doesn't have a default route anymore. You did configure a gateway, but it has disappeared. Something else is interfering with your IPv6 settings...
Jul
15
comment IPv6 network is unreachable. until reboot
Can you add the output of the commands ip -6 addr and ip -6 route?
Jul
9
comment ipv6 network unreachable
@MichaelHampton I know, it does work. However, if you don't have a /64 route for the local subnet everything is off-link and even local traffic has to go through the default gateway. If that default gateway is unreachable you lose all...
Jul
7
comment ipv6 network unreachable
And of course: check your ip6tables settings. You might be filtering ND traffic by accident
Jul
7
comment ipv6 network unreachable
Because I see that the default gateway address is (also) learned through Router Advertisements I am assuming that that address is ok
Jul
7
comment ipv6 network unreachable
The INCOMPLETE neighbour discovery is the problem. If you can't talk to your router then all communication ends (especially because you have your IPv6 address configured as a /128, so you don't have a local subnet (usually a /64) to talk to). This might be because of some strange multicast filtering as IPv6 Neighbour Discovery uses ethernet multicast.
Jul
7
answered Trusty IPV6 is disabled, but applications are still binding to IPV6 address ports
Jun
20
answered IPV6 dynamic route from DHCP
May
29
awarded  Good Answer
May
9
answered ipv6 forwarding kills ipv6 connection?
May
5
comment IPv6 does not work over bridge
Hmmm. Weird. All I can think of right now is to run tcpdump/wireshark/tshark on the interfaces to see where the packets get stuck.