[Xorp-users] BadPeer ...: Area ... not handled by eth0/eth0

[Atanu Ghosh]

Hi,

The message is telling you that OSPF packets are being received on
eth0/eth0 from a router which is in area 217.64.164.128, which in your
configuration is area 0.0.0.0. If you change your configuration to area
217.64.164.128 you will probably be able to peer with your upstream
routers.

	      Atanu.

>>>>> "Dirk" == Dirk H Schulz <dirk.schulz at kinzesberg.de> writes:

    Dirk> Hi Folks, I am new to running routers on my own and new to
    Dirk> Xorp and OSPF.

    Dirk> I have setup two routers using ospf. They are two
    Dirk> communication with two upstream routers using ospf as
    Dirk> well. Now my own routers find each other as neighbors (the do
    Dirk> not find the upstream routers, but that is a problem I have to
    Dirk> solve with the upstream provider, I think).

    Dirk> They seem to work, my routers, but both put out the following
    Dirk> message every few seconds:

    Dirk> 	BadPeer from line 379 of peer.cc: Area 217.64.164.128
    Dirk> not handled by eth0/eth0

    Dirk> I have not found anything relating in the docs, in Google nor
    Dirk> elsewhere.

    Dirk> 217.64.164.128 is the subnet used for area 0.0.0.1 on
    Dirk> interface bond0 on both routers. I do not understand why it
    Dirk> should be handled by eth0 which has a setting of
    Dirk> 217.64.170.238/29 resp. 217.64.170.230/29.

    Dirk> This is the configuration of one router, the other is nearly
    Dirk> identical (just other IP addresses):

    >> interfaces { restore-original-config-on-shutdown: true
    >> 
    >> interface eth0 { description: "external (area0) interface"
    >> disable: false default-system-config }
    >> 
    >> interface eth1 { description: "inter router interface" disable:
    >> false default-system-config }
    >> 
    >> interface bond0 { description: "area1 bonding interface" disable:
    >> false default-system-config } /* interface bond1 { description:
    >> "area2 bonding interface" disable: false default-system-config }
    >> */ }
    >> 
    >> fea { unicast-forwarding4 { disable: false forwarding-entries {
    >> retain-on-startup: false retain-on-shutdown: false } }
    >> unicast-forwarding6 { disable: true forwarding-entries {
    >> retain-on-startup: false retain-on-shutdown: false } } }
    >> 
    >> protocols { ospf4 { router-id: 217.64.170.238
    >> 
    >> area 0.0.0.0 { area-type: "normal" interface eth0 { vif eth0 {
    >> address 217.64.170.238 { priority: 128 hello-interval: 5
    >> router-dead-interval: 15 interface-cost: 1 retransmit-interval: 2
    >> transit-delay: 1 disable: false } } } interface eth1 { vif eth1 {
    >> address 192.168.11.1 { priority: 128 hello-interval: 5
    >> router-dead-interval: 15 interface-cost: 2 retransmit-interval: 2
    >> transit-delay: 1 disable: false } } } }
    >> 
    >> area 0.0.0.1 { area-type: "normal" interface bond0 { vif bond0 {
    >> address 217.64.164.129 { priority: 128 hello-interval: 5
    >> router-dead-interval: 15 interface-cost: 2 retransmit-interval: 2
    >> transit-delay: 1 disable: false } } } } /* area 0.0.0.2 {
    >> area-type: "normal" interface bond1 { vif bond1 { address
    >> 217.64.170.60 } } } */ } }

    Dirk> Any ideas? Every hint or help is appreciated.

    Dirk> Thanks in advance,

    Dirk> Dirk


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