STUN packets flooding

[Nikita Petrov]

Hello,

I've been watching WebRTC packets with WireShark and noticed a lot of STUN packets being sent. They look like keep-alive packets. Is this right? But it looks like there is too many of them. As per RFC5626, keep-alive packets should be sent once in 24-29 seconds.

[Nikita Petrov]

Forgot to mention: I was checking this with Chrome Stable and latest Chrome Canary

[Serge Lachapelle]

how many where you seeing?

how was the call setup?

can you file an issue and attach your trace and refer to the issue here?

--
 
 
 

[Sergio Garcia Murillo]

Hi all,

I am also seen it, like one stun packet per second or even half a second (Canary filtered log below). I am testing against my own media server (implementing ice-lite). I am having some problems with VP8 P frames that is causing chrome to send frequent rtcp picture lost indications, don't know if it may also be the cause of the STUN checks from chrome.

I can provide more info if needed.

[720:10360:1128/112004:VERBOSE4:port.cc(1094)] Jingle:Conn[audio:w9MiZNia:1:0:local:udp:192.168.64.1:63845->:1:0:local:udp:192.168.64.128:59916|CRWS|1]: Sending STUN ping mQ9wHcc6rZTv at 922096195
[720:10360:1128/112004:VERBOSE4:port.cc(1175)] Jingle:Conn[audio:w9MiZNia:1:0:local:udp:192.168.64.1:63845->:1:0:local:udp:192.168.64.128:59916|CRWS|1]: Received STUN ping response mQ9wHcc6rZTv, pings_since_last_response_=922096195 , rtt=1
[720:10360:1128/112004:VERBOSE4:port.cc(1024)] Jingle:Conn[audio:w9MiZNia:1:0:local:udp:192.168.64.1:63845->:1:0:local:udp:192.168.64.128:59916|CRWS|1]: UpdateState(): pings_since_last_response_=, rtt=100, now=922096675
[720:10360:1128/112004:VERBOSE4:port.cc(1094)] Jingle:Conn[audio:w9MiZNia:1:0:local:udp:192.168.64.1:63845->:1:0:local:udp:192.168.64.128:59916|CRWS|1]: Sending STUN ping 7k9CsclNCTBt at 922096675
[720:10360:1128/112004:VERBOSE4:port.cc(1175)] Jingle:Conn[audio:w9MiZNia:1:0:local:udp:192.168.64.1:63845->:1:0:local:udp:192.168.64.128:59916|CRWS|1]: Received STUN ping response 7k9CsclNCTBt, pings_since_last_response_=922096675 , rtt=2
[720:10360:1128/112005:VERBOSE4:port.cc(1024)] Jingle:Conn[audio:w9MiZNia:1:0:local:udp:192.168.64.1:63845->:1:0:local:udp:192.168.64.128:59916|CRWS|1]: UpdateState(): pings_since_last_response_=, rtt=100, now=922097170
[720:10360:1128/112005:VERBOSE4:port.cc(1094)] Jingle:Conn[audio:w9MiZNia:1:0:local:udp:192.168.64.1:63845->:1:0:local:udp:192.168.64.128:59916|CRWS|1]: Sending STUN ping m+TcYfgnoPFo at 922097173
[720:10360:1128/112005:VERBOSE4:port.cc(1175)] Jingle:Conn[audio:w9MiZNia:1:0:local:udp:192.168.64.1:63845->:1:0:local:udp:192.168.64.128:59916|CRWS|1]: Received STUN ping response m+TcYfgnoPFo, pings_since_last_response_=922097173 , rtt=9
[720:10360:1128/112005:VERBOSE4:port.cc(1024)] Jingle:Conn[audio:w9MiZNia:1:0:local:udp:192.168.64.1:63845->:1:0:local:udp:192.168.64.128:59916|CRWS|3]: UpdateState(): pings_since_last_response_=, rtt=100, now=922097653
[720:10360:1128/112005:VERBOSE4:port.cc(1094)] Jingle:Conn[audio:w9MiZNia:1:0:local:udp:192.168.64.1:63845->:1:0:local:udp:192.168.64.128:59916|CRWS|3]: Sending STUN ping IbYEDhqLzQFg at 922097653
[720:10360:1128/112005:VERBOSE4:port.cc(1175)] Jingle:Conn[audio:w9MiZNia:1:0:local:udp:192.168.64.1:63845->:1:0:local:udp:192.168.64.128:59916|CRWS|3]: Received STUN ping response IbYEDhqLzQFg, pings_since_last_response_=922097653 , rtt=1
[720:10360:1128/112006:VERBOSE4:port.cc(1024)] Jingle:Conn[audio:w9MiZNia:1:0:local:udp:192.168.64.1:63845->:1:0:local:udp:192.168.64.128:59916|CRWS|2]: UpdateState(): pings_since_last_response_=, rtt=100, now=922098133
[720:10360:1128/112006:VERBOSE4:port.cc(1094)] Jingle:Conn[audio:w9MiZNia:1:0:local:udp:192.168.64.1:63845->:1:0:local:udp:192.168.64.128:59916|CRWS|2]: Sending STUN ping djWyg61++yWn at 922098133
[720:10360:1128/112006:VERBOSE4:port.cc(1175)] Jingle:Conn[audio:w9MiZNia:1:0:local:udp:192.168.64.1:63845->:1:0:local:udp:192.168.64.128:59916|CRWS|2]: Received STUN ping response djWyg61++yWn, pings_since_last_response_=922098133 , rtt=1
[720:10360:1128/112006:VERBOSE4:port.cc(1024)] Jingle:Conn[audio:w9MiZNia:1:0:local:udp:192.168.64.1:63845->:1:0:local:udp:192.168.64.128:59916|CRWS|1]: UpdateState(): pings_since_last_response_=, rtt=100, now=922098613
[720:10360:1128/112006:VERBOSE4:port.cc(1094)] Jingle:Conn[audio:w9MiZNia:1:0:local:udp:192.168.64.1:63845->:1:0:local:udp:192.168.64.128:59916|CRWS|1]: Sending STUN ping h0emfpDVOCvB at 922098613
[720:10360:1128/112006:VERBOSE4:port.cc(1175)] Jingle:Conn[audio:w9MiZNia:1:0:local:udp:192.168.64.1:63845->:1:0:local:udp:192.168.64.128:59916|CRWS|1]: Received STUN ping response h0emfpDVOCvB, pings_since_last_response_=922098613 , rtt=2

Best regards
Sergio

--
 
 
 

[Serge Lachapelle]

again, how is this call setup. Is it using apprtc.appspot.com?

--
 
 
 

[Sergio Garcia Murillo]

Hi,

No, I am using mobicents test client which uses sip over websocekts. The remote peer is my mcu conferencing server doing playing sip.

http://code.google.com/p/sipservlets/wiki/HTML5WebRTCVideoApplication

I could setup a public access for you if it helps you or any other trace/log.

Best regards
Sergio

--
 
 
 

[Serge Lachapelle]

Right now, I am more interested in cases where this happens browser to browser, which is our current higher prio (naturally).

/Serge

--
 
 
 

[Sergio Garcia Murillo]

Understable, will keep you posted if I found more on the issue.

BR
Sergio

--
 
 
 

[Serge Lachapelle]

Thanks Sergio! Cool name btw :)

/S

--
 
 
 

[Nikita Petrov]

http://code.google.com/p/webrtc/issues/detail?id=1161

it looks like I get 4 packets per second.

I've tested it with apprtc now, the behavior is the same as with the solution we test against.

[Bryan Donnovan]

I have seen 20 stun bindings per second over TCP -- starts out every 500 ms then increases to every 50ms after 15 seconds:

http://code.google.com/p/webrtc/issues/detail?id=1143

[Vikas]

Hi,

As far i know, RFC 5245 doesn't mention how often stun connectivity
checks should be performed. I think currently we perform connectivity
check once every 5sec after connection is established. Well, we might
look into improving this. But just curious, what impact are you seeing
in your application due to this?

/Vikas

On Nov 28, 4:18 am, Nikita Petrov <hrun...@gmail.com> wrote:
> http://code.google.com/p/webrtc/issues/detail?id=1161
>
> it looks like I get 4 packets per second.
> I've tested it with apprtc now, the behavior is the same as with the
> solution we test against.
>
>
>
>
>
>
>
> On Wednesday, November 28, 2012 4:03:44 PM UTC+6, Serge Lachapelle wrote:
>
> > how many where you seeing?
> > how was the call setup?
> > can you file an issue and attach your trace and refer to the issue here?
>

> > On Wed, Nov 28, 2012 at 9:12 AM, Nikita Petrov <hru...@gmail.com<javascript:>