[Xorp-hackers] OSPF stuck in Exchange state.

[Atanu Ghosh]

Hi,

The comment is mis-leading and has been removed.

    Atanu.

>>>>> "Ben" == Ben Greear <greearb at candelatech.com> writes:

    Ben> Looks like the problem might be that we are dropping a packet,
    Ben> and the ospf code does not retransmit?  I see this comment in peer.cc:

    Ben> /**
    Ben> * XXX
    Ben> * The outgoing packets should be queued on the transmit queue, for
    Ben> * the time being just send them straight out.
    Ben> */
    Ben> template <typename A>
    Ben> bool
    Ben> PeerOut<A>::transmit(typename Transmit<A>::TransmitRef tr)
    Ben> {

    Ben> In the logs, I never see DataDescriptionReceived in the Exchange State:

    Ben> [root at lf1016-55 lanforge]# grep DataDescription x12.txt|grep "99.1.1.2"
    Ben> [ 2007/10/22 14:30:47 TRACE xorp_ospfv2 OSPF ] Event(DataDescriptionReceived-pseudo-event) Interface(12.16.12/12.16.12) Neighbour(99.1.1.2) State(ExStart)
    Ben> [ 2007/10/22 14:30:49 TRACE xorp_ospfv2 OSPF ] Event(DataDescriptionReceived-pseudo-event) Interface(12.16.12/12.16.12) Neighbour(99.1.1.2) State(ExStart)

    Ben> But, I do see an LoadingDone message, though it will be ignored since we are in the wrong state:

    Ben> [ 2007/10/22 14:30:51 TRACE xorp_ospfv2 OSPF ] Event(LoadingDone) Interface(12.16.12/12.16.12) Neighbour(99.1.1.2) State(Exchange)


    Ben> Off to try to figure out how we're supposed to do retransmits.

    Ben> Ben


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