LAN interface drops after every reboot
-
Hey everyone, been bashing my head at this for a while.
This happens even with a very basic installation:- 2 physical Realtek ports - One configured as WAN and another one as LAN.
- Nothing plugged into WAN
- Laptop plugged into LAN for config
Initial setup of pfsense with defaults -> everything works ok
After any reboot:
- Pfsense console states both interfaces, LAN has ip (i.e. 192.168.1.1/24) (monitor+keyboard plugged into box)
- Don't get a DHCP IP anymore on my laptop
- If the IP, mask, gateway and DNS are set up manually on the laptop, still cannot ping pfsense
- Cannot ping laptop host from pfsense console
- If I manually re-assign the interfaces (option 1) from the console, LAN connection is restored
- Cannot find any errors in the logs
If WAN is connected, all of the above still applies, plus:
- Pfsense console states both WAN and LAN interfaces have the correct IPs
- Can ping WAN services (i.e. google.com) from pfsense console
Tried factory resetting, reinstalling a fresh instance with the memstick installer to no avail.
Any clue as to what might be happening? I heard some people having similar issues with 2.6.0 but found no solution.
-
@remiul said in LAN interface drops after every reboot:
2 physical Realtek ports
Likely the RealTek drivers and their relatively poor support in FreeBSD. It's not a specific-to-pfSense 2.6 issue, though.
-
@rcoleman-netgate thanks! Was just reading about this on another thread. Different issue though. Will try to install the Realtek drivers and see if that fixes it.
-
Your WAN is a public IP there? What you describe could also be a subnet conflict.
-
@stephenw10 WAN has a public IP indeed. Could you expand on that? Not the biggest expert on networking. Anyways, and pardon me if this is a stupid question, wouldn't a subnetting issue be present before the reboot as well? Everything works perfectly fine before the first reboot. After a reboot it will only work again if I factory reset or if I re-assign the interfaces from scratch.
It also fails without the WAN port configured too, just LAN.
Is there also a way to check this in a specific log? -
If your WAN was configured as DHCP and connected behind some other router using the same subnet then it's possible to get a subnet conflict between WAN and LAN in pfSense. In that situation it can depend which interface came up last or timings at boot as to which route ends up being valid. So you can often find the LAN doesn't respond but only after the WAN pulls an IP for example.
But no you wouldn't see that without the WAN connected or with a public IP there.Check the main system log in /var/log/system.log for errors from the re driver if there are any.
Steve
-
@rcoleman-netgate ding ding ding!!! Followed these instructions
And evrything works completely fine now!!
Aparently 2.6.0 uses FreeBSD re(4) drivers, which screw up with realtek even more.
Thanks for the help! -
@remiul Well, that's a FreeBSD issue, but yes. There's good reason we recommend against using RealTek chipsets
-
@rcoleman-netgate gotcha. Gonna hang out with this machine for now but will chose one with intel NICs whenever I need to replace it. Thanks a lot!
