#863 closed request (fixed)
problem with v6 in TWC network
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | tbd | Milestone: | ietf-091 |
Component: | incoming | Keywords: | |
Cc: | My Current Location: | ||
My MAC Address: | My OS: |
Description
In the Tapa tower on wireless, v4 works flawlessly, v6 having lots of drops 4 hops along. I’m on ietf-hotel, channel 11. Traceroute here. dhcp-88e6.meeting.ietf.org (::) Sun Nov 9 07:05:06 2014 Keys: Help Display mode Restart statistics Order of fields quit Packets Pings Host Loss% Snt Last Avg Best Wrst StDev 1. 2001:67c:370:136::2 0.0% 4 4.8 5.2 2.8 9.7 3.1 2. 2605:e000:0:8::f:52 0.0% 4 5.5 4.5 3.7 5.5 0.7 3. 2605:e000:0:4::f:241 0.0% 4 5.5 14.4 3.2 45.6 20.8 4. 2605:e000:0:4::b:32 50.0% 4 5.4 5.3 5.2 5.4 0.1 5. 2605:e000:0:4::50 50.0% 4 54.0 53.0 51.9 54.0 1.5 6. 2001:1998:0:8::80 33.3% 4 58.3 56.2 54.1 58.3 3.0 7. 2001:1998:0:4::e0 0.0% 3 62.9 63.2 62.4 64.3 1.0 8. 2001:1998::66:109:6:143 0.0% 3 60.8 68.1 60.7 82.7 12.7 9. 2001:4f8:0:1::8:1 0.0% 3 101.5 74.5 60.9 101.5 23.3 10. 2001:4f8:1b:1::8:2 0.0% 3 63.0 65.0 63.0 66.2 1.8 11. 2001:4f8:3:36::235 0.0% 3 61.3 61.7 61.0 62.9 1. I’m getting 30-60% packet loss pretty consistently at hop 4 (2605:e000:0:4::b:32). I can switch to v4 to ssh to my server but lots of sites like ietf.org do have AAAA and it would be nice to not be testing lots of lousy happy eyeball implementations. ;) Not sure if this in IETF network or into TWC proper. Thanks! -- Paul Ebersman paul_ebersman@cable.comcast.com
Change history (10)
comment:1 Changed 6 years ago by
Owner: | changed from llynch@… to nkukich@… |
---|---|
Status: | new → assigned |
comment:2 Changed 6 years ago by
Owner: | changed from nkukich@… to cdoyle@… |
---|
comment:3 Changed 6 years ago by
comment:4 Changed 6 years ago by
Paul,
We're continuing to work with TWC on this. Sorry this is dragging out so long....
- Jim
comment:5 follow-up: 6 Changed 6 years ago by
Paul,
Could you test again? We believe we've identified the issue with TWC and resolved it.
Thanks!
- JIm
comment:6 Changed 6 years ago by
Replying to jim@…:
Paul,
Could you test again? We believe we've identified the issue with TWC and resolved it.
Thanks!
- JIm
Turns out that the ticketing system is handling replies different now then it was before. So sorry for the radio silence. Please click the link to check the ticket directly to see the current notes.
comment:7 Changed 6 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Paul,
We strongly believe this is resolved, so I'm going to resolve the ticket. If you find that not to be the case, please let us know and we'll be happy to work to address anything outstanding.
- JIm
comment:8 Changed 6 years ago by
Resolution: | fixed |
---|---|
Status: | closed → reopened |
As of yesterday morning, I was still seeing some drops but it was usable for SSH. By this morning, it’s effectively error free. Great job as always. Thanks! -- Paul Ebersman paul_ebersman@cable.comcast.com On 11Nov, 2014, at 1:15 PM, IETF Meeting/NOC <tickets@meeting.ietf.org> wrote: > #863: problem with v6 in TWC network > ----------------------------------+-------------------------------- > Reporter: Paul_Ebersman@… | Owner: cdoyle@… > Type: request | Status: closed > Priority: tbd | Milestone: ietf-91 > Component: incoming | Resolution: fixed > Keywords: | My Current Location: > My MAC Address: | My OS: > ----------------------------------+-------------------------------- > Changes (by jim@…): > > * status: assigned => closed > * resolution: => fixed > > > Comment: > > Paul, > We strongly believe this is resolved, so I'm going to resolve the > ticket. If you find that not to be the case, please let us know and we'll > be happy to work to address anything outstanding. > > - JIm > > -- > Ticket URL: <https://tickets.meeting.ietf.org/ticket/863#comment:7> > IETF Meeting/NOC <https://tickets.meeting.ietf.org> > IETF Meeting - NOC pages
comment:9 Changed 6 years ago by
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
Paul,
Many thanks! Re-Resolving.
- Jim
We are noticing the same thing for traffic transiting the TWC network over routers with 2605:e000: hextets. We've reached out to TWC and are working on alternative v6 routing strategies to mitigate the issue in the meantime.