[Xorp-users] IGMP and Multicast question

expo01 at free.fr expo01 at free.fr
Tue Feb 5 05:51:11 PST 2008


Hi,

We are trying to make the following work, as a test platform for now, but then
it will be needed in a real case operation :

mcast source-------Linux smcroute---------LinuxXORP-------mcast receiver
           ^                             ^        ^       ^
           |                             |        |       |
       192.168.1.1 		        eth0	 eth1     192.168.3.4
                                   192.168.2.3  192.168.3.3

smcroute is present only in the case of the test platform, it will later be
substituted with a Juniper router on which we will have no interaction possible.

The MC source is sending MC data to 230.1.1.1 (for the test)
This MC flow is seen on the Linux XORP router, interface eth0 (wireshark)
The fact to start the MC receiving application triggers an IGMP report, seen on
eth1 of the Linux XORP router.
There is no routing of the MC flow from the input interface eth0 to the output
interface eth1, on the Xorp router.

Our understanding of what should occur is probably wrong, but we thought that
the IGMP report received from the MC receiver should be enough for the XORP
router to have the necessary information to be able to forward the stream
received on eth0 to eth1. What is not correct in this assumption ?

Thanks in advance for helping.

Vincent

xorp traces extract:

[ 2008/02/05 11:01:53 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1
vif_index = 0 src = 192.168.1.1 dst = 230.1.1.1
[ 2008/02/05 11:02:03 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1
vif_index = 0 src = 192.168.1.1 dst = 230.1.1.1
[ 2008/02/05 11:02:04 TRACE xorp_igmp MLD6IGMP ] TX IGMP_MEMBERSHIP_QUERY from
192.168.3.3 to 224.0.0.1
[ 2008/02/05 11:02:04 TRACE xorp_igmp MLD6IGMP ] RX IGMP_MEMBERSHIP_QUERY from
192.168.3.3 to 224.0.0.1 on vif eth1
[ 2008/02/05 11:02:08 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT
from 192.168.3.4 to 230.1.1.1 on vif eth1
[ 2008/02/05 11:02:08 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT
from 192.168.3.4 to 224.0.0.251 on vif eth1
[ 2008/02/05 11:02:10 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT
from 192.168.3.3 to 224.0.0.2 on vif eth1
[ 2008/02/05 11:02:11 TRACE xorp_igmp MLD6IGMP ] RX IGMP_V2_MEMBERSHIP_REPORT
from 192.168.3.3 to 224.0.0.22 on vif eth1
[ 2008/02/05 11:02:13 TRACE xorp_fea MFEA ] RX kernel signal: message_type = 1
vif_index = 0 src = 192.168.1.1 dst = 230.1.1.1


Xorp configuration file :

/**** Interface list ****/
interfaces {
  interface eth0 {
    description: ""
    disable: false
    default-system-config
  }
  interface eth1 {
    description: ""
    disable: false
    default-system-config
  }
}

/**** Forwarding engine ****/
fea {
  unicast-forwarding4 {
    disable: false
  }
  unicast-forwarding6 {
    disable: false
  }
}

plumbing {
  mfea4 {
    disable: false
    interface eth0 {
      vif eth0 {
        disable: false
      }
    }
    interface eth1 {
      vif eth1 {
        disable: false
      }
    }
    interface register_vif {
      vif register_vif {
        disable: false
      }
    }
    traceoptions {
      flag all {
        disable: false
      }
    }
  }
}

/**** IGMP ****/
protocols {
  igmp {
    disable: false
    interface eth1 {
      vif eth1 {
        disable:false
      }
    }
    traceoptions {
      flag all {
        disable: false
      }
    }
  }
}

protocols {
  fib2mrib {
    disable: false
  }
 }



More information about the Xorp-users mailing list