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

PfSense 2.5 compatibility #49

Open ivanfarkas2 opened 3 years ago

ivanfarkas2 commented 3 years ago

PfSense 2.5 compatibility

What's the ETA for PfSense 2.5 compatibility and the right ng_etf.ko version. please?

owenthewizard commented 3 years ago

Duplicate of #41. See the upstream bug report.

ivanfarkas2 commented 3 years ago

The two are not related. I would like the documents to be updated for PfSense 2.5 and the source should have the proper ng_etf.ko. Please reopen the case.

aholmes55 commented 3 years ago

You do not need ng_etf.ko on pfsense 2.4.5 or later. ng_etf.ko is a kernel module but on 2.4.5 netgraph is built into the kernel. Make sure you are using the scripts in the main branch of monkwho's github and not the before 2.4.5 branch or the original aus scripts. The older scripts load the kernel module but this isn't necessary as netgraph is built in.

ivanfarkas2 commented 3 years ago

@aholmes55 "Make sure you are using the scripts in the main branch" The master (not main) branch does not have supplicant code.

elif [ "$EAP_MODE" = "supplicant" ]; then

Awaiting a relevant supplicant solution for pfSense 2.5.

ivanfarkas2 commented 3 years ago

Any progress?

jrstrunk commented 1 year ago

I just got the scripts in the master branch to work with pfSense 2.5.4 by doing everything in the readme, then resetting netgraph ( as described in the readme), and then running the script again. No idea why I have to reset netgraph and run the script again after it runs from shellcmd, but that was the only way I could get it to work. I tried to only run the script once, both with early shellcmd and one manually after the boot was done, but neither worked by itself, it had to be run two times with a netgraph reset in between. No idea why but I'm glad it's working.