Hanging/Crashing every few hours
-
LAN stays up, WAN goes down, and pinging / communicating with pfsense is lost
-
LAN stays up, WAN goes down, and pinging / communicating with pfsense is lost
Can you access the console next time the WAN goes down? I am pretty sure you are getting watchdog timeouts on your WAN ethernet adapter. What type of Realtek adapter are you using? How much traffic are you pushing through your WAN when the interface fails?
-
When the WAN goes down the box is hanging, accessing the webconfigurater or ssh-ing to the console does not respond.
The system just crashed in between auto-reboots, and looking at system.log the last entery was midnight last nihgt, which does not seem correct.
As a another clue, the system is up right now and email/web sites responding, but pings result in immediate time outs
-
will get the NIC details shortly
-
When the WAN goes down the box is hanging, accessing the webconfigurater or ssh-ing to the console does not respond.
The system just crashed in between auto-reboots, and looking at system.log the last entery was midnight last nihgt, which does not seem correct.
As a another clue, the system is up right now and email/web sites responding, but pings result in immediate time outs
This is probably due to a bad Realtek driver. Can you turn off the auto reboot? Otherwise, there is no point debugging this
-
I am way from the office ( its a small small company ) for the next week, which is why the auto-reboot is on, the webserver and email server need to be keep up ), when I get back I can turn it off, and reboot when need be
-
I am way from the office ( its a small small company ) for the next week, which is why the auto-reboot is on, the webserver and email server need to be keep up ), when I get back I can turn it off, and reboot when need be
no worries. i've been in your position before - have a nice evening
-
Ok I am back in the office and found the following message reported twice in the console when a crash happened :
re0: discard frame w/o leading ethernet header ( len 4294967292 pkt len 4294967292 )
does that help?
-
I'm going to follow this post intensely, as I have a very similar problem.
-
Ok I am back in the office and found the following message reported twice in the console when a crash happened :
re0: discard frame w/o leading ethernet header ( len 4294967292 pkt len 4294967292 )
does that help?
Definitely it's not good, but not always causes crash or hang.
DO you have polling enabled?
Does reverting back to 2.1 solves problem? -
I do not have device polling enabled, is it worth turning on?
-
where can I find older versions to try a reversion?
-
a new piece of the puzzle -> I was comparing my old config file to the current one line by line and noticed the old config had IPv6 config type for the WAN set to DHCP6 and the LAN set to track the WAN IPv6 Interface. I updated the new config to match and now when I see
re0 : discard frame w/o leading ethernet header (…....
re2 : watchdog timeout -
I do not have device polling enabled, is it worth turning on?
No, leave it disabled, it would not help.
http://mirror.transip.net/pfsense/downloads/ look for old version.
See if it helps -
Realtek driver claiming a frame was 4GiB in size? Sounds like a driver issue or memory corruption.
-
Try do disable driver options (see picture). This is more related to poorly supported faulty driver then hardware issue, but it could be both.
-
Following the suggestion on this thread : https://forum.pfsense.org/index.php?topic=101587.msg617211#msg617211 I set WAN to flowcontrol, master and LAN to master. This eliminated the watchdog timeout, and reduced the frequency of the discard frame from every 3-4 hours to roughly 11 - 12 hours.
I will try disabling driver options and see what happens
