On Mon, Oct 17, 2005 at 10:57:41AM -0400, stan wrote:
> On Mon, Oct 17, 2005 at 04:12:48PM +0159, Claudio Jeker wrote:
> > On Mon, Oct 17, 2005 at 09:39:01AM -0400, stan wrote:
>
> Hmm, that seems to have gotten me close. Here's the new ospfd.conf file:
>
>
> # $OpenBSD: ospfd.conf,v 1.2 2005/02/06 20:07:09 norby Exp $
>
> # global configuration
> router-id 170.85.113.111
>
> # areas
> area 0.0.0.120 {
> interface fxp0 {
> auth-type none
> }
> interface fxp2 {
> auth-type none
> passive
> }
> }
>
<config stripped a bit>
> And when I start up the ospfd executbale now I get:
>
>
> Script started on Mon Oct 17 10:38:04 2005
> phfw1# ospfd -d
> startup
> rde: new announced net 0.0.0.0/0
> rde: new announced net 170.85.106.128/25
> rde: new announced net 170.85.106.143/32
> rde: new announced net 170.85.113.0/25
> rde: new announced net 170.85.113.99/32
> rde: new announced net 192.168.254.0/24
> orig_rtr_lsa: area 0.0.0.120
> orig_rtr_lsa: stub net, interface carp1
> orig_rtr_lsa: stub net, interface carp0
> if_fsm: event UP resulted in action START and changing state for interface
> carp0 from DOWN to WAITING
> start_spf_timer: IDLE -> DELAY
> recv_packet: invalid checksum, interface carp0
> recv_packet: authentication error, interface carp0
> spf_calc: calculation started, area ID 0.0.0.120
> spf_calc: calculation ended, area ID 0.0.0.120
> spf_start_holdtimer: DELAY -> HOLD
> spf_timer: state HOLD -> IDLE
> recv_packet: invalid checksum, interface carp0
> recv_packet: authentication error, interface carp0
> recv_packet: invalid checksum, interface carp0
> recv_packet: authentication error, interface carp0
> recv_packet: invalid checksum, interface carp0
> recv_packet: authentication error, interface carp0
...
That is not the config you pasted before. You are running OSPF
over carp here. This is nuts and will not work. You can not run any kind
of routing protocol over carp without major issues! If you have two
routers in front of a common network use carp towards that network and
OSPF to connect the two routers to the backbone.
If one router fails ospf will take care and adjust the routing table.
Currently I think you need to use "redistribute static" for that setup or
wait a couple of days till I fixed something.
> phfw1# op ospfd -d
> startup
> orig_rtr_lsa: area 0.0.0.120
> rde: new announced net 0.0.0.0/0
> rde: new announced net 170.85.106.128/25
> rde: new announced net 170.85.106.143/32
> rde: new announced net 170.85.113.0/25
> rde: new announced net 170.85.113.99/32
> rde: new announced net 192.168.254.0/24
> orig_rtr_lsa: stub net, interface fxp2
> orig_rtr_lsa: stub net, interface fxp0
> if_fsm: event UP resulted in action START and changing state for interface
> fxp0 from DOWN to WAITING
> start_spf_timer: IDLE -> DELAY
> nbr_fsm: event HELLO_RECEIVED resulted in action START_INACTIVITY_TIMER and
> changing state for neighbor ID 170.85.115.1 from DOWN to INIT
> nbr_fsm: event 2_WAY_RECEIVED resulted in action EVAL and changing state for
> neighbor ID 170.85.115.1 from INIT to 2-WAY
> if_fsm: event NEIGHBORCHANGE resulted in action NOTHING and changing state
> for interface fxp0 from WAITING to WAITING
> recv_packet: packet sent to wrong address 170.85.113.99, interface fxp0
> spf_calc: calculation started, area ID 0.0.0.120
> spf_calc: calculation ended, area ID 0.0.0.120
> spf_start_holdtimer: DELAY -> HOLD
> recv_packet: packet sent to wrong address 170.85.113.99, interface fxp0
> spf_timer: state HOLD -> IDLE
> recv_db_description: packet ignored in state 2-WAY, neighbor ID 170.85.115.1
> recv_packet: packet sent to wrong address 170.85.113.99, interface fxp0
I bet 170.85.113.99 is the carp IP.
...
> I;ve confirmes with ethreal that the "invalid chcksum" errors are indeed
> invalid checksums being sent by the router that I'm exchanging routes with.
>
Iiick!
> But if I chage the interfaces to carp0, and carp1, which are respectively
> the "outside", and "inside" carp interfaces for this amchine, things don't
> work even this well:
>
As I said before don't run ospf over carp. It will not work. You can use
it fot the inside network but not for the one connected to the backbone.
> At this point in time I'm not even receiving the routes my neighber router
> is sending.
>
--
:wq Claudio
