Tore Anderson t...@fud.no writes:
* Bjørn Mork
Tore Anderson t...@fud.no writes:
This is implemented in Android - its wireless hotspot feature works just
fine using IPv6-only + 464XLAT as the upstream mobile connectivity. The
hotspot zone remains IPv4-only though,
Really? I have only
Tore Anderson t...@fud.no writes:
I think that your sharing must be some vendor add-on feature that's not
part of Android proper. After some searching for radish on
http://android.googlesource.com I think what you have is some
proprietary binary stuff originating with Qualcomm, see for
On 11/25/2013 10:48 PM, Lorenzo Colitti wrote:
On Tue, Nov 26, 2013 at 3:36 AM, Doug Barton do...@dougbarton.us
mailto:do...@dougbarton.us wrote:
DNS64 was a non-starter because there are always going to be IPv4
sites that hard-code IP addresses, and a non-trivial number of them
are
* Bjørn Mork
Tore Anderson t...@fud.no writes:
This is implemented in Android - its wireless hotspot feature works just
fine using IPv6-only + 464XLAT as the upstream mobile connectivity. The
hotspot zone remains IPv4-only though,
Really? I have only tested on Android 4.2 (without the
On 11/26/2013 12:22 AM, Lorenzo Colitti wrote:
On Tue, Nov 26, 2013 at 5:19 PM, Doug Barton do...@dougbarton.us
mailto:do...@dougbarton.us wrote:
Wait, what? The problem you describe is the one that 464xlat solves.
Didn't you just make my case? DNS64 didn't solve the problem, at
Hi,
On Tue, Nov 26, 2013 at 12:55:18AM -0800, Doug Barton wrote:
On 11/26/2013 12:31 AM, Gert Doering wrote:
I think he's saying that everyone should be using dual-stack, because
that's so much easier to roll out and maintain, and there's still plenty
of IPv4 left in the US region.
Le 2013-11-25 08:20, Dick Visser a écrit :
I'd like to 'upgrade' out existing NAT64/DNS64 setup to do 464XLAT, but
there aren't many docs about how to set 464XLAT to begin with.
FYI, our OpenBSD implementation of NAT64 also does NAT46. It's been part
of regular OpenBSD releases since 5.1. But
=cisco@lists.cluenet.de] On
Behalf Of Dick Visser
Sent: lundi 25 novembre 2013 14:20
To: ipv6-ops@lists.cluenet.de
Subject: 'Upgrading' NAT64 to 464XLAT?
hi guys
We've been running a NAT64/DNS64 set-up for a while now on some parts
of
our office network.
This seems to work well
Eric Vyncke (evyncke) evyn...@cisco.com writes:
464XLAT is contained within a host, so, you will need an
implementation for all your end host (laptop, tablets, ...)
I cannot see anything in RFC 6877 preventing a CLAT gateway serving more
than one host.
Bjørn
[mailto:ipv6-ops-bounces+evyncke=cisco@lists.cluenet.de] On
Behalf Of Dick Visser
Sent: lundi 25 novembre 2013 14:20
To: ipv6-ops@lists.cluenet.de
Subject: 'Upgrading' NAT64 to 464XLAT?
hi guys
We've been running a NAT64/DNS64 set-up for a while now on some parts
of
our office network
On 11/25/2013 05:20 AM, Dick Visser wrote:
We've been running a NAT64/DNS64 set-up for a while now on some parts
of our office network. This seems to work well, but it doens't work
for everything (e.g. Skype etc).
When it was first being considered there was a non-zero number of us who
made
* Dick Visser
I just am reading up on the RFC and it looks like it doesn't have to
be on the end host necessarily:
http://tools.ietf.org/html/rfc6877#section-6.5
This is implemented in Android - its wireless hotspot feature works just
fine using IPv6-only + 464XLAT as the upstream mobile
Tore Anderson t...@fud.no writes:
* Dick Visser
I just am reading up on the RFC and it looks like it doesn't have to
be on the end host necessarily:
http://tools.ietf.org/html/rfc6877#section-6.5
This is implemented in Android - its wireless hotspot feature works just
fine using
13 matches
Mail list logo
