Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    ATT Uverse RG Bypass (0.2 BTC)

    Scheduled Pinned Locked Moved
    Bounties
    80
    555
    1.0m
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • J
      jasonsansone @michaellacroix
      last edited by

      @michaellacroix everything functioned fine? My script survived and executes, but traffic didn't actually route properly across the net graph interface. Is the method and script the same as for AT&T? If not, I would like to compare the code.

      M 1 Reply Last reply Reply Quote 0
      • M
        michaellacroix @jasonsansone
        last edited by

        @jasonsansone I believe its different for frontier, we only need the netgraph script for the vlan tag to get an IP from the dhcp server. I believe ATT also uses some kind of authentication method? Not sure.

        1 Reply Last reply Reply Quote 0
        • B
          bigjohns97 @jasonsansone
          last edited by

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

          2.6.0 appears to break pfatt.sh. I had to downgrade. Just a heads up to anyone running this bypass.

          Can confirm this broke for me as well.

          T 1 Reply Last reply Reply Quote 0
          • B
            bigjohns97
            last edited by

            @jasonsansone how did you downgrade?

            J 1 Reply Last reply Reply Quote 0
            • J
              jasonsansone @bigjohns97
              last edited by

              @bigjohns97 Reinstall from USB created by 2.5.2 ISO and restore config.

              B 1 Reply Last reply Reply Quote 0
              • B
                bigjohns97 @jasonsansone
                last edited by

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

                @bigjohns97 Reinstall from USB created by 2.5.2 ISO and restore config.

                OOF, ended up putting the RG back inline.

                N 1 Reply Last reply Reply Quote 0
                • N
                  netnerdy @bigjohns97
                  last edited by

                  @bigjohns97 does wpa still authenticate? What output do you get for “wpa_cli status” after you disconnect and reconnect the ont ethernet cable?

                  B J 2 Replies Last reply Reply Quote 0
                  • B
                    bigjohns97 @netnerdy
                    last edited by

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

                    @bigjohns97 does wpa still authenticate? What output do you get for “wpa_cli status” after you disconnect and reconnect the ont ethernet cable?

                    Sorry, I had to bring the RG back inline and can no longer troubleshoot this.

                    1 Reply Last reply Reply Quote 0
                    • J
                      jasonsansone @netnerdy
                      last edited by

                      @netnerdy I use the tether method, not supplicant.

                      1 Reply Last reply Reply Quote 0
                      • T
                        t41k2m3 @bigjohns97
                        last edited by

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

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

                        2.6.0 appears to break pfatt.sh. I had to downgrade. Just a heads up to anyone running this bypass.

                        Can confirm this broke for me as well.

                        Does anyone know if this applies to both 2.6.0 and 22.01 plus (or just 2.6.0 confirmed at this time)?

                        B N 2 Replies Last reply Reply Quote 0
                        • B
                          bigjohns97 @t41k2m3
                          last edited by

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

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

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

                          2.6.0 appears to break pfatt.sh. I had to downgrade. Just a heads up to anyone running this bypass.

                          Can confirm this broke for me as well.

                          Does anyone know if this applies to both 2.6.0 and 22.01 plus (or just 2.6.0 confirmed at this time)?

                          Both judging from the responses on github

                          1 Reply Last reply Reply Quote 0
                          • N
                            nedyah700 Rebel Alliance @t41k2m3
                            last edited by

                            @t41k2m3 I used 22.01 and it stopped working as well.

                            1 Reply Last reply Reply Quote 0
                            • N
                              nedyah700 Rebel Alliance
                              last edited by

                              Okay, had some success today based on info I gathered from all the various discussions online. I think it is something to do with the em(4) driver. Do all of you having issues have Intel NIC's? I put together a test pfSense server from a bunch of spare parts and it worked right away on the latest release. After digging, I couldn't get any Intel NIC to work. Using what I had around (a few crappy USB dongles worked and old PC's with integrated NICs) I had success with everything not Intel GbE. When I re-upgraded my main pfSense box I was able to move my WAN link to an SFP slot (with RJ45 Module) with some success. I say "some" because all my SFP/RJ45 modules are 10GB and they do not negotiate well with the ONT.

                              Something interesting for me, if_em.ko is present in /boot/kernel on 2.6.0 but wasn't in my previous version of pfSense. My knowledge is limited but I am not sure where the driver was located in the previous version? Anyone smarter than me know?

                              Some Useful Links:
                              FreeBSD 12.3 Release Notes (em(4) driver notes) - https://www.freebsd.org/releases/12.3R/relnotes/
                              Reddit Discussion - https://www.reddit.com/r/PFSENSE/comments/ssgsha/psa_260_breaks_att_bypass/?sort=new
                              pfSense pfatt GIT Issue - https://github.com/MonkWho/pfatt/issues/67
                              OPNSense pfatt GIT Issue - https://github.com/MonkWho/pfatt/issues/65

                              B 1 Reply Last reply Reply Quote 0
                              • B
                                bigjohns97 @nedyah700
                                last edited by

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

                                Okay, had some success today based on info I gathered from all the various discussions online. I think it is something to do with the em(4) driver. Do all of you having issues have Intel NIC's? I put together a test pfSense server from a bunch of spare parts and it worked right away on the latest release. After digging, I couldn't get any Intel NIC to work. Using what I had around (a few crappy USB dongles worked and old PC's with integrated NICs) I had success with everything not Intel GbE. When I re-upgraded my main pfSense box I was able to move my WAN link to an SFP slot (with RJ45 Module) with some success. I say "some" because all my SFP/RJ45 modules are 10GB and they do not negotiate well with the ONT.

                                Something interesting for me, if_em.ko is present in /boot/kernel on 2.6.0 but wasn't in my previous version of pfSense. My knowledge is limited but I am not sure where the driver was located in the previous version? Anyone smarter than me know?

                                Some Useful Links:
                                FreeBSD 12.3 Release Notes (em(4) driver notes) - https://www.freebsd.org/releases/12.3R/relnotes/
                                Reddit Discussion - https://www.reddit.com/r/PFSENSE/comments/ssgsha/psa_260_breaks_att_bypass/?sort=new
                                pfSense pfatt GIT Issue - https://github.com/MonkWho/pfatt/issues/67
                                OPNSense pfatt GIT Issue - https://github.com/MonkWho/pfatt/issues/65

                                Yes I have an Intel NIC but I am using the IGB driver, at least I think I am because all of my interfaces are igb#

                                1 Reply Last reply Reply Quote 0
                                • N
                                  nedyah700 Rebel Alliance
                                  last edited by

                                  Okay, I got everything up and working on my regular Intel NIC. I’m not the biggest expert here so bear with me.
                                  Through troubleshooting I was able to get every non-Intel NIC to authenticate and pull DHCP. After more testing all igb(4) driver-based cards failed. In the /boot/kernel folder I noticed if_igb.ko is simply a shortcut to the em(4) driver (if_em.ko). I am guessing FreeBSD is using this combined driver from intel? https://www.intel.com/content/www/us/en/download/15187/intel-network-adapter-gigabit-base-driver-for-freebsd.html

                                  Alternatively, I found this driver that appears to be for igb(4) separately, and it seems newer. https://www.intel.com/content/www/us/en/download/14610/intel-network-adapter-driver-for-82575-6-and-82580-based-gigabit-network-connections-under-freebsd.html?wapkw=i350%20freebsd

                                  I downloaded a FreeBSD-12.3 VM, its related source code (amd64), and complied the separate igb(4) driver.

                                  I loaded my newly compiled if_igb.ko into the /boot/modules folder with chmod 555 permissions. Next, I added the following two lines to my /boot/loader.conf file to supersede the included driver.

                                  if_igb_load="YES"
                                  if_igb_name="/boot/modules/if_igb.ko"

                                  Rebooted and everything came up just fine!

                                  Feel free to use my compiled if_igb.ko if you don’t want to build your own.
                                  https://github.com/neydah700/pfsense_intel/blob/main/if_igb.ko

                                  Also, for reference here is my pfatt script if anyone needs a reference.
                                  https://github.com/neydah700/pfsense_intel/blob/main/pfatt_intel.sh

                                  A few notes:

                                  • 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.
                                  • I have an angry family since our internet has been up and down for a few days now.
                                  B 1 Reply Last reply Reply Quote 2
                                  • stephenw10S
                                    stephenw10 Netgate Administrator
                                    last edited by

                                    Did you test the updated merged driver? I imagine that might also work since that isn't using iflib either as far as I can see.

                                    This is nothing to do with ZFS.

                                    Steve

                                    N 2 Replies Last reply Reply Quote 0
                                    • N
                                      nedyah700 Rebel Alliance @stephenw10
                                      last edited by

                                      @stephenw10 I had a compile error with e1000_ich8lan.c. There were some indentations that threw errors. I think I have those resolved and am trying shortly.

                                      The ZFS think I mentioned is something different and probably just me doing something dumb. The script we are running using shellcmd would not run anymore from the /cf/conf directory. It worked on my non-ZFS 22.01 install but not my ZFS 22.01 install. I didn't do any troubleshooting after moving to /root/ solved it. Sorry for the confusion!

                                      1 Reply Last reply Reply Quote 0
                                      • stephenw10S
                                        stephenw10 Netgate Administrator
                                        last edited by

                                        Hmm, curious. I wouldn't have expected any difference between those locations. Unless it was an older ZFS install maybe? The default mount structure was changed at one time.

                                        Steve

                                        1 Reply Last reply Reply Quote 0
                                        • N
                                          nedyah700 Rebel Alliance @stephenw10
                                          last edited by

                                          @stephenw10 also, dumb question.

                                          Considering the shortcut from if_igb.ko to if_em.ko will this work in my loader.conf.local?

                                          if_em_load="YES"
if_em_name="/boot/modules/if_em.ko"

                                          Or will the shortcut cause the system to load the original em module for igb and I need something like below?

                                          if_em_load="YES"
if_em_name="/boot/modules/if_em.ko"
if_igb_load="YES"
if_igb_name="/boot/modules/if_em.ko"
                                          1 Reply Last reply Reply Quote 0
                                          • stephenw10S
                                            stephenw10 Netgate Administrator
                                            last edited by

                                            It would just fail to load since there is file: /boot/modules/if_em.ko

                                            The original modules are in /boot/kernel. If you don't set the name variable it will load those since they are in the default path. But you don't need or want to load those since they are in the kernel already.

                                            Steve

                                            N 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post