Unable to connect after install (Intel I210 NIC)
-
@stephenw10
sorry, my wrong. igb(x) ... from 0 to 5bye
-
Ok so you added the i210 NIC so you now you have additional NICs available?
Since they are also igb it has probably changed the interface order. Expension NICs are usually enumerated first so will offset existing NICs using the same driver.
-
No, they are always the same ones that are installed directly on the motherboard (Jetway G3NF692)
To test, since updating directly from pfsense didn't work, I took a second HD and tried to install version 2.7. The installation ends correctly but in the end, even if the 6 ports are detected, none of them can be reached. The automatic assignment of the interfaces does not work because it does not detect the status of UP (even if through the shell it is possible to see with the "ifconfig" command that the interfaces go to UP once the cable is connected). Therefore, by assigning them manually they are not reachable.By installing version 2.5.2 everything works correctly. It would appear that version 2.6 onwards no longer supports I210 interfaces even if they are declared compatible.
-
So it has some combination of i210 and i211 NICs and you can no longer use the i210 NICs?
Do you see any errors at boot?
Do you see anything in the packet counters?
-
Sorry... I'm a bit confused... too much work...
I only have 6 integrated I211AT NICs!!!
With PFsense 2.5.2 everything works, but versions from 2.6 onwards don't.I don't see any errors.
After installation, with the shell command "ifconfig" after connecting the cable I can see the status of the connected interface change to UP, but I cannot connect.
I can't even ping the network client nor can I ping the firewall from client. -
On that client : did it get a DHCP lease ?
If its a windows PC : typeipconfig /allIt should have a DNS IP and gateway IP : both are the pfSense LAN IP, and a network like /24 or 255.255.255.0 - the LAN IP matches the network ?
If so, this proofs that the pfSense DHCP server was set up and running on what is now the LAN interface => You know now that you have your device connected to what is known to pfSEnse as the LAN interface.
Initially, after a minimal 'WAN LAN 'interface assignment, the one and only firewall rule is placed on the LAN interface : the 'pass all' firewall rule.
cat /tmp/rules.debug | grep 'USER_RULE'There should be a (probably one) rule, starting with :
pass in quick on $LAN inet from ....
This rule is the one visible in the GUI on the LAN tab that allows traffic coming into this interface.
-
The problem occurs during the installation phase.
To explain better: if you install the old version 2.5.2 everything works correctly without any problem.
If I install 2.6 or 2.7 the installation completes correctly, but the device is not reachable in any way.
The impression is that there is a problem either with the network adapter driver or the default driver configuration has some errors.
Unfortunately I don't have any skills with FreeBSD to verify -
Hmm, OK so the first thing I would do here is check the boot log to see if any errors are shown when the driver attaches to the NICs.
If this is a serial console that's trivial and you can copy/paste that log output here.
-
I've never done serial link installations
I'll arrange to try that way. I need to get the appropriate cable.
In the meantime I'll try to follow some instructions found in the FreeBSD manual where they suggest how to modify the driver configuration file according to certain problems. FreeBSD (14) also declares NICS card compatibility -
You can still see it on a video console it's just more complex to do so. Scrollback through the buffer directly or pipe dmesg through more.
