Subj : IPV6 and Netgear To : Kees van Eeten From : Markus Reschke Date : Wed Aug 10 2016 14:27:34 Hello Kees! Aug 09 22:06 2016, Kees van Eeten wrote to Michiel van der Vlist: TL>>> I get a dialog box where you put in the "interface ID", which is the TL>>> host part of the IPv6 address. MvdV>> Having to enter only the host part instead of the entire 128 bit MvdV>> address makes sense. KvE> No it is confusing. It only makes sense if you only use one subnet KvE> In my setup it works for 2001:980:42ea:1::..... KvE> But what about the subnet. 2001:980:42ea:fd::..... The idea behind the interface part is, that a system may have several prefixes. Might be simpler to grasp for a normal user. KvE> To me it looks like only hosts on the direct connected LAN can be KvE> exposed to the Internet. When you think about it. It is probably not KvE> a bad thing, but it is a limitation that forced upon me. I'd rather KvE> decide for myself. It brakes the whole idea of prefix delegation, i.e. the router allows only one large flat network. That's a nightmare from a security standpoint. The vendors of SOHO routers still have to learn a lot about IPv6. And those "IPv6 ready" labels are total marketing BS. Half-baked IPv6 support, broken firewalls, lack of standard features and what have you. At the moment it's simply e-junk, which should be returned to the seller. Sorry for being harsh, but the vendors just need to create a proper web interface for the functions already in the OS (linux) or in open source daemons. It's so . Or they could collaborate with OpenWrt, which is years ahead. And before I forget to mention it, there are /126 and /127 xfer networks, rendering the interface input scheme from above useless. ciao, Markus --- * Origin: *** theca tabellaria *** (2:240/1661) .