Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Bob Yeaw <byeaw@widevine.com>
To: lartc@vger.kernel.org
Subject: [LARTC] building a multicast router
Date: Wed, 29 Jan 2003 17:42:16 +0000	[thread overview]
Message-ID: <marc-lartc-104386209517289@msgid-missing> (raw)

[-- Attachment #1: Type: text/plain, Size: 2666 bytes --]

Hi,

I have been reading: http://lartc.org/howto/lartc.multicast.html in effort
to understand how to route multicast traffic and just joined the group.

History: I am trying to multicast mpeg (using the videolan server) on a
private network.   The server side of the network is copper gigabit, which
connects to one of those cheap fast Ethernet switches with a single gigabit
uplink.   The problem I'm having is the ports are getting flooded on the
client side switch (i.e., all multicast traffic sent to all ports on the
switch).

After doing some research it sounds like installing a multicast router
between the client and server side is the best solution.  So that's what I'm
trying to do now.

I have Red hat Linux 7.3 installed. I've gone through the steps described on
the how-to (link above):

$ demsg | grep IGMP 
IP Protocols: ICMP, UDP, TCP, IGMP
$ cat /proc/sys/net/ipv4/ip_forward
1
$ netstat -rn
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt
Iface
192.168.3.0     0.0.0.0         255.255.255.0   U        40 0          0
eth1
10.100.100.0    0.0.0.0         255.255.255.0   U        40 0          0
eth0
127.0.0.0       0.0.0.0         255.0.0.0       U        40 0          0 lo
224.0.0.0       0.0.0.0         240.0.0.0       U        40 0          0
eth1
0.0.0.0         10.100.100.254  0.0.0.0         UG       40 0          0
eth0

# NOTE: eth1 is the client side, eth0 is the server side.

Problem:
The problem is that no multicast is getting through the router (unicast
traffic works fine).  When I run:

$ tcpdump -n -i eth0

I see all of the multicast traffic being sent. Unfortunately:

$ tcpdump -n -i eth1

shows none of that multicast traffic (whether the client has requested it or
not). Interestingly, when I run iptraf and select eth0 it reports little to
no activity, which indicates to me that the traffic is getting dropped at a
low level.

Question:
My question at this point is problem identification.  Is the router
configured correctly and acting as expected but the client just isn't
sending the IGMP join requests?  Do I need to install additional software
packages like Zebra or mrouted to make this work?  Am I completely missing
something?  

Any help or suggestions are greatly appreciated!

regards,

-bob



-bob



CONFIDENTIALITY NOTICE:  The information in this electronic mail
transmission contains confidential information intended only for the use of
the individual or entity named above.  If the reader of this message is not
the intended recipient, you are hereby notified that any dissemination,
distribution or copy of the transmission is strictly prohibited.

[-- Attachment #2: Type: text/html, Size: 4916 bytes --]

                 reply	other threads:[~2003-01-29 17:42 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=marc-lartc-104386209517289@msgid-missing \
    --to=byeaw@widevine.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox