I have a simple Linux OpenVPN client with the following interfaces:
eth01.2.3.4
tun010.0.0.5
The server side of the tunnel is 10.0.0.1 ...
>From the client, I can ping the server:
% ping -c 3 10.0.0.1
PING 10.0.0.1 (10.0.0.1) 56(84) bytes of data.
64 bytes from 10.0.0.1: icmp_seq=0 ttl=
If I'm understanding what you're trying to do, it falls into that lovely
category of either trivial or impossible. If 1.2.3.4 is the un-nat'd IP
that the client is connecting from, then, as I understand it, it's nearly
impossible because if you route packets to the client IP over the tunnel,
then
Hi Jordan,
If you want to reach the server from IP 1.2.3.4 the server will need to
now where toroute this IP ;-)
So in a simple config, the server would only need:
route 1.2.3.4
(if its only host 1.2.3.4 this will be sufficient; for a network you
will need "route ").
BUT, since you have a mu
