ATT Uverse RG Bypass (0.2 BTC)
-
I got the certs out again and now it doesn't work I can't get pass the
WPA_STATUS_CMD="wpa_cli status | grep 'suppPortStatus' | cut -d= -f2"
IP_STATUS_CMD="ifconfig ngeth0 | grep 'inet\ ' | cut -d' ' -f2"
/usr/bin/logger -st "pfatt" "waiting for EAP authorization..."
During all this messing. I deleted my cert, so I had to pull again.Here is my full script here is the script.txt
-
@stephenw10 The merged driver does not work for me. Same issue as stock install. The NIC's themselves work but my previous VLAN0 issue still occurs. EAP authentication passes and my other interfaces on the same card work without issue.
I am by no means an expert so I may have messed something up but when I run kldstat it clearly shows the custom if_em.ko driver/module loaded.
This is the source I used for the if_em.ko module was https://www.intel.com/content/www/us/en/download/15187/intel-network-adapter-gigabit-base-driver-for-freebsd.html
-
Hmm, I wonder if it attached. Check:
sysctl dev.igb.0The in kernel driver shows as:
dev.igb.0.iflib.driver_version: 7.6.1-kSteve
-
@sgc said in ATT Uverse RG Bypass (0.2 BTC):
I got the certs out again and now it doesn't work I can't get pass the
WPA_STATUS_CMD="wpa_cli status | grep 'suppPortStatus' | cut -d= -f2"
IP_STATUS_CMD="ifconfig ngeth0 | grep 'inet\ ' | cut -d' ' -f2"
/usr/bin/logger -st "pfatt" "waiting for EAP authorization..."
During all this messing. I deleted my cert, so I had to pull again.Here is my full script here is the script.txt
I got it to tether again but would like to get figure out why eap authorization does not work
-
Came here to say that dumb switch method still works in 2.6.0 with igb driver. I’m using the wpa_supplicant method. Good luck to people who use ngeth… Hopefully it will resolve soon.
-
@netnerdy said in ATT Uverse RG Bypass (0.2 BTC):
Came here to say that dumb switch method still works in 2.6.0 with igb driver. I’m using the wpa_supplicant method. Good luck to people who use ngeth… Hopefully it will resolve soon.
Could you share your way so I can get rid of ngeth
-
@netnerdy the stock igb driver or the custom one? Thanks!
-
@nedyah700 Bummer. I tried you solution, but it didn't work on my system.
I reviewed your script which is significantly different from mine. I don't have anything about wpa_supplicant.
My system has been working great for many years and I'm foggy on the details of how I made it all work :/
-
@nedyah700 yes it is stock igb.
If you want to get rid of ngeth, you need something that strips the vlan 0 from the network packets. This could be running pfsense under esxi and use a virtual network adapter set to “vlan 0” or plug a switch between your ONT and your pfsense, which is what I do.
-
You are correct. Despite showing loaded in kldstat it did not attach.
With my compiled igb module I don't get any of the iflib lines but with both the stock and compiled em module I still get
dev.igb.5.iflib.driver_version: 7.6.1-kI can try to re-compile?
-
Mmm, hard to say since it's em not igb.... doesn't override the in-kernel igb....which is actually just em.
But it's not iflib so I would imagine it isn't affected by the same issue. I'm not sure it's worth the effort.
We know this is an issue with the e1000 driver in 22.01/2.6 and netgraph/VLAN0.
Steve
-
ha! Yea I thought about that and tried just naming it if_igb.ko but that had the same result so who knows.
Anyways, hope the fix makes it in a future release. Appreciate it!
-
@stephenw10 just an FYI someone else used the combined em driver for an em based NIC and it resolved the issue for them.
-
are there any updates on this one? is there a chance the newer driver could make it into 2.6.1?
-
Not as the default since it's a non-iflib driver. What was tested here at least.
If the alternative Intel driver was available via ports if could be made available potentially.
The 'correct' solution here is to fix whatever broke netgraph support in the iflib driver. If that hasn't already happened.
Steve
-
I believe a fix for the iflib driver is available. Tracked in this Redmine regression. https://redmine.pfsense.org/issues/12821?next_issue_id=12820
Hope we can get that incorporated into the next release!
@stephenw10 said in ATT Uverse RG Bypass (0.2 BTC):
Not as the default since it's a non-iflib driver. What was tested here at least.
If the alternative Intel driver was available via ports if could be made available potentially.
The 'correct' solution here is to fix whatever broke netgraph support in the iflib driver. If that hasn't already happened.
Steve
-
Oh, yup that is in main so 2.7 snapshots now:
https://github.com/pfsense/FreeBSD-src/commit/9c762cc125c0c2dae9fbf49cc526bb97c14b54a4
So it looks like we are waiting for someone to test it in a 2.7 snap and provide some feedback.Steve
-
Ah! I missed the comitt. I'll try and give it a shot this weekend.
Thanks!
@stephenw10 said in ATT Uverse RG Bypass (0.2 BTC):
Oh, yup that is in main so 2.7 snapshots now:
https://github.com/pfsense/FreeBSD-src/commit/9c762cc125c0c2dae9fbf49cc526bb97c14b54a4
So it looks like we are waiting for someone to test it in a 2.7 snap and provide some feedback.Steve
@stephenw10 said in ATT Uverse RG Bypass (0.2 BTC):
Oh, yup that is in main so 2.7 snapshots now:
https://github.com/pfsense/FreeBSD-src/commit/9c762cc125c0c2dae9fbf49cc526bb97c14b54a4
So it looks like we are waiting for someone to test it in a 2.7 snap and provide some feedback.Steve
-
Guys, I’m having a hell of a time rolling back from 2.6.0 to 2.5.2 with bypass mode.
I made a USB with the 2.5.2 image, and put /config/config.xml on the FAT32 partition. The config was taken immediately before the upgrade, where the bypass had been happily chugging along for a year or more.
I ran through the installer, and when it rebooted I pulled the USB. pf happily booted into a fresh config. Ugh.
I rebooted with the USB plugged in, and used the BIOS boot selector to choose the internal disk. This time it picked up the config, but it complained that it couldn’t find pfatt.sh and negth0.
What do I need to do to get up and running again?
Thank you!
-
The script is not stored in the config so you would need to re-upload that. Unless you used the filer package maybe but then you would still need to reinstall that at first boot. But that can't happen until the WAN connects so you'd be in chicken/egg scenario there.
