Topics

Good morning,

I am hoping someone can please help me.

I am running a couple of dedicated game servers locally at home.  I have a VPN running which all of my traffic is routed through, however I want to have my game servers connected directly via my ISPs static WAN address instead of going out via the VPN interface, due to its highly dynamic IP nature.  I have it partially complete, with port forward NAT and firewall rules set for traffic inbound via my WAN interface to take priority and be passed to my internal server IP and port.  This works perfectly and I can directly connect to my game server using the external ISP static WAN IP and port, as can my friends, so this is all working as expected.

However, for both games, they do not appear in the game server lists used within the game search systems.  When I set the first up I assumed a bug, however the second also does the same.  In further checking, it appears that both games report their external IPs as being my VPN interface IP.  I realised that this is likely as, although my inbound traffic is coming via my ISP WAN interface, I obviously do not have anything setup for the outbound and therefore I assume their outbound traffic goes back out via my VPN interface and therefore they detect the IP for that as the one to think they are operating under.

I have therefore set NAT rules for the outbound so that traffic from my game server IPs and associated ports are NAT to my ISP WAN interface, with accompanying firewall rules on the LAN for traffic to be able to pass from the LAN to the ISP WAN interface.  These are set before the rules that push all my LAN traffic via the VPN interface, so they should take precedence.  However, my game servers continue to pick up the VPN interface IP as the one to use and I think I must have done something wrong.  Am I thinking along the right lines or do I have this all wrong please?

Good morning,

I've been experiencing an odd issue that I have been trying to resolve and initially thought was due to anything from a fault in OPNsense itself after an upgrade, to the Wireguard package I was using, to my hardware. But now I think it is something else entirely.

I have a basic small home server running Arch Linux which contains mostly media along with some other data, and a bunch of services mostly running in Docker. It's taken over from an old HP Microserver I had, and was originally built since around October 2018. From around that time I have been experiencing severe instability issues with OPNsense in that the whole system would lock up and the webgui and SSH would be unresponsive, I'd lose all networking, and have to reboot to get the system back up. This happens at least once a day, often twice or even more. As I said, I thought there must be a fault and I've been trying to rectify it without success. However, one of the OS drives in my server died end of April and it went offline for around 2-3 weeks. During this time I have had 0 failures on the OPNsense box. I got round to rebuilding the server the other day, with new drives and a slightly modified and fresh build, and immediately the issues have returned, with OPNsense failing twice a day over the last few days.

My main desktop uses Arch as well and hasn't triggered this response from OPNsense. I don't know if this is a hardware or software issue caused by my server or why it would even cause this. Having left it unplugged for a while, the failures stopped occuring. Does anyone have any idea as to why my server might be causing this, spanning two entirely separate installs of both OPNsense and Arch? Any advice would be appreciated. I don't even know what I'd look at log-wise to identify the cause.

I've been experiencing random kernel panics for a while that require a hard reboot of the system. I thought it was due to the update fault in 19.1 which has now been resolved. Then I discovered my SSD was dying and I thought it may be just related to that.

However, the 19.1 issue has been fixed and I am now running 19.1.4, and I have also replaced my SSD. After much testing, I have found that the system seems to panic and die after I have remotely connected via Wireguard from my phone to OPNsense and then disconnected. I do.not see the same issue if I switch to OpenVPN.

Checking online, it seems others have reported the same fault and that it is an error in the underlying 11.2 FreeBSD Wireguard implementation. Is this correct and the likely cause of my issues? If so I will have to switch back to OpenVPN for now. Wireguard has been superb in terms of connectivity, reduced battery consumption and ease of use, but I can't have it killing my system like this. Any confirmation or advice would be appreciated.