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.