How to route network traffic through different machine

[ed.barrett]

I am working for a testing company that can record and then playback
client traffic against a server.

We have been given a piece of software by a client that has the
connection string a.b.c.dort hard-coded in the software.

Normally we are used to software that has the domain name and then we
just set the hosts file to point the domain at where our sniffer tool
sits, and the tools sniffs and then forwards to the real server.

With this software there is no domain name so we are a bit stuck.

We have hoped the following would work:

route add destination localMachine

The port the software uses is 450 yet we see no traffic arrive on our
sniffing tool.

I am sure there must be a way to do this.

To summarise, when my local windows machine thinks it is talking to
a.b.c.d on port 450 I want it to talk to v.w.x.y on port 450.

Any help would be gratefully received.

Thanks

Ed

 

[johnsuth]

I am working for a testing company that can record and then playback
client traffic against a server.

We have been given a piece of software by a client that has the
connection string a.b.c.dort hard-coded in the software.

Normally we are used to software that has the domain name and then we
just set the hosts file to point the domain at where our sniffer tool
sits, and the tools sniffs and then forwards to the real server.

With this software there is no domain name so we are a bit stuck.

We have hoped the following would work:

route add destination localMachine

The port the software uses is 450 yet we see no traffic arrive on our
sniffing tool.

I am sure there must be a way to do this.

To summarise, when my local windows machine thinks it is talking to
a.b.c.d on port 450 I want it to talk to v.w.x.y on port 450.

Any help would be gratefully received.

There is probably an easier way but, you could pop an extra NIC into one
of your boxes, give it the IP address a.b.c.d, and provide a route to
that NIC.