Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Device does not respond to ping from other subnets #196
Reported by Bobby Smith via this post on the mailing list -
I am seeing a problem with IPv4 device emulation in Ostinato v0.8 when routing reply traffic via a default gateway to remote DUTs. I know this is a new feature so not 100% sure if this is user error, expected behavior, or a bug.
Here is a detailed description:
IPv4 emulated devices do not respond to non-local, DUT initiated traffic.
In the following diagram:
OA = Ostinato Agent (with 5x IPv4 emulated devices on local subnet A and default gateway correctly set)
If we ping the emulated devices from DG on the local subnet A we see replies
I have confirmed that the default gateway’s ARP entry on subnet A is correctly resolved within the emulated devices information window.
I have also run a packet capture on the Ostinato agent. I can see packets arrive from the DUT but no reply is sent. It would seem the IP stack on the emulated devices is not correctly using the default gateway to reply to remote traffic.
However I have noticed: If I create a stream from the emulated devices on subnet A to a DUT on remote subnet B and I use the “resolve” option for source and destination MACs then the IP stack correctly sends Ostinato initiated traffic via the default gateway.
Logs and capture file attached corresponding to steps taken:
Looking at the log, I guess the fun starts with