[Click] Questions of Click's Source Elements

[Eddie Kohler]

Bita

Elements that generate packets with Ethernet headers require the entire 
contents of the Ethernet headers to be specified.  I have no idea why 
you think this is unnecessary.  You can always specify 0:0:0:0:0:0 as a 
destination address, have fun getting such packets to your intended 
destination.

Rated, Random, and InfiniteSource generate raw arrays of data.  If you 
include (in the DATA argument) the bytes corresponding to an IP header, 
then you can direct the result to MarkIPHeader and get IP packets.

Eddie



betamaz wrote:
> Hi,
> 
> Can anyone explain to me why many source elements in click (such as 
> FastUDPFlows, FastTCPFlows, FastUDPSource) require that the ethernet address 
> of both source and destination to be specified? It seems to me that forcing 
> the user to include the ethernet address of the destination creates a lot of 
> unnessary work (might even hinder the sender).
> 
> 
> Second, what type of packets do RatedSource, RandomSource, InfiniteSource 
> create? They're not IP packets. Based on the info I got using ethereal I 
> think they're eth2 type packets.
> 
> Thanks a bunch,
> Bita.
> _______________________________________________
> click mailing list
> click at amsterdam.lcs.mit.edu
> https://amsterdam.lcs.mit.edu/mailman/listinfo/click
>