Pfsense won't recognize network card
-
Here 's the output of lshw
WARNING: you should run this program as super-user. ubuntu description: Computer width: 32 bits *-core description: Motherboard physical id: 0 *-memory description: System memory physical id: 0 size: 3826MiB *-cpu product: Intel(R) Pentium(R) D CPU 3.40GHz vendor: Intel Corp. physical id: 1 bus info: cpu@0 version: 15.6.5 serial: 0000-0F65-0000-0000-0000-0000 size: 1700MHz capacity: 1700MHz width: 64 bits capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx x86-64 constant_tsc pebs bts pni dtes64 monitor ds_cpl est cid cx16 xtpr pdcm lahf_lm cpufreq configuration: id=1 *-logicalcpu:0 description: Logical CPU physical id: 1.1 width: 64 bits capabilities: logical *-logicalcpu:1 description: Logical CPU physical id: 1.2 width: 64 bits capabilities: logical *-pci description: Host bridge product: 82Q963/Q965 Memory Controller Hub vendor: Intel Corporation physical id: 100 bus info: pci@0000:00:00.0 version: 02 width: 32 bits clock: 33MHz configuration: driver=agpgart-intel resources: irq:0 *-display description: VGA compatible controller product: 82Q963/Q965 Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@0000:00:02.0 version: 02 width: 64 bits clock: 33MHz capabilities: vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:42 memory:d0000000-d00fffff memory:c0000000-cfffffff ioport:30e0(size=8) *-usb:0 description: USB controller product: 82801H (ICH8 Family) USB UHCI Controller #4 vendor: Intel Corporation physical id: 1a bus info: pci@0000:00:1a.0 version: 02 width: 32 bits clock: 33MHz capabilities: uhci bus_master configuration: driver=uhci_hcd latency=0 resources: irq:16 ioport:3000(size=32) *-usb:1 description: USB controller product: 82801H (ICH8 Family) USB2 EHCI Controller #2 vendor: Intel Corporation physical id: 1a.7 bus info: pci@0000:00:1a.7 version: 02 width: 32 bits clock: 33MHz capabilities: ehci bus_master cap_list configuration: driver=ehci_hcd latency=0 resources: irq:16 memory:d0504000-d05043ff *-multimedia description: Audio device product: 82801H (ICH8 Family) HD Audio Controller vendor: Intel Corporation physical id: 1b bus info: pci@0000:00:1b.0 version: 02 width: 64 bits clock: 33MHz capabilities: bus_master cap_list configuration: driver=snd_hda_intel latency=0 resources: irq:43 memory:d0500000-d0503fff *-pci:0 description: PCI bridge product: 82801H (ICH8 Family) PCI Express Port 1 vendor: Intel Corporation physical id: 1c bus info: pci@0000:00:1c.0 version: 02 width: 32 bits clock: 33MHz capabilities: pci normal_decode bus_master cap_list configuration: driver=pcieport resources: irq:40 ioport:5000(size=4096) memory:d0800000-d09fffff ioport:d0a00000(size=2097152) *-pci:1 description: PCI bridge product: 82801H (ICH8 Family) PCI Express Port 5 vendor: Intel Corporation physical id: 1c.4 bus info: pci@0000:00:1c.4 version: 02 width: 32 bits clock: 33MHz capabilities: pci normal_decode bus_master cap_list configuration: driver=pcieport resources: irq:41 ioport:2000(size=4096) memory:d0100000-d01fffff ioport:d0600000(size=2097152) *-network description: Ethernet interface product: NetLink BCM5787 Gigabit Ethernet PCI Express vendor: Broadcom Corporation physical id: 0 bus info: pci@0000:03:00.0 logical name: eth1 version: 02 serial: 00:1a:6b:61:40:94 size: 100Mbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=tg3 driverversion=3.121 duplex=full firmware=sb v2.04 ip=192.168.0.65 latency=0 multicast=yes port=twisted pair speed=100Mbit/s resources: irq:44 memory:d0100000-d010ffff *-usb:2 description: USB controller product: 82801H (ICH8 Family) USB UHCI Controller #1 vendor: Intel Corporation physical id: 1d bus info: pci@0000:00:1d.0 version: 02 width: 32 bits clock: 33MHz capabilities: uhci bus_master configuration: driver=uhci_hcd latency=0 resources: irq:16 ioport:3020(size=32) *-usb:3 description: USB controller product: 82801H (ICH8 Family) USB UHCI Controller #2 vendor: Intel Corporation physical id: 1d.1 bus info: pci@0000:00:1d.1 version: 02 width: 32 bits clock: 33MHz capabilities: uhci bus_master configuration: driver=uhci_hcd latency=0 resources: irq:17 ioport:3040(size=32) *-usb:4 description: USB controller product: 82801H (ICH8 Family) USB UHCI Controller #3 vendor: Intel Corporation physical id: 1d.2 bus info: pci@0000:00:1d.2 version: 02 width: 32 bits clock: 33MHz capabilities: uhci bus_master configuration: driver=uhci_hcd latency=0 resources: irq:18 ioport:3060(size=32) *-usb:5 description: USB controller product: 82801H (ICH8 Family) USB2 EHCI Controller #1 vendor: Intel Corporation physical id: 1d.7 bus info: pci@0000:00:1d.7 version: 02 width: 32 bits clock: 33MHz capabilities: ehci bus_master cap_list configuration: driver=ehci_hcd latency=0 resources: irq:16 memory:d0504400-d05047ff *-pci:2 description: PCI bridge product: 82801 PCI Bridge vendor: Intel Corporation physical id: 1e bus info: pci@0000:00:1e.0 version: f2 width: 32 bits clock: 33MHz capabilities: pci subtractive_decode bus_master cap_list resources: ioport:4000(size=4096) memory:d0200000-d02fffff ioport:d0300000(size=1048576) *-network description: Ethernet interface product: RTL-8139/8139C/8139C+ vendor: Realtek Semiconductor Co., Ltd. physical id: 9 bus info: pci@0000:0a:09.0 logical name: eth0 version: 10 serial: 00:0b:2b:01:d3:7f size: 10Mbit/s capacity: 100Mbit/s width: 32 bits clock: 33MHz capabilities: bus_master cap_list rom ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=8139too driverversion=0.9.28 duplex=half latency=32 maxlatency=64 mingnt=32 multicast=yes port=MII speed=10Mbit/s resources: irq:21 ioport:4000(size=256) memory:d0200000-d02000ff memory:d0300000-d030ffff *-isa description: ISA bridge product: 82801HB/HR (ICH8/R) LPC Interface Controller vendor: Intel Corporation physical id: 1f bus info: pci@0000:00:1f.0 version: 02 width: 32 bits clock: 33MHz capabilities: isa bus_master cap_list configuration: latency=0 *-ide:0 description: IDE interface product: 82801H (ICH8 Family) 4 port SATA Controller [IDE mode] vendor: Intel Corporation physical id: 1f.2 bus info: pci@0000:00:1f.2 version: 02 width: 32 bits clock: 66MHz capabilities: ide bus_master cap_list configuration: driver=ata_piix latency=0 resources: irq:17 ioport:1f0(size=8) ioport:3f6 ioport:170(size=8) ioport:376 ioport:30b0(size=16) ioport:30a0(size=16) *-serial UNCLAIMED description: SMBus product: 82801H (ICH8 Family) SMBus Controller vendor: Intel Corporation physical id: 1f.3 bus info: pci@0000:00:1f.3 version: 02 width: 32 bits clock: 33MHz configuration: latency=0 resources: memory:d0504800-d05048ff ioport:3080(size=32) *-ide:1 description: IDE interface product: 82801HR/HO/HH (ICH8R/DO/DH) 2 port SATA Controller [IDE mode] vendor: Intel Corporation physical id: 1f.5 bus info: pci@0000:00:1f.5 version: 02 width: 32 bits clock: 66MHz capabilities: ide bus_master cap_list configuration: driver=ata_piix latency=0 resources: irq:18 ioport:3410(size=8) ioport:3404(size=4) ioport:3408(size=8) ioport:3400(size=4) ioport:30d0(size=16) ioport:30c0(size=16)*-network
description: Ethernet interface
product: NetLink BCM5787 Gigabit Ethernet PCI Express
vendor: Broadcom Corporation
physical id: 0
bus info: pci@0000:03:00.0
logical name: eth1
version: 02
serial: 00:1a:6b:61:40:94
size: 100Mbit/s
capacity: 1Gbit/s
width: 64 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=tg3 driverversion=3.121 duplex=full firmware=sb v2.04 ip=192.168.0.65 latency=0 multicast=yes port=twisted pair speed=100Mbit/s
resources: irq:44 memory:d0100000-d010ffff -
As far as I can see it should be supported by the bge(4) driver:
https://www.freebsd.org/cgi/man.cgi?query=bge&sektion=4&manpath=freebsd-release-ports
Can you boot from the pfSense install media and do this from the shell you can start instead of starting the installer:
dmesg | grep bgeDoes that produce any output and what does it say?
-
@kpa:
As far as I can see it should be supported by the bge(4) driver:
https://www.freebsd.org/cgi/man.cgi?query=bge&sektion=4&manpath=freebsd-release-ports
Can you boot from the pfSense install media and do this from the shell you can start instead of starting the installer:
dmesg | grep bgeDoes that produce any output and what does it say?
There is a lot of text so I took a screenshot
-
That's not good, the chip is recognized by the driver but something causes the driver initialization to fail. Can you see if there are BIOS updates for your board?
You can also see if this helps:
https://doc.pfsense.org/index.php/Tuning_and_Troubleshooting_Network_Cards#Broadcom_bce.284.29_Cards
-
i have the last bios update
I did a bios update two days ago after the computer bios was in French
ן download the bios from here
https://support.lenovo.com/il/en/downloads/migr-66068
my computer is
MT-M 8808-8HF
S/N: LKLWHF9is it worth a try earlier BIOS ?
-
updating
I've updated to earlier (2jjy47usa) BIOS
(The last one is 2jjy49usa)
and Same problemAfter searching Google I came across a post in the forum of pfsense (i have no link to it)
There, it is said that sometimes when an external card is connected, the internal is disconnected
I disconnected the external card (that is, I removed it from the computer)
And I turned on the system
Indeed now pfsense recognizes the internal card bge0The message did not say how to fix this situation
after using linux boot cd and windows install
both NIC work together
only on pfsense they dont work togetheri try to find a jumper on the motherboard
i did not see oneis there a way to make both NIC work ?
-
Indeed now pfsense recognizes the internal card bge0
Go to the BIOS and enable it would be my first try.
-
It's already enabled
-
My guess is that the BIOS is set to automatically disable the built-in NIC in case there's an add-on card installed, that makes sort of sense in a desktop system but is nonsense on a server type system.
I'd also guess that the developers of the Linux driver have found a way to enable the integrated Broadcom NIC regardless but the FreeBSD driver doesn't have the same workaround.
-
pfSense is able to attach to the Broadcom card and it can be assigned when the Realtek card is not in the box?
If that's the case then I'd throw the Realtek card away an look for something else. The rtl8139 is a truly terrible NIC.
https://github.com/pfsense/FreeBSD-src/blob/db53f09b3a68bfa850844e88c97535f277db4d71/sys/dev/rl/if_rl.c#L48
Steve
-
"snip"```
WARNING: you should run this program as super-user.
ubuntu
description: Computer
width: 32 bitsThis is under Linux (Ubuntu) and pfSense is based on FreeBSD and also could it be that this PC or pfSense box is a 32Bit version and you try out to install pfSensen version 2.4.0 that is coming only as a 64Bit version!!! Often, but not even, in the BIOS could be also set another Interrupt to many onboards NICs because tey are shared together with some PCIe slots, perhaps this might be then also the case here? Please have a look on this too. -
@kpa:
My guess is that the BIOS is set to automatically disable the built-in NIC in case there's an add-on card installed, that makes sort of sense in a desktop system but is nonsense on a server type system.
I'd also guess that the developers of the Linux driver have found a way to enable the integrated Broadcom NIC regardless but the FreeBSD driver doesn't have the same workaround.
The BIOS option associated with a network card is only
Whether to enabled the card or not to enabledThere is another option related to pxe boot (I added a screenshot)
I tried to run the system when the options are enabled. The same resultpfSense is able to attach to the Broadcom card and it can be assigned when the Realtek card is not in the box?
If that's the case then I'd throw the Realtek card away an look for something else. The rtl8139 is a truly terrible NIC.
https://github.com/pfsense/FreeBSD-src/blob/db53f09b3a68bfa850844e88c97535f277db4d71/sys/dev/rl/if_rl.c#L48
Steve
yes as i said
When I remove the external network card from the computer
And runs the system without the external card then pfsense recognizes the internal network card properlyI'll try another card
@BlueKobold:
"snip"```
WARNING: you should run this program as super-user.
ubuntu
description: Computer
width: 32 bitsThis is under Linux (Ubuntu) and pfSense is based on FreeBSD and also could it be that this PC or pfSense box is a 32Bit version and you try out to install pfSensen version 2.4.0 that is coming only as a 64Bit version!!! Often, but not even, in the BIOS could be also set another Interrupt to many onboards NICs because tey are shared together with some PCIe slots, perhaps this might be then also the case here? Please have a look on this too.I checked to see if it was suitable for 64 bit
i use this program https://www.grc.com/securable.htm
it give me The processor is 64 bit compatible
 -
Update
I brought four more network cards
That means there are currently 5 network cards
4 with pci connection
1 with pci-e-x1 connectionI tried to change
And those are the resultsThree of the cards with a pci connection
Once I connect the network card to the computer
I get the same result as the first network card
The system identifies only the external card but not the internal oneOn one card with a pci-e-x1 connection
When I connect it to a computer
The system identifies the internal card and not the external oneAnd the last card with a pci connection
Same
The system identifies the internal card and not the external oneAll cards are valid and working on windows xp / windows 7 / linux
-
All cards are valid and working on windows xp / windows 7 / linux
On the same motherboard?
It does look like that card is being disabled by attaching a different card. Can you not just use two additional NICs?
Steve
-
All cards are valid and working on windows xp / windows 7 / linux
On the same motherboard?
It does look like that card is being disabled by attaching a different card. Can you not just use two additional NICs?
Steve
yes on the same motherboard
i can use two additional cards
but the one i want to use is 10/100/1000
and all the other 4 is 10/100
the one on the boars is 10/100/1000I'll give it another try
I will try to get network cards that they are 10/100/1000The reason for all this is
That my current system is 32 bit
With 1.5 GHz memory and 10/100 network cards
And there is no upgrade to 32 bitThis computer I'm trying to install on is
With 4GB memory
And a 10/100/1000 network card -
Do you need more that 100Mbps? Having just one Gigabit NIC isn't going to help much, except maybe if you're using VLANs.
There appears to be some basic low level incompatibility with that on-board NIC and I don't think we are going to be able to help you with it.
pfSense 2.3.X will be supported for ~1 year so there's no rush to upgrade.
Steve
-
If after much trying you just can't get things to work, I suggest adding a cheap intel nic you buy off ebay for $10.
Get two and replace your current add-on card… It will save you trouble down the road. Make sure whatever you buy has native support for netmap.
Suricata needs it to work in inline mode. It might save you trouble later.
-
Do you need more that 100Mbps?
we have connections up to 500 MB
If after much trying you just can't get things to work, I suggest adding a cheap intel nic you buy off ebay for $10.
As I wrote I will try to retrieve other network cards
And if it does not work
Then another computerIn any case, thanks to everyone who tried to help
-
Network cards are usually cheaper than computers.
-
updating
I brought four new Intel network cards
With pci connection
And another Intel card with a pci-x connection
pfsense does not recognize any of them
I tried to connect two together or separately
The same resultIf Windows 2000 recognizes the network cards
(I connected two cards and the computer recognized the other two cards and the card on the board)
So pfsense should also identify them without problemsAnother question that may be related
When I installed the pfsense 2.4.0
The installation process was different from what I know
Perhaps I needed to do something different for pfsense to recognize the network cards ?
