Hi all,
I now have a firm understanding of the NDRA process for IPv6 and have the following quesiton regarding the secondary CPE autoconfig phase of DHCPv6-PD.
I have a working configuration on some Cisco equipment but need to get this working on the MX240.....
LNS configuration (acting as the DHCPv6-PD Server - kind of)
R4(config)#Ipv6 local pool cust-pool1 2001:db8:2:8000::/49 56
R4(config)#Ipv6 dhcp pool ISP-pool
R4(config-dhcpv6)#Prefix-delegation pool cust-pool1 lifetime infinite infinite
R4(config)#int <interface required>
R4(config-if)#Mac-address xxxx.xxxx.xxxx (Just use this if we want control rather than eui-64 controlling everything)
R4(config-if)#Ipv6 address 2001:db8:2:410::4/64
R4(config-if)#Ipv6 address fe80::4 link-local (We use this if we want to control everything rather than eui-64)
R4(config-if)#Ipv6 dhcp server ISP-pool
CPE Configuration
R10(config)#int g2/0
R10(config-if)#ipv6 enable
R10(config-if)#ipv6 address FROM-ISP ::0.0.0.0.1/64 (This means the /56 prefix (The first zero is the 8 bits this customer has to play with regarding subnets, if you like))
R10(config)#int g3/0
R10(config-if)#ipv6 enable
R10(config-if)#ipv6 address FROM-ISP ::1:0:0:0:1/64 (Notice that the leading zero is now a “1â€â€¦. If we wanted yet more subnets then that 1 would become a 2 and then 3 etc etc etc)
Could someone please let me know the same command structure to give the same results in Junos?
Also, please confirm if the configuration is on the CPE or the LNS and also the itnerface involved is the L2TP peer tunnel interface (I'm guessing it would be given that this is the only WAN link)....
The actual end result requirement would be that this is dealt with on the RADIUS via a PORTAL for the re-seller...... Again, guessing, this would involve us knowing wht the re-seller has sold the customer (in the way of IPv6) so that we can configure the CPE before shipping....
If anyone has any experience of configuring this on freeRADIUS, anyhelp would be greatly appreciated.
Thanks
Clive