[SOLVED] tcp connections break after 20-30 seconds on LAN static routes

[bmveee]

Hi everyone.

Huge fan of the opnsense platform and finally got around to upgrading my opnsense to 20.1.5. I actually installed it from scratch on a brand new disk (running on a physical Dell T420 box).  All went well, configured the interfaces, setup my rules, added static routes to OpenVPN tunnels (handled by another machine on my network), and this is where the fun began.

Now I was running an older release of opnsense prior to today (19.7.10) and did not have any issues.

The issue that became apparent is this. I have several OpenVPN tunnels going out to different remote hosts from my openvpn router (call it openvpn1, having IP address of 192.168.1.2).  The opnsense router has a LAN interface address of 192.168.1.1 and I have a bunch of static routes defined on opnsense to route through openvpn1 gateway.  All is well, routes are working. Great.  The issue that I came across with the new opnsense in the mix is that any TCP connection that is routed by opnsense to the openvpn1 gateway breaks after about 20-30 seconds, and I can't for the life of me understand what is causing it.  Now I know that the opnsense is somehow causing this because to test, I added a static route on my machine and bypassed opnsense - the connections didn't break.  Once I removed the static route, the connection died immediately.  Any ideas what's may be happening here?

Thanks in advance,

-Eugene.

[bmveee]

Actually - self resolved! I had to enable the option in Advanced firewall settings

Bypass firewall rules for traffic on the same interface

Duh ... must have been enabled on the old instance, so... never mind on that - for those who may get stuck with the same issue, hopefully this helps.

Cheers.

[Phil]

Hi,
Thx a lot

Best regards

[oshimapt]

sorry for digging this solved topic but i'm having this problem and the solution said here did not solve my issue.

i activated the Bypass firewall rules for traffic on the same interface but it keeps dropping the connection.

maybe i'm doing something wrong?

i'm using opnsense 22.7.7_1 on a hyper-v host