Hi,
I believe the simplest way to do it is this (works for me):
a. on machine B, in cmd, you say: route add <IP address of C> mask
255.255.255.255 <IP address of A>
b. on machine C, in cmd, you say: route add <IP address of B> mask
255.255.255.255 <IP address of A>
c. on machine A, enable IP forwarding: echo 1 >
/proc/sys/net/ipv4/ip_forward
This is the case when all three machines are on the same subnet.
Regards,
Danko Vilendecic
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, November 04, 2005 3:36 PM
Subject: [nistnet] working with nistnet
Hi,
I have NISTnet running (on machine A) without problems (atleast I think I
do).
I have machine B(WIndows 2003 server) and machine C (Windows XP Pro).
I would like to configure it in a way so when machine B pings C, it goes
via A, so I can control the delay.
Already tried changing the gateway on B and C to A's IP, but would work.
Any ideas what I need to do?
Thanks
Latif Yahya
This e-mail and any attachments transmitted with it are confidential
and
intended solely for the individual to whom it is addressed. If you are
not
the intended recipient, please do not copy or disclose its contents
but
delete the same from your system and notify the sender immediately.
The views expressed by an individual in this email are that of the author
and do not necessarily reflect views of Dealogic Holdings Plc and its
subsidiaries and associates.
This e-mail and any attachments are believed to be virus free, but it
is
the responsibility of the recipient to ensure this. Dealogic Holdings
Plc
disclaims liability for any loss or damage you suffer as a consequence
of
receiving this email.
===================================================================
_______________________________________________
nistnet mailing list
[email protected]
http://www-x.antd.nist.gov/mailman/listinfo/nistnet
_______________________________________________
nistnet mailing list
[email protected]
http://www-x.antd.nist.gov/mailman/listinfo/nistnet
