Initial Install No LAN Access

[techmattr]

I just setup opnsense on a spare machine and connected it to an unmanaged switch with my laptop. I manually assigned an IP to my laptop 192.168.1.2 and the LAN was autodetected on the opnsense and assigned 192.168.1.1. I cannot ping the laptop from the opnsense and I cannot ping the opnsense from the laptop.

This seems as basic as it can be and I have no idea why opnsense isn't working. If I do the exact same setup with pfsense it works fine.

Any ideas?

If I set my laptop to DHCP I get a 192.168.1.100 address but I still cannot ping the opnsense and opnsenese cannot ping the laptop. Also cannot reach the web GUI in case ICMP is blocked for some reason.

[Patrick M. Hausen]

OPNsense and pfSense assign the LAN and the WAN port in reverse order. You probably plugged your PC into WAN.
Ironically it was the pfSense project that switched the order after OPNsense was forked.

If you have some embedded device with "LAN", "WAN", ... printed on the ports keep in mind this is just ... print/paint. It does not necessarily bear any resemblance to which port does what.

[techmattr]

Its just a server with a intel pro 1000 pt quad port card. I used the autoconfigure to make sure it picked up the right port. I also tried re-configuring the LAN on the onboard intel 210 port. Same results. It will pick up an IP but they cannot ping each other and cannot reach the GUI.

Edit: I just installed pfsense again to make sure I wasn't crazy. And it does indeed work right out of the box with no issue. Reinstalled opnsense again with the same issue. Can't ping, no GUI access. I'm trying to migrate away from pfsense but this is not a great first impression. I've given the install the most basic easy to setup environment possible and it doesn't work out of the box....

[Patrick M. Hausen]

If you set the laptop to DHCP?

[techmattr]

If you set the laptop to DHCP?

Yup. That is the most confusing part to me. If I set laptop to DHCP it gets a 192.168.1.100 address assigned. Still cannot ping each other or reach GUI though.

[techmattr]

FYI. This is an issue with the Intel Pro/1000 PT Quad Port PCIe NIC. Possibly when another PCIe NIC is installed but seems like just more in gernal. So, I have two NICs in my lab machine. A Intel Pro/1000 PT Quad Port and a Supermicro AOC-STGN-i1S.

In this configuration OpnSense successfully communicated via DHCP but HTTP/HTTPS and ICMP failed. I haven't dug into why. If I remove the Supermicro AOC-STGN-i1S the Intel Pro/1000 PT Quad Port is still buggy and does not behave properly but I did manage to get about 80% successful ping replies and an unreliable connection to the Web GUI.

I swapped out the Intel Pro/1000 PT Quad Port for a Intel Pro/1000 PT Dual Port and everything works perfectly fine. I also tried a Intel Pro/1000 PT Single Port and a Intel Gigabit CT Desktop Adapter which both worked perfectly fine.

pfSense worked perfectly fine no matter what NICs were installed. OpnSense seems to have an issue with the Intel Pro/1000 PT Quad Port and possibly the Supermicro AOC-STGN-i1S. I haven't had time to put the Supermicro AOC-STGN-i1S back in for more testing.

I have three Intel Pro/1000 PT Quad Port cards though. One from HP, one from IBM and one from Intel. All three did not function correctly in OpnSense but did function perfectly fine everywhere else. Including just a vanilla install of FreeBSD 13.2. I had no problems configuring the Intel Pro/1000 PT Quad Port there. This seems to just be an issue with OpnSense.

[meyergru]

On the surface of it, when you google that specific card, you will see that there have been many different chipsets in them, like 82576, 82575 and 82571, some of which do reportedly not work.

There are reported problems of OEM-models, exactly the HP and IBM ones to disable MSI and MSX in the firmware. The older chips do not work very well on newer mainboards because of old PCIe 1.x versions and/or power saving.

Considering that DHCP works on your model, it is well possible that you can use tuneables to make them work and if they do on pfSense, I guess that some tuneables are set per default.

You could try to disable MSI-X, lowering the kernels buffers and/or disable ASPM.

For MSI-X, there is also an iflib setting.

[techmattr]

Thanks for the info. When I searched intel pro 1000 pt and opnsense all I found were posts saying that it works fine and the FreeBSD compatibility list that says it works fine.