curl-loader-devel — curl-loader usage and development issues

Re: curl-loader on Solaris?

[Frank F. <fra...@gm...>]

Hello Robert,

thanks for your fast reply!

On Sun, Apr 20, 2008 at 05:21:48PM +0300, Robert Iakobashvili wrote:
> On Sun, Apr 20, 2008 at 4:44 PM, Frank Fegert <fra...@gm...> wrote:
> > the FAQ mentions only Linux as a supported OS and the list archives
> > didn't indicate anyone trying to run curl-loader on Solaris. Before
> > i dig deeper in the sources, how are the chances of actually getting
> > curl-loader build and running on Solaris? Is it that Linux-specific
> > or is there a real chance it'll be running and give reasonable results?
> 
> We are using netlink sockets and secondary IP addresses.
> If Solaris supports them and has some such API, you can
> give it a try.
> If not, there is a plenty amount of work to do for that.

Netlink sockets are not supported on Solaris unless the XNET library
functions (see [1]) are fairly similar to the Linux netlink API. 
Secondary IP adresses are supported via logical interfaces and the
"if" ioctls SIOCLIFADDIF/SIOCLIFREMOVEIF, see [2].
In your opinion, would that be sufficient for an adaption to Solaris?
Or does anyone know an alternative to curl-loader runable on Solaris
(probably the wrong list to ask this ;-) )?

Thanks & best regards,

	Frank


[1] http://docs.sun.com/app/docs/doc/817-0696/6mgfrf0gr?l=en&q=3XNET&a=expand
[2] http://docs.sun.com/app/docs/doc/816-5177/if-7p?l=en&a=view

Re: curl-loader on Solaris?

[Robert I. <cor...@gm...>]

Hi Frank,

On Sun, Apr 20, 2008 at 4:44 PM, Frank Fegert <fra...@gm...> wrote:

> Hi all,
>
> the FAQ mentions only Linux as a supported OS and the list archives
> didn't indicate anyone trying to run curl-loader on Solaris. Before
> i dig deeper in the sources, how are the chances of actually getting
> curl-loader build and running on Solaris? Is it that Linux-specific
> or is there a real chance it'll be running and give reasonable results?
>
> Thanks & best regards,
>
>        Frank
>

We are using netlink sockets and secondary IP addresses.
If Solaris supports them and has some such API, you can
give it a try.
If not, there is a plenty amount of work to do for that.

Take care.

-- 
Sincerely,
Robert Iakobashvili
"Light will come from Jerusalem"
...................................................................
www.ghotit.com
An online speller for dyslectics and bad-spellers
...................................................................
http://curl-loader.sourceforge.net
An open-source web application testing tool
...................................................................

curl-loader on Solaris?

[Frank F. <fra...@gm...>]

Hi all,

the FAQ mentions only Linux as a supported OS and the list archives
didn't indicate anyone trying to run curl-loader on Solaris. Before
i dig deeper in the sources, how are the chances of actually getting
curl-loader build and running on Solaris? Is it that Linux-specific
or is there a real chance it'll be running and give reasonable results?

Thanks & best regards,

	Frank

RE: 401.2 messages

[Richard P. <rp...@ce...>]

Thanks!



rick parker : rp...@ce...<mailto:rp...@ce...> :  d 781 425 5200 x224 : www.certeon.com<http://www.certeon.com>
certeon - Accelerate Your Business

From: cur...@li... [mailto:cur...@li...] On Behalf Of Robert Iakobashvili
Sent: Friday, April 04, 2008 9:34 AM
To: curl-loader-devel
Subject: Re: 401.2 messages

Richard,

I have seen recently the following thread on curl news-group,
that may be related to your problems.


------------------------------------------------------------------------------------
NTLM authorization process falls down sometime

Daniel Stenberg to libcurl
show details Apr 3 (1 day ago) Reply

On Thu, 3 Apr 2008, CHADAL François [GIRCE] wrote:

With the debug trace, I've seen the NTLM response send by the client (my application) is missing, often or always, when libcurl re-use another connection (number connection is different) to re-isssue the HTTP request. When it is OK, libcurl send the NTLM message header, and when libcurl switch for using another free connection, the NTLM message header is not present.
It seems to be a bug.

This sounds exactly like this entry in docs/KNOWN_BUGS
37. Having more than one connection to the same host when doing NTLM
 authentication (with performs multiple "passes" and authenticates a
 connection rather than a HTTP request), and particularly when using the
 multi interface, there's a risk that libcurl will re-use a wrong connection
 when doing the different passes in the NTLM negotiation and thus fail to
 negotiate (in seemingly mysterious ways).
--

------------------------------------------------------------------------------------

Sincerely,
Robert Iakobashvili
"Light will come from Jerusalem"
...........................................................
http://curl-loader.sourceforge.net
An open-source web testing and traffic generation.

Re: 401.2 messages

[Robert I. <cor...@gm...>]

Richard,

I have seen recently the following thread on curl news-group,
that may be related to your problems.


------------------------------------------------------------------------------------
NTLM authorization process falls down sometime

Daniel Stenberg to libcurl
show details Apr 3 (1 day ago) Reply

On Thu, 3 Apr 2008, CHADAL François [GIRCE] wrote:

With the debug trace, I've seen the NTLM response send by the client (my
application) is missing, often or always, when libcurl re-use another
connection (number connection is different) to re-isssue the HTTP request.
When it is OK, libcurl send the NTLM message header, and when libcurl switch
for using another free connection, the NTLM message header is not present.
It seems to be a bug.

This sounds exactly like this entry in docs/KNOWN_BUGS
37. Having more than one connection to the same host when doing NTLM
 authentication (with performs multiple "passes" and authenticates a
 connection rather than a HTTP request), and particularly when using the
 multi interface, there's a risk that libcurl will re-use a wrong connection
 when doing the different passes in the NTLM negotiation and thus fail to
 negotiate (in seemingly mysterious ways).
-- 

------------------------------------------------------------------------------------

Sincerely,
Robert Iakobashvili
"Light will come from Jerusalem"
...........................................................
http://curl-loader.sourceforge.net
An open-source web testing and traffic generation.

Re: curl-loader crashing network on ubuntu machine

[Robert I. <cor...@gm...>]

Hi,

On Wed, Apr 2, 2008 at 12:12 PM, MLVJ <ml...@ya...> wrote:
>
>  The problem seems to be that curl-loader changes the
>  routing table, and blonks out the management interface
>  route.
>
>  Here's the route -n before running curl:
>  route -n
>  Kernel IP routing table
>  Destination     Gateway         Genmask         Flags
>  Metric Ref    Use Iface
>  10.59.70.64     0.0.0.0         255.255.255.240 U
>  0      0        0 eth0
>  10.59.241.128   0.0.0.0         255.255.255.224 U
>  0      0        0 eth1
>  0.0.0.0         10.59.70.65     0.0.0.0         UG
>  100    0        0 eth0
>  0.0.0.0         10.59.241.129   0.0.0.0         UG
>  100    0        0 eth1
>
>  ...and after running curl there's a new default route:
>  route -n
>  Kernel IP routing table
>  Destination     Gateway         Genmask         Flags
>  Metric Ref    Use Iface
>  10.59.70.64     0.0.0.0         255.255.255.240 U
>  0      0        0 eth0
>  10.59.241.128   0.0.0.0         255.255.255.224 U
>  0      0        0 eth1
>  0.0.0.0         10.59.70.65     0.0.0.0         UG
>  100    0        0 eth0
>  0.0.0.0         10.59.241.129   0.0.0.0         UG
>  100    0        0 eth1
>  10.59.0.0       0.0.0.0         255.255.0.0     U
>  0      0        0 eth0 (something like that)
>
>  so maybe an issue with the netmask, set to 16 in the
>  bulk.conf example. I have just set this to 25 (what
>  the actual netmask should be). Let's try that. Gosh it
>  didn't kill the network, and this route was added:
>  10.59.250.0     0.0.0.0         255.255.255.128 U
>  0      0        0 eth0


Good analyzes!
Y mean netmask 24 (not 25), worth trying it.
curl-loader opens the secondary ip-addreses similar to the command
#ip from the iproute or iproute2 package.

try to add these addresses by the command
# ip add .... (man ip)

If you see, that a new route appears, this means, that this is a kernel's
decision logic. Y can argue at linux-netdev, whether the logic is appropriate.

The simplest way to workaround it could be to edit the routing
table using either of the commands:
route
ip.

Sorry, curl-loader is a userland application and is not in position
to control the kernel's decisions.

Sincerely,
Robert Iakobashvili
"Light will come from Jerusalem"
...........................................................
http://curl-loader.sourceforge.net
An open-source web testing and traffic generation.

Re: curl-loader crashing network on ubuntu machine

[MLVJ <ml...@ya...>]

Hmm so we installed ubuntu gutsy gibbon on the same
hardware last night.

Exactly the same issue occurs; I've come into the
office physically to see what is shown on the machine
itself.

The problem seems to be that curl-loader changes the
routing table, and blonks out the management interface
route.

Here's the route -n before running curl:
route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags
Metric Ref    Use Iface
10.59.70.64     0.0.0.0         255.255.255.240 U    
0      0        0 eth0
10.59.241.128   0.0.0.0         255.255.255.224 U    
0      0        0 eth1
0.0.0.0         10.59.70.65     0.0.0.0         UG   
100    0        0 eth0
0.0.0.0         10.59.241.129   0.0.0.0         UG   
100    0        0 eth1

...and after running curl there's a new default route:
route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags
Metric Ref    Use Iface
10.59.70.64     0.0.0.0         255.255.255.240 U    
0      0        0 eth0
10.59.241.128   0.0.0.0         255.255.255.224 U    
0      0        0 eth1
0.0.0.0         10.59.70.65     0.0.0.0         UG   
100    0        0 eth0
0.0.0.0         10.59.241.129   0.0.0.0         UG   
100    0        0 eth1
10.59.0.0       0.0.0.0         255.255.0.0     U    
0      0        0 eth0 (something like that)

so maybe an issue with the netmask, set to 16 in the
bulk.conf example. I have just set this to 25 (what
the actual netmask should be). Let's try that. Gosh it
didn't kill the network, and this route was added:
10.59.250.0     0.0.0.0         255.255.255.128 U    
0      0        0 eth0

Didn't actually work, but that's probably a network
issue outside of the box now. Perhaps!

Unless there's another commonly made error?

Hopefully you will be able to use this configuration
issue to inform resolution of future problems.





      __________________________________________________________
Sent from Yahoo! Mail.
A Smarter Inbox http://uk.docs.yahoo.com/nowyoucan.html

Re: curl-loader crashing network on fedora machine

[Robert I. <cor...@gm...>]

Hi,

On Tue, Apr 1, 2008 at 4:06 PM, MLVJ <ml...@ya...> wrote:
> CURL-LOADER VERSION: 0.44
>
> HP ProLiant DL380
>
> LINUX DISTRIBUTION and KERNEL (uname -r):
> uname -r
> 2.6.15-1.2054_FC5smp
>
> gcc version 4.1.0 20060304 (Red Hat 4.1.0-3)
>
> COMPILATION AND MAKING OPTIONS (if defaults changed):
> $make optimize=1 debug=0
>
> COMMAND-LINE:
>
> ./curl-loader -f nte-conf/bulk.conf
>
> CONFIGURATION-FILE (The most common source of
> problems):
> Place the file inline here:
>
> cat bulk.conf
> ########### GENERAL SECTION
> ################################
>
> BATCH_NAME= bulk
> CLIENTS_NUM_MAX=200 # Same as CLIENTS_NUM
> #CLIENTS_NUM_START=10
> CLIENTS_RAMPUP_INC=5
> INTERFACE =eth0
> NETMASK=16
> IP_ADDR_MIN= 10.59.250.1
> IP_ADDR_MAX= 10.59.250.3
> IP_SHARED_NUM=3
> CYCLES_NUM= -1
> URLS_NUM= 1
>
> ########### URL SECTION
> ####################################
>
> URL=http://10.59.246.45/index.html
> #URL=http://localhost/apache2-default/ACE-INSTALL.html
> #URL=http://localhost/ACE-INSTALL.html
> URL_SHORT_NAME="local-apache"
> REQUEST_TYPE=GET
> TIMER_URL_COMPLETION = 5000
> TIMER_AFTER_URL_SLEEP = 500
>
>
> DESCRIPTION:
> After running the configuration file above, the
> network stops working - can't ping/telnet/ssh/anything
> to or from the machine, on the eth1 management
> interface.
> This makes it very hard to figure out what's going on,
> as the machine is remote to me!
>
> Note that the exact same file, but with ip addresses
> 192.168.1.1 and 192.168.1.3 (as per the example
> bulk.conf) doesn't stop the network.
>
> QUESTION/ SUGGESTION/ PATCH:
> How do we get it working?


Most probably somebody is using the addresses, starting from 10, that
you are trying to use. Reboot your linux (to clean up the secondary addresses
from curl-loader) or delete all secondary and clean the arp caches and ping
to that addresses prior to running curl-loader.

Since you are the second, who reported network problems with curl-loader
(the first was me, when discovered a linux kernel bug, now fixed),
I suspect, that you problems may be also related to your networking card, which
could be its poor or buggy support in your linux distribution.
To resolve it you may wish to install FC-8 or recent Debian.

Yet another option, that your routing somehow gets broken.
Therefore, please, look into your routing table before running curl-loader
and after. Note, that curl-loader does not effect routing tables.
Run traceroute.

Once I have seen a really weird case, where an old switch was auto-synched with
a new server card at 10 Mbps, thus curl-loader has filled the 10 Mbps,
and there was no room
for any other traffic.


All the above options are beyond the area of curl-loader application control.

Best wishes.

>
>
> Sincerely,
> Robert Iakobashvili
> "Light will come from Jerusalem"
> ...........................................................
> http://curl-loader.sourceforge.net
> An open-source web testing and traffic generation.

Re: curl-loader crashing network on fedora machine

[MLVJ <ml...@ya...>]

CURL-LOADER VERSION: 0.44

HW DETAILS: CPU/S and memory are must:
free
             total       used       free     shared   
buffers     cached
Mem:       3109056     264216    2844840          0   
  13472     195048
-/+ buffers/cache:      55696    3053360
Swap:      2031608          0    2031608
grep MemTotal /proc/meminfo
MemTotal:      3109056 kB

grep "model name" /proc/cpuinfo
model name      : Intel(R) Xeon(TM) CPU 3.06GHz
model name      : Intel(R) Xeon(TM) CPU 3.06GHz
model name      : Intel(R) Xeon(TM) CPU 3.06GHz
model name      : Intel(R) Xeon(TM) CPU 3.06GHz

HP ProLiant DL380

LINUX DISTRIBUTION and KERNEL (uname -r):
uname -r
2.6.15-1.2054_FC5smp

GCC VERSION (gcc -v):
gcc -v
Using built-in specs.
Target: i386-redhat-linux
Configured with: ../configure --prefix=/usr
--mandir=/usr/share/man --infodir=/usr/share/info
--enable-shared --enable-threads=posix
--enable-checking=release --with-system-zlib
--enable-__cxa_atexit --disable-libunwind-exceptions
--enable-libgcj-multifile
--enable-languages=c,c++,objc,obj-c++,java,fortran,ada
--enable-java-awt=gtk --disable-dssi
--with-java-home=/usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/jre
--with-cpu=generic --host=i386-redhat-linux
Thread model: posix
gcc version 4.1.0 20060304 (Red Hat 4.1.0-3)

COMPILATION AND MAKING OPTIONS (if defaults changed):

$make optimize=1 debug=0

COMMAND-LINE:
./curl-loader -f nte-conf/bulk.conf

CONFIGURATION-FILE (The most common source of
problems):
Place the file inline here:
cat bulk.conf
########### GENERAL SECTION
################################

BATCH_NAME= bulk
CLIENTS_NUM_MAX=200 # Same as CLIENTS_NUM
#CLIENTS_NUM_START=10
CLIENTS_RAMPUP_INC=5
INTERFACE =eth0
NETMASK=16
IP_ADDR_MIN= 10.59.250.1
IP_ADDR_MAX= 10.59.250.3
IP_SHARED_NUM=3
CYCLES_NUM= -1
URLS_NUM= 1

########### URL SECTION
####################################

URL=http://10.59.246.45/index.html
#URL=http://localhost/apache2-default/ACE-INSTALL.html
#URL=http://localhost/ACE-INSTALL.html
URL_SHORT_NAME="local-apache"
REQUEST_TYPE=GET
TIMER_URL_COMPLETION = 5000
TIMER_AFTER_URL_SLEEP = 500


DOES THE PROBLEM AFFECT:
       COMPILATION? No
       LINKING? No
       EXECUTION? No
       OTHER (please specify)?
Network stops.

Have you run $make cleanall  prior to $make ?
Yes

DESCRIPTION:
After running the configuration file above, the
network stops working - can't ping/telnet/ssh/anything
to or from the machine, on the eth1 management
interface.
This makes it very hard to figure out what's going on,
as the machine is remote to me!

Note that the exact same file, but with ip addresses
192.168.1.1 and 192.168.1.3 (as per the example
bulk.conf) doesn't stop the network.

QUESTION/ SUGGESTION/ PATCH:
How do we get it working?


      __________________________________________________________
Sent from Yahoo! Mail.
A Smarter Inbox http://uk.docs.yahoo.com/nowyoucan.html

Re: curl-loader crashing network on fedora machine

[Robert I. <cor...@gm...>]

Hi

On Tue, Apr 1, 2008 at 1:54 PM, MLVJ <ml...@ya...> wrote:

> Hi,
>
> I'd like to use curl-loader, so we took a fat hp dl585
> and installed fedora 5 on it (first disk that came to
> hand).
>
> It has two interfaces; eth1 is the management one, and
> eth0 is the data one, to be used for the load testing.
>
> I'd like some suggestions if possible as to how to
> figure out what's going wrong with my configuration.
>

Please,  feel the PROBLEM-REPORT-FORM in due course (in curl-loader
tarball) and
explain in more details what you mean as crashing network.

By the way, I would recommend you to install a less buggy Fedora-8
or even better Debian.

-- 
Sincerely,
Robert Iakobashvili
"Light will come from Jerusalem"
...........................................................
http://curl-loader.sourceforge.net
An open-source web testing and traffic generation.

curl-loader crashing network on fedora machine

[MLVJ <ml...@ya...>]

Hi,

I'd like to use curl-loader, so we took a fat hp dl585
and installed fedora 5 on it (first disk that came to
hand).

It has two interfaces; eth1 is the management one, and
eth0 is the data one, to be used for the load testing.

I'd like some suggestions if possible as to how to
figure out what's going wrong with my configuration.

Then I installed curl-loader 44, and tested by running

./curl-loader -f conf-examples/bulk.conf
...and that worked.

So I copied bulk.conf, changed the target URL, and it
still ran.

Then I changed the ip addresses from 192.168.1.1 - 3
to 10.59.250.1 -3, and it crashes the network almost
immediately.

Note - I also tried setting CYCLES to 10 and that
still terminates the network.

By "terminates the network" I mean that the network
doesn't respond any more, and I have to call somebody
to reboot the system from the console. They can't ping
out to the default gateway or anything.

Here's the bulk.conf which crashes the system:
[root@phload1 nte-conf]# cat bulk.conf
########### GENERAL SECTION
################################

BATCH_NAME= bulk
CLIENTS_NUM_MAX=200 # Same as CLIENTS_NUM
#CLIENTS_NUM_START=10
CLIENTS_RAMPUP_INC=5
INTERFACE   =eth0
NETMASK=16
IP_ADDR_MIN= 10.59.250.1
IP_ADDR_MAX= 10.59.250.3
IP_SHARED_NUM=3
CYCLES_NUM= -1
URLS_NUM= 1

########### URL SECTION
####################################

URL=http://10.59.246.45/index.html
#URL=http://localhost/apache2-default/ACE-INSTALL.html
#URL=http://localhost/ACE-INSTALL.html
URL_SHORT_NAME="local-apache"
REQUEST_TYPE=GET
TIMER_URL_COMPLETION = 5000
TIMER_AFTER_URL_SLEEP = 500

Here's the difference with the example file that
works:
[root@phload1 nte-conf]# diff bulk.conf
../conf-examples/bulk.conf
9,10c9,10
< IP_ADDR_MIN= 10.59.250.1
< IP_ADDR_MAX= 10.59.250.3
---
> IP_ADDR_MIN= 192.168.1.1
> IP_ADDR_MAX= 192.168.1.3
17c17
< URL=http://10.59.246.45/index.html
---
> URL=http://localhost/index.html

bulk.log contains lots and lots of these:
1 65 (10.59.250.2)  !! ERROR: Connection time-out
after 5019 ms
: eff-url: , url:

Here's the output:

[root@phload1 curl-loader-0.44]# ./curl-loader -f
nte-conf/bulk.conf
parse_config_file - loaded 1 batches

The configuration has been post-validated
successfully.

add_secondary_ip_addrs - setting secondary IP
10.59.250.1
add_secondary_ip_addrs - successfully added
10.59.250.1/16 IP-address.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
add_secondary_ip_addrs - successfully added
10.59.250.2/16 IP-address.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
add_secondary_ip_addrs - successfully added
10.59.250.3/16 IP-address.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.3
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.3/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.1
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.1/16" already exists.
add_secondary_ip_addrs - setting secondary IP
10.59.250.2
rtnl_talk(): RTNETLINK answers: File exists
add_secondary_ip_addrs - note: probably, the
IP-address "10.59.250.2/16" already exists.
main - added IP-addresses to the loading network
interface.

RUNNING LOAD















































============  loading batch is: bulk      
======================================
 Operations:             Success                
Failed                 Timed out
URL0:local-apache       0      0                0     
0                0      0
--------------------------------------------------------------------------------
Interval stats (latest:0 sec, clients:5,
CAPS-curr:5000):
H/F  
Req:0,1xx:0,2xx:0,3xx:0,4xx:0,5xx:0,Err:0,T-Err:0,D:0ms,D-2xx:0ms,Ti:0B/s,To:0B/s
H/F/S
Req:0,1xx:0,2xx:0,3xx:0,4xx:0,5xx:0,Err:0,T-Err:0,D:0ms,D-2xx:0ms,Ti:0B/s,To:0B/s
--------------------------------------------------------------------------------
Summary stats (runs:1 secs, CAPS-average:5):
H/F  
Req:0,1xx:0,2xx:0,3xx:0,4xx:0,5xx:0,Err:0,T-Err:0,D:0ms,D-2xx:0ms,Ti:0B/s,To:0B/s
H/F/S
Req:0,1xx:0,2xx:0,3xx:0,4xx:0,5xx:0,Err:0,T-Err:0,D:0ms,D-2xx:0ms,Ti:0B/s,To:0B/s
=================================================================================
 Automatic: adding 5 clients/sec. Stop inc and manual
[M].
=================================================================================
Read from remote host 10.59.241.135: Connection timed
out



      __________________________________________________________
Sent from Yahoo! Mail.
A Smarter Inbox http://uk.docs.yahoo.com/nowyoucan.html

Re: Cygwin compilation fails

[Robert I. <cor...@gm...>]

Tomy

On Tue, Mar 25, 2008 at 10:48 AM, Tomy aviv <i_r...@ho...> wrote:

>
> i will see where can i get hold of a linux machine :) ,
>
>

Mind the FAQs, please:
http://curl-loader.sourceforge.net/doc/index.html

Y can try a live-CD of Bugnux, which contains a pre-built curl-loader
with some older version.

Sincerely,
Robert Iakobashvili
"Light will come from Jerusalem"
...........................................................
http://curl-loader.sourceforge.net
An open-source web testing and traffic generation.

RE: Cygwin compilation fails

[Tomy a. <i_r...@ho...>]

Hi Robert,
 
thanks for your prompt replay which saved me a lot of effort,
i will see where can i get hold of a linux machine :) ,
 
Regards,
Tomy


Date: Tue, 25 Mar 2008 10:25:42 +0200From: cor...@gm...: cur...@li...: Cygwin compilation failsHi Tomy Aviv,
On Tue, Mar 25, 2008 at 10:14 AM, Tomy aviv <i_r...@ho...> wrote:


hi all,
i am getting the following error while trying to install curl-loader ver 0.43 on my cygwin
 
 ...local/curl-loader-0.43]$ makecd ./packages; tar zxf curl-7.17.0.tar.gz; ln -sf curl-7.17.0 curl; \patch -d curl -p1 < ../patches/curl-trace-info-error.patchpatch: not foundmake: *** [lib/libcurl.a] Error 127
 Please, note, that cygwin is not supported.To use curl-loader you need a real linux.Next time, please, provide a filled PRF. Thanks. Best wishes,-- Sincerely,Robert Iakobashvili"Light will come from Jerusalem"...........................................................http://curl-loader.sourceforge.netAn open-source web testing and traffic generation. 
_________________________________________________________________
Test your Star IQ
http://club.live.com/red_carpet_reveal.aspx?icid=redcarpet_HMTAGMAR

Cygwin compilation fails

[Robert I. <cor...@gm...>]

Hi Tomy Aviv,

On Tue, Mar 25, 2008 at 10:14 AM, Tomy aviv <i_r...@ho...> wrote:

> hi all,
> i am getting the following error while trying to install curl-loader ver
> 0.43 on my cygwin
>
>  ...local/curl-loader-0.43]$ make
> cd ./packages; tar zxf curl-7.17.0.tar.gz; ln -sf curl-7.17.0 curl; \
> patch -d curl -p1 < ../patches/curl-trace-info-error.patch
> patch: not found
> make: *** [lib/libcurl.a] Error 127
>
>
Please, note, that cygwin is not supported.
To use curl-loader you need a real linux.

Next time, please, provide a filled PRF. Thanks.

Best wishes,

-- 
Sincerely,
Robert Iakobashvili
"Light will come from Jerusalem"
...........................................................
http://curl-loader.sourceforge.net
An open-source web testing and traffic generation.

[Tomy a. <i_r...@ho...>]

hi all,
i am getting the following error while trying to install curl-loader ver 0.43 on my cygwin
 
 ...local/curl-loader-0.43]$ makecd ./packages; tar zxf curl-7.17.0.tar.gz; ln -sf curl-7.17.0 curl; \patch -d curl -p1 < ../patches/curl-trace-info-error.patchpatch: not foundmake: *** [lib/libcurl.a] Error 127
 
both make cleanall and make optimize=1 debug=0 options yield the same reuslt
 
can you please assist?
 
Regards,
Tomash
_________________________________________________________________
Test your Star IQ
http://club.live.com/red_carpet_reveal.aspx?icid=redcarpet_HMTAGMAR

Re: 401.2 messages

[Robert I. <cor...@gm...>]

Richard,

On Fri, Mar 7, 2008 at 5:42 PM, Richard Parker <rp...@ce...> wrote:

>  Here is my conf file.
>
>
>
Still, this is not a PRF as required.

> ########### GENERAL SECTION ################################
>
> BATCH_NAME=webhost-temp1
>
> CLIENTS_NUM_MAX=30
>
> CLIENTS_RAMPUP_INC=5
>
> CLIENTS_NUM_START=5
>
> INTERFACE=eth1
>
> NETMASK=24
>
> IP_ADDR_MIN=10.40.171.167
>
> IP_ADDR_MAX=10.40.171.197
>
> URLS_NUM=9
>
> CYCLES_NUM=-1
>
> TIMER_TCP_CONN_SETUP=10
>
> USER_AGENT=RICK_CURL
>
>
>
>
>
> ########### URL SECTION ####################################
>
>
>
> ### Login URL -  cycling
>
>
>
> # GET-part
>
> URL=http://webhost-temp1/Pages/Default.aspx
>
> URL_SHORT_NAME="default page"
>
> REQUEST_TYPE=GET
>
> WEB_AUTH_METHOD=NTLM
>
> WEB_AUTH_CREDENTIALS=administrator:password
>
> TIMER_URL_COMPLETION = 0 # In msec. When positive, Now it is enforced by
> cancelling url fetch on timeout
>
> TIMER_AFTER_URL_SLEEP = 500
>
>
curl-loader is using libcurl for HTTP stack.
libcurl states:
http://curl.netmirror.org/docs/manpage.html#--ntlm

you may try to run  curl-loader (with a single client)
adding to your command line options -v -u and looking
afterwards in the file webhost-temp1.log




Sincerely,
Robert Iakobashvili
"Light will come from Jerusalem"
...........................................................
http://curl-loader.sourceforge.net
An open-source web testing and traffic generation.

RE: 401.2 messages

[Richard P. <rp...@ce...>]

Here is my conf file.

########### GENERAL SECTION ################################
BATCH_NAME=webhost-temp1
CLIENTS_NUM_MAX=30
CLIENTS_RAMPUP_INC=5
CLIENTS_NUM_START=5
INTERFACE=eth1
NETMASK=24
IP_ADDR_MIN=10.40.171.167
IP_ADDR_MAX=10.40.171.197
URLS_NUM=9
CYCLES_NUM=-1
TIMER_TCP_CONN_SETUP=10
USER_AGENT=RICK_CURL


########### URL SECTION ####################################

### Login URL -  cycling

# GET-part
URL=http://webhost-temp1/Pages/Default.aspx
URL_SHORT_NAME="default page"
REQUEST_TYPE=GET
WEB_AUTH_METHOD=NTLM
WEB_AUTH_CREDENTIALS=administrator:password
TIMER_URL_COMPLETION = 0 # In msec. When positive, Now it is enforced by cancelling url fetch on timeout
TIMER_AFTER_URL_SLEEP = 500


### Cycling URL
URL=http://webhost-temp1/testing123/default.aspx
URL_SHORT_NAME="123 directory"
REQUEST_TYPE=GET
WEB_AUTH_METHOD=NTLM
WEB_AUTH_CREDENTIALS=administrator:password
TIMER_URL_COMPLETION = 0 # In msec. When positive, Now it is enforced by cancelling url fetch on timeout
TIMER_AFTER_URL_SLEEP = 500

### Cycling URL
#
URL=http://webhost-temp1/Docs
URL_SHORT_NAME="Documents Dir"
REQUEST_TYPE=GET
WEB_AUTH_METHOD=NTLM
WEB_AUTH_CREDENTIALS=administrator:password
TIMER_URL_COMPLETION = 0 # In msec. When positive, Now it is enforced by cancelling url fetch on timeout
TIMER_AFTER_URL_SLEEP = 500

### Cycling URL
#
URL=http://webhost-temp1/Docs/Documents/ethernet.pdf
URL_SHORT_NAME="Ethernet PDF"
REQUEST_TYPE=GET
WEB_AUTH_METHOD=NTLM
WEB_AUTH_CREDENTIALS=administrator:password
TIMER_URL_COMPLETION = 0 # In msec. When positive, Now it is enforced by cancelling url fetch on timeout
TIMER_AFTER_URL_SLEEP = 500

### Cycling URL
#
URL=http://webhost-temp1/Docs/Documents/CHG-DOC-10MB-1.doc
URL_SHORT_NAME="Word Doc"
REQUEST_TYPE=GET
WEB_AUTH_METHOD=NTLM
WEB_AUTH_CREDENTIALS=administrator:password
TIMER_URL_COMPLETION = 0 # In msec. When positive, Now it is enforced by cancelling url fetch on timeout
TIMER_AFTER_URL_SLEEP = 500



rick parker : rp...@ce...<mailto:rp...@ce...> :  d 781 425 5200 x224 : www.certeon.com<http://www.certeon.com>
certeon - Accelerate Your Business

From: cur...@li... [mailto:cur...@li...] On Behalf Of Robert Iakobashvili
Sent: Thursday, March 06, 2008 2:03 PM
To: curl-loader-devel
Subject: Re: 401.2 messages

Hi Richard,
On Thu, Mar 6, 2008 at 8:58 PM, Richard Parker <rp...@ce...<mailto:rp...@ce...>> wrote:

Hello,

I am using curl-loader to help me stress test a caching/proxy server.

The server I am using on the other end is a MOSS 2007 web-server.

I receive a good amount of 401.2 messages and am unsure if curl knows that this should prompt the client to start the NTLM 3 way handshake or not.

Please, provide the detailed PRF form.

--
Sincerely,
Robert Iakobashvili
"Light will come from Jerusalem"
...........................................................
http://curl-loader.sourceforge.net
An open-source web testing and traffic generation.

Re: 401.2 messages

[Robert I. <cor...@gm...>]

Hi Richard,

On Thu, Mar 6, 2008 at 8:58 PM, Richard Parker <rp...@ce...> wrote:

>  Hello,
>
> I am using curl-loader to help me stress test a caching/proxy server.
>
> The server I am using on the other end is a MOSS 2007 web-server.
>
> I receive a good amount of 401.2 messages and am unsure if curl knows that
> this should prompt the client to start the NTLM 3 way handshake or not.
>

Please, provide the detailed PRF form.

-- 
Sincerely,
Robert Iakobashvili
"Light will come from Jerusalem"
...........................................................
http://curl-loader.sourceforge.net
An open-source web testing and traffic generation.

401.2 messages

[Richard P. <rp...@ce...>]

Hello,
I am using curl-loader to help me stress test a caching/proxy server.
The server I am using on the other end is a MOSS 2007 web-server.
I receive a good amount of 401.2 messages and am unsure if curl knows that this should prompt the client to start the NTLM 3 way handshake or not.
I do have the following for each web-element so I think that I am using the correct NTLM parameters.
Anyone have an

### Cycling URL
#
URL=http://certeon-temp1/Docs/Documents/ethernet.pdf
URL_SHORT_NAME="Ethernet PDF"
REQUEST_TYPE=GET
WEB_AUTH_METHOD=NTLM
WEB_AUTH_CREDENTIALS=administrator:C3r130N
TIMER_URL_COMPLETION = 0 # In msec. When positive, Now it is enforced by cancelling url fetch on timeout
TIMER_AFTER_URL_SLEEP = 500

Re: Question about curl-loader

[Robert I. <cor...@gm...>]

Hi Noah,


On Tue, Feb 26, 2008 at 6:30 PM, Noah Krohn <mon...@gm...> wrote:

> I was wondering if you have ever used curl-loader to stress a generic TCP
> connection.  I have a torrent-like application that I'm working on testing
> and I'm trying to stress the tracker server.  The tool works marvelously for
> stressing the HTTP servers, but I can't figure out a way to have it stress a
> generic TCP connection.  Will the config files allow you to stress a TCP
> connection in this way or would it involve editing the source code?  I
> appreciate any advice you could offer.
>
> -Noah Krohn
>


Although you have picked out our private e-mails :-),
please, make your postings to the curl-loader-devel mailing list.
Thanks.

There are several tools for general TCP-stressing.
Most classical are collected here:
http://www.linux-foundation.org/en/Net:TCP_testing




-- 
Sincerely,
Robert Iakobashvili
"Light will come from Jerusalem"
...........................................................
http://curl-loader.sourceforge.net
An open-source web testing and traffic generation.

Dyslexia assistance web-site

[Robert I. <cor...@gm...>]

Since people on this list are wondering
about Michael and my activities and lower
development efforts at curl-loader, this is what we are doing
for several months:

www.ghotit.com

The context-spelling engine is at the site. We are correcting about 90% of
errors in the corpus
of the most heavy dyslectic texts (requires context), where
Microsoft Word and all other best spellers are at 35-40% level in the best
case. I do not think, however, that the site cab be useful for the "normal"
folks.

The site is not yet known to the public and is in the trial
stage, whereas some dyslectic users writing English are claiming, that
it is "the best tool" for them; such references serve for us as the source
of inspiration.

-- 
Sincerely,
Robert Iakobashvili
"Light will come from Jerusalem"
...........................................................
http://curl-loader.sourceforge.net
An open-source web testing and traffic generation.

Re: how does curl-loader use RTNETLINK

[Robert I. <cor...@gm...>]

Javier,

On Thu, Feb 21, 2008 at 2:33 PM, Javier Miranda <jam...@in...>
wrote:

> Ok, thanks for your fast reply!
> However, It would be useful that the loader, once when it has
> finished, could close or delete the secondary ip that assigns to the
> interface.


Agree. Y may wish to provide the patches for integration

>
> Additionally, it would be very helpul for me if you tell me how the
> loader allocates those directions and more especifically, how the
> server knows where to send back the responses to the virtual clients,
> since i have manually ping'ed the clients from the server without no
> response.


curl-loader allocated ip-addresses via netlink as the secondary addresses
and binds each virtual client to an address. Another option described in
FAQs is
to use the same ip-address for all clients and it could be an existing
address.

When you are ping-ing it goes by default thru the routing table.

ping with option -I  (capital I is for Interface) will make pin-ing via the
interface or IP-address, that follows:

#ping -I 192.168.1.100 192.168.1.1
send ICMP ECHO packet to the host/gateway 192.168.1.1 via ip-address
192.168.1.100 and not via
the routing table definitions.

Sincerely,
Robert Iakobashvili
"Light will come from Jerusalem"
...........................................................
http://curl-loader.sourceforge.net
An open-source web testing and traffic generation.

Re: how does curl-loader use RTNETLINK

[Javier M. <jam...@in...>]

Ok, thanks for your fast reply!
However, It would be useful that the loader, once when it has
finished, could close or delete the secondary ip that assigns to the
interface.
Additionally, it would be very helpul for me if you tell me how the
loader allocates those directions and more especifically, how the
server knows where to send back the responses to the virtual clients,
since i have manually ping'ed the clients from the server without no
response.
Sincerely,

On 2/20/08, Robert Iakobashvili <cor...@gm...> wrote:
> Hi Javier,
>
> On Feb 20, 2008 7:32 PM, Javier Miranda <jam...@in...> wrote:
>
> > add_secondary_ip_addrs - setting secondary IP 10.111.111.150
> > rtnl_talk(): RTNETLINK answers: File exists
>
> This means, that the secondary IP-address has been already
>  added to the interface, thus, it will be re-used
> >
> > add_secondary_ip_addrs - note: probably, the IP-address
> > "10.111.111.150/24" already exists.
> >
> > this is not really a problem when using the loader, but when I use the
> > same ip used by another machine (e.g. a virtual machine), the virtual
> > client replaces it (supplanting) and the host became unreachable (even
> > when curl-loader is down).
>
> Why to use the same IP? Y can use any IP-addresses, from any networks,
> just ensure routing.
>
>
> >
> > Do you know how to delete the file which is referenced by rtnl_talk()
> > ?, or if there is another way to solve this problem.
>
>
> Sure. The command ip is your friend:
> like # ip addr del .....
> look at #man ip
>
> Sincerely,
> Robert Iakobashvili
> "Light will come from Jerusalem"
> ...........................................................
>  http://curl-loader.sourceforge.net
> An open-source web testing and traffic generation.
> -------------------------------------------------------------------------
>  This SF.net email is sponsored by: Microsoft
>  Defy all challenges. Microsoft(R) Visual Studio 2008.
>  http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
>  curl-loader-devel mailing list
>  cur...@li...
> https://lists.sourceforge.net/lists/listinfo/curl-loader-devel
>
>


-- 
Javier Miranda
jam...@in...
8-552-6707

Re: TIMER_AFTER_URL_SLEEP question

[Pranav D. <pra...@gm...>]

On Tue, Feb 19, 2008 at 9:29 PM, Robert Iakobashvili
<cor...@gm...> wrote:
> Prahav,
>
>
> On Feb 19, 2008 11:46 PM, Pranav Desai <pra...@gm...> wrote:
> >
> >
> >
> > Well, the log I sent you was for only 5 users, so I dont see how it
> > could be a resource issue. In any case I will dig around a bit and see
> > if I have messed up something, especially with heavier load testing.
>
>
> The recommendations  are related to the "heavy" load.
> As you see in the FAQs, your memory should be about 35K per client and
> there are other issues in the FAQs.
>
>
> > Between, to set a proxy you can simply set the env. variable
> > (http_proxy=http://proxy_addr:prxoy_port) and libcurl will do it ...
> > pretty easy :-)
>
>
> So, we are supporting HTTP/FTP proxy right now. :)

thats right :-)

> I will add this tip to our FAQs.
>
>
> > Thanks for all your help.
> >
> > -- Pranav
>
> Thank  you.
>
> --
>
> Sincerely,
> Robert Iakobashvili
> "Light will come from Jerusalem"
> ...........................................................
>  http://curl-loader.sourceforge.net
> An open-source web testing and traffic generation.
> -------------------------------------------------------------------------
>  This SF.net email is sponsored by: Microsoft
>  Defy all challenges. Microsoft(R) Visual Studio 2008.
>  http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
>  curl-loader-devel mailing list
>  cur...@li...
>  https://lists.sourceforge.net/lists/listinfo/curl-loader-devel
>
>



-- 

------------------------------
http://pd.dnsalias.org

Re: how does curl-loader use RTNETLINK

[Robert I. <cor...@gm...>]

Hi Javier,

On Feb 20, 2008 7:32 PM, Javier Miranda <jam...@in...> wrote:

> add_secondary_ip_addrs - setting secondary IP 10.111.111.150
> rtnl_talk(): RTNETLINK answers: File exists


This means, that the secondary IP-address has been already
added to the interface, thus, it will be re-used

>
> add_secondary_ip_addrs - note: probably, the IP-address
> "10.111.111.150/24" already exists.
>
> this is not really a problem when using the loader, but when I use the
> same ip used by another machine (e.g. a virtual machine), the virtual
> client replaces it (supplanting) and the host became unreachable (even
> when curl-loader is down).


Why to use the same IP? Y can use any IP-addresses, from any networks,
just ensure routing.


> Do you know how to delete the file which is referenced by rtnl_talk()
> ?, or if there is another way to solve this problem.


Sure. The command ip is your friend:
like # ip addr del .....
look at #man ip

Sincerely,
Robert Iakobashvili
"Light will come from Jerusalem"
...........................................................
http://curl-loader.sourceforge.net
An open-source web testing and traffic generation.