From: "Igor M Podlesny" <for.poige+linux.nf@gmail.com>
To: netfilter@vger.kernel.org
Subject: IP_MULTICAST_LOOP? /Re: Netfilter "sees" locally originated multicast traffic as external-incoming one/
Date: Sun, 23 Mar 2008 23:26:35 +0700 [thread overview]
Message-ID: <43d009740803230926g20ec6f5dgc17ff4ece45097f6@mail.gmail.com> (raw)
On 23/03/2008, Igor M Podlesny <for.poige+linux.nf@gmail.com> wrote:
> Hello!
>
> Recently my home network got additional network connection, so I
> decided to try using Zebra to see if the whole set-up would be simpler
> and easier to maintain. During the test period I've noticed that
> Netfilter "sees" locally originated multicast traffic as
> external-incoming one:
[...]
> I'm not sure neither whether is this a bug or "feature" nor is this
> Netfilter's bug/feature at all -- more likely it's the kernel's issue.
> May be it's due to RIPv2/Zebra's "glitches"(?). What would you say?
I dug a bit more and can suggest that RIPv2/Zebra sets
IP_MULTICAST_LOOP flag. But then another question arises: is there a
good way to detect such kind a traffic with Netfilter? I mean such a
way that excludes a possibility for bogus traffic being treated as
IP_MULTICAST_LOOP.
--
End of message. Next message?
reply other threads:[~2008-03-23 16:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=43d009740803230926g20ec6f5dgc17ff4ece45097f6@mail.gmail.com \
--to=for.poige+linux.nf@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