Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
I am using VPN connection to get into another LAN which is 12000 miles away. Quite obvious.
Now, that far LAN uses its IP address schemes like 192.168.54.xx, 192.168.55.xx, 192.168.56.xx, 192.168.57.xx, 192.168.58.xx, 192.168.59.xx .
When I start my Cisco VPN client. I am able to ping 192.168.54.xx, 192.168.55.xx, 192.168.56.xx BUT I am not able to ping 192.168.57.xx, 192.168.58.xx, 192.168.59.xx.
So, what I am doing is first of all I log into some machine sa 192.168.54.3 and then from there 192.168.58.1. And I can do it quite successfully.
Now, logically I should be able to do it DIRECTLY as well. Since sometimes if 192.168.54.3 goes down, I am like screwed up.
But, I am not sure how to do this. What I tried is like adding route manually to Routing Table. But It dint help.
Few commands output... It may help understanding prob better.
[root@Viral ~]# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
204.57.xx.xx 192.168.6.1 255.255.255.255 UGH 0 0 0 eth0
192.168.54.0 192.168.7.58 255.255.255.0 UG 0 0 0 cipsec0
192.168.55.0 192.168.7.58 255.255.255.0 UG 0 0 0 cipsec0
192.168.52.0 192.168.7.58 255.255.255.0 UG 0 0 0 cipsec0
192.168.53.0 192.168.7.58 255.255.255.0 UG 0 0 0 cipsec0
192.168.50.0 192.168.7.58 255.255.255.0 UG 0 0 0 cipsec0
192.168.51.0 192.168.7.58 255.255.255.0 UG 0 0 0 cipsec0
192.168.1.0 192.168.7.58 255.255.255.0 UG 0 0 0 cipsec0
192.168.12.0 192.168.7.58 255.255.255.0 UG 0 0 0 cipsec0
192.168.10.0 192.168.7.58 255.255.255.0 UG 0 0 0 cipsec0
192.168.40.0 192.168.7.58 255.255.255.0 UG 0 0 0 cipsec0
192.168.56.0 192.168.7.58 255.255.255.0 UG 0 0 0 cipsec0
192.168.0.0 0.0.0.0 255.255.240.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
192.168.0.0 0.0.0.0 255.255.0.0 U 0 0 0 cipsec0
0.0.0.0 192.168.6.1 0.0.0.0 UG 0 0 0 eth0
[root@Viral ~]# ifconfig
cipsec0 Link encap:Ethernet HWaddr 00:0B:FC:F8:01:8F
inet addr:192.168.7.58 Mask:255.255.0.0
inet6 addr: fe80::20b:fcff:fef8:18f/64 Scope:Link
UP RUNNING NOARP MTU:1356 Metric:1
RX packets:149693 errors:0 dropped:443 overruns:0 frame:0
TX packets:108159 errors:0 dropped:674 overruns:0 carrier:0
RX bytes:156329456 (149.0 MiB) TX bytes:8675439 (8.2 MiB)