Hi,
We are building a VPN server with the purpose of connecting LTE-routers in a safe way to end-users. I've a question regarding the L3 Switch functionality. See the attachted image for the setup.
We are able to establish both VPN connections (L2TP/IPSec & OpenVPN) and we can ping the LTE-router from the Windows 10 device (ping 192.168.40.13). Also, the default route is working, i can ping something at the internet (e.g. google.). The Windows 10 laptop and the LTE router have the virtual switch as default gateway (the 30.250 and 40.250).
Now we want to be able to connect to something in the 192.168.20.0/24 subnet. We added a route table entry as follows (see also the image), 192.168.20.0/24 via 192.168.40.13. Still im not able to ping / reach the 192.168.20.0/24 subnet. The devices in this subnet have a default route to the LTE-Router (192.168.20.1). It looks like the Virtual L3 Switch is not routing the 192.168.20.0/24 subnet towards the 192.168.40.13 (= the LTE router).
Why is it not working? What are we missing? We have allready changed the metric of the route entry, deleted the default route.. but none is working.
Kind regards!
Layer-3 Routing issue
-
ArjanB
- Posts: 3
- Joined: Mon Jul 22, 2019 10:14 am
Layer-3 Routing issue
You do not have the required permissions to view the files attached to this post.
-
ArjanB
- Posts: 3
- Joined: Mon Jul 22, 2019 10:14 am
Re: Layer-3 Routing issue
The posted route (192.168.20.4/32 via 192.168.40.13) is an example. I allready tried a /24 route.. a default route etc.
Looks like the Virtual Router won't route traffic towards the LTE-router (192.168.40.13 via DHCP) at all.
By my knowledge; the Virtual Layer 3 switch must be able to route traffic, just like a normal router (?).
Looks like the Virtual Router won't route traffic towards the LTE-router (192.168.40.13 via DHCP) at all.
By my knowledge; the Virtual Layer 3 switch must be able to route traffic, just like a normal router (?).