Opened 2 months ago

Closed 2 months ago

#1253 closed task (not broken)

UDP reordering

Reported by: lars@… Owned by: jclarke@…
Priority: tbd Milestone: ietf-103
Component: wireless Keywords:
Cc: My Current Location:
My MAC Address: My OS:

Description

Confirmed with Lucy that it happens on the wireless (eduroam at least) but not the wired:

WIRED:
bash-4.4$ traceroute msquic.westus.cloudapp.azure.com
traceroute to msquic.westus.cloudapp.azure.com (40.112.166.115), 64 hops max, 52 byte packets
 1  rtra-hotel (31.133.160.2)  0.824 ms  0.381 ms  0.344 ms
 2  rtrb-rtra (31.130.231.33)  0.406 ms  0.611 ms  0.382 ms
 3  61.58.47.1 (61.58.47.1)  27.522 ms  2.523 ms  2.466 ms
 4  ae-4.r21.kslrml02.my.bb.gin.ntt.net (129.250.2.222)  51.178 ms  24.798 ms  24.728 ms
 5  ae-6.r21.sngpsi07.sg.bb.gin.ntt.net (129.250.3.51)  31.937 ms  31.502 ms  33.267 ms
 6  ae-9.r21.sngpsi05.sg.bb.gin.ntt.net (129.250.4.53)  32.472 ms  61.599 ms  36.815 ms
 7  ae-13.r00.sngpsi02.sg.bb.gin.ntt.net (129.250.4.74)  33.845 ms  33.922 ms  32.953 ms
 8  xe-0-1-0-2.r00.sngpsi02.sg.ce.gin.ntt.net (129.250.10.190)  35.480 ms  52.862 ms  34.556 ms
 9  ae33-0.sg1-96cbe-1a.ntwk.msn.net (104.44.239.200)  31.158 ms  31.413 ms  32.269 ms
10  104.44.232.11 (104.44.232.11)  99.263 ms
    ae6-0.osa01-96cbe-1a.ntwk.msn.net (104.44.224.203)  104.114 ms
    104.44.232.11 (104.44.232.11)  97.593 ms
11  ae20-0.icr01.osa31.ntwk.msn.net (104.44.236.105)  107.539 ms  108.503 ms
^C


WIRELESS:
bash-4.4$ traceroute msquic.westus.cloudapp.azure.com
traceroute to msquic.westus.cloudapp.azure.com (40.112.166.115), 64 hops max, 52 byte packets
 1  rtra-wireless (31.133.128.2)  9.249 ms  2.953 ms  1.323 ms
 2  rtrb-rtra (31.130.231.33)  3.657 ms  8.713 ms  6.032 ms
 3  61.58.47.1 (61.58.47.1)  5.290 ms  4.693 ms  3.157 ms
 4  ae-4.r21.kslrml02.my.bb.gin.ntt.net (129.250.2.222)  38.292 ms  26.205 ms  26.072 ms
 5  ae-6.r21.sngpsi07.sg.bb.gin.ntt.net (129.250.3.51)  49.023 ms  32.156 ms  36.263 ms
 6  ae-9.r21.sngpsi05.sg.bb.gin.ntt.net (129.250.4.53)  71.860 ms  45.352 ms  32.483 ms
 7  * ae-13.r00.sngpsi02.sg.bb.gin.ntt.net (129.250.4.74)  33.765 ms  34.265 ms
 8  xe-0-1-0-2.r00.sngpsi02.sg.ce.gin.ntt.net (129.250.10.190)  33.140 ms  53.646 ms  37.436 ms
 9  ae33-0.sg1-96cbe-1a.ntwk.msn.net (104.44.239.200)  57.300 ms
    ae13-0.sge-96cbe-1b.ntwk.msn.net (104.44.226.123)  36.351 ms  71.422 ms
10  104.44.232.11 (104.44.232.11)  350.227 ms
    ae6-0.osa01-96cbe-1a.ntwk.msn.net (104.44.224.203)  305.699 ms  668.084 ms

signature.asc

Attachments (1)

signature.asc (833 bytes) - added by lars@… 2 months ago.
Added by email2trac

Download all attachments as: .zip

Change history (3)

Changed 2 months ago by lars@…

Attachment: signature.asc added

Added by email2trac

comment:1 Changed 2 months ago by llynch@…

Component: incomingwireless
Owner: changed from < default > to jclarke@…
Status: newassigned
Type: requesttask

Joe -

Looks like your guess was a good one - packet re-ordering happens on the
wireless side but not on the wired.

You might want to pursue this a bit since it does effect the quic stack
Lars was running. May be more interesting than harmful.

  • Lucy

comment:2 Changed 2 months ago by jclarke@…

Resolution: not broken
Status: assignedclosed

This is expected with the operation of the wireless LAN controller. If this is a serious issue, we can look at experimenting with new QoS settings in a future meeting.

Note: See TracTickets for help on using tickets.