Route all traffic via 192.168.1.254 gateway connected via eth0 network interface: Linux add a default route using route command Most modern Linux distro recommend and use the ip command for setting or displaying default gateway IP address on Linux. I am going to show you both ip and route command examples. If you want to goto the 10.10.17.0, goto the 38.x (the x being the IP of the server with a nic on that subnet), but when I tried to add that route add I got the error mentioned earlier.Fig.02: ip command in action Linux route Add Command Examples So, since I am on a point to point, from my desktop, if I tracert the 10.10.17.x it goes to my local gateway, then out the public internet naturally dying out. I have ssh forwarding on a machine there, so I can ssh -X over, x-forward some of the management app's, but one is java based and extremely slow. I have a management network at the co-lo on a 10.10.17.x network with some APC PDU's and a few other devices. We are setup on a point to point VPN, so I can see one subnet of the network (a public 38.x network). that I made sure I was pretty clear, but to recap, they are not on the same wire, if so I could have added an alias IP or other ways to get to it.īut, if more info is needed, I already explained, at the local office we are on a 10.10.5.x network. lornix, the message I wrote was well written due to so many 'help me' etc. Segregated to another nic/wire to prevent that. Obviously, the admins don't want you on the 10.10.17.x subnet, and it was bad things happen when you cause address collisions on (if you don't possess a valid IP for that subnet, you shouldn't be playing Would ALREADY have a valid route/gateway setup. The irony being, IF you had a valid IP address on the 10.10.17.x subnet, you IF they ARE both on the same wire, AND you have a valid IP address to use, I doubt that the 10.10.5.x and 10.10.17.x subnets are running on the same Without permissions (and routing) being performed on the server. If the *SERVER* has a second nic, you cannot access the network on that nic Usually, you need to have a nic on that subnet too. > so), and if so, what's the correct syntax. > So can I route to that private throught that machine (I would think > think), yet when I try this at the command line > I should have no problem getting to it using that server (I would > servers has a 2nd nice on a private network 10.10.17.0 which he can see > a 10.10.5.x local, the vpn is on the public internet. > At the office, we have a point to point VPN working, the office we have Still new to the distro, but having a route question/problem.

Opensuse route gateway