PfSense not detecting Link Up/Down state on Jetway nf9n-2930 with ADE4INLANG
-
Hi!
We just did some tests with a Jetway nf9n-2930 board together with a ADE4INLANG 4x Intel 82574L plugin-card.
But we are now running into an issue with pfSense and detecting the link-state of the 4 network interfaces of the plugin-card.We tried version 2.3 and 2.4-beta, but similar behavior on both.
The EM-driver is used (em0-em3).So pfs is detecting the link-status "UP" event once after plugging in a active cable, but after that the link-state always stays "UP".
The link led's of the network interface itself work just fine, but the link up/down events don't come trough into pfs after that initial UP-event.Does anyone has seen this behavior before?
-
We just did some tests with a Jetway nf9n-2930 board together with a ADE4INLANG 4x Intel 82574L plugin-card.
What tests did you? And how did you exactly this tests? Which pfSense version is in the game here? And is this a fresh and full
installation or a NanoBSD on USB pen drive installation? Are any packets such as Snort, Squid or pfBlockerNG installed too?But we are now running into an issue with pfSense and detecting the link-state of the 4 network interfaces of the plugin-card.
The NIC is not a real NIC it is a daughter board from Jetway! And often the switch chip (PHY) behind the LAN ports is important fo
us to know. It can be that this PHY chip is not really supported by pfSense but the ordinary Intel Chip is well supported! Jetway often
uses PHY chips from Pericom as a hind for you to start searching.But we are now running into an issue with pfSense and detecting the link-state of the 4 network interfaces of the plugin-card.
Are they well running and working?
We tried version 2.3 and 2.4-beta, but similar behavior on both.
The EM-driver is used (em0-em3).For the Intel LAN chipset 82574L the em driver will be the right one! It is likes all other OS and drivers you can´t choose
a driver for a device it must be written exactly for that device.So pfs is detecting the link-status "UP" event once after plugging in a active cable, but after that the link-state always stays "UP".
Even if the cable will be plugged out?
The link led's of the network interface itself work just fine, but the link up/down events don't come trough into pfs after that initial UP-event.
This can be different here in that case because the NIC is not a plugin card, it is a Jetway daughter board that is connected in
an other way such a ordinary NIC will be.Does anyone has seen this behavior before?
Please trust me this behaviour is based or pointed to the daughterboard and its PHY chip on it and nothing more.
It is the same as with that Jetway board here: NF9HG-2930 the board itself is running like hell, but the both
daughterboards are not supported based on the soldered PHY chip from Pericom on the both boards!