New policies: enable/disable relay; port range

remoting/jingle_glue/network_settings.h

Index: remoting/jingle_glue/network_settings.h
diff --git a/remoting/jingle_glue/network_settings.h b/remoting/jingle_glue/network_settings.h
index a37b0bcb0facb4e57fff30802d23b0998ed0c715..cc6bb8c2b851b350e185c3e6b571240d9ba7386f 100644
--- a/remoting/jingle_glue/network_settings.h
+++ b/remoting/jingle_glue/network_settings.h
@@ -19,6 +19,9 @@ struct NetworkSettings {
     // Active NAT traversal using STUN and relay servers.
     NAT_TRAVERSAL_ENABLED,
 
+    // Active NAT traversal using STUN, but don't use relay servers.
+    NAT_TRAVERSAL_ENABLED_NO_RELAY,

[Sergey Ulanov, 2014/03/24 23:37:12]

This breaks LibjingleTransportFactory::EnsureFreshJingleInfo() which only
fetches STUN config in the NAT_TRAVERSAL_ENABLED mode. To avoid bugs like this,
it might be better to replace nat_traversal_mode with nat_traversal_flags and
separate flags for STUN, Relay, and outgoing connections.

[dcaiafa, 2014/03/26 15:29:16]

Good catch! Done.

+
     // Don't use STUN or relay servers. Accept incoming P2P connection
     // attempts, but don't initiate any. This ensures that the peer is
     // on the same network. Note that connection will always fail if