> > One of the interfaces, say eth1, is connected to an IPv6-only network that > doesn't do DHCPv6-PD. Another one is connected to an HNCP network, with > some other router publishing an IPv6 prefix delegation. > > eth1 > IPv6-only network ----- me ----- (HNCP network) ----- HNCP router with PD > > Since there's neither DHCPv6-PD nor DHCPv4 on the IPv6-only network, eth1 > is detected as internal. Since there's an IPv6 prefix delegation, the > HNCP daemon allocates a /64 to each link connected to each of its internal > interfaces and starts sending RAs on eth1. > > I'm now sending RAs on a production network, with no way for the network > administator to prevent that short of either (1) reconfiguring my router > (and any other Homenet routers that might be connected to this network), > or (2) enabling stateful DHCPv4 or DHCPv6-PD. I'm sorry, to me this seems a bit farfetched to blame this case on HNCP. If you would have connected any device that serves RA / DHCP on that interface you would have the exact same results. Since that can happen even with the HNCP router in place you would need to deal with it anyway.
Plus if a rogue RA / DHCP on one link breaks your whole "production network" you probably have other issues besides that. Personally I don't see the point here, to add logic and complexity to address this in HNCP - it just looks like the wrong place to fix it unless the general consensus is different. Cheers, Steven _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
