Opened 3 years ago

Closed 3 years ago

Last modified 2 months ago

#943 closed defect (worksforme)

just FYI regarding wifi

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

Description

Hi,

I am in Karlin I/II. I have a late 2013 15" retina macbook pro, running 
10.10.4.

I had continous wifi disconnects, it would connect, stay connected for 30 
seconds, then disconnect, I had to turn off/on wifi, then process 
restarted. This has happened to me before, primarly at earlier IETF 
meetings.

I shut down the macbook, and powered it back on again, which fixed the 
problem. This might very well be a problem with OSX and/or wifi card 
firmware, but I just wanted to let you know this happened. I since the 
cold boot, I have now been connected without issue for 30+ minutes. The 
cold boot approach has solved the problem at earlier IETFs as well.

I believe this might be an interaction between the type of APs being used 
here, and my macbook, because this has happened not only at earlier IETFs, 
but at a few other places for me as well during the 1.5 years I've had 
this macbook.

Is there anything I can do to find out more information next time this 
happens so the issue can be better diagnosed?

I arrived at the hilton early on saturday and successfully used the IETF 
network in hackathon and a few other places before this issue presented 
itself right now, so it might also be that it's just the AP here in Karlin 
I/II having problems. I had similar behaviour at earlier IETFs, that the 
problem just happened in a single room, so it might actually just be a 
single or few APs having this problem.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

Change history (14)

comment:1 Changed 3 years ago by jclarke@…

Owner: changed from llynch@… to jclarke@…
Status: newassigned

comment:2 Changed 3 years ago by llynch@…

Component: incomingwireless
Type: requestdefect

comment:3 Changed 3 years ago by jclarke@…

Hey, Mikael. I'm also in Karlin but not seeing any issues with my MacBook?. If you hold down Option and click on the WiFi? icon, what do you see for BSSID, RSSI, and noise? To what SSID are you associated? When you see this problem do you lose association, or is it that network responsiveness just stops?

comment:4 Changed 3 years ago by swmike@…

On Mon, 20 Jul 2015, IETF Meeting/NOC wrote:

> Hey, Mikael.  I'm also in Karlin but not seeing any issues with my 
> MacBook.  If you hold down Option and click on the WiFi icon, what do 
> you see for BSSID, RSSI, and noise?  To what SSID are you associated? 
> When you see this problem do you lose association, or is it that network 
> responsiveness just stops?

After reboot, the problem went away. I was using the "ietf" SSID, both 
before and after.

Well, the network became unresponsive, I don't remember if it 
de-associated or not, but I had to turn off/on the wifi to get it working 
again.

Currently I am seeing channel 136, 802.11ac, RSSI -51, noise -95 and tx 
rate around 190 megabit/s.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

comment:5 Changed 3 years ago by jclarke@…

On 7/20/15 05:02, Mikael Abrahamsson wrote:
> On Mon, 20 Jul 2015, IETF Meeting/NOC wrote:
>
>> Hey, Mikael.  I'm also in Karlin but not seeing any issues with my
>> MacBook.  If you hold down Option and click on the WiFi icon, what do
>> you see for BSSID, RSSI, and noise?  To what SSID are you associated?
>> When you see this problem do you lose association, or is it that
>> network responsiveness just stops?
>
> After reboot, the problem went away. I was using the "ietf" SSID, both
> before and after.
>
> Well, the network became unresponsive, I don't remember if it
> de-associated or not, but I had to turn off/on the wifi to get it
> working again.
>
> Currently I am seeing channel 136, 802.11ac, RSSI -51, noise -95 and tx
> rate around 190 megabit/s.
>

Thanks.  I'm on channel 60 on BSSID ending in fc:04.  Let me know if you 
see the problem again.

Joe

comment:6 Changed 3 years ago by swmike@…

On Mon, 20 Jul 2015, IETF Meeting/NOC wrote:

> Thanks.  I'm on channel 60 on BSSID ending in fc:04.  Let me know if you 
> see the problem again.

As of 15 minutes ago, me nor my colleague with a 2012 macbook pro can 
connect to the ietf ssid. I am now connected to the nat64 one.

We both get this error for the ietf one. I have tried removing the ssid 
and adding it back again in the OSX connection manager, it didn't fix 
anything.

https://discussions.apple.com/thread/1941869?start=0&tstart=0

This is the first time ever I have seen this error.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

comment:7 Changed 3 years ago by jclarke@…

On 7/20/15 05:09, Mikael Abrahamsson wrote:
> On Mon, 20 Jul 2015, IETF Meeting/NOC wrote:
>
>> Thanks.  I'm on channel 60 on BSSID ending in fc:04.  Let me know if
>> you see the problem again.
>
> As of 15 minutes ago, me nor my colleague with a 2012 macbook pro can
> connect to the ietf ssid. I am now connected to the nat64 one.
>
> We both get this error for the ietf one. I have tried removing the ssid
> and adding it back again in the OSX connection manager, it didn't fix
> anything.
>
> https://discussions.apple.com/thread/1941869?start=0&tstart=0
>
> This is the first time ever I have seen this error.
>

We're seeing this in other rooms.  Something is up, and we're 
investigating.  I'll keep you posted.

Joe

comment:8 Changed 3 years ago by jclarke@…

On 7/20/15 05:09, Mikael Abrahamsson wrote:
> On Mon, 20 Jul 2015, IETF Meeting/NOC wrote:
>
>> Thanks.  I'm on channel 60 on BSSID ending in fc:04.  Let me know if
>> you see the problem again.
>
> As of 15 minutes ago, me nor my colleague with a 2012 macbook pro can
> connect to the ietf ssid. I am now connected to the nat64 one.
>
> We both get this error for the ietf one. I have tried removing the ssid
> and adding it back again in the OSX connection manager, it didn't fix
> anything.
>
> https://discussions.apple.com/thread/1941869?start=0&tstart=0
>
> This is the first time ever I have seen this error.
>

ietf-legacy should work for you.

Joe

comment:9 Changed 3 years ago by jclarke@…

We are deploying a change to the APs that should fix this issue. Let me know if you see it again as well as the BSSID of the AP to which you're connected. Thanks.

comment:10 Changed 3 years ago by chelliot@…

Resolution: fixed
Status: assignedclosed

TKIP has been disabled throughout the IETF network. All encryption now uses AES, and the draconian measures that the WPA/TKIP standard require are no longer an issue.

I am closing this ticket. However, if you see this problem again please re-open this ticket.

And, of course, feel free to open another ticket if you have any network issues with the IETF network.

Thanks!
Chris.

comment:11 Changed 3 years ago by swmike@…

Resolution: fixed
Status: closedreopened
On Mon, 20 Jul 2015, IETF Meeting/NOC wrote:

> We are deploying a change to the APs that should fix this issue.  Let me 
> know if you see it again as well as the BSSID of the AP to which you're 
> connected.  Thanks.

Hi,

back to my original problem I reported in #943, I am in the plenary 
session room, 5th row from the front, middle section. I connected to ietf, 
ietf-nat64 and ietf-legacy, and they all worked for around 30 seconds, 
then both v4 and v6 stopped working. The wifi icon showed me as connected, 
tcpdump showed packets received (NS, ARP, so multicast and broadcast, but 
no unicast that I could find), I sent SYNs, but there was no response.

I did this 5 times, every time it would connect, I could send and receive 
packets normally for around 30 seconds, and then it stopped working. 
Identical behaviour on ietf, ietf-nat64 and ietf-legacy.

I then rebooted my macbook and now it's working properly. So as stated 
earlier in the ticket, this has happened to me before at the IETF and a 
few other places, and I believe there is some kind of interaction with 
Cisco APs that causes this problem. With other APs, I can go for months 
without seeing this problem.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

comment:12 Changed 3 years ago by chelliot@…

Interestingly, the APs in Karlin are running in autonomous mode, but the APs here in the Plenary are running in capwap mode using the Cisco 5760 wireless controller. I was hoping we'd see different behavior between the two.

You certainly shouldn't need to reboot your computer, and we would like to figure out what's causing this.

I'm going to speculate that it may have to do with the 802.11d country being sent to the client. The APs in Karlin report they are in CZ, so your laptop may have been unhappy when you first arrived here (note that at least some of the hotel APs are reporting they are in the US...).

The controller-based (capwap) APs here in the Plenary are reporting they are in the US due to the regulatory domain of all the APs we're using and how the wireless controller manages country codes and APs from different regulatory domains.

Please keep us informed--the most important info will continue to be your wireless MAC address and the BSSID (MAC address of the AP supplying the SSID you're connected to).

Thanks!
Chris.

comment:13 Changed 3 years ago by chelliot@…

Resolution: worksforme
Status: reopenedclosed

Mikael,

We haven't heard anything from you in two days. I'm going ahead and closing this ticket. Please feel free to re-open it if necessary.

Thanks for reporting this problem.
Chris.

comment:14 Changed 2 months ago by Rick Alfvin

Milestone: ietf-93ietf-093

Milestone renamed

Note: See TracTickets for help on using tickets.