Opened 4 years ago

Closed 4 years ago

Last modified 5 weeks ago

#705 closed request (fixed)

No PD on ietf-nat64 again.

Reported by: mellon@… Owned by: cdoyle@…
Priority: tbd Milestone: ietf-089
Component: incoming Keywords:
Cc: My Current Location:
My MAC Address: My OS:

Description

Help?

I'm down in Palace C.   Don't know if it's widespread.

Change history (8)

comment:1 Changed 4 years ago by llynch@…

Owner: changed from llynch@… to cdoyle@…
Status: newassigned

comment:2 Changed 4 years ago by cdoyle@…

Can you check to see if this is still an issue this morning. This did not look widespread and received no other reports of Nat64 issues. If you continue to have problems, I'll reach out to the local A10 guys about it.

comment:3 Changed 4 years ago by mellon@…

On Mar 6, 2014, at 8:36 AM, IETF Meeting/NOC <tickets@meeting.ietf.org> wrote:
> Can you check to see if this is still an issue this morning. This did not
> look widespread and received no other reports of Nat64 issues. If you
> continue to have problems, I'll reach out to the local A10 guys about it.

It's working at the moment (just got back to Palace C).   Thanks for looking into it!

comment:4 Changed 4 years ago by cdoyle@…

Resolution: fixed
Status: assignedclosed

Terrific, Ted. i'm going to close this ticket. Please let us know if you need anything else.

comment:5 Changed 4 years ago by bzeeb+ietf@…

Ted, I assume you are sitting behind me and I am sorry to have to tell you that we did not do anything in the last days that would change any behaviour on the nat64 network. I kept watching your reports but I fear the "spottiness" is not because of us but because of something else. Could be the A10 itself though we did see secondly RAs (not sure that's good either) when running tcpdump before.
Could also be one of the never fully understood problems with the current APs we have very occasionally only seen in the past that suddenly v6 stopped working until you re-associated. There's some overhaul of gear coming and we'll keep monitoring how these things will continue. One thing I am curious about is how you determine that you do not get RAs. Just checking your configuration or actually doing some packet sniffing? How long do you usually wait?

comment:6 Changed 4 years ago by mellon@…

Resolution: fixed
Status: closedreopened
On Mar 6, 2014, at 9:06 AM, IETF Meeting/NOC <tickets@meeting.ietf.org> wrote:
> APs we have very occasionally only seen in the past that suddenly v6
> stopped working until you re-associated.   There's some overhaul of gear
> coming and we'll keep monitoring how these things will continue.   One
> thing I am curious about is how you determine that you do not get RAs.
> Just checking your configuration or actually doing some packet sniffing?
> How long do you usually wait?

I have used more or less diligence in determining this from time to time, and one thing I did not try was de-associating and re-associating.   In general I wait for 30 seconds or so and do tcpdumps to look for RAs, but I think I may not have done that for the most recent report because I was getting used to the phenomenon.

It sounded like one of these instances was the result of congestion and another the result of a filter, so at least the congestion one was likely a heisenbug.   But yesterday's outage might well be due to the AP issue you described.   If it happens again I will try cycling the interface to see if that helps.

comment:7 Changed 4 years ago by bzeeb+ietf@…

Resolution: fixed
Status: reopenedclosed

Thanks for the info!

comment:8 Changed 5 weeks ago by Rick Alfvin

Milestone: ietf-89ietf-089

Milestone renamed

Note: See TracTickets for help on using tickets.