From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] ipv6 support for webrtc
Date: Fri, 6 Jun 2014 08:50:09 -0700 [thread overview]
Message-ID: <CAA93jw76BaOckP5pP=2vHR7ETMqP40p0EQEaS6E3LBPX=KYKXw@mail.gmail.com> (raw)
Has been tested through cero and appears to be working on (at least) a
modern chrome browser. Havent' tested firefox.
The site I used was:
https://apprtc.appspot.com/?ipv6=true
paste the resulting url to whoever you want to chat with via chat, and
hopefully, maybe it will negotiate a direct ipv6 connection between
you.
Now you too can enjoy the low latency video conferencing experience we
dreamed of when ipv6 was first designed!
(Most providers want to be MITM and/or provide conference services, so they
remain in the middle, but the above link does not.)
I'm told appear.in and meet.jit.si are doing more "of the right thing"
nowadays, too.
The relevant bug on this is
https://code.google.com/p/webrtc/issues/detail?id=1406
--
Dave Täht
reply other threads:[~2014-06-06 15:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw76BaOckP5pP=2vHR7ETMqP40p0EQEaS6E3LBPX=KYKXw@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox