From: "Adam M" <lkml@irotas.net>
To: "Kyle Moffett" <mrmacman_g4@mac.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Creating virtual interface triggers an IGMPv3 Join to Multicast DNS
Date: Tue, 07 Aug 2007 09:15:27 -0400 [thread overview]
Message-ID: <1186492527.30132.1204156793@webmail.messagingengine.com> (raw)
In-Reply-To: <6CADE9C0-2EE3-4404-B33B-0941533933D2@mac.com>
Hi Kyle,
Ah-hah, you nailed it right on the head. I unknowingly had Bonjour
running (must be installed by default on Fedora Core 3), which started a
process 'mDNSResponder'. I'm guessing that's the bugger that's fire off
these multicast joins.
Thanks for the tip!
-Adam
On Tue, 7 Aug 2007 00:30:36 -0400, "Kyle Moffett" <mrmacman_g4@mac.com>
said:
> On Aug 06, 2007, at 19:37:47, Adam M wrote:
> > Hi folks,
> >
> > For some reason, every time I create a virtual interface (using
> > tun), the interface immediately generates an IGMPv3 Join packet for
> > group 224.0.0.251, which (according to Google) is Multicast DNS.
> >
> > This packet is generated automatically and consistently. I'm
> > wondering why this should be the case, and if it can be disabled.
>
> You don't happen to be running "avahi" or one of the other Zeroconf/
> Bonjour/Rendezvous/$P2P_BUZZWORD_OF_THE_WEEK local-network-discovery
> daemons, do you? Most of those keep an eye out for new network
> interfaces and automatically start pushing multicast packets down
> them as soon as they appear, which is the most likely explanation for
> what you are seeing; as opposed to a kernel issue.
>
> Cheers,
> Kyle Moffett
>
prev parent reply other threads:[~2007-08-07 13:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 23:37 Creating virtual interface triggers an IGMPv3 Join to Multicast DNS Adam M
2007-08-07 4:30 ` Kyle Moffett
2007-08-07 13:15 ` Adam M [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=1186492527.30132.1204156793@webmail.messagingengine.com \
--to=lkml@irotas.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mrmacman_g4@mac.com \
/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