browser gui misery
-
Pfsense is working great, but for some reason the upgrade caused my Freenas to get dropped from the network. Now I can't access the Freenas webgui and pings are unsuccessful. It does not appear in the DHCP listing or on the ARP table.
I hooked up a monitor to the Freenas and everything looks fine. Rebooted both Freenas and pfsense a couple times, no joy. On the Freenas console it says, "The web interface is at: 192.168.1.175", but this is a lie.
Not necessarily Freenas experts here, but any ideas why the pfsense upgrade might cause this behavior?
-
Can you ping out from FreeNAS?
Is it showing a link on the NIC?
Traffic between a client on the LAN and the FreeNAS box would go directly, it wouldn't pass through pfSense at all.
Steve
-
I tried pinging the router (192.168.1.1) and also my desktop PC (.135) from the Freenas shell, but in both cases got "Host is down"
"Is it showing a link on the NIC?". Not sure how to check that...
"... it wouldn't pass through pfSense at all". But the Freenas should show up on my pfsense DHCP Leases page.
-
"Is it showing a link on the NIC?"
A-ha, no link lights! WTF? Now I'm really mystified!
-
@lyle817 said in browser gui misery:
A-ha, no link lights!
Well, change the cable, the port and/or switch it is connected to, or the NIC used by your FreeNAS.
If there is no "link", DHCP won't work. It's like there is no cable at all. -
Makes sense, thanks! I was thinking somehow the operating system was shutting down the NIC, but I see now this is likely a hardware problem just coincidental with my pfsense upgrade. Will attend to it tonight when I get back, thanks again guys!!!
-
G Gertjan referenced this topic on
