Connecting 2 systems using a switch - each on the next hop.
 

Hello everyone, I don't have much knowledge in routing and I've reached a problem that I'm unable to solve. Here is a quick diagram that I've made:
http://imageshack.us/f/37/netv2.png/



My goal is to enable System A to talk to System D. As of now, the System A is able to ping Linux Machine 1 and System B, but is unable to even ping Linux Machine 2.

System B is able to ping System A, Linux Machine 1, Linux Machine 2 and System C. In fact, Systems B and C are able to communicate just fine.

My question would be, what do I need to do in order to enable System A to talk to System D(and vice versa).

Things I've tried:

• Static routes in Linux Machine 1/2
• Static Routes in switch

None of these things seem to work, any help would be greatly appreciated!

Dear DarioGi,
Unless there's some overriding requirement that you haven't told us about, I suggest you reassign IP numbers so that all devices are on the same subnet (i.e. all IP numbers have the same first three numbers identical). I cannot immediately see why you need 172.10.1.x *and* 172.11.1.x numbers. Unless you have a very good reason, go for 172.10.x.x or 172.11.x.x all the way through.
Best wishes,
Flos

Thanks for the help, unfortunately, the IP's have to be as following: 172.(10/11).(1/2).(2-254) . I pretty much need to make it work with this IP structure since 10 is ethernet and 11 uses different fiber. Also, (1/2) there are many more linux machines.

In that case, try using the switch's IP as the default gateway on machines 1 & 2.
Good luck!
Flos

I'll give that a shot, but why would System B and System C be able to communicate with the current default gateways?

Figured it out, I needed to add static routes to another platform's gateway, thanks for the help flos.