HI, On Mon, May 03, 2021 at 12:38:21PM +0200, Jan Just Keijser wrote: > >> 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". > > > you're absolutely right,
Sometimes our code might be old, but still working :-)
> and I now remember the caveat that applies
> mostly when using "socks-proxy", not "http-proxy":
>
> what I'd normally do when using "socks-proxy" is set up an SSH tunnel to
> a remote host
> ssh -D 1080 <remote-host>
> and then tunnel the VPN traffic over that. The big caveat here is that
> when doing this, the "socks-proxy" IP address is actually
> localhost/127.0.0.1 : so OpenVPN might add an extra route to localhost ,
> but as soon as the default GW is redirected, the route to the original
> SSH server is gone.
Mmmh. Indeed, that one is a really tricky one. Even if we were to
add some sort of policy routing ("openvpn goes to main table, everything
else goes to 'into-tun' route table") it would still break the SSH session.
For IPv4, a host route
route $ssh_server_ip 255.255.255.255 net_gateway
should work, but OpenVPN won't be able to know the $ssh_server_ip address
by "magic lookup".
For IPv6, we have an open trac ticket to add "... net_gateway" functionality,
but someone was lazy in implementing it.
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
