From: Patrick McHardy <kaber@trash.net>
To: Jonothan Kane <jonothan.kane@gmail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: IPv4 traffic in 802.2 LLC SNAP frames queued to netfilter ...
Date: Mon, 08 Dec 2008 16:30:04 +0100 [thread overview]
Message-ID: <493D3D7C.8010404@trash.net> (raw)
In-Reply-To: <217983a50812072021k6f184240l23c7c7f80a5b3220@mail.gmail.com>
Jonothan Kane wrote:
> Hey all;
>
> I've got 2 devices connected through a transparent bridge.
> One of the devices uses the old Ethernet frame format as
> datalink transport the other uses the common Ethernet II
> format. The Ethernet II formated frames are being
> received by the netfilter connection tracking, while the
> old style frames are not.
>
> Is this normal ?
>
> Are old style Ethernet frames just not sent to the netfilter
> connection tracking system?
>
> Thanks for any help or information.
Linux doesn't handle IP in SNAP and the bridge netfilter code
also doesn't.
prev parent reply other threads:[~2008-12-08 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 4:21 IPv4 traffic in 802.2 LLC SNAP frames queued to netfilter Jonothan Kane
2008-12-08 15:30 ` Patrick McHardy [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=493D3D7C.8010404@trash.net \
--to=kaber@trash.net \
--cc=jonothan.kane@gmail.com \
--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