From: Ray Leach <raymondl@knowledgefactory.co.za>
To: Netfilter Mailing List <netfilter@lists.netfilter.org>
Subject: Re: Forwarding Multicast Traffic
Date: Tue, 10 Feb 2004 13:17:48 +0200 [thread overview]
Message-ID: <1076411868.2827.0.camel@raylinux.internal> (raw)
In-Reply-To: <F5200854-5AD1-11D8-87C2-000A95C71776@freezone.co.uk>
[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]
On Mon, 2004-02-09 at 09:31, ms419@freezone.co.uk wrote:
> Two machines communicate with one another using multicast - mDNS - when
> they are on the same network segment. When they are on separate network
> segments, however - though they can connect to one another across a
> router - they can't communicate using multicast. I presume that this is
> because the router isn't forwarding multicast traffic to other network
> segments? The router is running Linux kernel version 2.4.23 and
> iptables. How can I configure iptables to forward multicast traffic to
> other network segments?
>
Make sure you have the appropriate FORWARD and -t nat PREROUTING (if you
use NAT) rules to forward the multicast traffic (224.0.0.0)
> Thanks very much,
>
> Jack
--
--
Raymond Leach <raymondl@knowledgefactory.co.za>
Network Support Specialist
http://www.knowledgefactory.co.za
"lynx -source http://www.rchq.co.za/raymondl.asc | gpg --import"
Key fingerprint = 7209 A695 9EE0 E971 A9AD 00EE 8757 EE47 F06F FB28
--
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-02-10 11:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-09 7:31 Forwarding Multicast Traffic ms419
2004-02-10 11:17 ` Ray Leach [this message]
2004-02-10 11:26 ` Sebastian
-- strict thread matches above, loose matches on Subject: below --
2004-02-10 11:32 hclfm
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=1076411868.2827.0.camel@raylinux.internal \
--to=raymondl@knowledgefactory.co.za \
--cc=netfilter@lists.netfilter.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