search

MonkWho / pfatt

Enable true bridge mode for AT&T U-Verse and pfSense (this is a fork of an original repository https://github.com/aus/pfatt. Since it is not available anymore, I'll do my best to maintain a copy for people that still need a bypass)
438 stars 170 forks source link

OPNSense 21.7.8 & 22.1 support & WPA_supplicant configuration file #60

Open zombielinux opened 2 years ago

zombielinux commented 2 years ago

Updated code for using a wpa_supplicant configuration file and support for OPNsense 21.7.3.

Notable change is the addition of spoofing the $ONT_IF mac address BEFORE bringing the interface up.

Hou-dev commented 2 years ago

Thanks for this. I was thinking of implementing pfatt like this. Will test this later and report on this comment. Much more clearer with separate files for supplicant and bridge methods. Edit: There seems to be some issue with the latest firmware opnsense 22.1 with my intel and broadcom nic. Stuck on wpa authentication. Made sure to check all files and locations and they are correct. original_a9086da7-f6e2-44af-a781-3837bd64f106_PXL_20220206_084810558

owenthewizard commented 2 years ago

+1 would love to see this merged.

MrCaturdayNight commented 2 years ago

This current version worked for me on 21.7.8 as well. Thanks!

johnburbridge commented 2 years ago

@zombielinux confirmed this works on a fresh install of 22.1.2_2. What's interesting is that I did not have to assign ngeth0 to WAN. Its working with the previously assign physical interface (in my case igb0, on an Intel I350-AM4).

Am in the middle of upgrading to 22.1.4 but don't expect any issues.

Thanks so much for this! Would love to buy you a coffee.

UPDATE after upgrading from 22.1.2_2 -> 22.1.4: The physical IF was still able to acquire its ip address but there was no route out. On a whim, rather than manually assigning the route (which might change without notice) I switched over and assigned WAN to ngeth0 which made things start working again. It's not entirely clear if this was due to the upgrade or something to do with surviving a reboot, but I can confirm everything works after assigning WAN to ngeth0 and it does survive reboots.