Looks like the problem might be that we are dropping a packet,
and the ospf code does not retransmit? I see this comment in peer.cc:
/**
* XXX
* The outgoing packets should be queued on the transmit queue, for
* the time being just send them straight out.
*/
template <typename A>
bool
PeerOut<A>::transmit(typename Transmit<A>::TransmitRef tr)
{
In the logs, I never see DataDescriptionReceived in the Exchange State:
[EMAIL PROTECTED] lanforge]# grep DataDescription x12.txt|grep "99.1.1.2"
[ 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)
[ 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)
But, I do see an LoadingDone message, though it will be ignored since we are in
the wrong state:
[ 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)
Off to try to figure out how we're supposed to do retransmits.
Ben
--
Ben Greear <[EMAIL PROTECTED]>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
Xorp-hackers mailing list
[email protected]
http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers
