I cannot ping (reach) any other subnet into or across my (real-sim or real-sim-real) SITL simulation other than those directly connected to the SITL Gateway. How can I debug this?

Categories:
Solution Number:
S20848
Last Modified:
2013-08-20
Issue

I cannot ping (reach) any other subnet into or across my (real-sim or real-sim-real) SITL simulation other than those directly connected to the SITL Gateway. How can I debug this?

Solution

If from your real machine you are trying to reach an IP subnet that is not directly connected, you need to add a route in the route table in your real machine(s). The subnet could be either on the other real side of SITL simulation or somewhere in the simulation.------+ +--------+ +-------------+ +---------+ +------+real1 |-------|sitl-(i1|----|i2) Router(i3|----|i4)-sitl-|--|real2 |------+ +--------+ +-------------+ +---------+ +------+In the above diagram, if you are attempting to reach from 'real1' to anything other than 'i1' or 'i2', you need to do route add statements on 'real1' for each subnet you are trying to reach.Typically here's what a route add statement should look like if executed on 'real1' when you're adding a route to 'real2''s subnet. Be sure to check your OS specific syntax.Please refer to the presentation for session 1578 from OPNETWORK 2012, slide 50, which has a diagram of the settings needed in a real-sim-real scenario.route add 192.0.0.0(real2) mask 255.255.255.0(for instance) 10.0.0.1(IP address of i2)The IP addresses above for 'real2' and 'i2' are completely fictitious. Use the corresponding values from your network.

Environment

DES Kernel->SITL

Attachments
NOTICE: Riverbed® product names have changed. Please refer to the Product List for a complete list of product names.
Can't find an answer? Create a case