Again, confirm did not verify!

[tecoboot]

I opened this new ticket, which is probably a duplicate of #23. But the log of that ticket is a bit confusing...

When I have a network with quite a few nodes (15 or so), with some congestion (nearby test networks on same channel), I have the some nodes that log the "confirm did not verify!" over and over.

Fri Jun 3 10:32:52 2016 confirm did not verify
Fri Jun 3 10:32:52 2016 confirm did not verify!
Fri Jun 3 10:32:52 2016 confirm did not verify!
Fri Jun 3 10:32:53 2016 confirm did not verify!
Fri Jun 3 10:32:53 2016 confirm did not verify!
Fri Jun 3 10:32:53 2016 confirm did not verify!
Fri Jun 3 10:32:54 2016 confirm did not verify!
Fri Jun 3 10:32:54 2016 confirm did not verify!
Fri Jun 3 10:32:54 2016 confirm did not verify!
Fri Jun 3 10:32:54 2016 confirm did not verify!
Fri Jun 3 10:32:54 2016 confirm did not verify!
Fri Jun 3 10:32:55 2016 confirm did not verify!
Fri Jun 3 10:32:55 2016 confirm did not verify!
Fri Jun 3 10:32:55 2016 confirm did not verify!
Fri Jun 3 10:32:56 2016 confirm did not verify!
Fri Jun 3 10:32:56 2016 confirm did not verify!
Fri Jun 3 10:32:56 2016 confirm did not verify!
Fri Jun 3 10:32:56 2016 confirm did not verify!

With debug 15 and newline when idle:
3jun.txt

I restarted with debug=15 on all nodes, now it runs fine.
I'll restart some nodes and see what will happen.

[tecoboot]

After reboot of four nodes, two of them ran into problems. Tho other nodes (not rebooted) have also the problem.

MACs:
R21 00:0c:42:68:6d:ba
R26: 00:0c:42:68:6d:b0
R30: 00:0c:42:68:6d:c5
R178: 00:0c:42:68:6d:c3
(R21 and R26 were rebooted)

3jun-R21.txt
3jun-R26.txt
3jun-R30.txt
3jun-R178.txt

There is a negotiation loop between R21 and R30, and R26 and R178.