Matt Ventura <mattvent...@mattventura.net> wrote: > On 01/23/2015 04:05 AM, Sven Hartge wrote: >> Matt Ventura <mattvent...@mattventura.net> wrote:
> Well, that confirms my original suspicion. The F5 VPN is throwing its > default route over the original one, and that's causing traffic to the > OpenVPN server to try to route over the F5 VPN. Obviously this doesn't > work because the traffic to the F5 VPN needs to go through the OpenVPN > link, so it becomes circular. > What you need to do is add a route, something like: route add > <external IP of OpenVPN server> gw 192.168.1.1 dev eth0 so that the > traffic to the OpenVPN server can be routed properly. This then would complete the Trinity of VPN: one route 0/1, one route 128/1 and one host route to the other VPN endpoint so that it can be reached regardless of other routes. Grüße, Sven. -- Sigmentation fault. Core dumped. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/abb116082...@mids.svenhartge.de
