TTL Expired in transit pinging from bridge to host
Posted: Tue Nov 26, 2013 3:24 pm
Hello all,
First of all, i would like to thank you for such an amazing software. I would appreciate any help you give me as i am still trying to get acquianted with networking.
My issue is that i can ping from the server LAN to all devices on a bridge network but not the opposite. I get TTL expired in transit while pinging to a host network which has a server VPN software on it .
The Setup:
Server VPN Host network: 192.168.10.0 / 24 - VPN server software installed here
Bridge network (Remote branch location): 192.168.1.0/24 - VPN bridge software installed here
On the server, i created two local virtual hubs. One hub is named 'serverhub' which is locally bridged to my network adapter on the host network. The other hub is named 'branchhub' where i allow a cascading connection from remote location to this hub on my host network
Once connectivity is established, i use one L3 switch with the following settings. on that router
Virtual Interface - 192.168.10.253 with subnet 255.255.255.0 and attached to virtual interface 'serverhub'.
Virtual interface - 192.168.1.253 with subnet 255.255.255.0 and attached to virtual network 'branchhub'
I havent setup any routing tables.
One last setting i did on my bridge network router (192.168.1.1) is that i added a static route that says 192.168.10.0 with subnet 255.255.255.0 and gateway 192.168.1.253
so what happens from server side is that i can ping to any device on the 192.168.1.0 network. from the bridge network, i can ping only 192.168.1.253, which is the remote l3 switch virtual interface. I cannot ping 192.168.10.253 or any devices on the 192.168.10.0 network.
Please help me sort this issue so i can establish two way communication between the networks successfully.
Any help would be appreciated. Thanks.
First of all, i would like to thank you for such an amazing software. I would appreciate any help you give me as i am still trying to get acquianted with networking.
My issue is that i can ping from the server LAN to all devices on a bridge network but not the opposite. I get TTL expired in transit while pinging to a host network which has a server VPN software on it .
The Setup:
Server VPN Host network: 192.168.10.0 / 24 - VPN server software installed here
Bridge network (Remote branch location): 192.168.1.0/24 - VPN bridge software installed here
On the server, i created two local virtual hubs. One hub is named 'serverhub' which is locally bridged to my network adapter on the host network. The other hub is named 'branchhub' where i allow a cascading connection from remote location to this hub on my host network
Once connectivity is established, i use one L3 switch with the following settings. on that router
Virtual Interface - 192.168.10.253 with subnet 255.255.255.0 and attached to virtual interface 'serverhub'.
Virtual interface - 192.168.1.253 with subnet 255.255.255.0 and attached to virtual network 'branchhub'
I havent setup any routing tables.
One last setting i did on my bridge network router (192.168.1.1) is that i added a static route that says 192.168.10.0 with subnet 255.255.255.0 and gateway 192.168.1.253
so what happens from server side is that i can ping to any device on the 192.168.1.0 network. from the bridge network, i can ping only 192.168.1.253, which is the remote l3 switch virtual interface. I cannot ping 192.168.10.253 or any devices on the 192.168.10.0 network.
Please help me sort this issue so i can establish two way communication between the networks successfully.
Any help would be appreciated. Thanks.