Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] VLAN Routing drops after WAN Interface reload #1912

Closed
ghost opened this issue Nov 4, 2017 · 2 comments
Closed

[Bug] VLAN Routing drops after WAN Interface reload #1912

ghost opened this issue Nov 4, 2017 · 2 comments

Comments

@ghost
Copy link

ghost commented Nov 4, 2017

Hi guys,

My setup is based on inter-VLAN-routing, while using LACP.
My OPNsense version is:
OPNsense 17.7.7_1-amd64 FreeBSD 11.0-RELEASE-p12 OpenSSL 1.0.2l 25 May 2017

Since a few days my ISP is having problems which are leading to Interface reloadings from configd.py from time to time, which then end up in inter-VLAN routing problems. I get little drop outs to my NAS in another VLAN, while streaming music for example. This error came up:
wan error

When this happens, the connection to the file gets lost and thats really annoying.
Why is my WAN default Gateway intercepting inter-VLAN-routing which is directly connected?
When the WAN Interface reloads, my NAS is not able to answer, but it is a stateful packet inspection Firewall so there should be no need to add additional rules:
nas error tcp_pa

I changed one setting here, which maybe solved the problem but i am not sure:
gateway monitoring error

I deleted every VPN setting but still this is showing up in the system logs:
configd.py: [9bfef01c-16c1-4b6f-b303-c7341b49c1ba] Reloading filter
openvpn wan reload

I checked my offloading settings, but it didn't change after enabling or disabling Hardware Filtering, so that can't be the issue. Just for your interest, all my NICs are Intel NICs:
VLAN Hardware Filtering: Enable VLAN Hardware Filtering

Best regards,
Pitch

P.s.: While writing this i again had a Disconnect from the Internet "WAN_DHCP" Down, but the apinger state didn't got flushed so the connection to my NAS stayed up. Is that normal behaviour?

@AdSchellevis
Copy link
Member

just a quick note on "Restarting OpenVPN tunnels", it's only the event, it doesn't do anything if there are no tunnels configured, details in:

command on "/usr/local/opnsense/service/configd_ctl.py -m 'dyndns reload %T' 'rfc2136 reload %T' 'ipsecdns reload' 'openvpn reload %T' 'filter reload' "

@ghost
Copy link
Author

ghost commented Nov 5, 2017

Thank you very much for clarifying, since this was a big question on my mind. So i searched for something, which wasn't there anymore. Good to know. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant