Tunnel connection isn't fault tolerant

I have never had a problem with either of my hAP nodes failing to reconnect after an internet outage without having to power cycle them.  My primary hAP-at-home normally has several tunnels where the hAP is the client, and several tunnels where the hAP is the server.  In both conditions, the tunnels reconnect.

 

I doubt it's the version.  I have run every release version since 3.19.something and damn near every nightly build in between.
 

I just did a test with my hAP-at-Home node.  Prior to the test, there were three tunnels where my hAP was the tunnel server, and two tunnels where my hAP was the tunnel client.  For the test, I disabled VLAN 1 in my router.  This would result in all packets from the internet destined to the tunnel, and all packets from the hAP outbound on VLAN 1 ending up in the bit bucket.  The physical port 1 on the hAP would still be connected to the LAN switch, so there would be no change of status of the port itself.  It took a couple minutes before the hAP showed that all the tunnels were down, but as expected, they did go down.

After a couple minutes, I re-enabled VLAN 1 in my router and started watching the tunnel status pages in the hAP.  At no point did I check or un-ckeck the "Enabled" checkboxes, nor "Save Changes" - just toggled between the tunnel client and tunnel server pages.  The first tunnel where I am the server came up in about 30 second, and all except one client connection came up within two minutes.  I waited eight minutes for the one client connection, and it would not come up even after I cycled the "Enabled" checkbox (saving changed each time), and I could not ping the DNS entry for it, so I am suspecting something on the other end.

At the moment, that hAP is running nightly build 300.