Upgrade of pfsense to 2.7.0 from 2.6.0 breaks AT&T Bypass (Specific to me, I guess)

Echo2Niner

Preface. I have reverted to 2.6.0 to regain functionality and no longer have the error file to consult.

AT&T Modem: BGW210.
WAN NIC's: Intel X540-T2 Dual Port 10G 10GBase-T
LAN NIC's: Intel X520-DA2 Dual Port 10G SFP+ 10Gbase-SR

I'm unsure if this is specific to my setup or in general. The upgrade from 2.6.0 to 2.7.0 worked as it should with no errors. After rebooting, there is an error about a line(s) in the pfatt file. I've been using said file for about 2 years now. I search the internet and find a file that states it's for "newer" versions of pfsense. I tried that file in my upgraded version and could not ever get DHCP from modem. Shellcmd is setup to execute the pfatt files so... I plan to install 2.7.0 to cleanly so there's no residual issues from an upgrade and test again once I can get time and the family won't yell at me for the internet being down.

I don't mind running 2.6.0 for a bit longer but would prefer to be on the lastest stable version for all of it's added/fixed security aspects. Is there any one out there that has upgraded with success and using the pfatt file? If so, may I please get a copy of your file with your info removed. Any assistance would be appreciated. Thank you.

stephenw10

We'd need to see the errors you're hitting to know more.

If you upgrade to Plus you can use this instead:
https://docs.netgate.com/pfsense/en/latest/recipes/authbridge.html

Steve

Echo2Niner

@stephenw10
Thank you for your reply. Unfortunately, I have actually built out two fresh installs and used AuthBridge. I did this on two separate machines to confirm the functionality. Both had the same issue. The 802.1x auth would occur and receive a DHCP assigned IP but the machine would not be on the internet. I would have to log into the machine and go to Interfaces, choose one and click on save then apply. Once I did that I could then ping 8.8.8.8 from the WAN interface. I would generally pick the LAN interface to click on save. Most of the time it would work to get the machine able to ping 8.8.8.8. Sometimes I would have to choose the WAN connection. This proved to be the case on two separate machines with 2.6.0 installed with basic WAN/LAN config and upgraded to 23.05.1.

So for me, at this juncture, using the pfatt file is a much smoother experience than the current AuthBridge method which I think still needs some polishing but is definitely a step in the right direction. I used two HP EliteDesk 800 G's with a SuperMicro AOC-SG-I4 1GB 4 port NIC which I believe has the Intel I-350 chipset.

stephenw10

Then I would post in the main pfatt thread, someone else there has probably hit this: https://forum.netgate.com/topic/99190/att-uverse-rg-bypass-0-2-btc/537