Looking for thoughts on if this is really an issue!
I recently enabled IPv6 as my ISP (Sky UK) offer it. It was simple enough, simply selected Native mode and my clients got addresses and the router a global scope /56 prefix.
The only thing I've found which is a bit disturbing is the router responds to ICMP ping echo-request from the WAN side.
I have the IPv4 firewall set to not respond to ping on WAN, and also have the IPv6 firewall enabled (not that there are any real options for it).
I can't confess to being an IPv6 guru, but I'm thinking at least the option to blackhole WAN pings should be available?
As an aside, I also got dynv6.com working with a custom DDNS script (not that I have any real use for it - yet). I had to add a 'sleep 60' to the top of the ddns-start script though as the IPv6 address allocation takes 20-30 seconds longer than the IPv4, so on reboot I was updating <blank> IPv6 and would have to wait 24hrs for it to show the change (or do it manually).
I recently enabled IPv6 as my ISP (Sky UK) offer it. It was simple enough, simply selected Native mode and my clients got addresses and the router a global scope /56 prefix.
The only thing I've found which is a bit disturbing is the router responds to ICMP ping echo-request from the WAN side.
I have the IPv4 firewall set to not respond to ping on WAN, and also have the IPv6 firewall enabled (not that there are any real options for it).
I can't confess to being an IPv6 guru, but I'm thinking at least the option to blackhole WAN pings should be available?
As an aside, I also got dynv6.com working with a custom DDNS script (not that I have any real use for it - yet). I had to add a 'sleep 60' to the top of the ddns-start script though as the IPv6 address allocation takes 20-30 seconds longer than the IPv4, so on reboot I was updating <blank> IPv6 and would have to wait 24hrs for it to show the change (or do it manually).