Network testcases problem

[sasa sasa]

Hi,

Is the stress testing can be done with only one network interface?
Like in ftp4-download-stress testing it first down the interface link
and then try to give rsh command at the remote host which can't be
done in single network.
1) Could anybody give me some tips how to test these test cases?

Regards
Sasa

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Ltp-list mailing list
Ltp-list@...
https://lists.sourceforge.net/lists/listinfo/ltp-list

[Elder Costa-2]

sasa sasa wrote:

> Hi,
>
> Is the stress testing can be done with only one network interface?
> Like in ftp4-download-stress testing it first down the interface link
> and then try to give rsh command at the remote host which can't be
> done in single network.
> 1) Could anybody give me some tips how to test these test cases?
>
> Regards
> Sasa
>

AFAICT you need at least two network interfaces, one for control and
other for the tests themselves as some tests change the test interface
configuration. Have a look at the

$LTPROOT/testcases/network/stress/README

I am not sure if some tests could run on one interface only but probably
they will require much rework and will be more worksome than adding a
second interface to the target and host computers.

You will need to edit $LTPROOT/testscripts/networkstress.sh as well to
configure it for your specific setup.

Also some tests must fail if you are using Ubuntu or other Debian
derived distribution because the scripts rely on bash specific extension
(e.g. using source instead of '.'). Just change #!/bin/sh to #!/bin/bash
in the offending scripts.

Finaly, some tests fail because the inetd daemon receives too many
connections (you will se a "poll: protocol failure cirtuit setup"
message). If that happens you need to change /etc/inetd.conf to
something like:

shell stream tcp nowait.500 ....
                        ^^^^^^

and restart the inetd daemon.

HTH.

Elder.


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Ltp-list mailing list
Ltp-list@...
https://lists.sourceforge.net/lists/listinfo/ltp-list