Watchguard Firebox M440
-
Here is a better copy of the 2.3.5 log file.
-
Ok so that was the normal pfSense installed to CF? Not Nano by the looks if it.
Ok, so that at least proves it's not some odd driver regression. It seems more like a resource conflict of some sort though I don't see anything specific. I'll try to get that module built for 11.2.
Steve
-
@stephenw10 said in Watchguard Firebox M440:
Ok so that was the normal pfSense installed to CF? Not Nano by the looks if it.
Ok, so that at least proves it's not some odd driver regression. It seems more like a resource conflict of some sort though I don't see anything specific. I'll try to get that module built for 11.2.
Steve
Yes.. The normal pfSense installed to CF.. Please explain what you are building (module 11.2). When will it be available for me to test?
-
Hopefully it will be the igb kernel module that you can load in place of the in kernel driver but with debugging enabled.
It should be easy to build but it's been a while since I tried and I have to test it works at all locally before you try.
Steve
-
@stephenw10 said in Watchguard Firebox M440:
Hopefully it will be the igb kernel module that you can load in place of the in kernel driver but with debugging enabled.
It should be easy to build but it's been a while since I tried and I have to test it works at all locally before you try.
Steve
When will you have it available for testing? Anything else you want me to try?
-
Ok, so this works. But it is very verbose! Like it prints out a page of status info every second at the console.
0_1539553890564_if_igb.ko.txt
That is the replacement kernel module.Copy it to /boot/modules in the m440 and rename it
if_igb.ko.Then add the following line to /boot/loader.conf.local:
if_igb_load="yes"Then reboot.
Try to capture the console output covering the boot process. That should show it attempting to connect to the i354 NICs and why it's failing. You might have to disconnect the console once that happens because as I said it will continue to spam the console every second.
Steve
-
@stephenw10 said in Watchguard Firebox M440:
Ok, so this works. But it is very verbose! Like it prints out a page of status info every second at the console.
0_1539553890564_if_igb.ko.txt
That is the replacement kernel module.Copy it to /boot/modules in the m440 and rename it
if_igb.ko.Then add the following line to /boot/loader.conf.local:
if_igb_load="yes"Then reboot.
Try to capture the console output covering the boot process. That should show it attempting to connect to the i354 NICs and why it's failing. You might have to disconnect the console once that happens because as I said it will continue to spam the console every second.
Steve
Ok.. Will try it now.. Give me 30 minutes..
-
@stephenw10 said in Watchguard Firebox M440:
Ok, so this works. But it is very verbose! Like it prints out a page of status info every second at the console.
0_1539553890564_if_igb.ko.txt
That is the replacement kernel module.Copy it to /boot/modules in the m440 and rename it
if_igb.ko.Then add the following line to /boot/loader.conf.local:
if_igb_load="yes"Then reboot.
Try to capture the console output covering the boot process. That should show it attempting to connect to the i354 NICs and why it's failing. You might have to disconnect the console once that happens because as I said it will continue to spam the console every second.
Steve
I will be using WINSCP to copy the file to the M440 system...
-
Yeah, that's fine.
You don't really need to quote my whole post when you reply to me. There's only you and me here.
Doing so makes the thread waaaay longer.Steve
-
Added the module and updated the config file ... I don’t see anything verbosing on the console..
-
Hmm, you see it failing to load that, maybe an error at the beginning on the boot?
The module is built for pfSense 2.4.4 (FreeBSD 11.2). It won't load in 2.3.5.
Steve
-
I noticed this line in the boot log...
KDB: debugger backends: ddb.../if_igb.ko': input/output errors=[0x8+0x197280+0x8
Attached is the boot log....
-
Here is what I done so far based on your recommendation....
-
Hmm, only two possibilities I can see. I actually tested on a 2.4.5 snapshot but that's still build on FreeBSD 11.2.
Perhaps the file was borked somewhere by uploading/downloading via the forum:
[2.4.5-DEVELOPMENT][root@8860.stevew.lan]/root: sha256 /boot/modules/if_igb.ko SHA256 (/boot/modules/if_igb.ko) = d309d1b253ddf4a4444ab2c4fa16c71b2c880e7439f236a35395444edeb0db28I don't see that KDB line so I'm guessing the file was broken somehow. Checking sha256 sum should show that.
Steve
-
Will check now...
-
Looks OK here when I downloaded it from the forum though:
steve@steve-MMLP7AP-00 ~/Downloads $ sha256sum 1539553891669-if_igb.ko.txt d309d1b253ddf4a4444ab2c4fa16c71b2c880e7439f236a35395444edeb0db28 1539553891669-if_igb.ko.txtHmm
-
Getting a different checksum.. Here are the results..
-
To download, I right click on the file and select "Save Target As" to my Windows 10 machine. I rename the file and then use WINSCP to move the file to pfSense.
-
I downloaded the sha256sum program for Windows and I'm getting the same checksum on my Windows machine.. Hmm.
E:\Watchguard M440>sha256sum.exe if_igb.ko
d309d1b253ddf4a4444ab2c4fa16c71b2c880e7439f236a35395444edeb0db28 *if_igb.ko -
Ok.. Here is what is going on..
I used WINSCP to upload the file to pfSense. I ran the sha256 command on the file in pfSense and I get checksum "d309d1b253ddf4a4444ab2c4fa16c71b2c880e7439f236a35395444edeb0db28" which is what you get.
I reboot pfSense and for some reason the checksum of the file changes. I ran the sha256 command on the file in pfSense after the reboot and I get checksum "09baa21ec3e7f90e397be6fec895a80f9e5c2b70641eae57c61318ae173b1edc".
What is going on? Maybe the permissions on the file is incorrect..
