[UPDATE NOV 2017]
AT&T did an upgrade to my modem/router and the configuration I had working below suddenly stopped working. Going back to looking at solving this problem, I found a configuration that works. This seems more in-line with what everyone has been seeing.
I wanted to share with everyone a perfectly good working IPv6 configuration that works with AT&T GigaPower using the PACE 5268ac and DMZ plus. I am using a Edge Router Lite v1.9.7+hotfix.3
In the ATT device you can see under Settings -> Broadband -> Status
Dual-Stack IPv6 Internet Connection
Dual-Stack IPv6 Internet Address 2001:506:70b0:1b71::1
Dual-Stack IPv6 Default Gateway fe80::8626:2bff:fe83:b971
Dual-Stack IPv6 Delegated Prefix 2600:XXXX:XXXX:b710::/60
The delegated prefix is the network that is assigned to you. The ATT router breaks that down into /64’s. You can visit https://subnettingpractice.com/ipv6_subnetting.html to get a list of how your /60 will be carved into /64.
On the LAN status Settings -> LAN -> Status you will see under IPv6 Status
IPv6 Status
Link Local Address fe80::d6b2:7aff:fe4c:12bd
Delegated Address 2600:XXXX:XXXX:b710::1
So you can assume that the PACE has been delegated a /60 and is willing to give out /64's the devices behind it. For this reason I configured the PD as follows on eth0 ( there is really nothing to configure on eth1 ).
Interface facing the ATT Pace ( note the prefix length, this is important )
ethernet eth0 {
address dhcp
description Internet
dhcpv6-pd {
pd 0 {
interface eth1 {
host-address ::1
service slaac
}
prefix-length /64
}
rapid-commit enable
}
duplex auto
firewall {
in {
ipv6-name WANv6_IN
name WAN_IN
}
local {
ipv6-name WANv6_LOCAL
name WAN_LOCAL
}
}
speed auto
}
Internal interface:
ethernet eth1 {
address 192.168.2.1/24
description Local
duplex auto
speed auto
}
DNS masq with ra:
dns {
forwarding {
cache-size 150
listen-on eth1
options enable-ra
options dhcp-range=::1,constructor:eth1,ra-names,86400
}
}
One thing you should do is WATCH the ATT device. I did clean all IPV6 configuration from the interfaces of the edge router lite and then rebooted the edge router lite. This I did because even after removing the ipv6 configuration on the interfaces the show interfaces command still showed the interface with a v6 address and I could still ping. Not good!
So after a reboot everythign was gone. Then I added the configuration for eth0 dhcp-pd. At that point when I look at the ATT PACE router I can see that it came to life and could see under Settings -> Lan -> Lan Address Allocation:
![Screen Shot 2017-11-27 at 9.04.37 PM.png Screen Shot 2017-11-27 at 9.04.37 PM.png]()
So with the prefix assigned, the internal interface was assigned the b718 subnet from the /60 group and everything started working.
In the dnsmasq logs you can see the advertisement built for eth1
Nov 27 15:42:18 dnsmasq-dhcp[1650]: IPv6 router advertisement enabled
Nov 27 15:49:20 dnsmasq-dhcp[1650]: router advertisement on 2600:XXXX:XXXX:b718::, constructed for eth1
Nov 27 15:49:20 dnsmasq-dhcp[1650]: RTR-ADVERT(eth1) 2600:XXXX:XXXX:b718::
The radvd.conf file is set properly set automatically also:
interface eth1 {
# This section was automatically generated by the Vyatta
# configuration sub-system. Do not edit it.
#
# service type [slaac]
#
IgnoreIfMissing on;
AdvSendAdvert on;
RDNSS 2600:XXXX:XXX:b710::1 { };
AdvManagedFlag off;
AdvOtherConfigFlag off;
prefix ::/64 {
AdvOnLink on;
AdvAutonomous on;
};
};
And with that, magic… great speed as it’s just ipv6 routing on the Edge Router…
![Screen Shot 2017-09-17 at 3.07.44 PM.png Screen Shot 2017-09-17 at 3.07.44 PM.png]()