ATT Uverse RG Bypass (0.2 BTC)

nedyah700

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

stephenw10

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

nedyah700

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

timtrace

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!

stephenw10

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.

timtrace

@stephenw10, thank you! At the end of the pf install it offers to drop out to a shell, could I copy the script over from USB so it would be in place for the first boot?

stephenw10

Yes, probably. I've never tried to do that though. I'm also not burdened by AT&T.

I would probably install 2.5.2 clean.
Boot into the default install and upload the pfatt scripts.
Restore the config that presumably contains the shellcmds to run it.

Steve

nedyah700

Lucky!

@stephenw10 said in ATT Uverse RG Bypass (0.2 BTC):

Yes, probably. I've never tried to do that though. I'm also not burdened by AT&T.

I would probably install 2.5.2 clean.
Boot into the default install and upload the pfatt scripts.
Restore the config that presumably contains the shellcmds to run it.

Steve

timtrace

I’m getting a permissions error even though it’s 555 on the tree and the script. It’s happening if I use the installer shell, and also if I let the misconfigured pf boot and come into it by ssh. What might be happening, please?

sgc

@timtrace said in ATT Uverse RG Bypass (0.2 BTC):

I’m getting a permissions error even though it’s 555 on the tree and the script. It’s happening if I use the installer shell, and also if I let the misconfigured pf boot and come into it by ssh. What might be happening, please?

What folder is the sh in?

nedyah700

@timtrace When I clean installed 2.6.0 (and 22.01 on my pfSense+ Box) absolutely nothing I did allowed my pfatt script to runs successfully from the /cf/conf directory. I ended up moving it to /root/pfatt and everything worked. This seemed to only be an issue once I moved to a ZFS file system but who knows.

timtrace

Thanks, @stephenw10, @nedyah700, @sgc -- that worked!

For posterity :)

If you've been running in BYPASS MODE and want to get right back to it after a reinstall of pfSense and a restore of a backed-up configuration ...

1> Prepare a USB memstick:
https://docs.netgate.com/pfsense/en/latest/install/write-memstick.html

2> Choose your backup config file, make a copy, and rename the copy config.xml

3> Open config.xml in a text editor and change all references to pfatt.sh so they read like this: /root/pfatt/pfatt.sh

4> Put config.xml on the FAT partition on the memstick. Follow these instructions:
https://docs.netgate.com/pfsense/en/latest/backup/restore-during-install.html

5> Make a copy of your backup of pfatt.sh, open that copy in a text editor and make sure the values for ONT_IF, RG_IF, and RG_ETHER_ADDR are appropriate for your environment.

6> Copy the reviewed/edited copy of pfatt.sh to the root of the FAT partition on the memstick.

7> Install pfSense
https://docs.netgate.com/pfsense/en/latest/install/install-walkthrough.html

8> Near the end of the process, the installer will ask if you'd like to open a shell to make any final manual modifications. Answer yes.

9> These next commands will copy pfatt.sh from the memstick to the pfSense volume. They may not be 100% correct for all environments. Google will help you out

mkdir -p /root/pfatt
mkdir -p /mnt/usb
mount -t msdosfs /dev/da0s3 /mnt/usb/
cp /dev/da0s3/pfatt.sh /root/pfatt/pfatt.sh
chmod -R 555 /root/pfatt
exit

10> Reboot your pfSense and profit.

Caveats:

In step 9, the FAT partition on my memstick was /dev/da0s3. Yours may be different. You can start by viewing the output of this command and (probably) appending 3 for the FAT partition. Google can get you the rest of the way if you need help.

camcontrol devlist

For some reason, my installer wouldn't pick up config.xml during the installation process, so, I left my memstick plugged in for the first reboot and used the computer's boot manager to start pfSense from the hard disk. The ECL took over and all was right in the world.

If you're running pfBlockerNG in Python mode, you may have to disable Python in the DNS resolver before your fresh system will download any packages .... including pfBlockerNG. You can re-enable Python mode after everything settles down.

I hope all this typing helps someone out of a bind some day :)

t41k2m3

@stephenw10 or others - could anyone post specific config and commands to enable the new VLAN 0 support in pfsense+ 23.01?

According to a post in the thread below someone was able to get it "working successfully with AT&T [...] without the need for the pfatt [netgraph / ngeth0 interface] script."

https://redmine.pfsense.org/issues/12070

untamedgorilla

@t41k2m3 I definitely have it working. Nothing to do extra. I'm using the beta version 2.7.
2.7.0-DEVELOPMENT (amd64)
built on Mon Jan 02 06:04:33 UTC 2023
FreeBSD 14.0-CURRENT

And actually you don't need pfatt anymore at all. I don't even run it anymore. If you have gpon you just need a certain sfp+ plug, if you have xgspon (which I have, the 5gbps) you can purchase a fiber modem clone it to your current att router and you are good. I don't use the bgw320-505 ont/modem combo anymore.

stephenw10

Yeah, that feature request is to allow VLAN0 traffic and that is now working in 23.01 and 2.7. You can connect to an ISP that sends priority tagged DHCP replies and they will be passed. You will be able to pull a lease.
That doesn't mean the authentication stuff that AT&T required has changed. If your WAN still requires that you still need the pfatt script to make it happen. At least for now.
Internally we are testing with bridge-to that should make it much easier to accomplish. However if AT&T are removing the need for it that solves the problem anyway.

Steve

bigjohns97

@stephenw10 said in ATT Uverse RG Bypass (0.2 BTC):

Yeah, that feature request is to allow VLAN0 traffic and that is now working in 23.01 and 2.7. You can connect to an ISP that sends priority tagged DHCP replies and they will be passed. You will be able to pull a lease.
That doesn't mean the authentication stuff that AT&T required has changed. If your WAN still requires that you still need the pfatt script to make it happen. At least for now.
Internally we are testing with bridge-to that should make it much easier to accomplish. However if AT&T are removing the need for it that solves the problem anyway.

Steve

I have tried this personally using multiple pcp values (0,1,2) and have never been able to get an DHCP lease.

I do have an Intel e1000 based NIC and I have been disabling hwvlanfiltering before attemping to set the PCP value and run the wpa supplicant.

If someone who has done this successfully please post exactly what commands you ran to get it to work.

stephenw10

If you're connecting to AT&T and they still require auth then I expect to need the pfatt script.

If you're connecting to one of the other ISPs who use priority tagged DHCP where the cut-down script was required that should no longer be necessary in 23.01/2.7.

bigjohns97

@stephenw10 said in ATT Uverse RG Bypass (0.2 BTC):

If you're connecting to AT&T and they still require auth then I expect to need the pfatt script.

If you're connecting to one of the other ISPs who use priority tagged DHCP where the cut-down script was required that should no longer be necessary in 23.01/2.7.

Thanks Stephen, I tried posting in this thread https://redmine.pfsense.org/issues/12070 asking Christopher Cope to share what he used to get att bypass working without netgraph but he hasn't responded yet and I can't find anyway to reach out to him directly.

If there is a way to get it to work with att there are quite a few people who would love to know.

bk150

@bigjohns97

We have a discord that most of the folks from DSLreports have migrated to regarding discussion about AT&T specific bypass methods. There is a working GPON and XGS-PON bypass method. I can't speak much to the GPON method as I have XGS-PON but the XGS-PON method entails simply buying an Azores WAG-D20 and setting a handful of values on it. Once the device gets O5.1 status to the upstream OLT, you can send a DHCP request with the use of Netgraph on pfsense 2.7/23.01.

Hopefully it's not against the rules to post a link to the Discord (dm me if it gets removed): https://discord.gg/6TwFBquMTT

bigjohns97

@bk150 Let me check out the gpon method and see if it works for me, currently my ONT is terminated in the garage and I have a copper base NIC on my pfsense box so I would require a separate ONT to be able to work with current hardware.