[Xorp-users] Xorp-users Digest, Vol 70, Issue 10
Edwin Schokkenbroek
edwin at spacebugs.nl
Mon Jan 30 15:24:54 PST 2012
Hello Ben,
Thanks for your reply.
>>
>> 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?
That is the strange part. The configuration isn't changed between switching versions. For example on R4. When I do a show of interface and protocol options, they look the same:
beheer at R4> show version
Version 1.8.5
beheer at R4>
beheer at R4> show interfaces
epair1a/epair1a: Flags:<ENABLED,BROADCAST,MULTICAST> mtu 1500 speed unknown
inet 10.1.100.1 subnet 10.1.100.0/30 broadcast 10.1.100.3
physical index 2
ether 02:cb:55:00:04:0a
epair2a/epair2a: Flags:<ENABLED,BROADCAST,MULTICAST> mtu 1500 speed unknown
inet 10.1.100.5 subnet 10.1.100.4/30 broadcast 10.1.100.7
physical index 3
ether 02:33:5d:00:04:0a
beheer at R4# show interfaces
interface epair1a {
vif epair1a {
address 10.1.100.1 {
prefix-length: 30
broadcast: 10.1.100.3
}
}
}
interface epair2a {
vif epair2a {
address 10.1.100.5 {
prefix-length: 30
}
}
}
beheer at R4# show protocols ospf4
router-id: 10.1.100.1
area 0.0.0.0 {
interface epair1a {
vif epair1a {
address 10.1.100.1 {
}
}
}
interface epair2a {
vif epair2a {
address 10.1.100.5 {
}
}
}
beheer at R4> show version
Version 1.8-CT
beheer at R4> show interfaces
epair1a/epair1a: Flags:<ENABLED,BROADCAST,MULTICAST> mtu 1500 speed unknown
inet 10.1.100.1 subnet 10.1.100.0/30 broadcast 10.1.100.3
physical index 2
ether 02:c7:55:00:04:0a
epair2a/epair2a: Flags:<ENABLED,BROADCAST,MULTICAST> mtu 1500 speed unknown
inet 10.1.100.5 subnet 10.1.100.4/30 broadcast 10.1.100.7
physical index 3
ether 02:c3:55:00:04:0a
beheer at R4# show interfaces
interface epair1a {
vif epair1a {
address 10.1.100.1 {
prefix-length: 30
broadcast: 10.1.100.3
}
}
}
interface epair2a {
vif epair2a {
address 10.1.100.5 {
prefix-length: 30
}
}
}
beheer at R4# show protocols ospf4
router-id: 10.1.100.1
area 0.0.0.0 {
interface epair1a {
vif epair1a {
address 10.1.100.1 {
}
}
}
interface epair2a {
vif epair2a {
address 10.1.100.5 {
}
}
}
>
> Ever done a 'git bisect'? That should tell us what commit
> caused the problem..though it can take a while.
I don't know git enough to understand this, but if it helps to solve to problem I can try it. What do I have to do exactly ? Just run: 'git bisect' ?
Edwin Schokkenbroek
>
> Thanks,
> Ben
>
> --
> Ben Greear <greearb at candelatech.com>
> Candela Technologies Inc http://www.candelatech.com
>
>
>
> ------------------------------
>
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
>
>
> End of Xorp-users Digest, Vol 70, Issue 10
> ******************************************
The night, as a mystic wall. I like dry balconies. The sounds rising from the darkened city... The yellow light gives me no comfort at all.
More information about the Xorp-users
mailing list