[Xorp-users] Xorp, pimsm and ethertap

[Mike Horn]

Hi Calum,

No problem, hopefully we'll get this figured out.  Changing the "next-hop" to the peer address will only affect BGP updates sourced from this router (the peer router won't like the updates because they have a NEXT_HOP of it's own address) so I would changee it to 10.0.0.122.

If you can send the output from "show" in configuration-mode, I want to see how the tunnel interface is configured in XORP and the FEA configuration.  I'm thinking there is something related to how XORP is registering the interface that is causing the issue, but we'll need to dig further to find out.

-mike

----- Original Message -----
From: Calum <caluml@gmail.com>
To: Mike Horn <mhorn@vyatta.com>
Cc: xorp-users@xorp.org
Sent: Friday, February 24, 2006 4:01:18 PM GMT-0700
Subject: Re: [Xorp-users] Xorp, pimsm and ethertap

Hello Mike,

(Thanks for your help with this, btw).

You did ask me to change next-hop to 10.0.0.122 which is the address
of the local host.
(I have changed next hop to 10.0.0.121 but no difference).

I think the peering is OK, as I receive the routes in "show bgp
routes". (But I'm new to xorp, so maybe not..)

Here is route -n

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
10.0.0.76        0.0.0.0         255.255.255.252 U     0      0       
0 tapanother
10.0.0.120       0.0.0.0         255.255.255.252 U     0      0        0 taphush
82.x.x.x       0.0.0.0         255.255.255.248 U     0      0        0 eth0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
0.0.0.0         82.x.x.x   0.0.0.0         UG    0      0        0 eth0

> show interfaces
taphush/taphush: Flags:<ENABLED,BROADCAST,MULTICAST> mtu 1500
        physical index 12
        ether 4a:12:38:a6:de:7c

The problem being unable to ping .122 (local) was just a firewall rule.

The link is up, and fine:
# ping 10.0.0.121
PING 10.0.0.121 (10.0.0.121) 56(84) bytes of data.
64 bytes from 10.0.0.121: icmp_seq=1 ttl=64 time=1.19 ms
64 bytes from 10.0.0.121: icmp_seq=2 ttl=64 time=0.735 ms

--- 10.0.0.121 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 0.735/0.962/1.190/0.229 ms