[Xorp-users] Problem adding routes to custom devices

[Ben Greear]

On 05/19/2010 02:38 PM, Jeff Mitchell wrote:
> On 05/19/2010 04:06 PM, Ben Greear wrote:
>> On 05/19/2010 12:47 PM, Jeff Mitchell wrote:
>>> On 05/19/2010 02:16 PM, Ben Greear wrote:
>>>> It could indeed be a bug. You might try poking around in
>>>> the fea logic, adding debugging statements and such to see
>>>> if you can figure out what is happening.
>>>>
>>>> If you can get a reproducible test case that uses standard
>>>> linux kernels and no special software harness, I'll see
>>>> if I notice anything.
>>>
>>> I can try, creating a dummy or tun device and see if that happens.
>>>
>>>> Also, any errors of note in the xorp logs?
>>>
>>> Man, I'm an idiot. I expected to find ways to view xorp debugging
>>> information from within xorpsh; I actually looked through the user
>>> manual trying to find out how to view the debugging that I was turning
>>> on. Until you said this I didn't realize that it was probably in /var/log.
>>>
>>> I'll have to look at it and get back to you.
>>
>> When starting xorp rtrmgr, you can specify a log file.  That's probably
>> the preferred way to get logs.
>
> I don't see anything in the log files of note, grepping for things like
> the interface name and the route I'm trying to add.
>
> Here is "ip route" and "show route table ipv4 unicast final" when it
> works, with eth0.701:
>
> 192.168.71.0/24 dev eth0.701  proto kernel  scope link  src 192.168.71.11
> 192.168.81.0/24 dev eth0.801  proto kernel  scope link  src 192.168.81.1
> 172.18.8.0/24 dev eth0  proto kernel  scope link  src 172.18.8.143
> 169.254.0.0/16 dev eth0  scope link
> 192.168.0.0/16 via 192.168.71.1 dev eth0.701  proto xorp  metric 1 notify
> default via 172.18.8.1 dev eth0
>
>
> 192.168.0.0/16  [static(1)/1]
>                   >  to 192.168.71.1 via eth0.701/eth0.701
> 192.168.71.0/24 [connected(0)/0]
>                   >  via eth0.701/eth0.701
> 192.168.81.0/24 [connected(0)/0]
>                   >  via eth0.801/eth0.801
>
>
> Here is the same when it doesn't work, with abcd0:
>
> 192.168.71.0/24 dev abcd0  proto kernel  scope link  src 192.168.71.11
> 192.168.81.0/24 dev eth0.801  proto kernel  scope link  src 192.168.81.1
> 172.18.8.0/24 dev eth0  proto kernel  scope link  src 172.18.8.143
> 169.254.0.0/16 dev eth0  scope link
> default via 172.18.8.1 dev eth0
>
>
> show route table ipv4 unicast final
> 192.168.81.0/24 [connected(0)/0]
>                   >  via eth0.801/eth0.801
>
>
> I have a suspicion as to what may be wrong...here's the relevant output
> of "ip link":
>
> 4: eth0.801 at eth0:<BROADCAST,MULTICAST,UP,LOWER_UP>  mtu 1500 qdisc noqueue
>       link/ether 00:50:56:9e:1f:7f brd ff:ff:ff:ff:ff:ff
> 6: abcd0:<BROADCAST,MULTICAST,NOARP,UP,LOWER_UP>  mtu 1500 qdisc
> pfifo_fast qlen 100
>       link/void 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 brd
> ff:ff:ff:ff:ff:ff:00:00:00:00:00:00:00:00:00:00
> 7: pimreg at NONE:<NOARP,UP,LOWER_UP>  mtu 1472 qdisc noqueue
>       link/pimreg
>
> Note the type of "link/void" -- is it possible that XORP refuses to set
> routes pertaining to this link because of the link type, even though it
> will give the interface an IP address? If so, is there a way to disable
> this/fix this/prevent this? Or any other idea what's going wrong?

I'd say that's likely.  Can you just fix your network driver so that
it claims to be Ethernet?  That's what other virtual drivers, such as 'veth'
do...

You might look though the logs in detail, maybe searching for 'static', to
see if that module is complaining and not even attempting to set the route
through fea.

Thanks,
Ben

>
> Thanks,
> Jeff
>
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users


-- 
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc  http://www.candelatech.com