| /external/chromium_org/content/browser/renderer_host/p2p/ |
| socket_host_tcp_unittest.cc | 87 // Verify that we can send STUN message and that they are formatted
118 // Verify that we can receive STUN messages from the socket, and that
165 // Verify that we can't send data before we've received STUN response
179 // Verify that we can send data after we've received STUN response
239 // Verify that we can send STUN message and that they are formatted
267 // Verify that we can receive STUN messages from the socket, and that
311 // Verify that we can't send data before we've received STUN response
|
| socket_host.h | 74 // Verifies that the packet |data| has a valid STUN header. In case
|
| socket_host_udp.h | 71 // Set of peer for which we have received STUN binding request or
|
| socket_host_udp_unittest.cc | 186 // Verify that we can send STUN messages before we receive anything
212 // Verify that no data packets can be sent before STUN binding has
226 // Verify that we can send data after we've received STUN request
249 // Verify that we can send data after we've received STUN response
|
| /external/chromium/third_party/libjingle/source/talk/p2p/base/ |
| stunport.cc | 43 // Handles a binding request sent to the STUN server.
125 const std::string STUN_PORT_TYPE("stun");
160 // We will keep pinging the stun server to make sure our NAT pin-hole stays
209 // Look for a response from the STUN server.
239 LOG_J(LS_WARNING, this) << "StunPort: stun host lookup received error "
|
| port.h | 43 #include "talk/p2p/base/stun.h"
97 // sent through), the other side must send us a STUN binding request that is
160 // Indicates that we received a successful STUN binding request from an
224 // currently a connection. If this is an authenticated STUN binding request,
230 // If the given data comprises a complete and correct STUN message then the
232 // with this port's username fragment, msg will contain the parsed STUN
233 // message. Otherwise, the function may send a STUN response internally.
234 // remote_username contains the remote fragment of the STUN username.
365 // Called back when StunRequestManager has a stun packet to send
|
| stunport.h | 99 // DNS resolution of the STUN server.
102 // Sends STUN requests to the server.
|
| relayport.cc | 66 // Validates a response to a STUN allocate request.
72 // Sends a STUN allocate request message to the relay server.
79 // already STUN intended for the server, so no wrapping is necessary.
91 // packet in a STUN send / data indication.
115 // Sends the STUN requests to the server to initiate this connection.
124 // entry. This will wrap the packet in STUN if necessary.
529 // Otherwise, we must wrap the given data in a STUN SEND request so that we
670 LOG(INFO) << "Incoming packet was not STUN";
674 // The incoming packet should be a STUN ALLOCATE response, SEND response, or
687 LOG(INFO) << "Received BAD stun type from server: " << msg.type()
[all...] |
| relayserver.h | 40 #include "talk/p2p/base/stun.h"
113 // Processes the relevant STUN request types from the client.
167 // Sends a STUN message to the connected client with no wrapping.
|
| /external/chromium_org/third_party/libjingle/source/talk/p2p/base/ |
| port.h | 44 #include "talk/p2p/base/stun.h"
134 // This method will set the flag which enables standard ICE/STUN procedures
135 // in STUN connectivity checks. Currently this method does
136 // 1. Add / Verify MI attribute in STUN binding requests.
137 // 2. Username attribute in STUN binding request will be RFRAF:LFRAG,
283 // stun username attribute if present.
319 // currently a connection. If this is an authenticated STUN binding request,
325 // If the given data comprises a complete and correct STUN message then the
327 // with this port's username fragment, msg will contain the parsed STUN
328 // message. Otherwise, the function may send a STUN response internally
[all...] |
| asyncstuntcpsocket_unittest.cc | 147 // Testing a stun packet sent/recv properly.
196 // Verifying stun message with invalid length.
233 // a common one for both stun and turn.
253 // Verifying a legal large stun message.
|
| teststunserver.h | 37 // A test STUN server. Useful for unit tests.
|
| relayport.cc | 66 // Validates a response to a STUN allocate request.
72 // Sends a STUN allocate request message to the relay server.
79 // already STUN intended for the server, so no wrapping is necessary.
91 // packet in a STUN send / data indication.
115 // Sends the STUN requests to the server to initiate this connection.
124 // entry. This will wrap the packet in STUN if necessary.
541 // This is due to mapped address stun attribute is used for allocated
555 // Otherwise, we must wrap the given data in a STUN SEND request so that we
695 LOG(INFO) << "Incoming packet was not STUN";
699 // The incoming packet should be a STUN ALLOCATE response, SEND response, o
[all...] |
| stun.cc | 28 #include "talk/p2p/base/stun.h"
144 // Verifies a STUN message has a valid MESSAGE-INTEGRITY attribute, using the
153 // Getting the message length from the STUN header.
159 // Finding Message Integrity attribute in stun message.
194 // Stun message has other attributes after message integrity.
195 // Adjust the length parameter in stun message to calculate HMAC.
200 // Writing new length of the STUN message @ Message Length in temp buffer.
204 // |0 0| STUN Message Type | Message Length |
261 // Verifies a message is in fact a STUN message, by performing the checks
318 // and version is always 2 (10). If set, this is not a STUN packet
[all...] |
| /external/chromium_org/third_party/libjingle/source/talk/app/webrtc/ |
| peerconnectionfactory_unittest.cc | 58 static const char kStunIceServer[] = "stun:stun.l.google.com:19302";
151 // This test verifies creation of PeerConnection with valid STUN and TURN
172 "stun.l.google.com", 19302);
233 webrtc::PortAllocatorFactoryInterface::StunConfiguration stun(
235 stun_configs.push_back(stun);
|
| peerconnection.cc | 52 // The default stun port.
61 "stun", "stuns", "turn", "turns", "invalid" };
64 STUN, // Indicates a STUN server.
65 STUNS, // Indicates a STUN server used with a TLS session.
114 // draft-nandakumar-rtcweb-stun-uri-01
115 // stunURI = scheme ":" stun-host [ ":" stun-port ]
116 // scheme = "stun" / "stuns"
117 // stun-host = IP-literal / IPv4address / reg-nam
[all...] |
| /external/chromium_org/content/renderer/p2p/ |
| host_address_request.h | 24 // to resolve addresses of STUN and relay servers.
|
| /external/chromium_org/remoting/host/ |
| log_to_server_unittest.cc | 199 route2.type = protocol::TransportRoute::STUN;
210 IsTwoClientsConnected("direct", "stun")))
234 EXPECT_CALL(signal_strategy_, SendStanzaPtr(IsClientConnected("stun")))
247 route2.type = protocol::TransportRoute::STUN;
|
| server_log_entry.h | 54 // Adds a field describing connection type (direct/stun/relay).
|
| /external/chromium_org/remoting/jingle_glue/ |
| jingle_info_request.h | 30 // JingleInfoRequest handles requesting STUN/Relay information from
|
| /external/chromium_org/third_party/libjingle/source/talk/p2p/client/ |
| portallocator_unittest.cc | 277 cricket::ICE_CANDIDATE_COMPONENT_RTP, "stun", "udp", kClientAddr);
397 // We check the candidates for udp/stun/tcp ports, and the from address
413 // Check the port number for the STUN port object.
508 // Testing STUN timeout.
533 // Stun Timeout is 9sec.
558 // Each session should receive two proxy ports of local and stun.
641 cricket::ICE_CANDIDATE_COMPONENT_RTP, "stun", "udp", kClientAddr);
665 cricket::ICE_CANDIDATE_COMPONENT_RTP, "stun", "udp", kClientAddr);
678 // is allocated for udp and stun. Also verify there is only one candidate
679 // (local) if stun candidate is same as local candidate, which will be the cas
[all...] |
| connectivitychecker.cc | 29 static const char kDefaultStunHostname[] = "stun.l.google.com";
155 info.stun.start_time_ms = now;
296 nic_info->stun.rtt = now - nic_info->stun.start_time_ms;
298 LOG(LS_ERROR) << "Got stun address for non-existing nic";
304 LOG(LS_ERROR) << "Stun address error.";
|
| /external/chromium_org/remoting/protocol/ |
| jingle_session_manager.cc | 57 // TODO(sergeyu): Add support for multiple STUN/relay servers when
65 VLOG(1) << "STUN server: " << config.stun_server
110 // Request STUN/Relay info if necessary.
|
| /external/chromium_org/remoting/client/plugin/ |
| pepper_port_allocator.cc | 170 LOG(ERROR) << "Failed to resolve stun address "
176 LOG(WARNING) << "Received 0 addresses for stun server "
184 LOG(ERROR) << "Failed to get address for STUN server "
193 // HttpPortAllocatorSessionBase. This is necessary because STUN
196 // configuration for the case we resolve STUN address later. This
|
| /external/chromium/third_party/libjingle/source/talk/p2p/client/ |
| httpportallocator.cc | 106 talk_base::SocketAddress("stun.l.google.com", 19302));
134 // Creating stun sessions could also take time and could be done aysnc also,
136 // configs will have unresolved stun ips and will be discarded by the
|
