Comments
-
192.168.0.0/24 which is the subnet of location A. OK, I got it. Thanks to all for the discussion, especially to PeterUK for his idea to use 0.0.0.0/0. There is just one thing. The establishment of the connection looks like this in the LANCOM log: 2023-11-28 00:54:27 LOCAL0 Fehler last message repeated 2 times 2023-11-28…
-
I got it running finally! On the LANCOM side I configured 0.0.0.0/0 as remote network and the routes for the three networks to the tunnel. On the Zyxel side I just configured 0.0.0.0/0 as local policy. I did not configure any policy routes. There are just two static routes for the two special networks to the third router.…
-
Yes, I have remote access to the LANCOM and I can configure there the routing properly. The tunnel is configured for 0.0.0.0/0. All traffic but that for the three special subnets goes to the Internet. So, yes there it is possible to configure the tunnel as the next hop. On LANCOM side the VPN and the effective routing…
-
The configuration on the LANCOM side is easy. But I'm not sure how to configure in the Zyxel that the normal traffic goes to the Internet and not to the tunnel. Yesterday I configured for that a static route for 0.0.0.0/0 to wan1 and lost by that all VPN connections and hat to drive to location B to remove that route :-(…
-
So you mean to configure the VPN connection for 0.0.0.0/0 and to configure the routing of the three subnets by routing rules? Will try that.
-
Thanks for replying. This probably means that all traffic will be routed through the tunnel? This is not desired. The traffic to other networks should go to the internet directly.