[Xorp-users] FW: Unwanted Multicast ipv4 forwarding

[Pauchard Yves]

Hello,

 

I think I found the error: The source, destination and both XORP machine
ports are connected to the same switch... The XORP machine does not need
to route the Multicast packets, since the switch already forwards them
to all the ports (like a broadcast). I found this when the destination
received the multicast packets without XORP running.

 

I am sorry for the inquiry - it was not a XORP problem.

 

Regards,

 

Yves 

 

________________________________

From: Pauchard Yves 
Sent: May 8, 2006 9:01 AM
To: 'xorp-users at xorp.org'
Subject: Unwanted Multicast ipv4 forwarding

 

Hello,

 

I have the following network architecture :

 

     RP \ 

            --------- XORP ----- Destination

Source /

 

I want to use PIM on XORP to forward multicast streams from a VLC server
to one network to the other. See the configuration of XORP at the end of
this email.

 

Everything seems to work fine, Multicast SAP announcements are
propagated from the RP and the Source to the destination and I can
connect to a multicast stream from a VLC server on Source with a VLC
client on Destination.

 

The problem is, that as soon as the VLC server stream is turned on (RTP,
IP_destination=239.255.12.42), XORP forwards all these packets to the
Destination network, although no client is connected to the stream. Why
would that be?

 

I get these messages in the stdout from XORP when the VLC server is
running:

 

[ 2006/05/05 16:49:07 TRACE xorp_fea MFEA ] RX kernel signal:
message_type = 2 vif_index = 1 src = XX.XX.31.32 dst = 239.255.12.42

[ 2006/05/05 16:49:07 TRACE xorp_pimsm4 PIM ] RX WRONGVIF signal from
MFEA_4: vif_index = 1 src = XX.XX.31.32 dst = 239.255.12.42

 

Thanks for your help.

 

Regards,

 

Yves

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20060509/071807f4/attachment.html