Has there been any thought into adding parts of the "INFO" logging generated from the Network module, into an attribute of the connectionInformation JSON object returning from the Network event handler? Granted, this would be in addition to just signaling on a change in connection status, but this would give the connection event handler more information on the specific problem behind the lack of connection. In addition, the application could respond to the problem and determine whether or not it should continue attempting a connection, or just stop until the problem has been corrected.
There have been several changes to the Network module to accommodate WAN connections but nothing like you describe. It's a good idea, I've put in a new feature request to the product. Thanks.