867 reputation
512
bio website steffann.nl
location Apeldoorn, Netherlands
age 38
visits member for 3 years, 4 months
seen Dec 2 at 16:57

I started working in the Internet industry in 1995, when I helped to start up Computel Standby BV. I supported Computel while I was a student at Universiteit Twente. Computel started in Apeldoorn (NL) as a small ISP, started the Nederland.net foundation, and has grown into a server management company with its own small datacenter.

I became a RIPE Address Policy Working Group chair in May 2007, mostly because I am interested in the future of the Internet and I like to participate in things I think are important.

In May 2008 I left Computel and started working for Max.nl, which is a web application development company. In March 2010 I started my own company. I am focusing on internet infrastructure related subjects such as IPv6, routing and security. Since October 2010 I have been doing IPv6 related projects exclusively.


Nov
11
comment Ubuntu 14.04.1 LTS sever can't access ipv6 hosts
Your router seems to be announcing to your LAN that it can be a default IPv6 gateway and to provision your network with an IPv6 prefix from Comcast with autoconf enabled, but then not able to handle the IPv6 traffic. Maybe the IPv6 settings of the router are wrong, maybe the built-in firewall blocks your outbound traffic or something is wrong with your Comcast uplink. If you aren't a Comcast customer it's definitely the settings :)
Nov
6
comment IPV6 Gives out multiple subnets
SLAAC (Stateless Address Autoconfig) only works on /64 subnets. Don't use /60 on a LAN.
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.
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.
May
4
comment IPv6 does not work over bridge
IPv6 uses ip6tables. Can you check that one as well?
May
4
comment IPv6 does not work over bridge
If the VMs get IPv6 addresses that means there are IPv6 packets going over the bridge from the network to the VM. Otherwise the VMs wouldn't see the router advertisements. Is there any firewalling or filtering on the bridge?
Apr
15
comment How is information passed between ipconfig and the init process at boot time
I think that part goes back to /etc/network/interfaces. What happens when you also add your IPv6 configuration there, using the same settings as you have used earlier in the boot process?
Apr
12
comment How is information passed between ipconfig and the init process at boot time
Agree, it is not the issue here, but it is important :)
Apr
12
comment How is information passed between ipconfig and the init process at boot time
I think ipconfig supports IPv6 just fine, but it is old... These days it is better to use the 'ip' command. Much more flexible.
Apr
9
comment How is information passed between ipconfig and the init process at boot time
Ouch, a /108? While technically possible, that is really not good common practice. Stick to the default /64 unless you know what you are doing and what will and will not work.
Mar
22
comment Set primary IPv6 address
I just wrote a script that waits for given addresses to leave the tentative state. Might be useful in init scripts: pastebin.com/sAgRxbPY
Feb
25
comment How to add two IPv6 dns-nameservers into /etc/network/interfaces?
Also relevant: unix.stackexchange.com/questions/28004/…. It mentions >3 name servers, possible increased timeouts and running a local DNS cache instead of adding more name servers.