#1239 closed defect (fixed)

ipv6 wonkiness

Reported by: morrowc@… Owned by: Clemens Schrimpe
Priority: tbd Milestone: ietf-103
Component: network Keywords:
Cc: jari.arkko@… My Current Location:
My MAC Address: My OS:

Description

howdy!
I noticed that i can't ping (ipv6 ping) a bunch of things like:
  ~$ ping ipv6.google.com
PING ipv6.google.com(sin10s02-in-x0e.1e100.net (2404:6800:4003:80d::200e))
56 data bytes
^C
--- ipv6.google.com ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1020ms

$ ping www.google.com
PING www.google.com(sin10s02-in-x04.1e100.net (2404:6800:4003:80d::2004))
56 data bytes
^C
--- www.google.com ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2028ms


$ ping mailserver.ops-netman.net
PING mailserver.ops-netman.net(mail-v6.ops-netman.net
(2606:700:e:550:b00b::b00b)) 56 data bytes
^C
--- mailserver.ops-netman.net ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1002ms


I thought (until the third item) that this was my fault ... but! I think
it's not (at least not for the reason I originally thought)... I also can't
connect over ipv6 to services which SHOULD be running, like:
  $ telnet ipv6.google.com 443
Trying 2404:6800:4003:80d::200e...
^C


 $  telnet www.google.com 443
Trying 2404:6800:4003:80d::2004...
^C


$ telnet mailserver.ops-netman.net 22
Trying 2606:700:e:550:b00b::b00b...
^C


I CAN connect to these from a point not on the current IETF network:
$ telnet mailserver.ops-netman.net 22
Trying 2606:700:e:550:b00b::b00b...
Connected to mailserver.ops-netman.net.
Escape character is '^]'.
SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.10

morrowc@mailserver:~$ telnet 2404:6800:4003:80d::200e 443
Trying 2404:6800:4003:80d::200e...
Connected to 2404:6800:4003:80d::200e.
Escape character is '^]'.
^C


etc... I'm currently connected like:
wlp4s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 31.133.150.204  netmask 255.255.240.0  broadcast 31.133.159.255
        inet6 2001:67c:1232:144:b9ed:17ed:ae56:8b13  prefixlen 64  scopeid
0x0<global>
        inet6 fe80::62c4:fd66:ec98:d73  prefixlen 64  scopeid 0x20<link>
        ether f8:59:71:bc:c5:8c  txqueuelen 1000  (Ethernet)
        RX packets 31475690  bytes 39753655118 (37.0 GiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 8273253  bytes 3693695699 (3.4 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

morrowc@morrowc-glaptop2:~$ iw wlp4s0 link
Connected to 74:3e:2b:fd:a9:c8 (on wlp4s0)
SSID: ietf-hotel
freq: 2412
RX: 22645257 bytes (76760 packets)
TX: 5949851 bytes (12409 packets)
signal: -62 dBm
tx bitrate: 130.0 MBit/s MCS 14 short GI

bss flags: short-preamble short-slot-time
dtim period: 1
beacon int: 100

Change history (10)

comment:1 Changed 13 months ago by jim@…

Owner: changed from < default > to Clemens Schrimpe
Status: newassigned

comment:2 Changed 13 months ago by llynch@…

Component: incomingnetwork
Type: requestdefect

comment:3 in reply to:  3 ; Changed 13 months ago by morrowc@…

morrowc@morrowc-glaptop2:~$ iw wlp4s0 link
Connected to 74:3e:2b:bf:69:1c (on wlp4s0)
SSID: ietf-hotel
freq: 5240
RX: 796777 bytes (2126 packets)
TX: 442618 bytes (1443 packets)
signal: -65 dBm
tx bitrate: 130.0 MBit/s VHT-MCS 6 short GI VHT-NSS 2

bss flags: short-slot-time
dtim period: 1
beacon int: 100
morrowc@morrowc-glaptop2:~$ ping www.google.com
PING www.google.com(sin10s02-in-x04.1e100.net (2404:6800:4003:80d::2004))
56 data bytes
^C
--- www.google.com ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4072ms


still broken in hackathon.

On Sat, Nov 3, 2018 at 2:48 PM IETF Tickets/NOC <tickets@meeting.ietf.org>
wrote:

> #1239: ipv6 wonkiness
> ----------------------------+----------------------------------------
>       Reporter:  morrowc@…  |                Owner:  Clemens Schrimpe
>           Type:  defect     |               Status:  assigned
>       Priority:  tbd        |            Milestone:  ietf-103
>      Component:  network    |           Resolution:
>       Keywords:             |  My Current Location:
> My MAC  Address:            |                My OS:
> ----------------------------+----------------------------------------
> Changes (by llynch@…):
>
>  * type:  request => defect
>  * component:  incoming => network
>
>
> --
> Ticket URL: <https://tickets.meeting.ietf.org/ticket/1239#comment:2>
> IETF Tickets/NOC <https://tickets.meeting.ietf.org>
> IETF Meeting Tickets - NOC pages
>

comment:4 in reply to:  4 ; Changed 13 months ago by morrowc@…

morrowc@morrowc-glaptop2:~$ iw wlp4s0 link
Connected to 74:3e:2b:fe:4a:8c (on wlp4s0)
SSID: ietf-hotel
freq: 5200
RX: 359403 bytes (1034 packets)
TX: 151371 bytes (522 packets)
signal: -66 dBm
tx bitrate: 104.0 MBit/s VHT-MCS 5 VHT-NSS 2

bss flags: short-slot-time
dtim period: 1
beacon int: 100
morrowc@morrowc-glaptop2:~$ ping www.google.com
PING www.google.com(sin10s02-in-x04.1e100.net (2404:6800:4003:80d::2004))
56 data bytes
^C
--- www.google.com ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1012ms


different (again) BSSID.... also still broken. Trying now to find iw
commands to associate to the correct bssid.


On Sat, Nov 3, 2018 at 3:02 PM IETF Tickets/NOC <tickets@meeting.ietf.org>
wrote:

> #1239: ipv6 wonkiness
> ----------------------------+----------------------------------------
>       Reporter:  morrowc@…  |                Owner:  Clemens Schrimpe
>           Type:  defect     |               Status:  assigned
>       Priority:  tbd        |            Milestone:  ietf-103
>      Component:  network    |           Resolution:
>       Keywords:             |  My Current Location:
> My MAC  Address:            |                My OS:
> ----------------------------+----------------------------------------
>
> Comment (by morrowc@…):
>
>  {{{
>  morrowc@morrowc-glaptop2:~$ iw wlp4s0 link
>  Connected to 74:3e:2b:bf:69:1c (on wlp4s0)
>  SSID: ietf-hotel
>  freq: 5240
>  RX: 796777 bytes (2126 packets)
>  TX: 442618 bytes (1443 packets)
>  signal: -65 dBm
>  tx bitrate: 130.0 MBit/s VHT-MCS 6 short GI VHT-NSS 2
>
>  bss flags: short-slot-time
>  dtim period: 1
>  beacon int: 100
>  morrowc@morrowc-glaptop2:~$ ping www.google.com
>  PING www.google.com(sin10s02-in-x04.1e100.net (2404:6800:4003:80d::2004))
>  56 data bytes
>  ^C
>  --- www.google.com ping statistics ---
>  5 packets transmitted, 0 received, 100% packet loss, time 4072ms
>
>
>  still broken in hackathon.
>
>  On Sat, Nov 3, 2018 at 2:48 PM IETF Tickets/NOC <tickets@meeting.ietf.org
> >
>  wrote:
>
>  > #1239: ipv6 wonkiness
>  > ----------------------------+----------------------------------------
>  >       Reporter:  morrowc@…  |                Owner:  Clemens Schrimpe
>  >           Type:  defect     |               Status:  assigned
>  >       Priority:  tbd        |            Milestone:  ietf-103
>  >      Component:  network    |           Resolution:
>  >       Keywords:             |  My Current Location:
>  > My MAC  Address:            |                My OS:
>  > ----------------------------+----------------------------------------
>  > Changes (by llynch@…):
>  >
>  >  * type:  request => defect
>  >  * component:  incoming => network
>  >
>  >
>  > --
>  > Ticket URL: <https://tickets.meeting.ietf.org/ticket/1239#comment:2>
>  > IETF Tickets/NOC <https://tickets.meeting.ietf.org>
>  > IETF Meeting Tickets - NOC pages
>  >
>  }}}
>
> --
> Ticket URL: <https://tickets.meeting.ietf.org/ticket/1239#comment:3>
> IETF Tickets/NOC <https://tickets.meeting.ietf.org>
> IETF Meeting Tickets - NOC pages
>

comment:5 in reply to:  5 ; Changed 13 months ago by morrowc@…

bouncing around a bit in the BSSID land:
Connected to 74:3e:2b:be:41:98 (on wlp4s0)
SSID: ietf-hotel
freq: 2437
RX: 465581 bytes (916 packets)
TX: 69614 bytes (396 packets)
signal: -56 dBm
tx bitrate: 26.0 MBit/s MCS 3

bss flags: short-preamble short-slot-time
dtim period: 1
beacon int: 100
$ ping www.google.com
PING www.google.com(sin10s02-in-x04.1e100.net (2404:6800:4003:80d::2004))
56 data bytes
^C
--- www.google.com ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1027ms


$ sudo iw wlp4s0 link
Connected to 74:3e:2b:bf:4b:bc (on wlp4s0)
SSID: ietf-hotel
freq: 5220
RX: 51719 bytes (180 packets)
TX: 12815 bytes (61 packets)
signal: -74 dBm
tx bitrate: 86.7 MBit/s VHT-MCS 4 short GI VHT-NSS 2

bss flags: short-slot-time
dtim period: 1
beacon int: 100
morrowc@morrowc-glaptop2:~$ ping www.google.com
PING www.google.com(sin10s02-in-x04.1e100.net (2404:6800:4003:80d::2004))
56 data bytes
64 bytes from sin10s02-in-x04.1e100.net (2404:6800:4003:80d::2004):
icmp_seq=1 ttl=53 time=29.9 ms
^C

$ sudo iw wlp4s0 link
Connected to 74:3e:2b:be:be:78 (on wlp4s0)
SSID: ietf-hotel
freq: 2437
RX: 42349 bytes (201 packets)
TX: 21335 bytes (50 packets)
signal: -63 dBm
tx bitrate: 130.0 MBit/s MCS 14 short GI

bss flags: short-preamble short-slot-time
dtim period: 1
beacon int: 100
morrowc@morrowc-glaptop2:~$ ping www.google.com
PING www.google.com(sin10s02-in-x04.1e100.net (2404:6800:4003:80d::2004))
56 data bytes
^C
--- www.google.com ping statistics ---
2 packets transmitted, 0 received, 100% packet

$ sudo iw wlp4s0 link
Connected to 74:3e:2b:bf:4c:f8 (on wlp4s0)
SSID: ietf-hotel
freq: 2437
RX: 72299 bytes (313 packets)
TX: 27937 bytes (164 packets)
signal: -64 dBm
tx bitrate: 39.0 MBit/s MCS 10

bss flags: short-preamble short-slot-time
dtim period: 1
beacon int: 100
morrowc@morrowc-glaptop2:~$ ping www.google.com
PING www.google.com(sin10s02-in-x04.1e100.net (2404:6800:4003:80d::2004))
56 data bytes
^C
--- www.google.com ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1031ms



And finaly this is the original BSSID:
$ sudo iw wlp4s0 link
Connected to 74:3e:2b:fd:a9:c8 (on wlp4s0)
SSID: ietf-hotel
freq: 2412
RX: 78470 bytes (302 packets)
TX: 96698 bytes (162 packets)
signal: -65 dBm
tx bitrate: 21.7 MBit/s MCS 2 short GI

bss flags: short-preamble short-slot-time
dtim period: 1
beacon int: 100
morrowc@morrowc-glaptop2:~$ ping www.google.com
PING www.google.com(sin10s02-in-x04.1e100.net (2404:6800:4003:80d::2004))
56 data bytes
^C
--- www.google.com ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2037ms


and it's stil broken.

On Sat, Nov 3, 2018 at 3:52 PM Chris Morrow <morrowc@google.com> wrote:

>
> morrowc@morrowc-glaptop2:~$ iw wlp4s0 link
> Connected to 74:3e:2b:fe:4a:8c (on wlp4s0)
> SSID: ietf-hotel
> freq: 5200
> RX: 359403 bytes (1034 packets)
> TX: 151371 bytes (522 packets)
> signal: -66 dBm
> tx bitrate: 104.0 MBit/s VHT-MCS 5 VHT-NSS 2
>
> bss flags: short-slot-time
> dtim period: 1
> beacon int: 100
> morrowc@morrowc-glaptop2:~$ ping www.google.com
> PING www.google.com(sin10s02-in-x04.1e100.net (2404:6800:4003:80d::2004))
> 56 data bytes
> ^C
> --- www.google.com ping statistics ---
> 2 packets transmitted, 0 received, 100% packet loss, time 1012ms
>
>
> different (again) BSSID.... also still broken. Trying now to find iw
> commands to associate to the correct bssid.
>
>
> On Sat, Nov 3, 2018 at 3:02 PM IETF Tickets/NOC <tickets@meeting.ietf.org>
> wrote:
>
>> #1239: ipv6 wonkiness
>> ----------------------------+----------------------------------------
>>       Reporter:  morrowc@…  |                Owner:  Clemens Schrimpe
>>           Type:  defect     |               Status:  assigned
>>       Priority:  tbd        |            Milestone:  ietf-103
>>      Component:  network    |           Resolution:
>>       Keywords:             |  My Current Location:
>> My MAC  Address:            |                My OS:
>> ----------------------------+----------------------------------------
>>
>> Comment (by morrowc@…):
>>
>>  {{{
>>  morrowc@morrowc-glaptop2:~$ iw wlp4s0 link
>>  Connected to 74:3e:2b:bf:69:1c (on wlp4s0)
>>  SSID: ietf-hotel
>>  freq: 5240
>>  RX: 796777 bytes (2126 packets)
>>  TX: 442618 bytes (1443 packets)
>>  signal: -65 dBm
>>  tx bitrate: 130.0 MBit/s VHT-MCS 6 short GI VHT-NSS 2
>>
>>  bss flags: short-slot-time
>>  dtim period: 1
>>  beacon int: 100
>>  morrowc@morrowc-glaptop2:~$ ping www.google.com
>>  PING www.google.com(sin10s02-in-x04.1e100.net
>> (2404:6800:4003:80d::2004))
>>  56 data bytes
>>  ^C
>>  --- www.google.com ping statistics ---
>>  5 packets transmitted, 0 received, 100% packet loss, time 4072ms
>>
>>
>>  still broken in hackathon.
>>
>>  On Sat, Nov 3, 2018 at 2:48 PM IETF Tickets/NOC <
>> tickets@meeting.ietf.org>
>>  wrote:
>>
>>  > #1239: ipv6 wonkiness
>>  > ----------------------------+----------------------------------------
>>  >       Reporter:  morrowc@…  |                Owner:  Clemens Schrimpe
>>  >           Type:  defect     |               Status:  assigned
>>  >       Priority:  tbd        |            Milestone:  ietf-103
>>  >      Component:  network    |           Resolution:
>>  >       Keywords:             |  My Current Location:
>>  > My MAC  Address:            |                My OS:
>>  > ----------------------------+----------------------------------------
>>  > Changes (by llynch@…):
>>  >
>>  >  * type:  request => defect
>>  >  * component:  incoming => network
>>  >
>>  >
>>  > --
>>  > Ticket URL: <https://tickets.meeting.ietf.org/ticket/1239#comment:2>
>>  > IETF Tickets/NOC <https://tickets.meeting.ietf.org>
>>  > IETF Meeting Tickets - NOC pages
>>  >
>>  }}}
>>
>> --
>> Ticket URL: <https://tickets.meeting.ietf.org/ticket/1239#comment:3>
>> IETF Tickets/NOC <https://tickets.meeting.ietf.org>
>> IETF Meeting Tickets - NOC pages
>>
>

comment:6 Changed 13 months ago by Clemens Schrimpe

The hotel is working on it. We have finally (hopefully) gotten them into a "mode" where they hunt down "broken AP configs" themselves and they're now roaming the dungeons to do just that.

Bear with us, meanwhile!

comment:7 Changed 13 months ago by jim@…

Cc: jari.arkko@… added

Jari had opened another ticket (1240) that was the exact same issue, so I've closed that and added him as a CC here...

comment:8 Changed 13 months ago by jim@…

Our friends at GuesTek? claim to have made the changes necessary to fix this throughout the hotel. Our (limited) testing has indicated that this has been resolved. Please test and see if you see the fixed behavior? Will close this ticket in 24 hrs if nothing new pops up.

-JIm

comment:9 in reply to:  9 ; Changed 13 months ago by jari.arkko@…

I have verified that the fix now works in the area that I previously had a problem in (9th floor, terminal room).

Thanks!

Jari

> On 4 Nov 2018, at 15.06, IETF Tickets/NOC <tickets@meeting.ietf.org> wrote:
> 
> #1239: ipv6 wonkiness
> ----------------------------+----------------------------------------
>     Reporter:  morrowc@…  |                Owner:  Clemens Schrimpe
>         Type:  defect     |               Status:  assigned
>     Priority:  tbd        |            Milestone:  ietf-103
>    Component:  network    |           Resolution:
>     Keywords:             |  My Current Location:
> My MAC  Address:            |                My OS:
> ----------------------------+----------------------------------------
> 
> Comment (by jim@…):
> 
> Our friends at GuesTek claim to have made the changes necessary to fix
> this throughout the hotel. Our (limited) testing has indicated that this
> has been resolved. Please test and see if you see the fixed behavior? Will
> close this ticket in 24 hrs if nothing new pops up.
> 
> -JIm
> 
> -- 
> Ticket URL: <https://tickets.meeting.ietf.org/ticket/1239#comment:8>
> IETF Tickets/NOC <https://tickets.meeting.ietf.org>
> IETF Meeting Tickets - NOC pages

comment:10 Changed 13 months ago by jim@…

Resolution: fixed
Status: assignedclosed

Excellent! I'll close this. Please let us know if you have any further issues. Thanks for your help in testing!

Note: See TracTickets for help on using tickets.