LAN-to-LAN VPN (Using L3 IP Routing) problem
Posted: Sat Dec 16, 2017 7:16 am
Dear All,
I have setup LAN-to-LAN VPN for the network 172.16.100.0/24 and 172.18.100.0/24. Everything as stated in the manual https://www.softether.org/4-docs/1-manu ... P_Routing)
I set static routes on both the main network(Plasa) and the remote networks(Hexa). I have setup Virtual interface for Hexa 172.18.100.251 and Plasa 172.16.100.251 . Static Routes 172.16.100.0 outgoing interface 172.16.100.253 and 172.18.100.0 outgoing interface 172.18.100.251.The layer 3 switch is up and functional connected between the main network virtual hub, and the virtual hub that's connected to by the remote LANs. The remote LANs have cascade connection to the virtual hub on the main server, exactly as the guide instructs.
Each hub shows it's connections to the other LANs and they each are loading the IP tables properly, Please see the snapshot
Plasa Server (172.16.100.35) i have added following routes
route add 172.16.100.0 mask 255.255.255.0 172.16.100.35 -p
route add 172.16.100.0 mask 255.255.255.0 172.16.100.251 metric 10
Hexa Bridge (172.18.100.178) i have added following routes
route add 172.18.100.0 mask 255.255.255.0 172.18.100.178 -p
route add 172.18.100.0 mask 255.255.255.0 172.18.100.251 metric 10
Observation :
I can ping both interface ip (172.16.100.251 & 172.18.100.251) and can ping both server (172.16.100.35 & 172.16.100.178).
I can't ping any of the ip in the subnet (172.16.100.0/24 & 172.16.18.0/24 ) except interface and server ip
I hope Please Any one help me to fix the problem ?
I have setup LAN-to-LAN VPN for the network 172.16.100.0/24 and 172.18.100.0/24. Everything as stated in the manual https://www.softether.org/4-docs/1-manu ... P_Routing)
I set static routes on both the main network(Plasa) and the remote networks(Hexa). I have setup Virtual interface for Hexa 172.18.100.251 and Plasa 172.16.100.251 . Static Routes 172.16.100.0 outgoing interface 172.16.100.253 and 172.18.100.0 outgoing interface 172.18.100.251.The layer 3 switch is up and functional connected between the main network virtual hub, and the virtual hub that's connected to by the remote LANs. The remote LANs have cascade connection to the virtual hub on the main server, exactly as the guide instructs.
Each hub shows it's connections to the other LANs and they each are loading the IP tables properly, Please see the snapshot
Plasa Server (172.16.100.35) i have added following routes
route add 172.16.100.0 mask 255.255.255.0 172.16.100.35 -p
route add 172.16.100.0 mask 255.255.255.0 172.16.100.251 metric 10
Hexa Bridge (172.18.100.178) i have added following routes
route add 172.18.100.0 mask 255.255.255.0 172.18.100.178 -p
route add 172.18.100.0 mask 255.255.255.0 172.18.100.251 metric 10
Observation :
I can ping both interface ip (172.16.100.251 & 172.18.100.251) and can ping both server (172.16.100.35 & 172.16.100.178).
I can't ping any of the ip in the subnet (172.16.100.0/24 & 172.16.18.0/24 ) except interface and server ip
I hope Please Any one help me to fix the problem ?