Hi, On Mon, May 03, 2021 at 12:01:04PM +0200, Jan Just Keijser wrote: > > I would expect this to do the same thing it would do for the "non proxy" > > case - install a host route to the existing default gateway so packets > > to the server (and with proxy, to the proxy) can still flow. Then, > > change the default route into the tunnel. > > > > Of course there might be bugs - so you'll end up having to test this. > > > AFAIK this does *not* work for the "non proxy" case;
What exactly is "this" here?
Bypass routes for IPv4 (if you have "redirect-gateway" or "redirect-private"
in your config) and IPv6 (automatic) have been worked for a long time...
I just wasn't sure it would take the correct "remote IP" for socks/http
proxy setups.
> just checked the
> v2.5 sources and I cannot find anything special there:
>
> init.c:do_init_route_list() calls route.c:init_route_list()
> with "remote_host" set to "link_socket_current_remote(link_socket_info)"
>
> and that does not seem to take any proxy hosts into account.
But "link_socket_current_remote" is very likely to be "whoever we are
talking to right now", aka "the proxy".
> Also, as
> far as I remember this behaviour has not changed since OpenVPN 2.0/2.1 .
>
> Bug-worthy?
If you can clarify what exactly the "this" bit is that might not be
working, of course.
gert
--
"If was one thing all people took for granted, was conviction that if you
feed honest figures into a computer, honest figures come out. Never doubted
it myself till I met a computer with a sense of humor."
Robert A. Heinlein, The Moon is a Harsh Mistress
Gert Doering - Munich, Germany g...@greenie.muc.de
signature.asc
Description: PGP signature
_______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
