New installation (with reset), LAN does not work

darkcorner

This is the scenario.

Same PC-Pfsense, same NIC, same version of pfSense (2.6.0).
NICs assigned automatically (with "a"). The cables are colored and there is no way to confuse them.
Even the switches are the same, without VLAN configuration or anything else.
The Win10 PC is the same one used for over a year with this pfSense.
There is a new Win 11 PC

These are the steps:
A) Reset pfSense to factory settings (from console)
B) Assigned NIC (with "a")
C) WAN address (192.168.1.2) assigned via DHCP. From console, ping on google.com works
D) LAN address assigned 192.168.18.1/24, Static.
E) DHCP LAN 192.168.18.101-151

Here are the results:

The LEDs on the NICs and switches flash at 1000Mb.
PC Win10 and PC Win11 do not receive the IP from DHCP
If with static IP 192.168.18.51 and 55, both are able to Ping on the other PC, but none on 192.168.18.1
Obviously it is not possible to access the WebGui.

I tried to reset pfSense several times; to turn off the switches to cancel what they have in memory; to reset the network settings on the Win11 PC (I don't change the Win10 PC because it has always worked).
In the past this PC I have configured for pfSense at least 10 times for various tests and it has always worked. Now I go by heart. In any case, after the reset of pfSense I only did the assignment of NICs and IP addresses, nothing else.

I can't figure out what's wrong.

viragomann

@darkcorner said in New installation (with reset), LAN does not work:

If with static IP 192.168.18.51 and 55, both are able to Ping on the other PC, but none on 192.168.18.1

Why static when running a DHCP server on LAN?
Are the network masks set correctly?

Remove the switch and plug in a PC directly into pfSense LAN port. Set the PC NIC for DHCP configuration and try if you get access.

darkcorner

@viragomann
Point 2) PC Win10 and PC Win11 do not receive the IP from DHCP

Remove the switch and plug in a PC directly into pfSense LAN port. Set the PC NIC for DHCP configuration and try if you get access.
No Address

viragomann

@darkcorner
That's what I expect, since you mentioned they have static settings.
Therefor I requested you to change it to DHCP.

darkcorner

@viragomann
The pfSense LAN NIC has static IP and DHCP.
If I enable DHCP on the two PCs, it does not receive an IP, I must necessarily enable the static IP, but in doing so I see the second PC, but neither of them sees the pfSense LAN NIC.

darkcorner

@viragomann
The problem appears to be on re0, which is put down on boot.
I don't understand why, as it has been working with the latest configuration for months.
Now I've done a fresh install, not just a factory reset. I then tried to use the other two ports. On these DHCP works, but re0 obviously has problems.
How do I set it up from the console?

viragomann

@darkcorner
Are the other NICs Realtek as well?
I noticed as from other threads that there are issues with the Realtek driver and that there is a new driver available as a patch for pfSense, but didn't expect that it behaves like that.

darkcorner

@viragomann
They are all Realtek, damn them and their drivers.
However I solved it by putting two NICs on another PC where at least there is an Intel NIC that I use for the LAN.
How much time wasted for a PC that until a month ago was working without problems and in the last month has simply been turned off.
Thanks a lot for the support.