I have an openvpn server network (10.183.240.0/27) with server (.1 ) and clients (.2 - .5) with subnets (10.183.240.32/29 - .56/29). Subnerts are not communicating with each other.
Problem started when i changed LAN ip and openvpn connection (cert & ip updated), i’m not able to connect clients in subnet from server network. Yep, everything worked well before…
Inside LANs, clients are accessible and are working normally (new IP’s obtained from rut200’s dhcp).
I can ping rut200 from openvpn network, as well as i can ping server from router and from subnets, but ping does not work from server to clients.
I installed tcpdump and i can see (lan interface) a ping request to client but not a response from client.
I’ve tried to add static routes, played with fw rules but nothing helped. I think i have read whole wiki as well as forum, checked almost all i can imagine, but no.
Server network gateway is 10.183.240.1, which is also binded to public ip.
Gateways for client subnets are configured to be rut200’s ip in SUBNET, for example 10.183.240.56 is gw for devices in 10.183.240.56/29. From server network, 10.183.240.5 is assigned to this same router. Both of those IPs replies to ping and rut200 admin is available in both of those IPs.
so… you have RUT200… two LANs at the device. Because you change WAN to LAN. I gues… I draw will help…
But… you have three networks… one /27 and two /29
Sure… you can use secondary ip address at the same lan interface… no worries.
but… you cannot have dhcp server without VLAN in this interface… Do you have L2 Switch?
To make this work…
you need to have the first host ip at the network in the lan of your device (rut200)
sample.
server farm 10.183.240.1/27 (interface??)
lan(1) 10.183.240.33/29
lan(2) 10.183.240.57/29
all the connected ip devices, will have the lan ip address of that network in RUT200 as their gateway?
This will happen with the packet
x.x.x.2 ping x.x.x.60
x.x.x.2 wil send to x.x.x.1; because don’t find x.x.x.60
x.x.x.1 will redirect your packet to lan interface x.x.x.57
x.x.x.60 will receive the packet… because it don’t know where it is coming from… it will back to x.x.x.57