On 12/28/20 11:47 AM, Colin Ryan wrote:
Is the PI the default gateway device on the 178 network?
If not then your remote workstation connects, get's given a 10.7
address and is presented routes to the 178 network.
However upon leaving the eth0 inteface of your Pi out onto the LAN the
LAN
Good morning everybody,
I have no idea why routing doesn't work - and I thing I did everything I
have to do to make it work ...
When establishing a connection I can only ping the tun-devices
ip-adress, and the eht0-devices ip-adress, but I can't ping/traceroute
any other device on that
max.mus...@kaffeeschluerfer.com writes:
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
Ok, I added that to the server.
you will also need an iroute entry for your
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
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
