Assuming we have rules on the router to allow inter VLAN communications.
Currently, when IVPN is running, it is not possible to access to devices on other VLANs. This happens regardless of whether the Firewall is on or off.
I think this is just a problem caused by routing rules making it so that every IP in RFC 1918, 3927, 4291, 4193 that is not already on an existing interface to be routed through the VPN Tunnel.
Describe the solution you'd like
Provide or make it default so that IP addresses in RFC 1918, 3927, 4291, 4193 that are not already on an existing interface is routed through the physical interface instead.
Obviously, this should not affect emulated VLANs created by virtualization software.
Describe alternatives you've considered
Using upstream Wireguard client - I'd still prefer using IVPN's client so it would be really nice to see this implemented.
Feature request
Description
Assuming we have rules on the router to allow inter VLAN communications.
Currently, when IVPN is running, it is not possible to access to devices on other VLANs. This happens regardless of whether the Firewall is on or off.
I think this is just a problem caused by routing rules making it so that every IP in RFC 1918, 3927, 4291, 4193 that is not already on an existing interface to be routed through the VPN Tunnel.
Describe the solution you'd like
Provide or make it default so that IP addresses in RFC 1918, 3927, 4291, 4193 that are not already on an existing interface is routed through the physical interface instead.
Obviously, this should not affect emulated VLANs created by virtualization software.
Describe alternatives you've considered
Using upstream Wireguard client - I'd still prefer using IVPN's client so it would be really nice to see this implemented.