BPQ32 link check/polling bug?
- Just me or is this odd? Looks like the "node polling" gets itself into a bit of a loop at times? THis is "node polling" traffic between MOBRA (KB0WSA-6) and KYWIL (WA4ZKO-5):
13:11:54R KB0WSA-6>WA4ZKO-5 Port=8 <RR C P R0>
13:11:54T WA4ZKO-5>KB0WSA-6 Port=8 <RR R F R0>
13:11:55R KB0WSA-6>WA4ZKO-5 Port=8 <D C P>
13:11:55T WA4ZKO-5>KB0WSA-6 Port=8 <UA R F>
13:12:01R KB0WSA-6>WA4ZKO-5 Port=8 <C C P>
13:12:01T WA4ZKO-5>KB0WSA-6 Port=8 <UA R F>
13:12:10R WA4ZKO-6>WA4ZKO-5 Port=8 <RR C P R0>
13:12:10T WA4ZKO-5>WA4ZKO-6 Port=8 <RR R F R0>
13:13:49R KB0WSA-6>WA4ZKO-5 Port=8 <RR C P R0>
13:13:49T WA4ZKO-5>KB0WSA-6 Port=8 <RR R F R0>
and more of pretty much the same...
Causes the obsolescence counter to start decrementing down for a node that is still there:
KYWIL:WA4ZKO-5} Routes to: MOBRA:KB0WSA-6
207 3 8 KB0WSA-6
Then eventually the node (MOBRA in this case) is gone:
KYWIL:WA4ZKO-5} Not found
Seems most of the time the next nodes broadcast will clear things up. Sometimes it will not "fix" itself and the route will drop out for a bit as if the other node went off the air (but it's there).
When this happens initially, I've caught the other node with a wild (triple digit) obsolescence count if I do a N NODECALL on it.
Example: Not the "240" obs count.
KYWIL:WA4ZKO-5} Routes to: CTGATE:WA4ZKO-6 RTT=1 FR=48 B 1
> 207 240 8 WA4ZKO-6Anyone else seeing this? If you didn't watch fairly closely you may not even notice it (outside of brief intermittent loss of connectivity to an node) as it usually fixes itself in a few minutes. The route drops out, then the next node broadcast rebuilds it back.