Networking Forums

Networking Forums > Computer Networking > Linux Networking > NISTnet not working properly

Reply
Thread Tools Display Modes

NISTnet not working properly

 
 
Deepz
Guest
Posts: n/a

 
      07-26-2006, 06:09 PM
Hi, I have 2 win 2003 server machines with assigned Ip address
2.2.2.21( lets call it machine A) and 2.2.2.25 ( C)
and n/w mask 255.255.255.0

I have a Red hat machine ( machine B) that has 2 nics ( 2.2.2.30 and
2.2.2.31) on which I installed NISTnet with a warning

rmmod: module rtc is not loaded
Couldn't find rtc module -
/dev/rtc will be mostly unusable after running istnet. Sorry about
that.....
To prevent this message recompile rtc (Enhanced Real Time Clock
Support, under character devices) as a module.


I am new to Linux and dont know what affect this warning may have on
running Nistenet.

So now all 3 machines are there are same subnet / switch.

and the network configuration is

[ A ] 2.2.2.21 --------------> 2.2.2.31 [ B ] 2.2.2.30
<------------------- 2.2.2.25 [ C ]

on B routing to C is via gateway 2.2.2.30

on C routing to B is via gateway 2.2.2.31

But I dint add any route from B to either A/C . When I do that it gives
me error saying

Host name lookup failure

pinging B to both A / C works fine both ways ( ip_frowarding is set)

Entries in NISTnet are
src dest TOS delay duplicates
......

A 2.2.2.30(B) - 10 ms 60%
A 2.2.2.31(B) - 10 ms 60%
C 2.2.2.30(B) - 10 ms 60%
C 2.2.2.31(B) - 10 ms 60%
A C - 10 ms 60%


When I run 2 different instances of same application on both A and C
that use TCp sockets to connect to each other ,the aplication runs the
same way whether NISTnet is set ON or OFF. ( when I disable any of the
nic on linux box , the applcation stops , meaning routing between A and
C is hapening through the linux box)

concerns/observations

1. when I ping from B to A/ C duplicates come as expected but delay is
always less than 1 ms.

2. Is the problem is due to rtc warning I got . I mean is nistnet
installed properly.

Please comment . My project is struck at this point.

Thanks!

-Deepz.

 
Reply With Quote
 
 
 
 
Allen McIntosh
Guest
Posts: n/a

 
      07-26-2006, 11:45 PM
Deepz wrote:
> Hi, I have 2 win 2003 server machines with assigned Ip address
> 2.2.2.21( lets call it machine A) and 2.2.2.25 ( C)
> and n/w mask 255.255.255.0
>
> I have a Red hat machine ( machine B) that has 2 nics ( 2.2.2.30 and
> 2.2.2.31) on which I installed NISTnet with a warning
>
> rmmod: module rtc is not loaded
> Couldn't find rtc module -
> /dev/rtc will be mostly unusable after running istnet. Sorry about
> that.....
> To prevent this message recompile rtc (Enhanced Real Time Clock
> Support, under character devices) as a module.
>
> I am new to Linux and dont know what affect this warning may have on
> running Nistenet.


None at all. Nistnet needs to take over the realtime clock. When
nistnet is done, it leaves the rtc unusable. If the rtc code has been
compiled as a module you can just reload the module. Unfortunately, in
stock RedHat kernels, the rtc code is not compiled this way. If you
reboot when you are finished with nistnet, you may get some complaints
about rtc access, but that's all. I've been there & done that
occasionally, and had no trouble.

> So now all 3 machines are there are same subnet / switch.
>
> and the network configuration is
>
> [ A ] 2.2.2.21 --------------> 2.2.2.31 [ B ] 2.2.2.30
> <------------------- 2.2.2.25 [ C ]
>
> on B routing to C is via gateway 2.2.2.30
>
> on C routing to B is via gateway 2.2.2.31


Put A and C on separate class C networks, and add the appropriate routes
through B. Anything else is just going to cause you trouble.

> But I dint add any route from B to either A/C . When I do that it gives
> me error saying
>
> Host name lookup failure


You don't need to add routes on B. Were you adding routes by name
instead of by address?
>
> pinging B to both A / C works fine both ways ( ip_frowarding is set)
>
> Entries in NISTnet are
> src dest TOS delay duplicates
> .....
>
> A 2.2.2.30(B) - 10 ms 60%
> A 2.2.2.31(B) - 10 ms 60%
> C 2.2.2.30(B) - 10 ms 60%
> C 2.2.2.31(B) - 10 ms 60%
> A C - 10 ms 60%
>
>
> When I run 2 different instances of same application on both A and C
> that use TCp sockets to connect to each other ,the aplication runs the
> same way whether NISTnet is set ON or OFF. ( when I disable any of the
> nic on linux box , the applcation stops , meaning routing between A and
> C is hapening through the linux box)
>
> concerns/observations
>
> 1. when I ping from B to A/ C duplicates come as expected but delay is
> always less than 1 ms.


When you are testing, it's a lot easier to debug a single entry (from A
to C, for example) that adds a large deterministic delay and nothing
else. Then run ping continuously from A to C (I assume windows will let
you do that).

> 2. Is the problem is due to rtc warning I got .


Shouldn't be.

> I mean is nistnet
> installed properly.


Looks like it. Use cnistnet to see if the kernel module has the delay
right.
 
Reply With Quote
 
Deepz
Guest
Posts: n/a

 
      07-27-2006, 09:58 PM
Hi Allen!

Thanks for replying
I did what you said. I set up 2 seperate class C subnets on a common
switch But I am still facing some problem. The NISTnet simulates only
when both the src and dest are set to 0.0.0.0
When I set src and dest as machine A & C ( IP addresses )
respectively or the other way round, things dont work out for me.

Pinging, tracert - everything works fine.

Please let me know what could be the problem.

 
Reply With Quote
 
Allen McIntosh
Guest
Posts: n/a

 
      07-28-2006, 12:28 AM
Deepz wrote:

> I set up 2 seperate class C subnets on a common
> switch But I am still facing some problem. The NISTnet simulates only
> when both the src and dest are set to 0.0.0.0
> When I set src and dest as machine A & C ( IP addresses )
> respectively or the other way round, things dont work out for me.
>
> Pinging, tracert - everything works fine.
>
> Please let me know what could be the problem.


Need more information. Please post output (from machine B) of
cnistnet -R
route -n
ifconfig
and also the addresses of A and C.
 
Reply With Quote
 
Deepz
Guest
Posts: n/a

 
      07-28-2006, 03:53 PM
These are the outputs you asked for.


IP address of A is 192.168.1.21 ( has default gateway 192.168.1.31 -
subnet mask - 255.255.255.0)

Ip address of C is 192.168.2.25 ( has default gateway 192.168.2.35 -
subnet mask - 255.255.255.0)

On machine B

[root@localhost nistnet.2.0.12b]# cnistnet -R
cnistnet -a 192.168.1.21 192.168.1.31 --drop 19.9997
cnistnet -a 192.168.1.21 192.168.2.25 --delay 1000.000
cnistnet -a 192.168.1.31 192.168.2.35 --delay 10.000 --drop 19.9997
--dup 39.999
4


[root@localhost nistnet.2.0.12b]# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0
eth1
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0
eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0
lo


[root@localhost nistnet.2.0.12b]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:0C:29:3B:47:8B
inet addr:192.168.1.31 Bcast:192.168.1.255
Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:207436 errors:0 dropped:0 overruns:0 frame:0
TX packets:200106 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:15553330 (14.8 Mb) TX bytes:13385704 (12.7 Mb)
Interrupt:10 Base address:0x1080

eth1 Link encap:Ethernet HWaddr 00:0C:29:3B:47:95
inet addr:192.168.2.35 Bcast:192.168.2.255
Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:130874 errors:0 dropped:0 overruns:0 frame:0
TX packets:123566 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:9465222 (9.0 Mb) TX bytes:7289754 (6.9 Mb)
Interrupt:9 Base address:0x10a0

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:120 errors:0 dropped:0 overruns:0 frame:0
TX packets:120 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:10102 (9.8 Kb) TX bytes:10102 (9.8 Kb)

Thanks!

-Deepz

 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
NISTnet not working properly Deepz Linux Networking 0 07-26-2006 06:09 PM
Auto-recconect not working properly using ADSL modem on XP SP2 nospamx1@yahoo.co.uk Broadband 5 12-17-2005 11:27 AM
ICS not working properly AuthorizedUser Wireless Networks 2 08-23-2004 04:46 AM
Sockets not working properly George Linux Networking 0 04-30-2004 02:32 PM
network connection not working properly Douglas Schofield Windows Networking 0 02-13-2004 07:06 PM



1 2 3 4 5 6 7 8 9 10 11