Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 17 Jul 1996 14:54:59 -0400 (EDT)
From:      Mike Newell <mnewell@kaizen.net>
To:        questions@freebsd.org
Cc:        multimedia@freebsd.org
Subject:   Multicast routing questions
Message-ID:  <Pine.SGI.3.92.960717141517.11177A-100000@dada.kaizen.net>

next in thread | raw e-mail | index | archive | help
About a year ago I had problems with multicast routing in 2.0R; at that
time I got some help from Soochon Radee and Bill Fenner.  I've since
upgraded to 2.1.0R and I find I still have the same problems.  To recap:

I have two FreeBSD machines connected together as below:


          Home Net                                Office Net
     +---------+---------+              +--------+-----------+------+
               |                                 |           |
               |                                 |           |
          +----+-----+                      +----+---+    +--+----+
          | bigpuppy +---[BSP]==//==[BSP]---+ Pentup |    | Cisco |
          +----------+                      +--------+    +-------+
                                                              |
                                                              V to MCI


Pentup is a Pentium 166 running FBSD 2.1R/mrouted V3.8.  It has a tunnel
connection to Internet MCI and provides MBONE access to our office net.
That works fine.

Pentup also has a PPP link over an ISDN line (BSP = BitSurfr Pro) to my
home machine, "bigpuppy".  Bigpuppy is also a Pentium 166 running FBSD
2.1R/mrouted V3.8.  Addressing is as follows:

         Pentup
           Ethernet (de0)      206.27.236.33/24
           PPP0                206.27.237.13/30
         Bigpuppy
           PPP0                206.27.237.14/30
           Ethernet (ed1)      206.27.237.17/28

thus the PPP link and the two Ethernets form their own networks.  [IP
routing table maintenance is currently very manual 'cause of the variable
subnets; I'm gonna install gated tonight... :-)]

[1] The first problem is when I bring up mrouted it does not like
interface PPP0 and I have to disable it.  This is a long standing problem;
even though the PPP interfaces are marked as multicast capable mrouted
will not recognize them.  Bill Fenner kindly sent me a patch back in
August (to "in_var.h"); I applied it to my current system and rebuilt the
kernel and mrouted on bigpuppy but it still fails.  :-( As a workaround
I've disabled the interface in the mrouted.conf file and establish a
tunnel between the machines.

[2] The second problem is sdr and sd do not see any sessions when run on
bigpuppy.  When run from hosts on the office net I DO see them, so it
looks like our multicast access to MCI is working just fine.
Unfortunately I don't have another machine on my home net that's running
multicast software (we had to borrow my spare FBSD machine for work...) so
I don't know if bigpuppy is actually forwarding multicast packets to the
Ethernet.

Pentup's mrouted.conf looks like:

  phyint ppp0 disable
  tunnel 206.27.236.33 204.70.74.61 metric 1 threshold 32
  tunnel 206.27.236.33 206.27.237.17 metric 1 threshold 16 rate_limit 100

and bigpuppy's looks like:

  phyint ppp0 disable
  tunnel 206.27.237.17 206.27.236.33 metric 1 threshold 16 rate_limit 100

When I start up the mrouted's I do see the traffic lights flash.  "netstat
-g" shows (a REALLY long list of) multicast routes being built.  "mrinfo"
from bigpuppy shows:

  127.0.0.1 (localhost.newell.arlington.va.us) [version 3.8,prune,genid,mtrace]:
    206.27.237.17 -> 0.0.0.0 (local) [1/1/querier/leaf]
    206.27.237.14 -> 0.0.0.0 (local) [1/1/disabled]
    206.27.237.17 -> 206.27.236.33 (pentup.kaizen.net) [1/16/tunnel]

and on Pentup I see:

  127.0.0.1 (localhost) [version 3.8]:
    206.27.236.33 -> 0.0.0.0 (local) [1/1/querier/leaf]
    206.27.237.13 -> 0.0.0.0 (local) [1/1/disabled]
    206.27.236.33 -> 204.70.74.61 (dec3800-2-fddi-0.Washington.mci.net) [1/32/tunnel]
    206.27.236.33 -> 206.27.237.17 (bigpuppy.newell.arlington.va.us) [1/16/tunnel/leaf]

so the tunnels appear to be up.  "tcpdump -i ppp0" on bigpuppy also shows
not only igmp traffic but also ip-in-ip packets when sd/sdr are running.
"map-mbone" on bigpuppy shows:

  Multicast Router Connectivity:

  206.27.237.13 (mcnsisdn.kaizen.net): alias for 206.27.236.33

  206.27.237.14 (mcnsisdn.newell.arlington.va.us): alias for 206.27.237.17

  206.27.237.17 (bigpuppy.newell.arlington.va.us): <v3.8>
      206.27.237.14:  206.27.237.14 (mcnsisdn.newell.arlington.va.us) [1/1/disabled]
      206.27.237.17:  206.27.236.33 (pentup.kaizen.net) [1/16/tunnel]
                      206.27.237.17 (bigpuppy.newell.arlington.va.us) [1/1/querier]

  206.27.236.33 (pentup.kaizen.net): <v3.8>
      206.27.237.13:  206.27.237.13 (mcnsisdn.kaizen.net) [1/1/disabled]
      206.27.236.33:  206.27.237.17 (bigpuppy.newell.arlington.va.us) [1/16/tunnel]
                      204.70.74.61 (dec3800-2-fddi-0.Washington.mci.net) [1/32/tunnel]
                      206.27.236.33 (pentup.kaizen.net) [1/1/querier]

  204.70.74.61 (dec3800-2-fddi-0.Washington.mci.net): no response to query

Soochon Radee sent me some patches for 2.0R in March of '95 to fix this
(they were pretty extensive); he said they had also been submitted to the
FBSD team for inclusion in the next release.  Are they still applicable to
2.1R?  Or is there some other fix I should be applying???

Thanks loads!

Mike





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SGI.3.92.960717141517.11177A-100000>