From: Simon Tennant <simon@imaginator.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Multicast love
Date: Thu, 16 Mar 2006 09:20:12 +0000 [thread overview]
Message-ID: <20060316092012.GA9194@imaginator.com> (raw)
I am trying to get multicast traffic to traverse 3 different subnets
call connected to the same linux router. This is primarily to get
rendezvous/zeroconf services working for Macs on the network. Being
able to experiment with the VideoLAN client's multicasting abilities
would be a bonus.
I see that rendezvous sends out packets with a TTL of 1 and expects
them back with a TTL of 255 so I guess I will have to do some packet
mangling in iptables.
The limited documentation out there recommends running a multicast
router like PimD. What does this add to the setup? Surely it's just a
cast of some iptables rules allowing 224/4 between networks?
Am I missing the point here? Any good documents on multicast?
S.
--
Simon Tennant ________________ http://imaginator.com/~simon/contact
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
reply other threads:[~2006-03-16 9:20 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=20060316092012.GA9194@imaginator.com \
--to=simon@imaginator.com \
--cc=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.