Hello,
Greenbird a écrit :
> The OpenVPN server is seeing the packets from the client but it's
> sending ARP whois packets for the clients IP address. Only problem being
> that it's sending them on the internal subnet NIC rather than the tunnel
> interface so it's not getting any replies.
Usually ARP requests on the wrong interface indicates a routing problem.
You can check the routing decision for a destination address with the
command "ip route get <address>".
> OpenVPN server
> --------------
[...]
> Public subnet (Public IP redacted):
> eth1 Link encap:Ethernet HWaddr 00:22:15:7F:76:C9
> inet addr:1.2.3.4 Bcast:1.2.3.255 Mask:255.255.255.0
Note : When you make up an IPv4 address, you could use the address range
192.0.2.0/24 which is reserved for the purpose of examples and
documentation. 1.2.3.4 is allocated, and probably not to you.
> inet6 addr: 1::2:3:4:5/64 Scope:Link
Note : Making up a link local IPv6 address is pointless, it is derived
from the MAC address so it can be recalculated easily.
> Tunnel interface:
> tun0 Link encap:UNSPEC HWaddr
> inet addr:10.91.92.1 P-t-P:10.91.92.2 Mask:255.255.255.255
[...]
> netstat -r (Public IP redacted):
Note : Please use -n so addresses are not translated into names, which
is confusing.
> Destination Gateway Genmask Flags MSS Window irtt Iface
[...]
> 10.91.92.0 elephant.nowher 255.255.255.0 UG 0 0 0 eth0
> 10.91.92.0 10.91.92.2 255.255.255.0 UG 0 0 0 tun0
These are two conflicting routes. One must be wrong.
> Client System
> -------------
[...]
> Tunnel interface:
> tun0 Link encap:UNSPEC HWaddr
> inet addr:10.91.92.10 P-t-P:10.91.92.9 Mask:255.255.255.255
The addresses don't match the addresses of the tunnel interface on the
server.