Subject: (fwd) Carlos Picoto: PIMv1 on Linux

From: "John M. Zwiebel" <[email-masked]>
Date: Tue, 11 Mar 1997 14:51:49 -0800

It may be under development, but it does exist.

z

------- Forwarded Message

From:  Carlos Picoto <[email-masked]>
Subject:  PIMv1 on Linux

  Hello all,
  
  Quick introduction
  ----
  Our group at  University of Lisbon has contributed for  the IPv6 stack availa
	  ble in Linux ([email-masked]). 
  We are now devoting our efforts to provide PIMv2 on IPv4 and IPv6.
  
  W've started with the PIMd implementation from Ahmed Helmy
  and after a "downgrade" and a lot of byte ordering coding,  it talks with PIM
	  v1 (Dino Sparse Mode Flag).
  In the following example ranger.di.fc.ul.pt is provinding multicast connectiv
	  ity for the 194.117.20 subnet
  ranger is a P100, wih 2 ethernet cards 
  
  gt-ul>mrinfo
  192.67.76.15 (gt-difcul.di.fc.ul.pt) [version cisco 11.1] [flags: PMS]:
    192.67.76.15 -> 192.67.76.155 (ranger.di.fc.ul.pt) [1/1/pim]
    192.67.76.15 -> 192.67.76.13 (gt-rdis.di.fc.ul.pt) [1/1/pim]
    193.137.1.4 -> 193.137.1.1 (LISBOA-GTRCCN13.smds.rccn.net) [1/1/pim]
    193.137.1.4 -> 193.137.1.5 (LISBOA-LIP.smds.rccn.net) [1/1/pim]
    193.137.1.4 -> 193.137.1.8 (LISBOA-CNIG.smds.rccn.net) [1/1/pim]
    192.67.76.15 -> 194.117.20.10 (sitio.di.fc.ul.pt) [1/1/tunnel/querier/disab
	  led
  /down/leaf]
  
  gt-ul>sh ip pim neighbor
  PIM Neighbor Table
  Neighbor Address  Interface          Uptime    Expires   Mode
  192.67.76.155     Ethernet1/0        00:58:49  00:01:30  Sparse       (DR)
  192.67.76.13      Ethernet1/0        1w1d      00:01:21  Sparse
  193.137.1.1       Serial2/0          5d08h     00:01:20  Sparse
  193.137.1.5       Serial2/0          5d08h     00:01:10  Spa
  193.137.1.8 Serial2/0

  [cap@ranger cap]$ cat /proc/net/ip_mr_vif
  Interface      Bytes In  Pkts In  Bytes Out  Pkts Out  Flags Local    Remote
   0 eth0           2601       33       448         5   00030 192.67.76.155 
   1 eth1           1752       24         0         0   00030 194.117.20.231 
   2 pim_reg           0        0         0         0   000A0 192.67.76.155 

  [cap@ranger cap]$ cat /proc/net/ip_pim_neighbors
  
  PIM Neighbor Table
  Neighbor Address  Interface      Uptime   Expires  Mode
    192.67.76.15       eth0       00:01:45  00:26:38 Sparse
    192.67.76.13       eth0       00:01:53  00:26:46 Sparse
  
  [cap@ranger cap]$ cat /proc/net/ip_pim_mroute
  
  Multicast Routing Table
       Source         Group     Incoming Outgoing           Flags
  (192.67.76.160,224.2.127.253), (Pkts:1, Bytes:32, WrIif:0)
    Incoming interface: eth0, RPF nbr 192.67.76.160
    Outgoing interface list:
           eth1, Forward, 00:02:03/00:01:33, threshold  1
  
  (192.67.76.14,224.1.127.255), (Pkts:3, Bytes:84, WrIif:0)
    Incoming interface: eth0, RPF nbr 192.67.76.14
    Outgoing interface list:
           eth1, Forward, 00:03:02/00:02:32, threshold  1
  
  (192.67.76.160,224.2.127.254), (Pkts:2, Bytes:64, WrIif:0)
    Incoming interface: eth0, RPF nbr 192.67.76.160
    Outgoing interface list:
           eth1, Forward, 00:03:06/00:02:36, threshold  1

  
  The IPv4 kernel changes will be integrated in the Linux development version 2
	  .1.21
  The pimd provides basic PIMv1 funcionality.
  Next Steps: 
  -Support the mtools 
  -Activate the V2 code on IPv4 
  -IPV6 kernel support

  If anyone wants to try this just drop me an e-mail.
  ./Carlos Picoto
  University of Lisbon

------- End of Forwarded Message