LAN Interface stops working some times - pfsense 2.3.2
-
Hi,
Having some issues since upgrading to 2.3.2
I have a minecraft server running on a local machine in my network that is forwarded with a NAT rule from WAN interface so people can access it using my domain.
The thing is that when people connect from outside, every now and then the LAN interface stops working.
Some time we can play for like 2h and then it crashes, some times it creashes after playing a few minutes. Can't really see any pattern to when it happens, just that it only happens when playing minecraft connected via my WAN interface redirected to local server on LAN.I can't ping pfsense from any computer but when connected with console calble i can access stuff from WAN interface but not on LAN. After taking down LAN interface and bringing it up again every thing is fine.
After the upgrade to 2.3.2 this started to happen, and it only happens when some one is inside MineCraft connecting from outside via the NAT rule.
After not beeing able to find what was causing the problem I did a factory reset and only added the NAT rule for minecraft. This to make sure that there was nothing else I had configured or installed that was causing the problem. It still happened…Im running pfsense 2.3.2 on a Watchguard Firebox x750e.
Here is my NAT rule:
I have also tried it with only TCP for protocol and with associated filter rule and with/without nat reflection on. There is no difference, still crashes.
I have tried turning on UPnP & NAT-PMP, but that made no difference either.
By the way, I'm not running out of memory or CPU or anything like that. Every thing looks normal, no high load as far as I can see. Can't find anything useful in the logs either (although I'm not an network expert…).
If someone has an idéa of what might be the problem, it would be greatly appreciated :)
-
bump
-
Same issue here. Problem happens when a single machine on the LAN creates 1000ish new states and moves traffic at a rate of about 20mbit. A reboot resolves the issue but it almost immediately breaks again when the machine starts downloading/uploading again. Stopping the machine whose traffic causes this resolves the issue.
When the issue occurs, the LAN interface stops functioning. It does not send any traffic onto the network, nor does it see any traffic coming into it.
-
It's not your rule. Rules either work or they don't. If it used to perform well and then changed after an upgrade, you might want to try with either 2.3.3 or 2.4.0 beta and see if the problem persists. You could also change the LAN NIC and see if the problem persists.
-
Im running pfsense 2.3.2 on a Watchguard Firebox x750e.
Sounds like it could be driver or hardware related, but likely work-around-able if you can figure out why its going for a loop. Ive personally had very bad experiences on every piece of watchguard hardware ive ever had the misfortune of using, but thats mostly with their rom still on it, only twice with one that was pfsense loaded.(550e's not 750s)
i know its a stab in the dark, but if you have it enabled, try disabling any of the offloading options. I would lean towards it being directly related to the nic itself, or the driver in use.