Bypass VPN using Port
-
Hi,
I have a VPN setup so all traffic from a specific Aliases IP goes through that VPN.
However, there is one segment of traffic I do NOT want going via the VPN (relates to Plex). The is traffic from the Aliases IP on Port 32400.
Now I thought this could be achieve with another LAN rule above the VPN rule set which simply contains the port (in this case Aliases Port). To show you what I mean here is my setup:
But, this doesn't appear to work. Could someone help me understand if this is possible and also how it can be done?
Many Thanks
-
@lockie
Presumably you should leave the source port at "any", since they are almost dynamic. -
@viragomann I've changed it to the below but it doesn't appear to make a difference in terms of working.
-
@lockie said in Bypass VPN using Port:
The is traffic from the Aliases IP on Port 32400.
Is this the only one port within the Plex alias?
Is it the destination or source port? -
@viragomann No, the ports in that alias are:
-
@viragomann I have also tried a single port like so with the same result:
-
@lockie
I'm in doubt that these all ports are meant to be directed out to the WAN gateway. You might need some of theme for internal communications relating to Plex. So you must not state a gateway in the rule.Since you do policy routing for the VPN, I assume, WAN is still your default gateway anyway. So there is no need to state a gateway in this rule. Just set the rule above the VPN policy routing rule.
-
@viragomann do you mean like this?
-
@lockie
Exactly. -
@viragomann K, because that doesn't appear to work.
-
@lockie
Does it work in any case, apart from policy routing? -
@viragomann I don't know what you mean?
My initial question was how can I route traffic from a single IP and Port to WAN instead of VPN. I don't know what works because I've not got it working.
What I have working is routing traffic based on an IP to VPN.
-
@viragomann as an additional note I can see that when testing Plex via its interface. It's still using a Public IP of the VPN and not of the WAN. So I assume the traffic is not getting forwarded correctly to the WAN instead of the VPN based on the port.
-
@lockie
So I suspect, the you have the default route pointing to the VPN gateway. This might not be that what you want indeed, since you set up a policy routing rule for the VPN.To investigate, please post the IPv4 routing table.
-
-
@lockie
Diagnostics > Routes -
@viragomann Sorry there's lots of private info in there. Is there something you're looking for in particular? I do want to share, I just don't want all my IP's on here :)
-
@lockie said in Bypass VPN using Port:
Sorry there's lots of private info in there.
Private infos? Private IPs?
There should be routes at all.
There is no need to hide private IPs, but public ones possibly.Particularly I'd like to check the route pointing to the VPN gateway.
-
What does this plex port do, what is the destination?
-
