ATT Uverse RG Bypass (0.2 BTC)
-
@bulldog5 said in ATT Uverse RG Bypass (0.2 BTC):
Not sure why you guys are continuing to waste your time trying to re-invent the wheel. Use the wpa_supplicant method from: https://github.com/aus/pfatt/tree/supplicant
If you have your certs extracted already, follow the directions. the netgraph part in that script works just fine, you don't need to screw around with a dumb switch for VLAN0. Let it do its thing, and forget about it.
I had no idea there was a supplicant method. I will switch over this weekend.
-
@pyrodex why not? (I don't do traffic shapping) but I'm interested in why it doesn't work.
-
@bulldog5 said in ATT Uverse RG Bypass (0.2 BTC):
@pyrodex why not? (I don't do traffic shapping) but I'm interested in why it doesn't work.
Traffic shaping works for me. Using CoDel.
-
@bulldog5 said in ATT Uverse RG Bypass (0.2 BTC):
Not sure why you guys are continuing to waste your time trying to re-invent the wheel. Use the wpa_supplicant method from: https://github.com/aus/pfatt/tree/supplicant
If you have your certs extracted already, follow the directions. the netgraph part in that script works just fine, you don't need to screw around with a dumb switch for VLAN0. Let it do its thing, and forget about it.
I couldn't get netgraph to work but I have had no issues with the VMware method.
-
I recently got certs from an nvg-589 so I could switch from the full netgraph to supplicant. I'm having the same issue as @AiC0315 where it hangs on waiting for eap authorization. The only difference is my pem files were already correctly named and have proper permissions so I'm at a loss.
The RGW I purchased was configured for dsl when I downloaded the certs. I have since factory reset the unit to verify that it would connect and it did. Do I need to redownload the certs now that it's in ethernet mode? (edit - Apparently I can't get into ssh anymore)
I have disabled the old pfatt script but I didn't disable the 5268ac reauth script. Could that be causing issues?
Lastly, I have changed the spoofed mac from my 5268ac to match the mac of the extracted certs.
edit - Finally got it working after making the changes suggested here - https://github.com/aus/pfatt/pull/19#issuecomment-605648696
-
I have been running pfSense for many years. I think I’ve been using it for around 10 years (having come from SmoothWall, which stagnated over 10 years ago). I have been happy with my ISP, which I’ve had since 2006; including a move in 2011 to my current home. Alas, the wife wanted to buy a new house and we take possession of the new house tomorrow. Unfortunately, my current ISP did not expand to the community where my new house has been built for whatever reason, even though it remains in the same small city. Instead, I will have to move to AT&T if I wish to maintain having synchronous gigabit service. My current ISP provides a fiber gateway that only operates in bridge mode. At the utility service demarcation location of my house, the fiber comes in to the gateway with six RJ45 network jacks and four RJ12 telephone jacks. Port #1 on this gateway goes directly into a router while the other five are to be routed to set-top boxes, should I chose their video service, which I don’t; I also do not use the telephone jacks.
In my research of AT&T, it appears that instead of having an all-in-one box that exists on the side of the house, they route the fiber to an Optical Network Terminal inside the home, which then runs to a Residential Gateway, which appears to be a WiFi router. I do not want to use a WiFi router but continue using my pfSense and my Unifi UAP-AC Pro access points placed strategically in the new house. I have read about different ways to get around this and want to make it as seamless as possible.
Of all the methods I’ve seen, it appears that the Github project “pfatt” appears to be the best solution for bypassing the residential gateway. As I read further, there are two different methods of using it with one taking quite a bit of skill to pull off; the “netgraph” method or the “WPA Supplicant” method. I believe I will be starting off by using the original, “netgraph” method of connecting the WAN port of the pfSense to the ONT and placing the RG on a third Ethernet port (my pfSense machine has four gigabit ports, so not a big deal for me). The idea of using the WPA Supplicant method is intriguing, but it sounds difficult to acquire the keys needed to facilitate it... I've seen people talking about opening up a gateway, desoldering a memory chip to put in a chip reader to dump data. If there is an easier way to get the needed information, I would love to learn about it.
I have already downloaded the script, compiled my “ng_etf.ko” and copied it to the kernel and modified the script with the known Ethernet ports each device will be plugged into. I know I will need to obtain the MAC address of my RG when it arrives, move my script, and enable it in the “/conf/config.xml” but what else will I need to do? Do I need to tell the installer to put it into a certain mode? Should I pretend like I’m going to use the gateway the way AT&T anticipates most people do while the installer is there and then change everything once they are gone?
Is there some other forum for discussing this? It seems odd that the only support is following a single thread, covering several different aspects of the process. It would make more sense if the Netgate pfSense forum had a category for “Third-party Packages, Plugins, or Mods” and then create sub-categories below that. Upon asking a question on the Github page for pfatt, I was curtly told to look at the bounties section of this forum. Searching through a single, disjointed thread is like searching for a needle in a haystack; especially since the thread isn’t labeled “pfatt”.
-
@RonRN18 The easiest way to get the certs is to find somebody selling them. I was able to get mine from a guy on the dslreports forums. Once setup the wpa supplicant method works very well. The only problem I had was my Intel N3700 powered pfsense box would not pull full line speed, it topped out around 500mbps. I have sense moved to a Xeon E3-1220V3 and have no problems pulling full line speed. I've had my gateway unplugged since September 2019.
-
@RonRN18 said in ATT Uverse RG Bypass (0.2 BTC):
In my research of AT&T, it appears that instead of having an all-in-one box that exists on the side of the house, they route the fiber to an Optical Network Terminal inside the home, which then runs to a Residential Gateway, which appears to be a WiFi router. I do not want to use a WiFi router but continue using my pfSense and my Unifi UAP-AC Pro access points placed strategically in the new house. I have read about different ways to get around this and want to make it as seamless as possible.
My setup is probably the same as what you describe (incl UAP-ACpro inside my LAN). When the ATT gigfiber was installed I was using an SG-2440. Many have said it works w/ 1g but I had poor throughput and finally did the pfatt with netgraph. It did increase my speed but not significantly. Not close to 1g.
So based on comments others made I upgraded my pfSense appliance and run now run an SG-5100. I get the full 1g now. The 5100 is a bit overkill for my usage but I had read mixed reviews about the 3100 and decided to go for more HP.
I don't run a web server. I'm just a home internet user. Near as I can tell, the deal with ATT router is the NAT table (on my BG210 it is in /diagnostics menu) filling up. My system has been running for many months and that table, max of 8192, is at a whopping 77.
I did not reload pfatt on the 5100 and instead have occasionally checked the NAT table. All is well so my advise is to try your setup w/o the bypass first and see if you can live with it.
I disabled the ATT wifi and run their router in IP Passthru mode and altered the dhcp lease time to 99 days. My IP has not changed in the past many months.
Good luck.
-
@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