All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] UDP multicast stream and NAT
Date: Mon, 12 Dec 2005 02:08:54 +0000	[thread overview]
Message-ID: <439CDBB6.5070307@dsl.pipex.com> (raw)
In-Reply-To: <20051207221003.32802.qmail@web60924.mail.yahoo.com>

Andy Furniss wrote:
> Gabriel wrote:
> 
>> Hi, my ISP is streaming some local concert using UDP
>> multicasting. I followed the instructions on the site which
>> described how to set VLC in order to view the stream, but
>> it didn't work. I am behind a Linux router/firewall doing
>> NAT. Using google, I quickly found out that the
>> netfilter/conntrack code doesn't support NATing multicast
>> traffic. I thought about bridging the internet facing
>> interface (eth0) and (one of) the internal interfaces (the
>> one my computer is plugged into). This way I could set my
>> IP to be public and no routing/NAT would be done on the
>> Linux box. The only problem is that the box has 2 more NICs
>> in it and there are other people connected to those NICs
>> that need to use that connection (hence need to be NATed).
>>
>> Then I tried thinking about a DMZ-like solution where my
>> box would be in the DMZ, but I can't see that working
>> either because I only have one public IP assigned.
>>
>> Can anyone think of any other way for me to be able to view
>> the stream?
>>
>> Thanks.
>>
> 
> I also don't think the bridging will work.
> 
> AIUI stateless NAT using ip doesn't work with 2.6 kernels so thinking 
> about iptables only.
> 
> Maybe you could get something working with the raw table, you can bypass 
> conntrack with that but then I am not sure if you could dnat it ...
> 
> There is another iptables target ROUTE maybe you could use that. If the 
> LAN PC is running Linux then you could setup a vlan/tunnel/something and 
> ROUTE it down there.
> 
> I would also ask this on the netfilter users list.

Anothe thought - I would tcpdump on the internet interface and check if 
you can see multicast traffic.

If you can then try making a normal dnat rule something like -

iptables -I PREROUTING -t nat -i ppp0 --src 224.0.0.0/4 -j DNAT --to 
192.168.0.3

I don't think my isp does multicast - so I have never tried to get it to 
work and haven't got a clue really :-)

Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2005-12-12  2:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-07 22:10 [LARTC] UDP multicast stream and NAT Gabriel
2005-12-09 20:53 ` Gabriel
2005-12-10 12:38 ` sophana
2005-12-11 21:21 ` Andy Furniss
2005-12-12  2:08 ` Andy Furniss [this message]
2005-12-12 22:35 ` Gabriel
2006-07-22 18:07 ` Andy Furniss

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=439CDBB6.5070307@dsl.pipex.com \
    --to=andy.furniss@dsl.pipex.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.