[Click] generating random destination IP packets?

[Eddie Kohler]

Hi Azeem,

1. Yes, I believe both SetRandIPAddress and AnonymizeIPAddress can 
generate broadcast addresses, although SetRandIPAddress can generate 
random addresses *within a prefix*, which can avoid multicast.  Patches 
welcome.

2. Kernel or user space?  Our tests were in user space -- special 
handling might be required for the kernel, haven't looked into it.

Eddie


Azeem Khan wrote:
> Hello everyone,
> 
> Oh good. Now I have two methods to do almost the same thing. Thanks a lot Eddie and Breyer. I will try using this second method also.
> 
> Actually right now CPU performance does not seem to be a bottleneck, the I/O bus seems to be the one. I just cannot saturate my gigabit link. I have NAPI enabled in the Linux 2.6.16.13 kernel but Click is not able to do device polling (only FromDevice). I am using 32-bit Intel PCI 82540EM cards. I will be looking into that next.
> 
> I have a couple of questions though,
> 
> 1. The RandIPAddress / AnonymizeIPAddress elements: Can they generate invalid addresses like network addresses or broadcast addresses or anything else which might get dropped by the router?
> 
> 2. I want to use the routing table for stress testing that you have posted in the comparison review of all the different routing lookup implementations; the one with 167K entries. But, when I use it, I get an out of memory error. Do I need to recompile Click with some options /changes? (I have 2GB RAM on the system under test).
> 
> 
> Thank You.
> 
> Azeem Khan.
> Bombay, India.
> 
> 
> 
> ________________________________
>> Date: Fri, 20 Apr 2007 09:46:14 +0200
>> From: bcronje at gmail.com
>> To: kohler at cs.ucla.edu
>> Subject: Re: [Click] generating random destination IP packets?
>> CC: azeem_k at hotmail.com; click at pdos.csail.mit.edu
>>
>> Oops, sorry Azeem. I didn't know about StoreIPAddress :)
>> On 4/19/07, Eddie Kohler > wrote:
>> Hi Azeem,
>> You are missing one additional step: StoreIPAddress.
>> FastUDPSource -> SetRandIPAddress -> StoreIPAddress(16) ->
>> SetUDPChecksum -> SetIPChecksum should do it.
>> If you are really trying to max out your outgoing bandwidth, you might
>> want to alter FastUDPSource to set random destination IP addresses
>> yourself, to avoid the additional checksums. But don't optimize
>> prematurely, of course: wait and see if you have a problem.
>> Eddie
>> Azeem Khan wrote:
>>> Hello everyone,
>>>
>>> I wish to generate UDP/IP packets with random destination IP addresses at different rates. From reading the Click element documentation, I believe that FastUDPSource + SetRandIPAddress + SetUDPChecksum + SetIPChecksum should do the trick. Am I correct?
>>>
>>> Will SetRandIPAddress also set the IP destination address randomly besides the annotation?
>>>
>>> If so, can anyone give me an example on how to use the SetRandIPAddress element? I cannot seem to get it right. I am not clear on what the arguments mean.
>>>
>>>
>>> Thank You.
>>>
>>> Azeem Khan
>>> Bombay, India.
>>> _________________________________________________________________
>>> Get the new Windows Live Messenger!
>>> http://get.live.com/messenger/overview
>>> _______________________________________________
>>> click mailing list
>>> click at amsterdam.lcs.mit.edu
>>> https://amsterdam.lcs.mit.edu/mailman/listinfo/click
>> _______________________________________________
>> click mailing list
>> click at amsterdam.lcs.mit.edu
>> https://amsterdam.lcs.mit.edu/mailman/listinfo/click
> 
> _________________________________________________________________
> Search from any Web page with powerful protection. Get the FREE Windows Live Toolbar Today!
> http://toolbar.live.com/?mkt=en-in