3 ms·
They need to be logically accessible because they are managed devices. NAT doesn't work in this case. Of course, IPv6 is the more correct solution, if you can m
by mburns 11y ago
They need to be logically accessible because they are managed devices. NAT doesn't work in this case. Of course, IPv6 is the more correct solution, if you can manage it (no pun intended).
See Comcast's presentation about their motivations: http://meetings.ripe.net/ripe-54/presentations/IPv6_management.pdf http://meetings.ripe.net/ripe-54/presentations/IPv6_manageme...
- tedunangst 11y agoThanks, that's interesting, but doesn't explain why "federated net 10 islands" can't work, except to say it can't. New York (time warner) and Chicago (Comcast) are obviously managed separately. Why can't Comcast manage Boston and Chicago as separate networks? Is every single customer nationwide working off the same dhcp/update/management server, etc.?
- wtallis 11y agoBased on the kinds of multi-state outages they suffer from, I'd say they often are all having all modems hitting the same auth/DHCP/DNS servers. Back when I was on BellSouth DSL, every time they had a DNS outage everybody would reboot their modem and that would bring down the DHCP server, but if you used third-party DNS you could remain online while the entire SE US lost DSL for an hour or two.