[rtcweb] ICE does not work if both peers are behind symmetric NAT
Iñaki Baz Castillo <ibc@aliax.net> Sat, 24 September 2011 20:30 UTC
Return-Path: <ibc@aliax.net>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 110D321F8B4F for <rtcweb@ietfa.amsl.com>; Sat, 24 Sep 2011 13:30:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.642
X-Spam-Level:
X-Spam-Status: No, score=-2.642 tagged_above=-999 required=5 tests=[AWL=0.035, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ttwqaI8Xv8Fe for <rtcweb@ietfa.amsl.com>; Sat, 24 Sep 2011 13:30:47 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 81BC121F8B4B for <rtcweb@ietf.org>; Sat, 24 Sep 2011 13:30:47 -0700 (PDT)
Received: by vws5 with SMTP id 5so5536440vws.31 for <rtcweb@ietf.org>; Sat, 24 Sep 2011 13:33:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.29.75 with SMTP id i11mr4627725vdh.296.1316896404889; Sat, 24 Sep 2011 13:33:24 -0700 (PDT)
Received: by 10.220.94.200 with HTTP; Sat, 24 Sep 2011 13:33:24 -0700 (PDT)
Date: Sat, 24 Sep 2011 22:33:24 +0200
Message-ID: <CALiegfnf3=mPAupRtjoqz+fNfxT5V8yivoQB+bgrvAVWp5CVog@mail.gmail.com>
From: Iñaki Baz Castillo <ibc@aliax.net>
To: rtcweb@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: [rtcweb] ICE does not work if both peers are behind symmetric NAT
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Sep 2011 20:30:48 -0000
Hi, I expect this topic has already been addressed in this maillist. But it not, I would like to comment that ICE does not work when both peers are behind symmetric NAT (very common in home routers). In that case, the only solution is to use TURN by adding it the last candidate in the ICE SDP, but TURN requires authentication and, of course, a TURN server. Has been this topic discussed? If the website supposed to provide the WebRTC client with information about which TURN server to use and username:password for using it? Thanks a lot. -- Iñaki Baz Castillo <ibc@aliax.net>
- [rtcweb] ICE does not work if both peers are behi… Iñaki Baz Castillo
- Re: [rtcweb] ICE does not work if both peers are … Alfred E. Heggestad
- Re: [rtcweb] ICE does not work if both peers are … Iñaki Baz Castillo
- Re: [rtcweb] ICE does not work if both peers are … Harald Alvestrand
- Re: [rtcweb] ICE does not work if both peers are … Roman Shpount
- Re: [rtcweb] ICE does not work if both peers are … Cameron Byrne
- Re: [rtcweb] ICE does not work if both peers are … Roman Shpount