ATT Uverse RG Bypass (0.2 BTC)
-
@JonH in my current setup, I have 1g service through a different ISP and while I don’t get a full 1000 Mbps, I generally see 750-850 Mbps download and 800-875 Mbps upload.
I run about about 20-30 VMs on 3 bare-metal multi-cpu servers. I also run 5 desktops, 3 laptops, 2 tablets, 2 smartphones, 4 TVs with at least Internet connected video streaming device each. I then have about 10 SBCs (Raspberry Pis of each generation, Beaglebone, Pine64, and another “knock-off”/alternative). I have several other connected devices. I have well over 100 statically assigned IPs in my house. This is why I’m looking at bypassing AT&T’s NATting device.
It’s my hobby, but this is one aspect I have limited experience (bypassing the RG) and finding very limited community support. I know I will eventually figure it all out, once I’ve played with it a while, I’m just trying to learn from other mistakes so I can make different mistakes, not just repeating mistakes of others.
-
@RonRN18 said in ATT Uverse RG Bypass (0.2 BTC):
It’s my hobby, but this is one aspect I have limited experience (bypassing the RG) and finding very limited community support. I know I will eventually figure it all out, once I’ve played with it a while, I’m just trying to learn from other mistakes
I get that. It wouldn't hurt to try ATT as installed and then move to pfatt if needed. When you get it all sorted out it would be nice to find out what you ended up doing.
-
@RonRN18 You should try the bypass method of cloning the ATTRG MAC address to PFSense WAN and use a switch for VLAN0 connection to the ONT. I am running PFSense baremetal on a Dell R210II directly connected to the ATT ONT through a Netgear GSS108E switch and getting a public IP. I had to reconnect the BGW210 2 times in 2019 to reauth the connection, otherwise the connection lasted through multiple server restarts over the year. Currently sitting at 85 days uptime since last reboot and haven't had to reauth in 2020 yet. When I do need to reauth, I plug in the BGW210 power and login to the Netgear switch and flip the VLANs real quick. Takes about 2 mins and most of that is waiting for the BGW210 to boot up and reauth, I could probably automate it if I had to do it enough. I also ran the same scenario in a PFSense VM in ESXI with no issues. PFATT would be nice if it was baked in and just worked with ease, and we didn't have to deal with ATT certs. But for now, this is the "easiest" bypass method.
-
The prices on ebay for the certs has really sky rocketed. I guess good 'ol supply and demand. I remember paying $20 for a nvg589 a year ago. Rooted and pulled the certs. These days they're (the certs) are going for $100+.
-
@aus why did you take down the pfatt github repo?
-
I was wondering the same thing. I was getting ready to do it when I couldnt find the repo anymore. :(
-
Lets hope someone who still has the recent scripts can make them available.
-
@ikkuranus
I came here wondering the same thing. Was just about to try it.. It looks like there's a clone here, but is outdated according to the internet archive..Edit: Maybe just use this repo
https://github.com/0xC0ncord/pfatt -
It turns out that I have a clone from 04/19/2020 so looks like I am good to go. I would like to know what happen though...
-
@GPz1100 Do you need the scripts?
-
@AiC0315 I need them too please
-
@hfrazier since this was a public repo, do we know which is the new parent where future work should go? If he deleted/made private, there should have been a split and all the forks should have gotten reparented.
edit: looks like MonkWho is the new parent repo, based on the graph. Here's all the most recent updates for anyone who needs them https://github.com/MonkWho/pfatt/network
-
@andrewpdupuis Ah, thanks! I had found that repo just wasn't sure if it was the latest.
-
This post is deleted! -
@hfrazier Looks like the latest fork from that is found at https://github.com/neclimdul/pfatt
-
Does anyone have the zip of https://github.com/aus/pfatt/tree/supplicant ?
-
I decided to check if there were any changes to pfatt last week and found out that original is now gone and my fork became a new parent. No idea how or why.
I will maintain it to the best of my abilities. I pulled some requests and done some commits to clean things up. Screwed up a little when I was uploading the supplicant branch but got it all fixed up now. I also separated OPNsense specific script into it's own file for clarity. So currently https://github.com/MonkWho/pfatt contains the latest files.
@GPz1100 said in ATT Uverse RG Bypass (0.2 BTC):
Does anyone have the zip of https://github.com/aus/pfatt/tree/supplicant ?
A copy of it is here - https://github.com/MonkWho/pfatt/tree/supplicant. It contains most recent files. Unfortunatly this branch was not there when I originally created my fork so I had to semi-manually recreate it from a backup I had locally.
-
@MonkWho I just want to say thank you for carrying the torch. I just recently discovered this whole workaround thing - was getting discouraged trying to find a way to build the netgraph for my SG3100 - then found out it is included with pfsense now. Except on 2.4.5, the ng_etf package is missing! lol
https://redmine.pfsense.org/issues/10463
So now I must wait until 2.4.5-p1 release to be able to set this all up. Anyways, thank you for carrying on the work @aus started.
-
@glio Maybe I am missing something, I am running 2.4.5 with the supplicant bypass. I did install it on an earlier version.
-
@AiC0315 The EAP proxy is not available without ng_etf being present. I've not previously set up this stuff on earlier versions so maybe that's the difference.
