Opened 4 years ago

Closed 4 years ago

Last modified 5 weeks ago

#623 closed request (wontfix)

Issue about "intercontinental" SSID and Samsung Android phone

Reported by: evyncke@… Owned by: cdoyle@…
Priority: minor Milestone: ietf-087
Component: other Keywords: Hotel WAP
Cc: ietf@… My Current Location:
My MAC Address: My OS:

Description

Hello,

In our room (AP A4 :56 :30 :CD :A8 :A0) on the 4th floor of Intercontinental (but also in other locations), all my devices (MacBook, iPad, BlackBerry) work fine except for my old Samsung android phone...

The Samsung phone gets an IPv4 address:  130.129.66.37 that is pingable from outside of the IETF network but the Samsung cannot reach anything... some applications (Foursquare) even display a message about 'cannot resolve host' which leads to suspect a DNS problem...

Any clue how to solve the issue?

We went to another place with WiFi and the Samsung works fine, at home we are also dual-stack (but with no local IPv6 DNS server)

Thanks in advance for your help

-éric

Change history (11)

comment:1 Changed 4 years ago by llynch@…

Cc: ietf@… added
Component: incomingwireless
Owner: changed from llynch@… to cdoyle@…
Status: newassigned

comment:2 in reply to:  description Changed 4 years ago by cdoyle@…

Well you are most certainly connecting to a hotel AP, so that's not going to work in our favor. They have a mixed deployment, so it stands to reason the AP's in the guest areas could be different than the AP's in the other common areas. This could explain why your phone connects in the common areas, but not in your room. I also know (as I'm sure you do as well) that Samsung Android devices have well documented issues with various vendor WAP's. If this is the issue, then I'm sad to say that we probably won't be able to determine a resolution.

The hotel is your best resource right now as they are still responsible for the network hardware that supports the guest rooms. I would suggest you call them and report your issue. If you can determine the type of Cisco WAP, we can check to see if there are any specific issues (like, for example, if they are using old 1040's - https://supportforums.cisco.com/thread/2189958).

What is your room number? I can also go run up to that floor and see if I can locate a WAP on the ceiling to check.

Colin

Replying to evyncke@…:

Hello,

In our room (AP A4 :56 :30 :CD :A8 :A0) on the 4th floor of Intercontinental (but also in other locations), all my devices (MacBook, iPad, BlackBerry) work fine except for my old Samsung android phone...

The Samsung phone gets an IPv4 address:  130.129.66.37 that is pingable from outside of the IETF network but the Samsung cannot reach anything... some applications (Foursquare) even display a message about 'cannot resolve host' which leads to suspect a DNS problem...

Any clue how to solve the issue?

We went to another place with WiFi and the Samsung works fine, at home we are also dual-stack (but with no local IPv6 DNS server)

Thanks in advance for your help

-éric

comment:3 Changed 4 years ago by cdoyle@…

Component: wirelessother
Keywords: Hotel WAP added
Priority: tbdminor

comment:4 Changed 4 years ago by evyncke@…

Colin

Thanks for your reply. My room is on the 4th floor: 428

And, I was unaware of this issue with Cisco WAP & Samsung phones. Obviously based on the OUI  A4:56:30:CD:A8:A0, it is indeed a Cisco WAP.

What is really puzzling is that the phone has associated with the SSID, DHCPv4 went OK (at least I have an IPv4 address 130.129.66.37), can even browse using a IPv4 litteral as URL but not a FQDN. It seems an issue with DNS & this SSID :-(

Best regards and thanks for your help

-éric

> -----Original Message-----
> From: IETF Meeting/NOC [mailto:tickets@meeting.ietf.org]
> Sent: dimanche 28 juillet 2013 09:18
> To: Eric Vyncke (evyncke); cdoyle@verilan.com; llynch@civil-tongue.net
> Cc: ietf@verilan.com
> Subject: Re: [IETF Meeting/NOC] #623: Issue about "intercontinental" SSID
> and Samsung Android phone
> 
> #623: Issue about "intercontinental" SSID and Samsung Android phone
> ----------------------------+--------------------------------
>       Reporter:  evyncke@…  |                Owner:  cdoyle@…
>           Type:  request    |               Status:  assigned
>       Priority:  tbd        |            Milestone:  ietf-87
>      Component:  wireless   |           Resolution:
>       Keywords:             |  My Current Location:
> My MAC  Address:            |                My OS:
> ----------------------------+--------------------------------
> 
> Comment (by cdoyle@…):
> 
>  Well you are most certainly connecting to a hotel AP, so that's not going
> to work in our favor. They have a mixed deployment, so it stands to reason
> the AP's in the guest areas could be different than the AP's in the other
> common areas. This could explain why your phone connects in the common
> areas, but not in your room. I also know (as I'm sure you do as well) that
> Samsung Android devices have well documented issues with various vendor
> WAP's. If this is the issue, then I'm sad to say that we probably won't be
> able to determine a resolution.
> 
>  The hotel is your best resource right now as they are still responsible
> for the network hardware that supports the guest rooms. I would suggest  you
> call them and report your issue. If you can determine the type of  Cisco
> WAP, we can check to see if there are any specific issues (like, for
> example, if they are using old 1040's -
> https://supportforums.cisco.com/thread/2189958).
> 
>  What is your room number? I can also go run up to that floor and see if I
> can locate a WAP on the ceiling to check.
> 
>  Colin
> 
>  Replying to [ticket:623 evyncke@…]:
>  > {{{
>  > Hello,
>  >
>  > In our room (AP A4 :56 :30 :CD :A8 :A0) on the 4th floor of
> Intercontinental (but also in other locations), all my devices (MacBook,
> iPad, BlackBerry) work fine except for my old Samsung android phone...
>  >
>  > The Samsung phone gets an IPv4 address:  130.129.66.37 that is pingable
> from outside of the IETF network but the Samsung cannot reach anything...
>  some applications (Foursquare) even display a message about 'cannot
> resolve host' which leads to suspect a DNS problem...
>  >
>  > Any clue how to solve the issue?
>  >
>  > We went to another place with WiFi and the Samsung works fine, at home
> we are also dual-stack (but with no local IPv6 DNS server)  >  > Thanks in
> advance for your help  >  > -éric  > }}}
> 
> --
> Ticket URL: <https://tickets.meeting.ietf.org/ticket/623#comment:2>
> IETF Meeting/NOC <https://tickets.meeting.ietf.org>
> IETF Meeting - NOC pages

comment:5 Changed 4 years ago by evyncke@…

And for what it is worth, this morning during the breakfast, the Samsung worked perfectly fine (and as expected had believed that it is located in Orlando ;-))

-éric

> -----Original Message-----
> From: IETF Meeting/NOC [mailto:tickets@meeting.ietf.org]
> Sent: dimanche 28 juillet 2013 09:18
> To: Eric Vyncke (evyncke); cdoyle@verilan.com; llynch@civil-tongue.net
> Cc: ietf@verilan.com
> Subject: Re: [IETF Meeting/NOC] #623: Issue about "intercontinental" SSID
> and Samsung Android phone
> 
> #623: Issue about "intercontinental" SSID and Samsung Android phone
> ----------------------------+--------------------------------
>       Reporter:  evyncke@…  |                Owner:  cdoyle@…
>           Type:  request    |               Status:  assigned
>       Priority:  tbd        |            Milestone:  ietf-87
>      Component:  wireless   |           Resolution:
>       Keywords:             |  My Current Location:
> My MAC  Address:            |                My OS:
> ----------------------------+--------------------------------
> 
> Comment (by cdoyle@…):
> 
>  Well you are most certainly connecting to a hotel AP, so that's not going
> to work in our favor. They have a mixed deployment, so it stands to reason
> the AP's in the guest areas could be different than the AP's in the other
> common areas. This could explain why your phone connects in the common
> areas, but not in your room. I also know (as I'm sure you do as well) that
> Samsung Android devices have well documented issues with various vendor
> WAP's. If this is the issue, then I'm sad to say that we probably won't be
> able to determine a resolution.
> 
>  The hotel is your best resource right now as they are still responsible
> for the network hardware that supports the guest rooms. I would suggest  you
> call them and report your issue. If you can determine the type of  Cisco
> WAP, we can check to see if there are any specific issues (like, for
> example, if they are using old 1040's -
> https://supportforums.cisco.com/thread/2189958).
> 
>  What is your room number? I can also go run up to that floor and see if I
> can locate a WAP on the ceiling to check.
> 
>  Colin
> 
>  Replying to [ticket:623 evyncke@…]:
>  > {{{
>  > Hello,
>  >
>  > In our room (AP A4 :56 :30 :CD :A8 :A0) on the 4th floor of
> Intercontinental (but also in other locations), all my devices (MacBook,
> iPad, BlackBerry) work fine except for my old Samsung android phone...
>  >
>  > The Samsung phone gets an IPv4 address:  130.129.66.37 that is pingable
> from outside of the IETF network but the Samsung cannot reach anything...
>  some applications (Foursquare) even display a message about 'cannot
> resolve host' which leads to suspect a DNS problem...
>  >
>  > Any clue how to solve the issue?
>  >
>  > We went to another place with WiFi and the Samsung works fine, at home
> we are also dual-stack (but with no local IPv6 DNS server)  >  > Thanks in
> advance for your help  >  > -éric  > }}}
> 
> --
> Ticket URL: <https://tickets.meeting.ietf.org/ticket/623#comment:2>
> IETF Meeting/NOC <https://tickets.meeting.ietf.org>
> IETF Meeting - NOC pages

comment:6 in reply to:  description Changed 4 years ago by cdoyle@…

I went and looked around, but the AP's must be in the ceiling so no dice.

Would you like me to follow-up with the hotel?

C

Replying to evyncke@…:

Hello,

In our room (AP A4 :56 :30 :CD :A8 :A0) on the 4th floor of Intercontinental (but also in other locations), all my devices (MacBook, iPad, BlackBerry) work fine except for my old Samsung android phone...

The Samsung phone gets an IPv4 address:  130.129.66.37 that is pingable from outside of the IETF network but the Samsung cannot reach anything... some applications (Foursquare) even display a message about 'cannot resolve host' which leads to suspect a DNS problem...

Any clue how to solve the issue?

We went to another place with WiFi and the Samsung works fine, at home we are also dual-stack (but with no local IPv6 DNS server)

Thanks in advance for your help

-éric

comment:7 Changed 4 years ago by evyncke@…

Yes, please but low priority as I am not in meeting floor with IETF & eduroam working ;-)

> -----Original Message-----
> From: IETF Meeting/NOC [mailto:tickets@meeting.ietf.org]
> Sent: dimanche 28 juillet 2013 14:29
> To: Eric Vyncke (evyncke); cdoyle@verilan.com; llynch@civil-tongue.net
> Cc: ietf@verilan.com
> Subject: Re: [IETF Meeting/NOC] #623: Issue about "intercontinental" SSID
> and Samsung Android phone
> 
> #623: Issue about "intercontinental" SSID and Samsung Android phone
> ----------------------------+--------------------------------
>       Reporter:  evyncke@…  |                Owner:  cdoyle@…
>           Type:  request    |               Status:  assigned
>       Priority:  minor      |            Milestone:  ietf-87
>      Component:  other      |           Resolution:
>       Keywords:  Hotel WAP  |  My Current Location:
> My MAC  Address:            |                My OS:
> ----------------------------+--------------------------------
> 
> Comment (by cdoyle@…):
> 
>  I went and looked around, but the AP's must be in the ceiling so no dice.
> 
>  Would you like me to follow-up with the hotel?
> 
>  C
> 
>  Replying to [ticket:623 evyncke@…]:
>  > {{{
>  > Hello,
>  >
>  > In our room (AP A4 :56 :30 :CD :A8 :A0) on the 4th floor of
> Intercontinental (but also in other locations), all my devices (MacBook,
> iPad, BlackBerry) work fine except for my old Samsung android phone...
>  >
>  > The Samsung phone gets an IPv4 address:  130.129.66.37 that is pingable
> from outside of the IETF network but the Samsung cannot reach anything...
>  some applications (Foursquare) even display a message about 'cannot
> resolve host' which leads to suspect a DNS problem...
>  >
>  > Any clue how to solve the issue?
>  >
>  > We went to another place with WiFi and the Samsung works fine, at home
> we are also dual-stack (but with no local IPv6 DNS server)  >  > Thanks in
> advance for your help  >  > -éric  > }}}
> 
> --
> Ticket URL: <https://tickets.meeting.ietf.org/ticket/623#comment:6>
> IETF Meeting/NOC <https://tickets.meeting.ietf.org>
> IETF Meeting - NOC pages

comment:8 in reply to:  description Changed 4 years ago by anonymous

I'm going to close this ticket as a matter of course as this is a hardware-specific compatibility issue between your device and the hotel infrastructure. Please let us know if your discussions with the hotel yield any answers, specifically what type of hardware they have deployed for the guest rooms. Ultimately, I'm pretty sure there is no resolution to your issue, so I do apologize for whatever magic combination of chipsets are causing this.

Replying to evyncke@…:

Hello,

In our room (AP A4 :56 :30 :CD :A8 :A0) on the 4th floor of Intercontinental (but also in other locations), all my devices (MacBook, iPad, BlackBerry) work fine except for my old Samsung android phone...

The Samsung phone gets an IPv4 address:  130.129.66.37 that is pingable from outside of the IETF network but the Samsung cannot reach anything... some applications (Foursquare) even display a message about 'cannot resolve host' which leads to suspect a DNS problem...

Any clue how to solve the issue?

We went to another place with WiFi and the Samsung works fine, at home we are also dual-stack (but with no local IPv6 DNS server)

Thanks in advance for your help

-éric

comment:9 Changed 4 years ago by anonymous

Issue exists between Samsung wi-fi and hotel WAP's. Some Samsung phones have known issues with Cisco (and other vendor) WAP's.

comment:10 Changed 4 years ago by cdoyle@…

Resolution: wontfix
Status: assignedclosed

comment:11 Changed 5 weeks ago by Rick Alfvin

Milestone: ietf-87ietf-087

Milestone renamed

Note: See TracTickets for help on using tickets.