#1227 closed request (pending)

Eduroam : Traffic stopped passing

Reported by: benoit@… Owned by: panda@…
Priority: minor Milestone: ietf-102
Component: wireless Keywords:
Cc: My Current Location: NOC
My MAC Address: 9c:b6:d0:8a:9b:1b My OS:

Description

Benoît reports that while connected to Eduroam he had lost traffic twice, while not being dropped from Eduroam. After reassociating it work, and then lost traffic again.

Benoît came to NOC to report issue, and was tested connecting to ietf-legacy102 (successful), and then back to eduroam (successful)..

Benoît is going to report back with any further issues they may have.

-Con

Attachments (1)

2018-07-16_1920x1080_17:34:53.png (1.9 MB) - added by b.viguier@… 14 months ago.
Note that you have to 6 hours to get local time…

Download all attachments as: .zip

Change history (14)

comment:1 Changed 14 months ago by panda@…

Owner: changed from ralfvin@… to panda@…
Status: assignedaccepted

Hi Con,

Thank you for your report.

I have checked the log and found an interference is reported by the AP that his device had associated with around 13:50. I don't think it is an eduroam-specific issue but a WiFi? issue. I'll work on rearrangement of WiFi? channels to improve the quality of service.

Thank you!
Hirochika Asai

comment:2 Changed 14 months ago by llynch@…

Hi -

I'm in Centre-Ville and just lost connections on Eduroam - reconnected to IETF and I have packets.

  • Lucy

[root@hecate llynch]# ifconfig
ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500

inet 172.16.138.156 netmask 255.255.255.0 broadcast 172.16.138.255
inet6 fe80::8edd:783c:8348:aad7 prefixlen 64 scopeid 0x20<link>
ether 00:0c:29:e2:01:73 txqueuelen 1000 (Ethernet)
RX packets 434222 bytes 441914396 (421.4 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 161714 bytes 16586687 (15.8 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536

inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 2720 bytes 224408 (219.1 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2720 bytes 224408 (219.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

comment:3 Changed 14 months ago by llynch@…

and connected now via eduroam

root@hecate llynch]# ifconfig
ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500

inet 172.16.138.156 netmask 255.255.255.0 broadcast 172.16.138.255
inet6 fe80::8edd:783c:8348:aad7 prefixlen 64 scopeid 0x20<link>
ether 00:0c:29:e2:01:73 txqueuelen 1000 (Ethernet)
RX packets 434719 bytes 442075088 (421.5 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 162189 bytes 16652746 (15.8 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536

inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 3200 bytes 264188 (257.9 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3200 bytes 264188 (257.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

comment:4 Changed 14 months ago by panda@…

Hi Lucy,

ens33 seems to be wired port. Can you give us the information of your wireless interface so that I can check the authentication log of eduroam?

Thanks.
Hirochika Asai

comment:5 Changed 14 months ago by b.viguier@…

Hi,

I'm constantly pinging to monitor my internet connection, here is what I saw when Lucy and I lost connection.

64 bytes from 8.8.8.8: icmp_seq=1769 ttl=46 time=27.483 ms
64 bytes from 8.8.8.8: icmp_seq=1770 ttl=46 time=27.837 ms
64 bytes from 8.8.8.8: icmp_seq=1771 ttl=46 time=486.606 ms
92 bytes from dhcp-8544.meeting.ietf.org (31.133.133.68): Destination Host Unreachable
92 bytes from dhcp-8544.meeting.ietf.org (31.133.133.68): Destination Host Unreachable
92 bytes from dhcp-8544.meeting.ietf.org (31.133.133.68): Destination Host Unreachable
64 bytes from 8.8.8.8: icmp_seq=1813 ttl=46 time=47.788 ms
64 bytes from 8.8.8.8: icmp_seq=1814 ttl=46 time=26.644 ms

iwconfig was still displaying that I'm connected to Eduroam though.

Changed 14 months ago by b.viguier@…

Note that you have to 6 hours to get local time...

comment:6 Changed 14 months ago by b.viguier@…

Note subtract 6 hours to get local time...

2018-07-16_17:22:32: 64 bytes from 8.8.8.8: icmp_seq=206 ttl=46 time=26.472 ms
2018-07-16_17:22:33: 64 bytes from 8.8.8.8: icmp_seq=207 ttl=46 time=26.339 ms
2018-07-16_17:22:34: 64 bytes from 8.8.8.8: icmp_seq=208 ttl=46 time=26.318 ms
2018-07-16_17:22:35: 64 bytes from 8.8.8.8: icmp_seq=209 ttl=46 time=31.617 ms
2018-07-16_17:22:36: 64 bytes from 8.8.8.8: icmp_seq=210 ttl=46 time=28.560 ms
2018-07-16_17:22:37: 64 bytes from 8.8.8.8: icmp_seq=211 ttl=46 time=26.488 ms
2018-07-16_17:22:38: 64 bytes from 8.8.8.8: icmp_seq=212 ttl=46 time=25.526 ms
2018-07-16_17:23:46: 92 bytes from biv-xps (31.133.133.68): Destination Host Unreachable
2018-07-16_17:24:14: 92 bytes from biv-xps (31.133.133.68): Destination Host Unreachable
2018-07-16_17:24:42: 92 bytes from biv-xps (31.133.133.68): Destination Host Unreachable
2018-07-16_17:25:10: 92 bytes from biv-xps (31.133.133.68): Destination Host Unreachable
2018-07-16_17:25:41: 92 bytes from biv-xps (31.133.133.68): Destination Host Unreachable
2018-07-16_17:26:09: 92 bytes from biv-xps (31.133.133.68): Destination Host Unreachable
2018-07-16_17:26:37: 92 bytes from biv-xps (31.133.133.68): Destination Host Unreachable
2018-07-16_17:27:05: 92 bytes from biv-xps (31.133.133.68): Destination Host Unreachable
2018-07-16_17:27:36: 92 bytes from biv-xps (31.133.133.68): Destination Host Unreachable
2018-07-16_17:28:04: 92 bytes from biv-xps (31.133.133.68): Destination Host Unreachable
2018-07-16_17:28:32: 92 bytes from biv-xps (31.133.133.68): Destination Host Unreachable
2018-07-16_17:29:00: 92 bytes from biv-xps (31.133.133.68): Destination Host Unreachable
2018-07-16_17:29:31: 92 bytes from biv-xps (31.133.133.68): Destination Host Unreachable
2018-07-16_17:29:59: 92 bytes from biv-xps (31.133.133.68): Destination Host Unreachable
2018-07-16_17:30:27: 92 bytes from biv-xps (31.133.133.68): Destination Host Unreachable
2018-07-16_17:30:57: 92 bytes from biv-xps (31.133.133.68): Destination Host Unreachable
2018-07-16_17:31:25: 92 bytes from biv-xps (31.133.133.68): Destination Host Unreachable
2018-07-16_17:31:54: 92 bytes from biv-xps (31.133.133.68): Destination Host Unreachable
2018-07-16_17:32:24: 92 bytes from biv-xps (31.133.133.68): Destination Host Unreachable
2018-07-16_17:32:46: 92 bytes from dhcp-8544.meeting.ietf.org (31.133.133.68): Destination Host Unreachable
2018-07-16_17:32:54: 92 bytes from dhcp-8544.meeting.ietf.org (31.133.133.68): Destination Host Unreachable
2018-07-16_17:33:04: 92 bytes from dhcp-8544.meeting.ietf.org (31.133.133.68): Destination Host Unreachable
2018-07-16_17:33:12: 92 bytes from dhcp-8544.meeting.ietf.org (31.133.133.68): Destination Host Unreachable
2018-07-16_17:33:22: 92 bytes from dhcp-8544.meeting.ietf.org (31.133.133.68): Destination Host Unreachable
2018-07-16_17:33:30: 92 bytes from dhcp-8544.meeting.ietf.org (31.133.133.68): Destination Host Unreachable
2018-07-16_17:33:38: 92 bytes from dhcp-8544.meeting.ietf.org (31.133.133.68): Destination Host Unreachable
2018-07-16_17:33:47: 92 bytes from dhcp-8544.meeting.ietf.org (31.133.133.68): Destination Host Unreachable
2018-07-16_17:33:56: 92 bytes from dhcp-8544.meeting.ietf.org (31.133.133.68): Destination Host Unreachable
2018-07-16_17:34:04: 92 bytes from dhcp-8544.meeting.ietf.org (31.133.133.68): Destination Host Unreachable
2018-07-16_17:34:14: 92 bytes from dhcp-8544.meeting.ietf.org (31.133.133.68): Destination Host Unreachable
2018-07-16_17:34:22: 92 bytes from dhcp-8544.meeting.ietf.org (31.133.133.68): Destination Host Unreachable
2018-07-16_17:34:30: 92 bytes from dhcp-8544.meeting.ietf.org (31.133.133.68): Destination Host Unreachable
2018-07-16_17:34:39: 92 bytes from dhcp-8544.meeting.ietf.org (31.133.133.68): Destination Host Unreachable
2018-07-16_17:34:48: 92 bytes from dhcp-8544.meeting.ietf.org (31.133.133.68): Destination Host Unreachable
2018-07-16_17:34:56: 92 bytes from dhcp-8544.meeting.ietf.org (31.133.133.68): Destination Host Unreachable
2018-07-16_17:35:05: 92 bytes from dhcp-8544.meeting.ietf.org (31.133.133.68): Destination Host Unreachable
2018-07-16_17:35:13: 92 bytes from dhcp-8544.meeting.ietf.org (31.133.133.68): Destination Host Unreachable
2018-07-16_17:35:21: 92 bytes from dhcp-8544.meeting.ietf.org (31.133.133.68): Destination Host Unreachable
2018-07-16_17:35:31: 92 bytes from dhcp-8544.meeting.ietf.org (31.133.133.68): Destination Host Unreachable
^C
ping 31.133.128.1
PING 31.133.128.1 (31.133.128.1): 56 data bytes
92 bytes from biv-xps (31.133.133.68): Destination Host Unreachable
92 bytes from biv-xps (31.133.133.68): Destination Host Unreachable
92 bytes from biv-xps (31.133.133.68): Destination Host Unreachable
92 bytes from biv-xps (31.133.133.68): Destination Host Unreachable
92 bytes from biv-xps (31.133.133.68): Destination Host Unreachable
92 bytes from biv-xps (31.133.133.68): Destination Host Unreachable
92 bytes from biv-xps (31.133.133.68): Destination Host Unreachable
92 bytes from biv-xps (31.133.133.68): Destination Host Unreachable
92 bytes from biv-xps (31.133.133.68): Destination Host Unreachable
92 bytes from dhcp-8544.meeting.ietf.org (31.133.133.68): Destination Host Unreachable
92 bytes from dhcp-8544.meeting.ietf.org (31.133.133.68): Destination Host Unreachable
92 bytes from dhcp-8544.meeting.ietf.org (31.133.133.68): Destination Host Unreachable
92 bytes from dhcp-8544.meeting.ietf.org (31.133.133.68): Destination Host Unreachable
92 bytes from dhcp-8544.meeting.ietf.org (31.133.133.68): Destination Host Unreachable
92 bytes from dhcp-8544.meeting.ietf.org (31.133.133.68): Destination Host Unreachable
92 bytes from dhcp-8544.meeting.ietf.org (31.133.133.68): Destination Host Unreachable
92 bytes from dhcp-8544.meeting.ietf.org (31.133.133.68): Destination Host Unreachable
sudo ip addr       
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: wlp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 9c:b6:d0:8a:9b:1b brd ff:ff:ff:ff:ff:ff
    inet 31.133.133.68/20 brd 31.133.143.255 scope global dynamic noprefixroute wlp1s0
       valid_lft 1090sec preferred_lft 1090sec
    inet6 2001:67c:370:128:1ff9:4604:2328:d2f9/64 scope global dynamic noprefixroute 
       valid_lft 2591933sec preferred_lft 604733sec
    inet6 fe80::3eac:27a4:c1d7:a2d5/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
sudo iwconfig 
               
wlp1s0    IEEE 802.11  ESSID:"eduroam"  
          Mode:Managed  Frequency:5.5 GHz  Access Point: 38:90:A5:EE:ED:07   
          Bit Rate=6 Mb/s   Tx-Power=23 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:on
          Link Quality=59/70  Signal level=-51 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:11   Missed beacon:0

lo        no wireless extensions.

comment:7 Changed 14 months ago by panda@…

Hi,

Thank you for your providing the detail information.

The log says:
10:48 ch.161
10:49-10:50 ch.36
10:51 ch.48
10:52-11:17 ch.161
11:18-now ch.100

Did you manually try to re-associate? If not, there seems to be a compatibility issue with your WiFi? hardware/driver. Can you tell us your WiFi? chipset and version? I'll also investigate a further possibility.

Thank you.
Hirochika Asai

comment:8 Changed 14 months ago by panda@…

Oops, it was a little bit unclear.

The log says that your device frequently changed access points. The following is the time and the channel your were using:
10:48 ch.161
10:49-10:50 ch.36
10:51 ch.48
10:52-11:17 ch.161
11:18-now ch.100

comment:9 Changed 14 months ago by b.viguier@…

Hardware is as follow:

sudo lshw -C network
  *-network                 
       description: Wireless interface
       product: QCA6174 802.11ac Wireless Network Adapter
       vendor: Qualcomm Atheros
       physical id: 0
       bus info: pci@0000:01:00.0
       logical name: wlp1s0
       version: 32
       serial: 9c:b6:d0:8a:9b:1b
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=ath10k_pci driverversion=4.16.0-2-amd64 firmware=WLAN.RM.4.4-00022-QCARMSWPZ-2 ip=31.133.133.68 latency=0 link=yes multicast=yes wireless=IEEE 802.11
       resources: irq:131 memory:dc000000-dc1fffff
sudo modinfo ath10k_pci
filename:       /lib/modules/4.16.0-2-amd64/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko
firmware:       ath10k/QCA9377/hw1.0/board.bin
firmware:       ath10k/QCA9377/hw1.0/firmware-5.bin
firmware:       ath10k/QCA6174/hw3.0/board-2.bin
firmware:       ath10k/QCA6174/hw3.0/board.bin
firmware:       ath10k/QCA6174/hw3.0/firmware-6.bin
firmware:       ath10k/QCA6174/hw3.0/firmware-5.bin
firmware:       ath10k/QCA6174/hw3.0/firmware-4.bin
firmware:       ath10k/QCA6174/hw2.1/board-2.bin
firmware:       ath10k/QCA6174/hw2.1/board.bin
firmware:       ath10k/QCA6174/hw2.1/firmware-5.bin
firmware:       ath10k/QCA6174/hw2.1/firmware-4.bin
firmware:       ath10k/QCA9887/hw1.0/board-2.bin
firmware:       ath10k/QCA9887/hw1.0/board.bin
firmware:       ath10k/QCA9887/hw1.0/firmware-5.bin
firmware:       ath10k/QCA988X/hw2.0/board-2.bin
firmware:       ath10k/QCA988X/hw2.0/board.bin
firmware:       ath10k/QCA988X/hw2.0/firmware-5.bin
firmware:       ath10k/QCA988X/hw2.0/firmware-4.bin
firmware:       ath10k/QCA988X/hw2.0/firmware-3.bin
firmware:       ath10k/QCA988X/hw2.0/firmware-2.bin
license:        Dual BSD/GPL
description:    Driver support for Qualcomm Atheros 802.11ac WLAN PCIe/AHB devices
author:         Qualcomm Atheros
alias:          pci:v0000168Cd00000050sv*sd*bc*sc*i*
alias:          pci:v0000168Cd00000042sv*sd*bc*sc*i*
alias:          pci:v0000168Cd00000046sv*sd*bc*sc*i*
alias:          pci:v0000168Cd00000056sv*sd*bc*sc*i*
alias:          pci:v0000168Cd00000040sv*sd*bc*sc*i*
alias:          pci:v0000168Cd0000003Esv*sd*bc*sc*i*
alias:          pci:v0000168Cd00000041sv*sd*bc*sc*i*
alias:          pci:v0000168Cd0000003Csv*sd*bc*sc*i*
alias:          pci:v00000777d000011ACsv*sd*bc*sc*i*
depends:        ath10k_core
retpoline:      Y
intree:         Y
name:           ath10k_pci
vermagic:       4.16.0-2-amd64 SMP mod_unload modversions 
parm:           irq_mode:0: auto, 1: legacy, 2: msi (default: 0) (uint)
parm:           reset_mode:0: auto, 1: warm only (default: 0) (uint)
Last edited 14 months ago by b.viguier@… (previous) (diff)

comment:10 Changed 14 months ago by panda@…

Thank you. We'll see if there's a known issue and seek for workaround.

comment:11 Changed 14 months ago by b.viguier@…

I have been on ietf-legacy102 for about 1:10 hour, no loss of ping and ping6.

comment:12 Changed 14 months ago by panda@…

Good news! So, the problem seems to be specific to 802.1X. I've created a special SSID that disables suspicious configuration (session timeout), ietf-test, with the same credential as ietf. Can you try ietf-test?

Thanks!
Hirochika Asai

comment:13 Changed 14 months ago by panda@…

Resolution: pending
Status: acceptedclosed

Hi,

Thanks to your troubleshooting, we could found that the cause was the compatibility between your device and our controllers for Session Timeout configuration. Our network has been in production so I would not like to make a change to the global configuration. However, we will test and deploy the workaround in the next meeting in Bangkok.

Thank you!
Hirochika Asai

Note: See TracTickets for help on using tickets.