Shop holiday gifts while you still can - Everyone gets our best deals on any smartphone!
Need help with your equipment?
melloa's profile



2 Messages

Wednesday, October 16th, 2019 12:44 PM

RG210-700/u-verse/pfSense/IPv6 configuration multiple interfaces



I'm running a 100Mb dry copper with a RG210-700 and five static IPs. Behind of it I use a pfSense firewall, that handles all the internet traffic.

That pfSense has four interfaces:



- OPT1

- OPTs

The WAN has all five static IPs; the LAN a, OPT1, and OPT2


Up to this point all IPv4.


Configured my WAN to DHCP6 and the LAN to track WAN, all works fine. The WAN get XXXX:XXXX:XXXX1:2d80:XXXX:XXXX:XXXX:XXXX/64 and the LAN XXXX:XXXX:XXXX:2d8f:XXXX:XXXX:XXXX/64.


It seems I'm getting 16 /64 subnets.


When creating VMs and connecting their WANs to the RG, I get the same subnet on them, as the baremetal above. The LAN interfaces, got IPv6s from other subnets, but all inside the 2d8 /60 range.


When trying to change the prefix delegation on the WAN side to /60, and track all LAN interfaces to it, the RG won't provide any subnet and all LAN interfaces won't get an IPv6, so tracking can only be used for one LAN interface with the /64 received.


With that said, does anyone know how to statically configure multiple LAN interfaces with IPv6 , considering that the designation received is /64 on the WAN and the first LAN interface is tracking WAN?


Thanks in advance for your thoughts.

ACE - Professor


5.6K Messages

4 years ago

Try posting the question here.


Several people there use pfsense and static ip’s. 




2 Messages

4 years ago

dslreports ... long time I visit that page. Will do it, thanks.



241 Messages

I've got a similar setup that has been working perfectly for almost 6 months. Here is a post I wrote detailing how I got it working. Long story short, the Uverse box will only assign /64 networks, but will assign 8 of them. The next requirement is a properly crafted DHCP6c request. There is no way from the PF GUI to configure it.

The configuration kind of worked on a 5268ac, but the 5268ac would forget that it gave out the lease and purge the routing table before the lifetime of the lease was over. I could never figure out how to force PF to renew quicker than 1/2 of the valid lifetime advertised. I switched to a NVG599 and the valid lifetime was 4 hours instead of a week. It automatically renews every 2 hours and I haven't had any downtime since I did that.

I don't know how the BGW210 will behave, but I imagine it will be similar.

Not finding what you're looking for?