From: ratheesh k <ratheesh.ksz@gmail.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Netfilter mailing list <netfilter@vger.kernel.org>
Subject: Re: printk mac address --hangs
Date: Fri, 14 May 2010 09:11:26 +0530 [thread overview]
Message-ID: <AANLkTinU5_rypwmxae3656PKIyyO4dNo_txoLegXmCFR@mail.gmail.com> (raw)
In-Reply-To: <AANLkTiks_dxzBC-TT58Y0EpjKniUVfEDry66meYFsFc5@mail.gmail.com>
On Fri, May 14, 2010 at 8:07 AM, ratheesh k <ratheesh.ksz@gmail.com> wrote:
> On Fri, May 14, 2010 at 12:56 AM, Jan Engelhardt <jengelh@medozas.de> wrote:
>>>Packets from lo will hit NF_IP_LOCAL_OUT hook ?
>>
>> Clearly.
>
> Could you please explain a little about the traversal of a local
> packet . say if i do : ping 127.0.0.1 .? what are the chains/hooks it
> will hit ?
>
> Is there any API to check whether it is a ether packet or not ?
> Thanks,
> Ratheesh
>
> On Fri, May 14, 2010 at 12:56 AM, Jan Engelhardt <jengelh@medozas.de> wrote:
>> On Thursday 2010-05-13 19:24, ratheesh k wrote:
>>
>>>On Thu, May 13, 2010 at 10:46 PM, Jan Engelhardt <jengelh@medozas.de> wrote:
>>>> Your hook received packets from all interfaces, including lo and
>>>> ethhdr-less tunnels.
>>>
>>>Packets from lo will hit NF_IP_LOCAL_OUT hook ?
>>
>> Clearly.
>>
>>>Could you please tell example for ether less packet ?
>>
>> As I said, all links that do not are of "ether" type (see `ip list`)
>>
>
OK , lo packet will hit INPUT and OUTPUT . loop packet wont have ether
header ?>
Is there any API to check whether it is a ether packet or not ?
Thanks,
Ratheesh
prev parent reply other threads:[~2010-05-14 3:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 15:45 printk mac address --hangs ratheesh k
2010-05-13 16:19 ` Jan Engelhardt
2010-05-13 17:07 ` ratheesh k
2010-05-13 17:16 ` Jan Engelhardt
2010-05-13 17:24 ` ratheesh k
2010-05-13 19:26 ` Jan Engelhardt
2010-05-14 2:37 ` ratheesh k
2010-05-14 3:41 ` ratheesh k [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTinU5_rypwmxae3656PKIyyO4dNo_txoLegXmCFR@mail.gmail.com \
--to=ratheesh.ksz@gmail.com \
--cc=jengelh@medozas.de \
--cc=netfilter@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).