Closed
Bug 1321805
Opened 8 years ago
Closed 6 years ago
ICE in webrtc sometimes do not sent STUN package
Categories
(Core :: WebRTC: Networking, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: wanghb89, Unassigned, NeedInfo)
Details
(Whiteboard: [needinfo 2016/12/02 to reporter])
User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.99 Safari/537.36
Steps to reproduce:
I use iceServers:[{urls:"stun:xxx.xxx.xxx.xxx:4000"}]} to set webrtc peerconnection.
I write the stun server by myself.
Actual results:
When the stun server is in the LAN, I can get the stun binding request package.
But when it is not in the LAN, There is no stun binding request package.
I think whatever the network is , There should be stun binding request package
Expected results:
There should be stun binding request package.
Comment 1•8 years ago
|
||
Have you checked with Wireshark or some other network tracer that Firefox is really not sending something, or is you observation purely based on your server not receiving anything?
If the stun server is not in the LAN where is it hosted? Public IP I assume?! Any firewalls in between Firefox and that stun server which could potentially drop packets on unknown port 4000?
Flags: needinfo?(wanghb89)
Whiteboard: [needinfo 2016/12/02 to reporter]
(In reply to Nils Ohlmeier [:drno] from comment #1)
> Have you checked with Wireshark or some other network tracer that Firefox is
> really not sending something, or is you observation purely based on your
> server not receiving anything?
>
> If the stun server is not in the LAN where is it hosted? Public IP I
> assume?! Any firewalls in between Firefox and that stun server which could
> potentially drop packets on unknown port 4000?
I use the wireshark to check whether the firefox send stun binding request. There is no stun binding request. I can get the local ip address(192.168.*.*) behind the NAT by print candidate, but I cannot get the public IP Address.
Comment 4•8 years ago
|
||
(In reply to wanghb89 from comment #2)
> (In reply to Nils Ohlmeier [:drno] from comment #1)
> > If the stun server is not in the LAN where is it hosted? Public IP I
> > assume?! Any firewalls in between Firefox and that stun server which could
> > potentially drop packets on unknown port 4000?
>
> I use the wireshark to check whether the firefox send stun binding request.
> There is no stun binding request. I can get the local ip
> address(192.168.*.*) behind the NAT by print candidate, but I cannot get the
> public IP Address.
I assume with "print candidate" you mean logging the candidate after your JS code receives the candidates via the onicecandidate callback.
But to repeat my question from before: where is your stun server running if it's not in the same LAN?
Is it running on a publicly routable IP?
> I assume with "print candidate" you mean logging the candidate after your JS
> code receives the candidates via the onicecandidate callback.
yes, you are right!
>
> But to repeat my question from before: where is your stun server running if
> it's not in the same LAN?
> Is it running on a publicly routable IP?
The stun server is not in the same LAN. It is running on a publicly routable IP.
BTW, I want to ask if the IP impact on onicecandidate callback? As Far As I Understand, onicecandidate callback should send stun package to the stun server.
Updated•6 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•