[Click] Packets Gets garbled !!!!

[Eddie Kohler]

Um, Mogul,

Thomas Paine is right: you need to get rid of the Ethernet header (if there is 
one) and use CheckIPHeader/MarkIPHeader to set the "IP header annotation".  If 
eth0 generates Ethernet, you'll also need a Classifier to select out the 
IP-in-Ethernet packets.

Eddie


Paine, Thomas Asa wrote:
> IM,
> 	I'm not 100% sure this is your problem, but if you don't first
> use CheckIPHeader, CheckIPHeader2, or MarkIPHeader BEFORE using a
> IPClassifier it will cause Segmentation faults.  I'm relatively knew to
> this framework, but from my little experience, I'm guessing this has to
> do with the headroom that is left in the packet buffer in the heap.  It
> allows for elements to grow headers without needing to reallocate
> memory.  This may be what is happening in your case.  By not first
> defining/marking the header offset, you are getting garbage back or
> running off the end of a buffer.  Hope this helps.  The IPClassifier
> documentation is where I first seen reference to this, but it may also
> be mentioned in your routing elements.
> 
> 
> Thanks, 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 
> Thomas Paine (paineta at uwec.edu) 
> University of Wisconsin - Eau Claire 
> Computing & Networking Services 
> garbage foo(garbage g){return(g);};  
> 
> 
> -----Original Message-----
> From: click-bounces at amsterdam.lcs.mit.edu
> [mailto:click-bounces at amsterdam.lcs.mit.edu] On Behalf Of Indian Mogul
> Sent: Saturday, October 02, 2004 8:07 PM
> To: click at amsterdam.lcs.mit.edu
> Subject: [Click] Packets Gets garbled !!!!
> 
> Hi, 
>      I have a very simple case for implementing a routing table (RT) in
> click and the output of the click is totally garbled. Here is my
> scenario:
> 
> <Config File>
> FromDevice(eth0) -> rt:: StaticIPLookup
> (129.107.0.0/16 0, 129.107.10.0/24 1, 0/0 2)
> 
> rt[0]-> ToDump (f0.dump, ENCAP IP);
> rt[1]-> ToDump (f1.dump, ENCAP IP);
> rt[2]-> ToDump (f2.dump, ENCAP IP);
> 
> </Config File>
> 
> I have the following problems: 
>  1. I am running click on a machine on
> 129.107.10.23/24
>  I find that all the output is directed toward f2.dump even though I
> have packets with dst addr 129.107.10.23 (me),
> 
> 2. The output of f2.dump is totally screwed up. Upon opening with
> ethereal I see src and dst addr as N/A.
> 
> 3. If I triy using with IPClassfier (with the appropriate syntax), I get
> a segmentation fault.
> 
> 4. I am running click 1.4.2 on linux 2.4.21
> 
> Thanks,
> IM 
> 
> 
> 		
> _______________________________
> Do you Yahoo!?
> Declare Yourself - Register online to vote today!
> http://vote.yahoo.com
> _______________________________________________
> 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