Custom query (827 matches)

Collyer room, Samsung J3Pro, Android 7.0, Aug 2017 patch level.

Connection to ietf-legacy100 works fine.

Connect to ietf-nat64-unencrypted, Android reports 'Internet may not be
available'. Icon in top screen bar shows an exclamation. It's possible to
browse the web for a few minutes, network is disconnected afterwards.

This seems to be very similar to #1162, only that in my case I get
disconnected after a few minutes.

Hi,

In V6OPS on the ietf-nat64 SSID.

Runnning MacOS 10.12.6

Works:

Using Apple Mail, works with my gmail account (send this email)
Using Thunderbird to my home email account on Rackspace.  Rackspace doesn’t support IPv6, worked fine.

Safari:  Browsing works fine.  Haven’t seen any problem.

Crome:  Same as Safari.  I run IPvFoo on Safari.  It shows interesting connections, including 64: prefix addresses.  See attached file.

IETF Meeting materials manager:  Worked fine.

Dropbox works.

Adium to talk.google.com works.

iTunes works.


Odd Behavior:

Crome: Going to maps.google.com, it shows me at the Prague Hilton.
Safari: Says it can’t find my location:  "Your location could not be determined”
Apple Maps:  Can’t determine location
Crome: Going to https://www.wunderground.com/fullscreenweather, shows me in Singapore

Not Working:

Check Point Software VPN  (not a new problem)

signature.asc​

We debugged this extensively in the NOC today, but filing this ticket for tracking.

Pixel 2 devices cannot use ietf-nat64. The observed symptom is that they connect fine, but then stay in state "connected, no Internet" indefinitely.

Based on debugging it appears that this is because the wifi controller does not allow hosts that do not support DHCPv6 and do not support legacy EUI-64 addresses. Link-local works fine.

We have verified that the devices are correctly sending DAD and MLD for their global addresses.