Re: [90attendees] iPhone wifi weirdness during the conference

[Warren Kumari <[e-mail]>]

On Sun, Jul 27, 2014 at 1:31 PM, William Atwood
<[e-mail]> wrote:
> Michael,
>
> The issue of being shunted off to Google UK was probably due to Google's
> "location" service, which still thought that the IETF was in London
> (which is the last place where 31.133.x.y was seen).  I live in Montreal
> (Canada), and even if I enter google.com, I end up on google.ca.  The
> first morning, I had occasion to open google maps, and when the screen
> came up, it was centered on London.
>
> Chris,
>
> Given the rather strong connection between the senior management at the
> IETF and the senior management at Google, I am wondering if a way could
> be found to "advise" Google (and some of the other location services) as
> to where 31.133.x.y is going to be next.  Google's location service
> thought that I was in London; another IP lookup service that I accessed
> thought that we were in Atlanta.


There is actually a protocol for this --
http://tools.ietf.org/html/draft-google-self-published-geofeeds-02 --
and we even publish a feed: http://noc.ietf.org/geo/google.csv

This file lets Google (and other folk who geolocate) know ahead of
time where the prefixes live. We did all the right bits - we started
announcing the space a few weeks early, we announced it from the right
AS, etc -- unfortunately I forgot the critical step of actually
updating the file... Erik Kline pointed this out to me on the 22nd,
but by then it was too late to make a difference...

So, the Google part at least was my fault. We had tried to progress
this document, but it died because of privacy concerns, and the
authors got tired of pushing it uphill...

W
>
>   Bill
>
>
>
> On 27/07/2014 12:51 PM, Michael StJohns wrote:
>> On 7/26/2014 4:27 PM, Chris Elliott wrote:
>>> We can't fix what we don't know about.
>>
>> Hi Chris -
>>
>> I, like the others, encountered problems with my iPhone and iPad.  But
>> not with my laptop.  That to me said that it was probably something I'd
>> done to myself rather than an issue with the network.  That, coupled
>> with no other reports on the mailing list, led to me not filing a report.
>>
>> I also encountered the issues with connecting to ietf-a through those
>> devices similar to what was mentioned elsewhere, primarily in the
>> lobby.  I didn't use any of the encrypted wireless SSIDs.
>>
>> Unfortunately, all the nice tools I have on my laptop to figure out
>> things don't exists on my iP* devices.
>>
>> My issues manifested with problems reaching certain sites, notably
>> Google.  I kept getting shunted off to Google UK from time to time. That
>> was particularly problematic in that the furshlinger Safari version that
>> is current no longer has separate bars for search vs urls and that led
>> to some interesting  cursing on my part.  I ended up using Bing a number
>> of times as it was reasonably responsive.
>>
>> I've got an iPhone 5s and an iPad mini - both running ios 7.1.2.  I'm
>> suspicious of ipv6 routing related to this issue.
>>
>> In any event, I'll know to report these at the next IETF.
>>
>> Thanks for the good work you and the NOC did during this last IETF.
>>
>> Mike
>>
>>
>>
>>>
>>> My iPhone5 worked reliably across all networks, except for ietf-hotel
>>> in my room, but I was in a corner room at the very end of the hall. My
>>> laptop even had issues there, despite the much better antenna. My
>>> Airport Express solved that problem and gave me much better wifi
>>> performance in my room using the room wired connection. Other folks I
>>> know had Androids of various types and they also worked well on our
>>> networks.
>>>
>>> Please report such issues when it happens--this meeting (and many
>>> others) Verilan is contracted to support the network and staff the
>>> help desk. Please make use of them, either in person or by submitting
>>> a report to [e-mail]
>>> <mailto:[e-mail]>, as noted in the Network Information
>>> page. It is obviously too late now, unfortunately.
>>>
>>> The information that would help us debug these issues include:
>>>
>>>  - The model of device, the version of OS it is running, and the MAC
>>> addresses you used on it's wifi interfaces
>>>  - The SSID you are connecting to
>>>  - The BSSID of the AP you attach to (MAC address of the AP)
>>>  - Where this happened
>>>  - Description of what didn't work, and, if other networks work, what
>>> did. Include the v4 or v6 addresses and router and/or DNS addresses
>>> you got, or which you didn't get.
>>>  - If you are using the 802.1X encrypted networks (ietf.1x, ietf-a.1x,
>>> and eduroam), exactly where it failed. Did you get authenticated? How
>>> do you have your 802.1X supplicant (client) configured? Do you have
>>> our certificate in your certificate store or are you asked to accept
>>> it? Are you using ietf/ietf as username and password for the ietf*.1x
>>> nets? Are you using TTLS or PEAP with MS-CHAPv2 or GTC inner EAP methods?
>>>  - If you did get addresses, could you ping the router, DNS server? If
>>> so, where couldn't you reach, and what does a traceroute show?
>>>
>>> Don't worry if you can't supply all of the above. It's great if you
>>> can, and we can help you find what we need if you can't. If you can
>>> only supply some information, the MAC addresses you used on device's
>>> wifi interfaces is the most important for us to start tracking down
>>> where things didn't work. Often we can determine the issue and help
>>> you re-configure your devices in minutes. It might take longer if it
>>> is a network issue, but we were only affected by a single bug, and it
>>> did not affect any attendees, that we configured a workaround for this
>>> time. We had no other problems that we knew about.
>>>
>>> Safe travels, and hope to see you in Hawaii!
>>> Chris.
>>>
>>>
>>>
>>> On Sat, Jul 26, 2014 at 3:00 PM, Andrew G. Malis <[e-mail]
>>> <mailto:[e-mail]>> wrote:
>>>
>>>     On my iPhone5s, "ietf" worked very well in the meeting floors. In
>>>     my room, "ietf-hotel" was useless, and I used Rogers for the
>>>     iPhone; I used the wired connection for my Mac, and I would have
>>>     used Internet sharing on the laptop if I had needed it, but Rogers
>>>     worked fine.
>>>
>>>     Cheers,
>>>     Andy
>>>
>>>
>>>
>>>     On Sat, Jul 26, 2014 at 12:18 PM, Reinaldo Penno
>>>     <[e-mail] <mailto:[e-mail]>> wrote:
>>>
>>>         Jeff,
>>>
>>>         same here. I noticed not only on iPhone but my Android phone
>>>         was well.
>>>
>>>         And in general "ietf-hotel" was very flaky across all devices
>>>         I tried, including a Mac and a Lenovo Windows laptop.
>>>
>>>         thanks,
>>>
>>>
>>>
>>>         On 7/26/14, 9:05 AM, Jeff Haas wrote:
>>>
>>>             This is mostly a post-IETF poll to see if others saw
>>>             similar issues.  Wifi on my laptop (Mac) worked fine
>>>             throughout the conference.  My iphone on the other hand,
>>>             seemed to have all sorts of issues with the wifi:
>>>             - "ietf" would connect most of the time, but not always
>>>             give me an address.  Occasionally I'd get ipv6 dns address.
>>>             - "ietf-hotel" would connect most regularly, especially in
>>>             my room but connectivity to the outside world was flakey
>>>             at best.
>>>             - The ietf-a, and all .1x networks simply gave up
>>>             immediately and fell back to the other config.
>>>
>>>             Mostly I solved my issues by disabling the wifi and
>>>             falling back to Rogers.
>>>
>>>             Did anyone else see similar issues?
>>>
>>>             In the future, what sort of troubleshooting is good for
>>>             diagnosing the root cause of such problems?
>>>
>>>             -- Jeff
>>>
>>>
>>>             _______________________________________________
>>>             90attendees mailing list
>>>             [e-mail] <mailto:[e-mail]>
>>>             https://www.ietf.org/mailman/listinfo/90attendees
>>>
>>>
>>>         _______________________________________________
>>>         90attendees mailing list
>>>         [e-mail] <mailto:[e-mail]>
>>>         https://www.ietf.org/mailman/listinfo/90attendees
>>>
>>>
>>>
>>>     _______________________________________________
>>>     90attendees mailing list
>>>     [e-mail] <mailto:[e-mail]>
>>>     https://www.ietf.org/mailman/listinfo/90attendees
>>>
>>>
>>>
>>>
>>> --
>>> Chris Elliott
>>> [e-mail] <mailto:[e-mail]>
>>>
>>>
>>> _______________________________________________
>>> 90attendees mailing list
>>> [e-mail]
>>> https://www.ietf.org/mailman/listinfo/90attendees
>>
>>
>>
>> _______________________________________________
>> 90attendees mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/90attendees
>>
>
> --
> Dr. J.W. Atwood, Eng.             tel:   [phone] x3046
> Distinguished Professor Emeritus  fax:   [phone]
> Department of Computer Science
>    and Software Engineering
> Concordia University EV 3.185     email:[e-mail]
> 1455 de Maisonneuve Blvd. West    http://users.encs.concordia.ca/~bill
> Montreal, Quebec Canada H3G 1M8
>
> _______________________________________________
> 90attendees mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/90attendees