It would be better if you attach the real Wireshark dump. I need to see sequence numbers, gaps etc.
///jon Xpl++ wrote: > Hi Jon, > > Read below .. > > Jon Paul Maloy ??????: > >> This scenario can easily be confirmed by doing a >> wireshark dump when a link goes stale. If you even >> could catch the moment when it happens, i.e. see the >> packet that is never delivered, we would have a good >> clue to follow. >> >> Wireshark... >> >> > Well, I managed to do a wireshark dump and force the link to .. fail or > whatever :) > The sequence of events looks like this: > > A > B: fragmenter: first > A > B: fragmenter: fragment * 10 > A > B: fragmenter: last > > ... this repeats several times with 2 * (B > A: link state: state) > almost always present somewhere within that 12 pack sequence ... and > then ... > > A > B: fragmenter: first > A > B: fragmenter: fragment * 8 [note it probably should have been 10, > as 95% ot fragmented packets in my cluster are 16K sent over mtu of 1500] > B > A: payld: norej: directmsg [this is an unrelated communication by > other threads] > B > A: payld: norej: namedmsg [this seems to be the first pack of a > SEQPACKET connection using implicit connect, made by some other thread] > B > A: payld: norej: namedmsg [yet another like the one above] > B > A: link state: state > A > B: link state: state > B > A: link state: state [these 3 link state msgs happen within 0.1ms > (!) so probably the A>B link state pack is not related to the B>A ones > .. those always tend to come in pairs] > > ... and from that point on the only thing comming from A are (A > B: > link state: state) packets with B _always_ responding immediately with a > (B > A: link state: state) packet. Apart from that B seems to be just > trying to continue business as usual. > 10 seconds later I see a long sequence of (B > A: payld: norej: > directmsg ErrNoPort) and then again B just tries to send it's standart > directmsg/namedmsg queries to A, but nothing really happens. > > A link reset (disable/enable bearer @B) restore normal operation. > Wireshark dump was done @B. > So .. I got this far. Any ideas? > > Regards > Peter Litov. > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > tipc-discussion mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/tipc-discussion > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ tipc-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tipc-discussion
