On 2014-05-02, Brad Smith <b...@comstyle.com> wrote: > On 02/05/14 10:24 AM, Peter J. Philipp wrote: >> On 05/02/14 16:13, Stefan Sperling wrote: >>> OpenBSD doesn't support IPv6 autoconf on routers (i.e if forwarding >>> is enabled). Some ISPs have started using autoconf to assign a >>> global prefix for use on the WAN link. This violates early IPv6 RFCs >>> which said that a router cannot do autoconf. There is a newer RFC which >>> clears this up but OpenBSD doesn't support it yet: >>> http://tools.ietf.org/html/rfc6204 >>> >>> However, using a global prefix on your WAN link is usually not a >>> hard requirement since link-local addresses are sufficient for this. >>> >>> Try setting a default route that points to pppoe0: >>> >>> !/sbin/route add -inet6 default -ifp pppoe0 fe80:: >>> >>> Your router should now be able to reach the IPv6 internet. >>> >> >> Thanks Stefan for the good explanation and the setting! I'll try it out >> in a bit.
Note that this was broken for about 3 weeks recently; if this "route add" fails with an error when you try it, then try a newer snapshot. >>> Once this works you need to get your LAN connected, too. >>> Did you get a static IPv6 prefix from your ISP for your LAN? >>> >> >> Unfortunately it's all dynamic. M-Net used to be a friend about static >> IP addresses (which allowed me a tunnel to sixxs before), but they have >> turned against giving out static, whether v4 or v6. If I remember right >> they assign a /64 for the link, and give out a /48 somehow which is >> dynamic too. > > You would need a DHCPv6-PD capable DHCPv6 client such as wide-dhcpv6. This is standard configuration for most ISPs doing v6 (both for static and dynamic IPs, though obviously if it's static you have a workaround).
