| reply to jcmh
Re: World IPv6 Day said by jcmh:If you can't get what you want over IPv6, then there's no point. There is a point: avoid the need for double-NAT at the ISP level, replacing it by a 4to6 gateway once ISPs get to the point where they might start having to put their subscribers on CG-NAT.
said by jcmh:As for CPE routers etc... Most of these problems can be fixed with firmware/software updates anyways. They may be upgradable/fixable but for now, many of them still require manual setup for IPv6 which is counter-productive for adoption. |
|
brad
join:2007-09-06
Etobicoke, ON | said by InvalidError:They may be upgradable/fixable but for now, many of them still require manual setup for IPv6 which is counter-productive for adoption.
You have to configure new CPE anyway.
Most of the manual setup I've seen is because ISPs do not have their side setup properly. TSI being one such ISP. |
|
| said by brad:You have to configure new CPE anyway. You do not need to manually setup IPv4 subnet, you get that from PPPoE or DHCP. With IPv6, many broadband routers only support manual setup.
said by brad:Most of the manual setup I've seen is because ISPs do not have their side setup properly. TSI being one such ISP. Automatic setup works fine with TSI IPv6 using Windows' dialer. Simply enable IPv6 in the dialer config and connect. |
|
brad
join:2007-09-06
Etobicoke, ON | said by InvalidError:You do not need to manually setup IPv4 subnet, you get that from PPPoE or DHCP. With IPv6, many broadband routers only support manual setup.
The comment was about configuring the router period. When you buy the router for the first time it has to be setup. Especially so if you're using PPPoE.
Yes and they have to be manually setup because the ISP hasn't setup their end properly.
said by InvalidError:Automatic setup works fine with TSI IPv6 using Windows' dialer. Simply enable IPv6 in the dialer config and connect.
Exactly. An end host vs a router. Your host is using an address configured via RA. The routers need DHCPv6-PD.
That doesn't change what I said. TSI still needs to fix their end of things. |
|
| said by brad:Exactly. An end host vs a router. Your host is using an address configured via RA. The routers need DHCPv6-PD. Route Advertisement / SLAAC works just as well for routers and hosts since if you advertise a /64 to a host, it will simply fill the remaining 64 bits using SLAAC if enabled, which it is by default. A router would simply use the subnet address to generate its WAN address (usually whatever::1) and either re-advertise the subnet on the LAN or start allocating addresses from that IPv6 subnet using local DHCP.
Routers do not need to receive their IPv6 allocation through DHCPv6. All the IPv6 papers I remember reading say RA/SLAAC prefix delegation is the preferred method in the absence of specific reasons to use DHCP such as wanting to manage static IPv6 addresses using DHCP. |
|
brad
join:2007-09-06
Etobicoke, ON | said by InvalidError:Route Advertisement / SLAAC works just as well for routers and hosts since if you advertise a /64 to a host, it will simply fill the remaining 64 bits using SLAAC if enabled, which it is by default. A router would simply use the subnet address to generate its WAN address (usually whatever::1) and either re-advertise the subnet on the LAN or start allocating addresses from that IPv6 subnet using local DHCP.
Routers do not need to receive their IPv6 allocation through DHCPv6. All the IPv6 papers I remember reading say RA/SLAAC prefix delegation is the preferred method in the absence of specific reasons to use DHCP such as wanting to manage static IPv6 addresses using DHCP.
I'll have to track this down to see if this has changed but the spec does not allow for RA on a router. You're not supposed to use RA on a host with more than one interface. Ya I know that's kind of strange nowadays and even end hosts can have more than one interface nowadays but that's how it was defined.
Also I didn't mean the /64 for the PPP interface. I was referring to the /56 or whatever prefix for behind the router. AFAIK RA does not propagate such prefixes anyway and that's why I'm mentioning DHCPv6-PD. |
|
