Home / user-940931

T0maas's questions

Martin Hope
T0maas
Asked: 2022-02-24 05:10:30 +0800 CST
  • 1

I've setup my openvpn server, but I have this problem:

Clients connects in this order:

  1. client_A connects succesfully to server using it's own key.
  2. client_B connects to server using client_A's key and gets same ip as client_A.

When I try to ping client_A packets goes to client_B instead of client_A.

I don't have duplicate-cn in my server config.

How can I prevent this behavior? I want to kick client_B immediately and keep only client_A.

openvpn vpn-client
Martin Hope
T0maas
Asked: 2021-11-23 02:50:42 +0800 CST
  • 0

I have two computers connected to same VPN (hamachi) network. There are in different places. Lets say I have this addresses:

Machine A: (rpi zero - using wifi)

wlan0:
    inet 192.168.2.160  netmask 255.255.255.0

ham0:
    inet 25.61.150.71  netmask 255.0.0.0

Machine B (laptop - using wifi):

wlan0:
    inet 192.168.0.103  netmask 255.255.255.0

ham0:
    inet 25.72.151.72  netmask 255.0.0.0

Each machine can ping each other. But what must I do if I want to access some other machine on Machine A network from Machine B?

For example on Machine B:

ping 192.168.2.123

192.168.2.123 is located on Machine A LAN.

I've tried this:

Machine A (as root):

LAN=wlan0
HAM=ham0

echo 1 > /proc/sys/net/ipv4/ip_forward
iptables -t nat -A POSTROUTING -o $LAN -j MASQUERADE  
iptables -A FORWARD -i $LAN -o $HAM -m state --state RELATED,ESTABLISHED -j ACCEPT
iptables -A FORWARD -i $HAM -o $LAN -j ACCEPT

Machine B:

sudo ip route add 192.168.2.0/24 via 25.61.150.71

But without success.

I cant ping 192.168.2.123 from machine B.

How can I do this properly?

Edit: Commands written above seems to be correct. I've tested similar setup with freelan vpn instead of hamachi and it works.

vpn routing local-area-network