Opened 11 months ago

Closed 7 months ago

#1171 closed defect (duplicate)

ietf-nat64 does not work on Pixel 2

Reported by: lorenzo@… Owned by: panda@…
Priority: tbd Milestone: ietf-100
Component: nat64 Keywords:
Cc: furry@…, ek@…, quiche@… My Current Location:
My MAC Address: My OS: Android 8.1.0

Description

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.

Attachments (1)

nat64.pcap (28.5 KB) - added by lorenzo@… 11 months ago.
tcpdump as seen by host

Download all attachments as: .zip

Change history (5)

Changed 11 months ago by lorenzo@…

Attachment: nat64.pcap added

tcpdump as seen by host

comment:1 Changed 11 months ago by panda@…

Status: newaccepted

Thanks for trying the NAT64 network (SSID ietf-nat64) and reporting your experience. As far as we can tell, the issue you reported is either an issue of the NAT64 implementation’s handling of that specific traffic or the given application vendor's implementation. We’re collecting all the issues that come up and will pass the reports back to the vendor at the end of the week. Hopefully this will lead to better implementations and greater functionality for the next meeting. If you’re curious about other known issues, please see https://tickets.meeting.ietf.org/wiki/nat64

If you have additional input on this issue please update the ticket, if you see new issues please open additional tickets.

Thanks -

comment:2 Changed 11 months ago by jim@…

Resolution: pending
Status: acceptedclosed

Lorenzo,

Just to close the loop on this. Joe Clark has identified this issue within Cisco as being tracked in CSCvg77190. It is targeted to be fixed in an upcoming 8.3 maintenance release. We can test again in London.

Resolving as pending.

  • Jim

comment:3 Changed 7 months ago by Hans Kuhn

Resolution: pending
Status: closedreopened

Re-opening. See ticket:1080

comment:4 Changed 7 months ago by jim@…

Resolution: duplicate
Status: reopenedclosed

This was a specific case of the general issue tracked in ticket:1080, that tickled a bug in the Pixel2, rendering it unable to connect. Per conversations with Lorenzo, we'll close this as no longer reproducible, and continue to track the underlying issue in ticket:1080.

Note: See TracTickets for help on using tickets.