MikroTik

If I have two MT boxes, one setup up as an IPv4 PPPoE server and the other as an IPv4 PPPoE client, I can add IPv6 to this connection by simply adding DHCPv6 to the PPPoE tunnel. First I create an IPv6 pool on the server with my desired Prefix (>/64) and a Prefix Length of 64. Then in the PPPoE server profile, I set DHCPv6 PD Pool to the name of the pool I just created. On the client I add the DHCPv6 Client to the pppoe-out interface. I make up a name for the pool and set the prefix length to 64 in the DHCPv6 Client. When I check my PC connected to the client LAN interface, I now have a Global IPv6 address and a link-local gateway address; everything works.

Now I remove the MT Client and add a router such as the Linksys EA3500 which is supposed to be IPv6 ready. When I check the PC, it has a Global IPv6 address from my pool, but there is no default gateway. When I check the RA announcements, I see that the router lifetime is set to 0s, meaning, "I'm not a default gateway". I've tried three different brands of routers all with the same result.

So, my questions. Does anyone know why the MT client router succeeds where the others fail? Does anyone know of a router brand that works with a dual IP stack to a native IPv6 network over PPPoE? And best of all, does anyone know what needs to be added to the MT server that will make non-MT routers work?

Using Wireshark, watching the traffic between the MT server and the EA3500, we see the EA3500 asking for a non-temporary address and prefix. However, the MT server returns only the prefix and no address.

According to RFC 6204, if the EA3500 does not receive an address, then it is not supposed to advertise itself as a default route on the LAN interface - and it doesn't.

So, I guess the question is how do you configure the MT server to hand out a non-temporary address. The MT Client does not appear to follow RFC 6204. In fact, the MT client creates a default route even when it is told not to in the DHCPv6 Client setup (bug?).