IPv6 from home
May. 8th, 2016 09:35 am![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
mtbcA few years ago I experimented with IPv6 from home; my ISP offered a tunnel that I could reach over IPv4. I got things working reasonably except for that my wireless access points seemed to swallow my router advertisements so I postponed the effort. Incidentally, access points that I subsequently owned had a different surprise where they would swallow certain DHCP responses in a manner happening to exactly fit a bug in a certain version of Linux.
My current ISP offers IPv6 directly and this morning I thought I would get around to taking another look at it. Our home gateway/router runs OpenBSD 5.9 and gets its IP address from our ISP over DHCP. I have now managed to get it to a state where I can ping6 other external machines. However, it starts working only after ifconfig pppoe0 inet6 autoconf and my reading suggests that perhaps routers oughtn't do this, at least not after I someday use sysctl to turn on net.inet6.ip6.forwarding to offer IPv6 internally. For the moment I block IPv6 traffic on the internal-facing interface as I have rather more research to do before allowing it, especially regarding blocking some ICMP: I tread carefully when I know I'm in new waters.
I do actually have a static address assignment from my ISP, perhaps I ought to just set that and see if I can still get to a state where I can ping6. For now I'm still trying to scrape together a clear picture from what I can find out online. It certainly doesn't seem to be as trivial as IPv4.
My current ISP offers IPv6 directly and this morning I thought I would get around to taking another look at it. Our home gateway/router runs OpenBSD 5.9 and gets its IP address from our ISP over DHCP. I have now managed to get it to a state where I can ping6 other external machines. However, it starts working only after ifconfig pppoe0 inet6 autoconf and my reading suggests that perhaps routers oughtn't do this, at least not after I someday use sysctl to turn on net.inet6.ip6.forwarding to offer IPv6 internally. For the moment I block IPv6 traffic on the internal-facing interface as I have rather more research to do before allowing it, especially regarding blocking some ICMP: I tread carefully when I know I'm in new waters.
I do actually have a static address assignment from my ISP, perhaps I ought to just set that and see if I can still get to a state where I can ping6. For now I'm still trying to scrape together a clear picture from what I can find out online. It certainly doesn't seem to be as trivial as IPv4.
