Wi-fi on floor 14

[simon.perreault@…]

Looks like my AP is borked. See attached screenshot.

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

screenshot.jpg​

[simon.perreault@…]

Added by email2trac

[llynch@…]

C -

Let me know if this should go to Verilan instead this time out

[chelliot@…]

Simon,

Please give us some information. While the screenshot was interesting, it did not inform us of the SSID you were trying to associate to. It would be even more informative if you could give us a BSSID, if available, which it might not be in this situation.

Also, can you try getting to the SSID in question from your laptop or phone?

Let us know.
Chris.

[anonymous]

The process for this week is for any in-room issues to initially be handled by the standard hotel tech support (which is provided by Roomlinx). If there's an infrastructure issue or something else beyond 1st level support, they will escalate to the IETF NOC via a local phone which rotates through VeriLAN staff.

[simon.perreault@…]

Le 2013-11-03 07:56, IETF Meeting/NOC a écrit :
>   Please give us some information. While the screenshot was interesting, it
>   did not inform us of the SSID you were trying to associate to.

Hyatt_Vancouver

> It would be
>   even more informative if you could give us a BSSID, if available, which it
>   might not be in this situation.

Argh, you're so right, sorry I didn't think of this. This morning the 
problem had gone away. I thought you guys had fixed the problem, but 
maybe I was just hitting a different BSSID. I'm not in my room right now 
so I can't verify.

>   Also, can you try getting to the SSID in question from your laptop or
>   phone?

Laptop.

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

[Bill Fenner]

Both this ticket and #644 seem to be explained by a rogue DHCP server in someone's room, serving 192.168.200.1/24.

[anonymous]

Simon,

It's possible that your Asus device is misconfigured and is trying to be a dhcp server on the hotel wireless network. Can you disable it? Contact me in room 1501 ASAP.

If it's not your's it's another Asus device...

Thanks!
Chris.

[simon.perreault@…]

Le 2013-11-03 10:31, IETF Meeting/NOC a écrit :
>   Simon,
>
>   It's possible that your Asus device is misconfigured and is trying to be a
>   dhcp server on the hotel wireless network. Can you disable it? Contact me
>   in room 1501 ASAP.
>
>   If it's not your's it's another Asus device...

I don't have any Asus device, or any other AP. It must be somebody else's.

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

[chelliot@…]

Simon,

I misunderstood your ticket. I thought you sent us a screenshot of your
device. OK--We have the mac address of the device and should be able to
track it down.

Thanks!
Chris.


On Sun, Nov 3, 2013 at 10:36 AM, Simon Perreault <
simon.perreault@viagenie.ca> wrote:

> Le 2013-11-03 10:31, IETF Meeting/NOC a écrit :
>
>    Simon,
>>
>>   It's possible that your Asus device is misconfigured and is trying to
>> be a
>>   dhcp server on the hotel wireless network. Can you disable it? Contact
>> me
>>   in room 1501 ASAP.
>>
>>   If it's not your's it's another Asus device...
>>
>
> I don't have any Asus device, or any other AP. It must be somebody else's.
>
>
> Simon
> --
> DTN made easy, lean, and smart --> http://postellation.viagenie.ca
> NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
> STUN/TURN server               --> http://numb.viagenie.ca
>



-- 
Chris Elliott
chelliot@pobox.com

[anonymous]

Simon,

It appears that we have at least temporarily bumped the offending device off the network. We also have alerts set if it's rediscovered. And we have a good idea of the room(s) this is coming from.

So, I'll keep this ticket open for now. Please update if you see the same or a similar problem.

Chris.

[chelliot@…]

Simon,

As this device is no longer causing a problem, I am closing this ticket.

Please feel free to reopen it if you have the same problem again.

Chris.

[Rick Alfvin]

Milestone renamed