Custom query (1019 matches)

I don’t expect resolution, just providing this for documentation:

When using ietf-nat64, I am unable to use Jabber.
I’m using Adium v. 1.5.10.4 (4/27/17) as my client.
My account is on gmail.com

I would guess that it’s an authentication problem to gmail.com over jabber
protocol, but it’s just a guess.

I also can’t access AIM:
login.oscar.aol.com port 5190

Oh, fwiw, I’m using a MacBook Air from 2011, running El Capitan v 10.11.6. I
can’t upgrade to Sierra due to insufficient disk space (which is why I
deleted wireshark and can’t provide a packet trace).

Lee

A message for the NOC team,

*Please note this is not a rant or a 'trouble ticket', just observations I
hope would be useful*

After the discussion today at v6ops I gently encouraged some of my friends
here to migrate over from 'legacy' to nat64. They then did start to
experience issues.

In my data sample (of 2) i noted in both cases this had nothing to do with
v4 vs. v6 but more to do with the channel negotiation and 5GHz capabilities
of the devices in question.
a quick (rough) survey shows there are various locations in the building
where 5GHz is virtually non existent, with sufficient enough loss to
encounter packet loss.

As such I would state that any assertion that ~300 users on legacy or
2.4-only were having nat64 issues is based on a false premise as there are
likely more than one reason users would coalesce here.

Might I suggest that future meetings also have a dual frequency nat64, or
indeed a 2.4 only nat64 so that you can separate assumptions made around
channel availability and IP scheme.

Thank you for your efforts, an exclusive nat64 user since ietf89.

CraigT

My internet access is horribly slow in Room 8082, if it works at all.
Anything that can be done to help remedy this would be most
appreciated.

Jodi Haasz

Sent from my iPhone