Opened 11 months ago

Closed 11 months ago

Last modified 7 months ago

#1117 closed defect (fixed)

ietf-nat64 completely dead in Congress III

Reported by: mellon@… Owned by: panda@…
Priority: tbd Milestone: ietf-099
Component: wireless Keywords:
Cc: My Current Location:
My MAC Address: My OS:

Description

Not obvious what's going on here--I connected to ietf, and that's working.
  The nat64 network _was_ working, but slowly died over the course of the
first 20 minutes of the meeting, and is not completely non-functional, as
far as I can tell.

Hm, correction, turns out that the ietf ssid is also behaving badly, so
perhaps this is just a radio issue.   May be interference: I am now
connected using my phone, and performance is slightly better, but still a
lot of jitter, which suggests lots of layer 2 retries.

Change history (9)

comment:1 Changed 11 months ago by llynch@…

Component: incomingwireless
Owner: changed from < default > to panda@…
Status: newassigned
Type: requestdefect

comment:2 in reply to:  2 ; Changed 11 months ago by mellon@…

It is now working, and performance is pretty good.

On Tue, Jul 18, 2017 at 10:06 AM, IETF Tickets/NOC <tickets@meeting.ietf.org
> wrote:

> #1117: ietf-nat64 completely dead in Congress III
> ---------------------------+--------------------------------
>       Reporter:  mellon@…  |                Owner:  panda@…
>           Type:  defect    |               Status:  assigned
>       Priority:  tbd       |            Milestone:  ietf-99
>      Component:  wireless  |           Resolution:
>       Keywords:            |  My Current Location:
> My MAC  Address:           |                My OS:
> ---------------------------+--------------------------------
> Changes (by llynch@…):
>
>  * owner:  < default > => panda@…
>  * status:  new => assigned
>  * component:  incoming => wireless
>  * type:  request => defect
>
>
> --
> Ticket URL: <https://tickets.meeting.ietf.org/ticket/1117#comment:1>
> IETF Tickets/NOC <https://tickets.meeting.ietf.org>
> IETF Meeting Tickets - NOC pages
>

comment:3 Changed 11 months ago by jim@…

Resolution: fixed
Status: assignedclosed

Ted,

Thanks. The wireless team did some tuning in that room and things looked better from our side as well. I'm going to close this ticket, but please do reply and re-open if things go south for you again.

Appreciate the report and the attempt to use NAT64!

  • Jim

comment:4 in reply to:  4 ; Changed 11 months ago by mellon@…

Resolution: fixed
Status: closedreopened
Thanks.   Actually, the network is sucking again, unfortunately:

ping -6 home.fugue.com
PING home.fugue.com(mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net) 56 data bytes
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=1
ttl=55 time=200 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=2
ttl=55 time=272 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=3
ttl=55 time=483 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=4
ttl=55 time=1876 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=5
ttl=55 time=1966 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=6
ttl=55 time=1184 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=7
ttl=55 time=701 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=8
ttl=55 time=1230 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=9
ttl=55 time=334 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=10
ttl=55 time=287 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=11
ttl=55 time=601 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=12
ttl=55 time=350 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=13
ttl=55 time=1431 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=14
ttl=55 time=1035 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=15
ttl=55 time=450 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=16
ttl=55 time=285 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=17
ttl=55 time=5540 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=18
ttl=55 time=5110 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=19
ttl=55 time=4622 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=20
ttl=55 time=4537 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=21
ttl=55 time=3568 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=22
ttl=55 time=2569 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=23
ttl=55 time=294 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=24
ttl=55 time=625 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=25
ttl=55 time=4930 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=26
ttl=55 time=5583 ms
64 bytes from 2001:470:1f10:1110::2: icmp_seq=27 ttl=55 time=7066 ms
64 bytes from 2001:470:1f10:1110::2: icmp_seq=28 ttl=55 time=8125 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=29
ttl=55 time=7314 ms

64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=38
ttl=55 time=18009 ms

64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=39
ttl=55 time=17044 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=40
ttl=55 time=16128 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=41
ttl=55 time=15680 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=42
ttl=55 time=14778 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=43
ttl=55 time=13883 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=44
ttl=55 time=12938 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=45
ttl=55 time=11938 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=46
ttl=55 time=10938 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=47
ttl=55 time=9938 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=48
ttl=55 time=8948 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=49
ttl=55 time=8256 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=50
ttl=55 time=7256 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=51
ttl=55 time=6256 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=52
ttl=55 time=5929 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=53
ttl=55 time=5218 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=54
ttl=55 time=4219 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=55
ttl=55 time=511 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=56
ttl=55 time=1102 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=57
ttl=55 time=1179 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=58
ttl=55 time=1210 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=59
ttl=55 time=282 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=60
ttl=55 time=1071 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=61
ttl=55 time=500 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=62
ttl=55 time=528 ms

64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=58
ttl=55 time=1210 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=59
ttl=55 time=282 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=60
ttl=55 time=1071 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=61
ttl=55 time=500 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=62
ttl=55 time=528 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=63
ttl=55 time=309 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=64
ttl=55 time=1197 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=65
ttl=55 time=377 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=66
ttl=55 time=1076 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=67
ttl=55 time=2735 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=68
ttl=55 time=522 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=69
ttl=55 time=856 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=70
ttl=55 time=496 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=71
ttl=55 time=349 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=72
ttl=55 time=1074 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=73
ttl=55 time=394 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=74
ttl=55 time=1368 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=75
ttl=55 time=505 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=76
ttl=55 time=1672 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=77
ttl=55 time=2001 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=78
ttl=55 time=331 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=79
ttl=55 time=1794 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=80
ttl=55 time=1959 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=81
ttl=55 time=416 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=82
ttl=55 time=677 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=83
ttl=55 time=807 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=84
ttl=55 time=202 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=85
ttl=55 time=583 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=86
ttl=55 time=557 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=87
ttl=55 time=362 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=88
ttl=55 time=433 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=89
ttl=55 time=269 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=90
ttl=55 time=1088 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=91
ttl=55 time=1005 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=92
ttl=55 time=3249 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=93
ttl=55 time=3925 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=94
ttl=55 time=3186 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=95
ttl=55 time=2266 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=96
ttl=55 time=413 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=97
ttl=55 time=390 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=98
ttl=55 time=3159 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=99
ttl=55 time=2164 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=100
ttl=55 time=2764 ms
64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=101
ttl=55 time=2235 ms

comment:5 in reply to:  5 ; Changed 11 months ago by mellon@…

(I'm seeing similar behavior if I ping the router's ll address.)

On Tue, Jul 18, 2017 at 11:41 AM, Ted Lemon <mellon@fugue.com> wrote:

> Thanks.   Actually, the network is sucking again, unfortunately:
>
> ping -6 home.fugue.com
> PING home.fugue.com(mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net) 56 data bytes
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=1 ttl=55 time=200 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=2 ttl=55 time=272 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=3 ttl=55 time=483 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=4 ttl=55 time=1876 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=5 ttl=55 time=1966 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=6 ttl=55 time=1184 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=7 ttl=55 time=701 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=8 ttl=55 time=1230 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=9 ttl=55 time=334 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=10 ttl=55 time=287 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=11 ttl=55 time=601 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=12 ttl=55 time=350 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=13 ttl=55 time=1431 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=14 ttl=55 time=1035 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=15 ttl=55 time=450 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=16 ttl=55 time=285 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=17 ttl=55 time=5540 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=18 ttl=55 time=5110 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=19 ttl=55 time=4622 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=20 ttl=55 time=4537 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=21 ttl=55 time=3568 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=22 ttl=55 time=2569 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=23 ttl=55 time=294 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=24 ttl=55 time=625 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=25 ttl=55 time=4930 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=26 ttl=55 time=5583 ms
> 64 bytes from 2001:470:1f10:1110::2: icmp_seq=27 ttl=55 time=7066 ms
> 64 bytes from 2001:470:1f10:1110::2: icmp_seq=28 ttl=55 time=8125 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=29 ttl=55 time=7314 ms
>
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=38 ttl=55 time=18009 ms
>
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=39 ttl=55 time=17044 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=40 ttl=55 time=16128 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=41 ttl=55 time=15680 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=42 ttl=55 time=14778 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=43 ttl=55 time=13883 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=44 ttl=55 time=12938 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=45 ttl=55 time=11938 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=46 ttl=55 time=10938 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=47 ttl=55 time=9938 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=48 ttl=55 time=8948 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=49 ttl=55 time=8256 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=50 ttl=55 time=7256 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=51 ttl=55 time=6256 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=52 ttl=55 time=5929 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=53 ttl=55 time=5218 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=54 ttl=55 time=4219 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=55 ttl=55 time=511 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=56 ttl=55 time=1102 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=57 ttl=55 time=1179 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=58 ttl=55 time=1210 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=59 ttl=55 time=282 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=60 ttl=55 time=1071 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=61 ttl=55 time=500 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=62 ttl=55 time=528 ms
>
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=58 ttl=55 time=1210 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=59 ttl=55 time=282 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=60 ttl=55 time=1071 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=61 ttl=55 time=500 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=62 ttl=55 time=528 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=63 ttl=55 time=309 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=64 ttl=55 time=1197 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=65 ttl=55 time=377 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=66 ttl=55 time=1076 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=67 ttl=55 time=2735 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=68 ttl=55 time=522 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=69 ttl=55 time=856 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=70 ttl=55 time=496 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=71 ttl=55 time=349 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=72 ttl=55 time=1074 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=73 ttl=55 time=394 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=74 ttl=55 time=1368 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=75 ttl=55 time=505 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=76 ttl=55 time=1672 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=77 ttl=55 time=2001 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=78 ttl=55 time=331 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=79 ttl=55 time=1794 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=80 ttl=55 time=1959 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=81 ttl=55 time=416 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=82 ttl=55 time=677 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=83 ttl=55 time=807 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=84 ttl=55 time=202 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=85 ttl=55 time=583 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=86 ttl=55 time=557 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=87 ttl=55 time=362 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=88 ttl=55 time=433 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=89 ttl=55 time=269 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=90 ttl=55 time=1088 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=91 ttl=55 time=1005 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=92 ttl=55 time=3249 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=93 ttl=55 time=3925 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=94 ttl=55 time=3186 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=95 ttl=55 time=2266 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=96 ttl=55 time=413 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=97 ttl=55 time=390 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=98 ttl=55 time=3159 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=99 ttl=55 time=2164 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=100 ttl=55 time=2764 ms
> 64 bytes from mellon-1-pt.tunnel.tserv9.chi1.ipv6.he.net: icmp_seq=101 ttl=55 time=2235 ms
>
>

comment:6 Changed 11 months ago by panda@…

I'm sorry but I couldn't reproduce it because the session was over when I jumped into the room. I'll keep my eyes on Congress Hall 1/2/3 during after noon sessions, and try to improve it.

Thank you.
-- Hirochika Asai

comment:7 in reply to:  7 ; Changed 11 months ago by mellon@…

Thanks!

On Jul 18, 2017 11:56 AM, "IETF Tickets/NOC" <tickets@meeting.ietf.org>
wrote:

> #1117: ietf-nat64 completely dead in Congress III
> ---------------------------+--------------------------------
>       Reporter:  mellon@…  |                Owner:  panda@…
>           Type:  defect    |               Status:  reopened
>       Priority:  tbd       |            Milestone:  ietf-99
>      Component:  wireless  |           Resolution:
>       Keywords:            |  My Current Location:
> My MAC  Address:           |                My OS:
> ---------------------------+--------------------------------
>
> Comment (by panda@…):
>
>  I'm sorry but I couldn't reproduce it because the session was over when I
>  jumped into the room. I'll keep my eyes on Congress Hall 1/2/3 during
>  after noon sessions, and try to improve it.
>
>  Thank you.
>  -- Hirochika Asai
>
> --
> Ticket URL: <https://tickets.meeting.ietf.org/ticket/1117#comment:6>
> IETF Tickets/NOC <https://tickets.meeting.ietf.org>
> IETF Meeting Tickets - NOC pages
>

comment:8 Changed 11 months ago by panda@…

Resolution: fixed
Status: reopenedclosed

Again, thank you very much for your report.

We tuned our wireless networks in Congress Hall 1/2/3 last night.
I'm closing this ticket but please reopen it if you have any problems again.

Thank you!
Hirochika Asai

comment:9 Changed 7 months ago by Rick Alfvin

Milestone: ietf-99ietf-099

Milestone renamed

Note: See TracTickets for help on using tickets.