DHCPv6 with AT&T Uverse issue
-
@JKnott here ya go, sorry about that packetcapture-igc0-20230930172601.zip
-
Why is it so different from what mine looks like? DHCPv6 works pretty much the same as on IPv4, with 4 steps to getting the address.
-
@JKnott I don't know what to tell ya! I wish I knew, I am still trying to figure out what the issue is with my setup.
-
I see you do get a solicit, advertise, request and a reply between their DHCP servers and your pfSense box.
Mine gets stuck between replies, rebinds and solicit/advertise.
There's something either not listening to a reply, or gets ignored. AT&T's IPv6 implementation is a pain in the butt.
-
Try connecting a computer to the modem and see if it gets an IPv6 address. You can also install Wireshark on the computer to do the captures.
Is there anyone else here who's on AT&T that can help? I'm on Rogers, in Canada, and they work fine.
-
@JKnott IPv6 works fine with their gateway.
AT&T goes out of their way to make sure that you only use their gateway and pay for it for as long as you have their service, even though is absolutely terrible and unreliable.
I’ve been able to bypass it entirely for over 2 years now, but only over IPv4. From what I read, some folks have been able to get IPv6 leases with some additional work, but I’m stuck.
-
Same problem. Any update?
-
@jmmm I moved on with OPNsense and it worked on the first try. Full IPv6 routing with no issues. I never figured out why it wouldn’t work with pfSense.
-
Has anyone using any of the uATT Fiber gateway bypass methods gotten IPV6 working with ATT Fiber?
-
after a bunch of screwing around, I have it working. I wrote up what I found here:
https://forum.netgate.com/topic/188676/ipv6-dhcp-client-with-att-fiber-without-gateway-workingIn particular:
In the instructions at [https://docs.netgate.com/pfsense/en/latest/recipes/authbridge.html], section Add Modem-WAN Bridge Rule, the instructions say to set Protocol
Any. If you do this, the DHCP6 requests from the modem will be forwarded through PFSENSE to the ONT and cause XID mismatch errors. This should instead be set for Protocol IEEE 802.1X.and a lot of rebooting or it will not work.
