[Xorp-users] xorp configuration question

[Pavlin Radoslavov]

[Apology for the late response; I am still trying to catch-up with
old email...]

> I'm trying to implement the following configuration:
> I've a router with CentOS 4 installed. The bonding is configured and
> iptables/cbq/quagga are running. bond1 - is the interface where
> clients subnets are terminated on configured subinterfaces (approx. 20
> subinterfaces). Only IPv4 is supported.
> I would like to install and run XORP for multicast traffic routing
> between clients (bond1) and other network (bond0) (bond0 is not
> configured now in XORP, I know; this will be the next step).
> Here is my config.boot:

<DEL>

> Output of `xorprtr_mgr -v' may be found here:
> http://awanti.com/xorp.debug
> 
> The problematic places in that output are delimited with '---'.
> So, the questions are:
> 1. What 'no interface found' means? What cannot be found and why?

The FEA has tried to decode the NETLINK info about an unicast
forwarding entry, but that entry didn't contain the next-hop
interface index. Eventually, adding some printf() to method
NlmUtils::nlm_get_to_fte_cfg() inside fea/netlink_socket_utils.cc
aided by the output from the "netstat -rn" or "ip route list"
commands may help to discover the problematic entry. 

> 2. Why 'Target "fea" does not exist or is not enabled' message comes up? The
> fea part is actually configured.
> 3. 'Target "IGMP" does not exist or is not enabled'. The same
> question.

You can safely ignore the (2) and (3) messages above. In your case
those are transient startup messages that may appear while the
particular module is starting.

> 4. What 'RX packet from 192.168.25.227 to 239.255.255.250: no vif
> found' means? How to configure XORP to understand that traffic?

The MFEA has received a multicast packet and that packet is suppose
to come from a directly-connected host. However, 192.168.25.227
doesn't belong to any of the configured subnet addresses, hence the
MFEA rejects it.

If 192.168.25.227 is indeed a directly-connected source, you would
have to configure a network interface with a subnet address that
covers 192.168.25.227 .


Pavlin