Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm testing a NEWT configuration to be used for an Internet simulation between 16 peers. The NEWT host will be running on a dedicated PC as opposed to one of the peers, and all peers and the NEWT host will be physically connected to the same network. The PC that I'm using as a NEWT host to test the configuration is running Windows 7, and this will most likely be the version of Windows used for the Internet simulation.

The route command is sufficient to make the peers attempt to use the NEWT host as a gateway; with the appropriate routes configured on the peers, NEWT's RT packet monitor shows packets sent from one peer to another peer arriving at the NEWT host.

But the route command isn't sufficient to make the NEWT host actually be a gateway; packets sent from one peer to another do not reach their destinations when the peers try to use the NEWT host as a gateway.

The fact that the NEWT host would have to forward the packets via the same interface on which they arrived may be part of the problem, but I would prefer to avoid using multiple interfaces on the NEWT host.

So is there a way to make a PC running Windows 7 forward packets on the same interface on which they arrived?

share|improve this question
Minor thing, but what is NEWT? – Journeyman Geek Mar 8 '12 at 15:55
Network Emulator for Windows Toolkit. – TheBeardyMan Mar 8 '12 at 16:00

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.