RE: mc_forwarding Option in sys.net.ipv4.conf.all

RE: mc_forwarding Option in sys.net.ipv4.conf.all

[Brian Raymond]

My hope was that IGMP proxying/routing is something that's implemented in
Linux (how Windows pulls it off) so that it would just be a matter of
turning it on and setting a couple of config options. Right now the network
uses PIM-DM & IGMPv2 on the routers. I haven't found a decent daemon, which
does PIM-DM, and I'm a little concerned with the daemon forwarding all of
the MC traffic to the clients. There is a lot of MC traffic on the network
and the groups are very dynamic so from the sounds of it I'm going to have
to hash through a routing daemon to get things to work.

Thanks for the info. 



Brian Raymond

--
Systems Engineering
Joint Warfighting Center
116 Lakeview Parkway
Suffolk, VA 23435
757-686-7135

-----Original Message-----
From: Pekka Savola [mailto:pekkas@netcore.fi]
Sent: Friday, May 10, 2002 9:38 AM
To: Brian Raymond
Cc: 'linux-kernel@vger.kernel.org'; 'linux-ppp@vger.kernel.org';
'linux-net@vger.kernel.org'
Subject: Re: mc_forwarding Option in sys.net.ipv4.conf.all

On Fri, 10 May 2002, Brian Raymond wrote:
> I've been working on a Linux PPTP VPN server for clients that require
> multicasting. I only have one physical interface in the box and I'm using
> the PoPToP package for PPTP support. Getting the VPN setup and working
> hasn't been a problem, getting the multicast traffic to flow between the
ppp
> and eth0 interface is causing me a whole lot of problems. What do I need
to
> do so that I can tell the kernel to forward all relevant multicast traffic
> through to the clients (in essence just a simple IGMP router)? I've been
> looking at mrouted, pimd-dense and mrtd but haven't had any luck getting
> them to work because of the dynamic nature of the PPP interfaces.

You need to run mrouted, pimd (sparse or dense) or something like on the
router.  Can't you just restart the daemon when the PPP interface switches
state?

An alternative mechanisms would be:
 - using bridging (not applicable in this scenario)
 - doing IGMP proxying and other tricks on the router (haven't been
implemented at least in Linux AFAIK).

--
Pekka Savola                 "Tell me of difficulties surmounted,
Netcore Oy                   not those you stumble over and fall"
Systems. Networks. Security.  -- Robert Jordan: A Crown of Swords

mc_forwarding Option in sys.net.ipv4.conf.all

[Brian Raymond]

Mostly support question, send to kernel list because of confusion with
mc_forwarding being set as read only.

I've been working on a Linux PPTP VPN server for clients that require
multicasting. I only have one physical interface in the box and I'm using
the PoPToP package for PPTP support. Getting the VPN setup and working
hasn't been a problem, getting the multicast traffic to flow between the ppp
and eth0 interface is causing me a whole lot of problems. What do I need to
do so that I can tell the kernel to forward all relevant multicast traffic
through to the clients (in essence just a simple IGMP router)? I've been
looking at mrouted, pimd-dense and mrtd but haven't had any luck getting
them to work because of the dynamic nature of the PPP interfaces.

My backup is a W2K server which I've had some luck getting to work but I
would really hate to use it unless I need to because there is a huge
political battle raging right now about Linux being a sub standard OS.

Thanks.

Brian Raymond

Re: mc_forwarding Option in sys.net.ipv4.conf.all

[Pekka Savola]

On Fri, 10 May 2002, Brian Raymond wrote:
> I've been working on a Linux PPTP VPN server for clients that require
> multicasting. I only have one physical interface in the box and I'm using
> the PoPToP package for PPTP support. Getting the VPN setup and working
> hasn't been a problem, getting the multicast traffic to flow between the ppp
> and eth0 interface is causing me a whole lot of problems. What do I need to
> do so that I can tell the kernel to forward all relevant multicast traffic
> through to the clients (in essence just a simple IGMP router)? I've been
> looking at mrouted, pimd-dense and mrtd but haven't had any luck getting
> them to work because of the dynamic nature of the PPP interfaces.

You need to run mrouted, pimd (sparse or dense) or something like on the 
router.  Can't you just restart the daemon when the PPP interface switches 
state?

An alternative mechanisms would be:
 - using bridging (not applicable in this scenario)
 - doing IGMP proxying and other tricks on the router (haven't been 
implemented at least in Linux AFAIK).

-- 
Pekka Savola                 "Tell me of difficulties surmounted,
Netcore Oy                   not those you stumble over and fall"
Systems. Networks. Security.  -- Robert Jordan: A Crown of Swords