[Xorp-users] Xorp 1.8.5 OSPF adjacencies problems on FreeBSD 8.2 with jails.

[Ben Greear]

On 01/29/2012 12:46 PM, Edwin Schokkenbroek wrote:
> Hello list,
>
> When I upgrade Xorp to version 1.8.5 it seems that OSPF has trouble forming adjacencies. I use FreeBSD 8.2 and running the Xorp inside jails. OSPF is configured on virtual ethernet interfaces (epair). The configuration is simple: Two jails are connected together by an epair interface.
>
> I upgraded Xorp by moving the original version out of the way:
>
> cd /usr/local
> mv xopr xorp-1.8
>
> After that I rebooted to machine, so that only the operating system is started. No jails are started or Xorp.
>
> Then I cloned the git repository with git clone, compiled and installed Xorp.
>
> When I created the jails again, and starting Xorp, OSPF is not forming any neighborship.
>
> The configuration used in both cases are exactly the same.
>
> Before I upgraded to Xorp 1.8-CT
>
> beheer at R4>  show version
> Version 1.8-CT
> beheer at R4>
>
>
> [start]#>  Welcome to XORP on R4
> beheer at R4>  show ospf4 neighbor
>    Address         Interface             State      ID              Pri  Dead
> 10.1.100.2       epair1a/epair1a        Full      10.1.100.2       128    38
> 10.1.100.6       epair2a/epair2a        Full      10.1.100.6       128    37
> beheer at R4>
>
> With Xorp 1.8.5 OSPF isn't working:
>
> [start]#>  Welcome to XORP v1.8.5 on R4
> Version tag: 92efc7d  Build Date: 2012-01-29 20:11 64-bit
>
> Version 1.8.5
> beheer at R4>  show ospf4 neighbor
>    Address         Interface             State      ID              Pri  Dead
> beheer at R4>
>
>
> When I move the 1.8.5 version out of the way, and moving back the 1.8 tree, everything works again.
> In the log file I see the next error:
>
> [ 2012/01/29 21:30:37.814126  ERROR xorp_ospfv2:4699 OSPF ospf/xrl_io.cc:162 send_cb ] Cannot send a packet on interface epair2a vif epair2a: 102 Command failed Error while sending to vif: epair2a:epair2a  src: 10.1.100.5  dest: 224.0.0.5:  sendmsg(proto 89 size 64 from 10.1.100.5 to 224.0.0.5 on interface epair2a vif epair2a) failed: Invalid argument
>
> Any help on this is much appreciated

Does the IP in the error message in match the interface?

Ever done a 'git bisect'?  That should tell us what commit
caused the problem..though it can take a while.

Thanks,
Ben

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