On Mon, 25 Jun 2001, Akshay Adhikari wrote: > hi, > not a solution to your problem, but just a thought on > what tcpdump is showing you. > just thinking.....is tcpdump getting confused because > of how libpcap works? > afaik, pcap filters the packet before it hits the IP > code, and returns you the packet ethernet header > onwards. Thats what i am hoping for ...that tcpdump picks up the packet much before the IP layer, because i dont want those packets to go directly to the IP layer. They should pass through my virtual layer where i strip off "myheader" and then pass it onto the IP layer. I need to see my packets at the destination machine and so i had to use tcpdump because some debugging printks that i put into net_bh() bombs (kernel panics) when handling so many packet types. I need to construct a few debugging statements which will take care of all permutations and combinations of pkts e.g. ARP, ICMP, TCP, UDP etc. etc. >So it wouldnt make a difference what you set > skb->nh.iph to. Tcpdump is just picking up the packet > given to it be pcap, and displaying it..... > > akshay > > --- Amit Kucheria <amitk@ittc.ku.edu> wrote: > > Hi Akshay, > > > > Thanks for your reply. > > > > I am looking at the ip_build_xmit() code, but i have > > a feeling that this > > is not my problem. The 16 bytes is the length of > > 'myheader' and is not > > something related to a multiple of 16 bytes. > > > > My packets travel from one machine to another but > > they dont go up the > > protocol stack on the destination machine. > > Following is the output of tcpdump at the > > destination machine for ping > > traffic that i am sending (ping data set to 0xff). - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org
