netdev
[Top] [All Lists]

Re: loopback packet processing.

To: MANJUNATH <manjunath@xxxxxxxxxxxxxxxxx>
Subject: Re: loopback packet processing.
From: Harsh <hanemade@xxxxxxxxx>
Date: Wed, 15 Dec 2004 14:38:54 +0530
Cc: netdev@xxxxxxxxxxx
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=cw8DsdbKbdQ5ZHwW1Yr7N02rOM62WxQ53xOPFsYOYbNK0yuUm6FeS/722ZHSrHWrPwNOZQ4x8WBsVkutsIfm16C48TdeAREnADYtOnZk5Fa4NpDKi8CnNcyECIBUXZFAbe+aPgf+fPsIz05n0NM5J9DKxN2uMfc/sFAmOPe+DzU=
In-reply-to: <Pine.BSF.4.58.0412141649050.71544@ece.iisc.ernet.in>
References: <cfc9593604121402424f2a9ba5@mail.gmail.com> <Pine.BSF.4.58.0412141649050.71544@ece.iisc.ernet.in>
Reply-to: Harsh <hanemade@xxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
Hi MANJUNATH,
         I actually did a lot work on kernel packet processing and 
found that ping packet creation enters in ethernet.c.
           Also can you tell me what happens in ip_finish_output2 when
ping ICMP packet is created by kernel? what header is added there.
            Also in receving end control enters in ethernet.c to check
eth->h_proto field which is ETH_P_IP. How & where it is added by
kernel in case of PING packet?

regards,
Harsh.

On Tue, 14 Dec 2004 16:53:33 +0530 (IST), MANJUNATH
<manjunath@xxxxxxxxxxxxxxxxx> wrote:
> 
> 
> Hi,
> 
>   When u send data to the loopback address, control never
>   Enters "ethernet" modules.(Data link layer)
> 
>   Since ping inturn uses program interface to ICMP which is a part
>   of IPV4 s/w, for loopback ping IP modules themselves replies. Ethernet
>   does not come into picture.
> 
> cheers,
> Manjunath
> 
>

<Prev in Thread] Current Thread [Next in Thread>