Bypass At&t fiber BGW210-700
-
pkg install ng_etf-kmod-0.1 I don't get an error on the install it says it completed...maybe my expectation is wrong. I am assuming (which I know I should not) that the pkg installs all the variables and I simply have to connect the att gateway to the wan port on the pfsense box and the att ont to the lan side of the pfsense box and reboot.
-
Right and I assume you see the install happen after that rather than an error? The more info you give us the better we can help you here.
Please give the full console output of you trying to load that module and the error it returns.
Steve
-
using the shellcmd configuration Shellcmd Type earlyshellcmd...do I need to put
the full <earlyshellcmd>/root/bin/pfatt.sh</earlyshellcmd>
or simply /root/bin/pfatt.sh
also where do I find those logs you mentioned?
-
You don't need the tags just the full path to the command:
/root/bin/pfatt.sh
Just copy and paste the console showing you running the command and whatever the output is.
Steve
-
ok also do I still need to run those chmod commands?
noted: chmod +x /root/bin/pfatt.sh
chmod 555 /boot/kernel/ng_etf.ko
-
I did not after installing from the pkg. You might well have to if you uploaded the module manually.
It would show a permissions error if that were the case though.
Steve
-
I ran dmesg -a and got the out put below.
Initializing.................. done.
Starting device manager (devd)...kldload: can't load ums: No such file or directory
done.
Loading configuration......done.
linker_load_file: Unsupported file type
kldload: an error occurred while loading the module. Please check dmesg(8) for more details.
Updating configuration...done.
Checking config backups consistency.................................done.
Setting up extended sysctls...done.
Setting timezone...done.
Configuring loopback interface...done.
Starting syslog...done.
Starting Secure Shell Services...done.
Setting up interfaces microcode...done.
Configuring loopback interface...done.
Creating wireless clone interfaces...done.
Configuring LAGG interfaces...done.
Configuring VLAN interfaces...done.
Configuring QinQ interfaces...done.
Configuring IPsec VTI interfaces...done.
Configuring WAN interface...
em0: link state changed to UP
done.
Configuring OPT1 interface...done.
Configuring OPT2 interface...done.
Configuring OPT3 interface...done.
Configuring LAN interface...done.
Configuring CARP settings...done.
Syncing OpenVPN settings...done.
pflog0: promiscuous mode enabled
Configuring firewall......done.
Starting PFLOG...done.
Setting up gateway monitors...done.
Setting up static routes...done.
Setting up DNSs...
Starting DNS Resolver...
em4: link state changed to UP
em2: link state changed to UP
em3: link state changed to UP
em1: link state changed to UP
done.
Synchronizing user settings...done.
Starting webConfigurator...done.
Configuring CRON...done.
Starting NTP time client...done.
Starting DHCP service...done.
Starting DHCPv6 service...done.
Configuring firewall......done.
Generating RRD graphs...done.
Starting syslog...done.
Starting CRON... done.
Starting package Shellcmd...done.
pfSense 2.4.4-RELEASE (Patch 3) amd64 Wed May 15 18:53:44 EDT 2019
Bootup complete -
Ok you are saying the module will not load. We need to see exactly how you're trying to load it and what errors it produces. Here's me doing the same on a local device:
[2.4.4-RELEASE][admin@pfsense.fire.box]/root: kldstat Id Refs Address Size Name 1 21 0xffffffff80200000 2ddcbe8 kernel 2 1 0xffffffff83221000 10a0 cpuctl.ko 3 1 0xffffffff83223000 2ed0 cryptodev.ko 4 1 0xffffffff83226000 10810 dummynet.ko 5 1 0xffffffff83237000 a34 ng_etf.ko [2.4.4-RELEASE][admin@pfsense.fire.box]/root: kldunload ng_etf [2.4.4-RELEASE][admin@pfsense.fire.box]/root: kldload ng_etf [2.4.4-RELEASE][admin@pfsense.fire.box]/root: kldload ng_etf kldload: can't load ng_etf: module already loaded or in kernel
I first check what modules are loaded with kldstat. Then unload ng_etf. The load it. Then try to load it again which produces an error.
Steve
-
This is what came back
[2.4.4-RELEASE[admin@pfSense.localdomain]/root: kldstat
Id Refs Address Size Name
1 3 0xffffffff80200000 2ddcbe8 kernel
2 1 0xffffffff83221000 10a0 cpuctl.ko
[2.4.4-RELEASE][admin@pfSense.localdomain]/root: kldunload ng_etf
kldunload: can't find file ng_etf
[2.4.4-RELEASE][admin@pfSense.localdomain]/root: kldload ng_etf
kldload: an error occurred while loading the module. Please check dmesg(8) for more details.
[2.4.4-RELEASE][admin@pfSense.localdomain]/root:]
1 3 0xffffffff80200000 2ddcbe8 kernel
2 1 0xffffffff83221000 10a0 cpuctl.ko
[2.4.4-RELEASE][admin@pfSense.localdomain]/root: -
Ok, if you run
dmesg
after trying to load the module does it give any further information? -
@stephenw10 said in Bypass At&t fiber BGW210-700:
kldload ng_etf
%(#000000)[%(#000000)[linker_load_file: Unsupported file type
linker_load_file: Unsupported file type
[2.4.4-RELEASE][admin@pfSense.localdomain]/root: kldstat
Id Refs Address Size Name
1 3 0xffffffff80200000 2ddcbe8 kernel
2 1 0xffffffff83221000 10a0 cpuctl.ko
[2.4.4-RELEASE][admin@pfSense.localdomain]/root: kldunload ng_etf
kldunload: can't find file ng_etf
[2.4.4-RELEASE][admin@pfSense.localdomain]/root: kldload ng_etf
kldload: an error occurred while loading the module. Please check dmesg(8) for more details.
[2.4.4-RELEASE][admin@pfSense.localdomain]/root: dmesg
linker_load_file: Unsupported file type
[2.4.4-RELEASE][admin@pfSense.localdomain]/root:]] -
Hmm, OK I suggest you have a bad module file there somewhere. Remove the package:
[2.4.4-RELEASE][admin@pfsense.fire.box]/root: pkg remove ng_etf-kmod Checking integrity... done (0 conflicting) Deinstallation has been requested for the following 1 packages (of 0 packages in the universe): Installed packages to be REMOVED: ng_etf-kmod-0.1 Number of packages to be removed: 1 Proceed with deinstalling packages? [y/N]: y [1/1] Deinstalling ng_etf-kmod-0.1... [1/1] Deleting files for ng_etf-kmod-0.1: 100%
Then search for any remaining rogue module files:
[2.4.4-RELEASE][admin@pfsense.fire.box]/root: find / -name "*ng_etf*" /root/var/cache/pkg/ng_etf-kmod-0.1-10b4f7c3eb.txz /root/var/cache/pkg/ng_etf-kmod-0.1.txz
On my system they are only in the package cache which is fine. If you have others remove them.
Then reboot, check you still don't have any module file present and then re-install the package and retry.
Steve
-
[2.4.4-RELEASE][admin@pfSense.localdomain]/root: find / -name "ng_etf"
/root/bin/ng_etf.ko
/var/cache/pkg/ng_etf-kmod-0.1-10b4f7c3eb.txz
/var/cache/pkg/ng_etf-kmod-0.1.txz
/boot/kernel/ng_etf.ko
[2.4.4-RELEASE][admin@pfSense.localdomain]/root: [2.4.4-RELEASE][admin@pfSense.localdomain]/root: find / -name "ng_etf"
[2.4.4-RELEASE][admin@pfSense.localdomain]/root:: Too many arguments.
[2.4.4-RELEASE][admin@pfSense.localdomain]/root: /root/bin/ng_etf.ko
/root/bin/ng_etf.ko: Permission denied.
[2.4.4-RELEASE][admin@pfSense.localdomain]/root: /var/cache/pkg/ng_etf-kmod-0.1-10b4f7c3eb.txz
/var/cache/pkg/ng_etf-kmod-0.1-10b4f7c3eb.txz: Permission denied.
[2.4.4-RELEASE][admin@pfSense.localdomain]/root: /var/cache/pkg/ng_etf-kmod-0.1.txz
/var/cache/pkg/ng_etf-kmod-0.1.txz: Permission denied.
[2.4.4-RELEASE][admin@pfSense.localdomain]/root: /boot/kernel/ng_etf.ko
/boot/kernel/ng_etf.ko: Exec format error. Binary file not executable.
[2.4.4-RELEASE][admin@pfSense.localdomain]/root: [2.4.4-RELEASE][admin@pfSense.localdomain]/root:
[2.4.4-RELEASE][admin@pfSense.localdomain]/root: -
@stephenw10 said in Bypass At&t fiber BGW210-700:
find / -name "ng_etf"
2.4.4-RELEASE][admin@pfSense.localdomain]/root: rm /root/bin/ng_etf.ko
[2.4.4-RELEASE][admin@pfSense.localdomain]/root: rm /var/cache/pkg/ng_etf-kmod-0.1-10b4f7c3eb.txz
[2.4.4-RELEASE][admin@pfSense.localdomain]/root: rm /var/cache/pkg/ng_etf-kmod-0.1.txz
[2.4.4-RELEASE][admin@pfSense.localdomain]/root: rm /boot/kernel/ng_etf.ko
[2.4.4-RELEASE][admin@pfSense.localdomain]/root: rm /root/bin/ng_etf.ko
rm: /root/bin/ng_etf.ko: No such file or directory
[2.4.4-RELEASE][admin@pfSense.localdomain]/root: rm /var/cache/pkg/ng_etf-kmod-0.1-10b4f7c3eb.txz
rm: /var/cache/pkg/ng_etf-kmod-0.1-10b4f7c3eb.txz: No such file or directory
[2.4.4-RELEASE][admin@pfSense.localdomain]/root: rm /var/cache/pkg/ng_etf-kmod-0.1.txz
rm: /var/cache/pkg/ng_etf-kmod-0.1.txz: No such file or directory
[2.4.4-RELEASE][admin@pfSense.localdomain]/root: rm /boot/kernel/ng_etf.ko
rm: /boot/kernel/ng_etf.ko: No such file or directory
[2.4.4-RELEASE][admin@pfSense.localdomain]/root: find / -name "ng_etf"
[2.4.4-RELEASE][admin@pfSense.localdomain]/root: -
You have to use at least the trainling
*
or it won't anything:find / -name "ng_etf*"
If there are no more instances then reinstall the pkg and try to load the module again.
Steve
-
Ok no more load issue it loads now... one more thing to get straight before I reboot
(1) ONT from outside goes to EM0
(2) ONT from Residential Gateway goes to EM1is this correct?
Could not wait curiosity got the best of me. rebooted with the above config. it booted but had no internet. I ran the network trouble shooter from windows and it came back with DNS issue.
-
No way I can answer that without knowing how you have it connected. However it looks like you donlt have em interfaces at all from your previous posts. If that's have you have it configured in pfSense and the script is still the same then the ONT should be on igb0 and the BGW210-700 on igb1.
Steve
-
Ok I have tried both
ONT on em0 and the BGW210-700 on em1.(1) ONT from outside goes to EM0
(2) ONT from Residential Gateway goes to EM1
dpinger refuses to start1 6 0xffffffff80200000 2ddcbe8 kernel
2 1 0xffffffff83221000 10a0 cpuctl.ko
3 1 0xffffffff83223000 a34 ng_etf.ko
[2.4.4-RELEASE][admin@pfSense.localdomain]/root:em1: permanently promiscuous mode enabled
em0: permanently promiscuous mode enabled
em0: link state changed to UP
em1: link state changed to UP
em1: link state changed to DOWN
pflog0: promiscuous mode enabled
em4: link state changed to UP
em2: link state changed to UP
em3: link state changed to UP
em1: link state changed to UP
[2.4.4-RELEASE][admin@pfSense.localdomain]/root: -
What happened when you got yo step 7 here: https://github.com/aus/pfatt#install
Did you see the ngeth0 interface and assign it as WAN?
Since you are re-assigning the interfaces it shouldn't matter which one you use as long as they are actually connected to the devices you set in the script.
Check the log file the script makes each time it runs: /var/log/pfatt.log
There should be some good troubleshooting info there if it's still not working.Steve
-
- Next, we spoof the MAC address of the residential gateway and request a DHCP lease on ngeth0. The packets get tagged as VLAN0 and exit to the ONT.
are you talking about this step above ...if so I did place my residential gateway mac in PFatt,sf. does it need to go someplace else?
I never got any prompts to configure any thing on boot up..can I configure manually from GUI?