Netgate 6100 Instability

bseballjon9

Hi everyone,
I have a weird issue with my Netgate 6100 MAX where it will stop responding randomly. I utilize the IX1 interface with a Netgate branded SFP+ 10g hooked up to my core switch. The 6100 wont respond to ping, no management, and no traffic allowed (internet comes to a halt. No ping from LAN, no dns, etc). Anyone know if this is a hardware issue or what steps I can take next? If I try a "reboot" using the console (yes the console still works) it just completely locks up. It never "reboots" until I pull the power cable and then everything is fine for x days.

I removed all packages except "patches". I've had issues with this Netgate 6100 for quite some time i'm honestly thinking I have a dud. I've bought brand new SFP+ for my switch, new cables, i've tried to use an ethernet instead of fiber, no difference.

I can replicate the problem if I save too many changes to config, the web UI will lock up until I use SSH and restart php. That will work for about a day until the whole thing locks up again.

WN1X

@bseballjon9 Can you see what is happening via the console cable?

stephenw10

Yes, what's happening or not happening at the console when that happens?

Does it still have a WAN IP? Can you ping out to some external IP?

Try dropping to the command prompt (menu option 8) and running ifconfig -a

Is the LAN (ix1) still shown as UP and active.

bseballjon9

@stephenw10 Sorry for the delay i’ve been a little busy at work lately. I believe it’s related to this somehow https://redmine.pfsense.org/issues/12853#:~:text=We%20temporally%20resolved%20the%20issue%20putting%20%22Disable%22%20in,%2F%20NAT%20%2F%20Port%20Forward%20%2F%20Edit%22%20sections.

As soon as I enable Pure NAT with reflection I start to see errors in system log like can’t forward to interface igc0 (WAN). Then the whole dang thing locks up. Console works but none of my interfaces do.

I can confirm with it off it hasn’t “froze” on me once. I enabled it because it seems UPnP won’t work unless pure NAT is enabled.

stephenw10

Hmm, UPnP should not require NAT reflection of any sort. What exactly fails without it enabled?

But the same thing would apply. To have any idea what's happening we need to get to the failed state then test what's actually failed. So can you ping out still can you ping internal devices from the console etc.

If it fails after some time with NAT reflection enabled it could be some sort of memory leak as jimp mentioned on the bug. Check the memory usage in Status > Monitoring.