From: "Sebastian" <basti79@basti79.de>
To: netfilter@lists.netfilter.org
Subject: RE: Forwarding Multicast Traffic
Date: Tue, 10 Feb 2004 12:26:11 +0100 [thread overview]
Message-ID: <000201c3efc8$b06829e0$0200a8c0@basti79> (raw)
In-Reply-To: <F5200854-5AD1-11D8-87C2-000A95C71776@freezone.co.uk>
Hi there...
As you said multicast traffic is normaly not routed. But you can do a
view steps to do this. First enable multicast support and multicast
routing in the routers linux kernel. I've tried to route multicast
packets with the iptables -j ROUTE target IIRC, but that doesn't seem to
work. The much cleaner is to use the multicast routing daemon (mrouted).
On debian systems you can easily apt-get the packet, on other systems i
suggest to google around.
Greets
Basti.
> -----Original Message-----
> From: netfilter-admin@lists.netfilter.org
> [mailto:netfilter-admin@lists.netfilter.org] On Behalf Of
> ms419@freezone.co.uk
> Sent: Monday, February 09, 2004 8:31 AM
> To: netfilter@lists.netfilter.org
> Subject: Forwarding Multicast Traffic
>
>
> 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?
>
> Thanks very much,
>
> Jack
>
>
>
next prev parent reply other threads:[~2004-02-10 11:26 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
2004-02-10 11:26 ` Sebastian [this message]
-- 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='000201c3efc8$b06829e0$0200a8c0@basti79' \
--to=basti79@basti79.de \
--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