On Tuesday, July 02, 2013 08:31:35 AM Seth Mos wrote: > For now, if you have a mixed client network there is no > getting around advertising both DHCP6 and SLAAC to get > all clients to work. MacOS 10.6 does not have a DHCP6 > client for example. (And yes, I still run that).
Mobile-wise, we're slowly settling into iOS, Android and Windows Mobile (only a few folks are running the Lumia). Some folk running Mac are still on pre-Lion, but those will quickly be moved to Mountain Lion, at least, before we roll out. > Regarding DHCP6 on the WAN we support DHCP-PD, Address or > just DNS resolvers. Last I worked on this we had no > client for RA DNS advertisements yet. The binary radns > does exist but that was never finished. Our corporate WAN runs inside an l3vpn (VPNv4). By the time we get this going, we shall also be deploying 6VPE. > On the LAN side of things we have DHCP6 for the clients > as well as DHCP-PD for the routers so you can > daisy-chain routers, that is how IPv6 is designed to > work. This is also the reason why I fume at the short > sighted providers just handing out a single /64 which is > just braindead and stiffling innovation. Well, we own the backbone, so every office will be assigned a /56. But yes, ISP's should be handing out either /48's or /56's to customers. Although, if you're interested, "draft-ietf- v6ops-64share-07" talks about how a /64 sent to a tethered mobile phone can be extended to a LAN behind the phone. Cheers, Mark.
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ List mailing list [email protected] http://lists.pfsense.org/mailman/listinfo/list
