Do not spam "Connect failed with 101/65" in logs.

webrtc/base/network.cc

Index: webrtc/base/network.cc
diff --git a/webrtc/base/network.cc b/webrtc/base/network.cc
index 36d028b49348e899874296b01646f5017a7043f2..ba056e4635d0be6de427a6203beb6eae3c590a86 100644
--- a/webrtc/base/network.cc
+++ b/webrtc/base/network.cc
@@ -839,7 +839,12 @@ IPAddress BasicNetworkManager::QueryDefaultLocalAddress(int family) const {
   if (socket->Connect(SocketAddress(
           family == AF_INET ? kPublicIPv4Host : kPublicIPv6Host, kPublicPort)) <
       0) {
-    LOG(LS_INFO) << "Connect failed with " << socket->GetError();
+    if (socket->GetError() != ENETUNREACH

[honghaiz3, 2016/09/28 19:36:30]

Should we log an error message if the query for both IPv4 and IPv6 failed?
That might provide some meaningful information when debugging networking issues.

[skvlad, 2016/09/28 21:22:54]

This would have to be elsewhere in NetworkManager - probably done only once
instead of every N seconds. The message I'm silencing wasn't useful for that as
it didn't say which of the two interfaces were unreachable - one (which is
expected) or both (which isn't).

[honghaiz3, 2016/09/28 21:33:05]

Agree that can be done in a separate CL. Perhaps add a TODO here and/or file a
bug for that. 

[skvlad, 2016/09/28 22:27:46]

Filed https://bugs.chromium.org/p/webrtc/issues/detail?id=6438.

+        && socket->GetError() != EHOSTUNREACH) {
+      // Ignore the expected case of "host/net unreachable" - which happens if
+      // the network is V4- or V6-only.
+      LOG(LS_INFO) << "Connect failed with " << socket->GetError();
+    }
     return IPAddress();
   }
   return socket->GetLocalAddress().ipaddr();