[Xorp-users] Multicast testbed
Garry Peirce
peirce at maine.edu
Wed Apr 7 07:13:06 PDT 2010
Looks like you're seeing PIM Hellos on interfaces you should not be.
Given - 'My network : Server --->Switch --> xorp1 --->xorp2--->Client',
none of these errors should be seen on Xorp1.
WARNING xorp_pism3 PIM ] RX PIM_HELLO from 10.10.10.2 to 224.0.0.13 on vif
eth0: source must be directly connected
WARNING xorp_pism3 PIM ] RX PIM_HELLO from 192.168.1.199 to 224.0.0.13 on
vif eth0: source must be directly connected
WARNING xorp_pism3 PIM ] RX PIM_HELLO from 192.168.1.199 to 224.0.0.13 on
vif eth1: source must be directly connected
Perhaps you may actually all these interfaces on the same switch in the same
vlan - ?
From: xorp-users-bounces at xorp.org [mailto:xorp-users-bounces at xorp.org] On
Behalf Of Shaila Jimenez
Sent: Wednesday, April 07, 2010 6:58 AM
To: xorp-users at xorp.org
Subject: {Disarmed} [Xorp-users] Multicast testbed
Hi users!
I'm trying to run xorp in a multicast scenario using Ubuntu and VLC as a
server streamer. Previously, i used xorp in a basic multicast topology and
all was fine (server ---> xorp router --> client). Now i want to use two
xorp routers (then if works, i have until 8 routers). I've read all the
official documentation and other xorps user's messages but i still don't
understand some warnings that appears when xorp starts.
My network : Server --->Switch --> xorp1 --->xorp2--->Client
Server (VLC stream to 232.10.10.10 and ttl=3)
- eth0: 192.168.0.10 (Internal LAN)
- eth1: Internet
XORP 1
- eth0: 192.168.0.199
- eth1: 10.10.10.1
XORP 2:
- eth5: 10.10.10.2
- eth6: 192.168.1.199
Client (VLC)
- eth0: 192.168.1.22 (gateway 192.168.1.199)
No other gateways are configured.
* The two routers had this modules configured (see config files below):
interfaces, fea, mfea4, igmp, pimsm4, fib2mrib.
* I'm using satic routes (see config files below).
* RP: the xorp1 is configured as a satic rps.
When i start xorp1,xorp2 and vlc i see a lot of warnings and i dont now what
im doing wrong.
XORP1:
WARNING xorp_pism3 PIM ] RX PIM_HELLO from 10.10.10.2 to 224.0.0.13 on vif
eth0: source must be directly connected
WARNING xorp_pism3 PIM ] RX PIM_HELLO from 192.168.1.199 to 224.0.0.13 on
vif eth0: source must be directly connected
WARNING xorp_pism3 PIM ] RX PIM_HELLO from 192.168.1.199 to 224.0.0.13 on
vif eth1: source must be directly connected
WARNING xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.1.22
to 224.0.0.22 on vif eth1: source must be directly connected
WARNING xorp_igmo MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_QUERY from 192.168.1.199
to 224.0.0.1 on vif eth0: source must be directly connected
WARNING xorp_igmp MLD6IGMP ] RX IGMP_V3_MEMBERSHIP_REPORT from 192.168.0.10
to 224.0.0.22 on vif eth1: source must be directly connected
XORP2:
WARNING xorp_pism3 PIM ] RX PIM_HELLO from 192.168.0.199 to 224.0.0.13 on
vif eth6: source must be directly connected
WARNING xorp_pism3 PIM ] RX PIM_HELLO from 192.168.0.199 to 224.0.0.13 on
vif eth5: source must be directly connected
WARNING xorp_pism3 PIM ] RX PIM_HELLO from 10.10.10.1 to 224.0.0.13 on vif
eth6: source must be directly connected
WARNING xorp_fea FEA ] proto_socket_read() failed:RX packet from 10.10.10.1
to 224.0.0.1 pif_index 6: no vif found
TRACE xorp_pimsm4 PIM ] RX WRONGVIF signal from MFEA_4: vif_index= 1 src =
192.168.0.10 dst=239.255.10.10 (a lot of this type)
I can see video in the client but the quality is very poor :(
What is wrong...the xorps or my network's config? i need to add other
gateways at the network's config?
Any help would be appreciated.
Thanks.
============================================================================
=============
XORP1 CONFIG:
interfaces {
interface eth0 {
description: "ethernet0"
disable: false
default-system-config
}
interface eth1 {
description: "ethernet1"
disable: false
default-system-config
}
}
fea {
unicast-forwarding4 {
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
}
}
}
}
protocols {
igmp {
disable: false
interface eth0 {
vif eth0 {
version: 3
disable: false
}
}
interface eth1 {
vif eth1 {
version: 3
disable: false
}
}
traceoptions {
flag all {
disable: true
}
}
}
}
protocols {
pimsm4 {
disable: false
interface eth0 {
vif eth0 {
disable: false
}
}
interface eth1 {
vif eth1 {
disable: false
}
}
interface register_vif {
vif register_vif {
disable: false
}
}
static-rps {
rp 192.168.0.199 {
group-prefix <http://224.0.0.0/4> MailScanner has detected a
possible fraud attempt from "224.0.0.0" claiming to be 224.0.0.0/4 {
}
}
}
protocols {
static {
mrib-route <http://192.168.1.0/24> MailScanner has detected
a possible fraud attempt from "192.168.1.0" claiming to be 192.168.1.0/24 {
next-hop: 10.10.10.2
}
}
}
switch-to-spt-threshold {
/* aprox. 1K bytes/s (10Kbps) threshold */
disable: false
interval: 100
bytes: 102400
}
traceoptions {
flag all {
disable: true
}
}
}
}
protocols {
fib2mrib {
disable: false
}
}
XORP 2 CONFIG:
interfaces {
interface eth5 {
description: "Ethernet5"
disable: false
default-system-config
}
interface eth6 {
description: "Ethernet6"
disable: false
default-system-config
}
}
fea {
unicast-forwarding4 {
disable: false
}
}
plumbing {
mfea4 {
disable: false
interface eth5 {
vif eth5 {
disable: false
}
}
interface eth6 {
vif eth6 {
disable: false
}
}
interface register_vif {
vif register_vif {
disable: false
}
}
traceoptions {
flag all {
disable: false
}
}
}
}
protocols {
igmp {
disable: false
interface eth5 {
vif eth5 {
version: 3
disable: false
}
}
interface eth6 {
vif eth6 {
version: 3
disable: false
}
}
traceoptions {
flag all {
disable: true
}
}
}
}
protocols {
pimsm4 {
disable: false
interface eth5 {
vif eth5 {
disable: false
}
}
interface eth6 {
vif eth6 {
disable: false
}
}
interface register_vif {
vif register_vif {
disable: false
}
}
static-rps {
rp 192.168.0.199 {
group-prefix <http://224.0.0.0/4> MailScanner has detected a
possible fraud attempt from "224.0.0.0" claiming to be 224.0.0.0/4 {
}
}
}
protocols {
static {
mrib-route <http://192.168.0.0/24> MailScanner has detected
a possible fraud attempt from "192.168.0.0" claiming to be 192.168.0.0/24 {
next-hop: 10.10.10.1
}
}
}
switch-to-spt-threshold {
/* aprox. 1K bytes/s (10Kbps) threshold */
disable: false
interval: 100
bytes: 102400
}
traceoptions {
flag all {
disable: true
}
}
}
}
protocols {
fib2mrib {
disable: false
}
}
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20100407/aeb765da/attachment-0001.html
More information about the Xorp-users
mailing list