Bypass At&t fiber BGW210-700
-
Nice!
-
Can I use the wireless portion of the BGW210-700 as an access point or is it completely out of the equation at this point?
-
Short answer: no.
It may be possible to configure something but I would not. It would be though the AT&T router so all the nat and firewall would apply there as well as in pfSense. It would be entirely separate from the LAN. Also you would probably be the only person running that config so it's hard to say what you might run into.
Steve
-
Thanks Steve...I also lost some speed dropped to 100 Mbits I have Gig fiber. I reset the the BGW210-700 to factory defaults brought up the network and did a speeds test through the BGW210-700 and it came back to 997 on the download and 837 on the upload...I then rebooted the Pfsense and connect. Ran another speed test again and they came back normal. Is this something I will have to do normally?
-
I would not expect so. I do not have that type of connection though so I have no way to know for sure. @sherpagoodness may be able to tell what to expect.
Steve
-
@sherpagoodness Hey since I bypassed ATT BGW210-700... my speed dropped to 100 Mbits I have Gig fiber. I reset the the BGW210-700 to factory defaults brought up the network and did a speeds test through the BGW210-700 and it came back to 997 on the download and 837 on the upload...I then rebooted the Pfsense and connect. Ran another speed test again and they came back normal. I just checked it a gain and it's back to 100 mbits... Is this something I will have to do normally?
-
@stephenw10 I was recently running into the same issue with the package install as well. Currently running pfsense 2.4.5, when trying to pull the package and install I'm getting "no packaged available to install mactching 'ng_etf-kmod'. Were these pulled or no longer available, or is it related to differing versions?
-
Hmm, it does appear to be missing. Digging.....
-
Ok, you should not need to install that pkg any longer as the Netgraph etf module is now in the base install:
[2.4.5-RELEASE][root@pfsense.fire.box]/root: kldstat -v | grep ng_etf 533 ng_etfSteve
-
@stephenw10 that explains it then, I had originally used the pre compiled file which was meant for x64 and not ARM (I believe) and then after upgrade removed the file thinking it was the the pre compiled and not the new one.
Any chance I can still pull the arm kernel from somewhere, or if it I just reset the device will it get restored?
-
Hmm, I don't believe it in the ARM kernel. What device do you have?
-
@stephenw10 I just got the SG-1100 a few days ago.
Also tried the factory reset, looking in /boot/kernel I don’t see the file now.
-
Ok, it doesn't appear to be in the aarch64 kernel either. The pkg was available for all architectures in 2.4.4 though.
I have asked about it internally.Steve
-
Thanks @stephenw10 it you could let me know I would appreciate it!
-
[spam was here]
-
Um.... what? Smells like spam...
Edit: Yup spam.Anyway: https://redmine.pfsense.org/issues/10463
-
Thanks @stephenw10 so it sounds like in this case it’s only going to be available in 64 bit for 2.4.5.
Would it be possible to get the compiled file from the 2.4.4 build that was for arm and I can try that out?
-
Yes, and it does appear to load OK but I have no way to test it:
[2.4.5-RELEASE][admin@1100-4.stevew.lan]/root: pkg add https://repo01.netgate.com/pkg/pfSense_factory-v2_4_4_aarch64-pfSense_factory-v2_4_4/All/ng_etf-kmod-0.1.txz Fetching ng_etf-kmod-0.1.txz: 100% 4 KiB 3.8kB/s 00:01 Installing ng_etf-kmod-0.1... Extracting ng_etf-kmod-0.1: 100% [2.4.5-RELEASE][admin@1100-4.stevew.lan]/root: kldload ng_etf [2.4.5-RELEASE][admin@1100-4.stevew.lan]/root: kldstat Id Refs Address Size Name 1 11 0xffff000000000000 17c01a0 kernel 2 1 0xffff000040f47000 41000 safexcel.ko 3 1 0xffff000040fa0000 41000 cryptodev.ko 4 1 0xffff000041123000 31000 ng_etf.koSteve
-
@stephenw10 will give this a shot, I did add the package from the repo and was able to load it up with kldload so that's promising :)
I appreciate your help!
-
@stephenw10 as a follow-up it does work on SG-1100 with 2.4.5, I was able to set it up and am now bypassing the ATT RG completely.
One thing I did run into was that my interface names differed from the output of ngctl and ifconfig, so I needed to manually change some parts of the script.
But so far so good!
