Bug 624187 - unable to connect at Starbucks
Summary: unable to connect at Starbucks
Alias: None
Product: Fedora
Classification: Fedora
Component: wireless-tools
Version: 13
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-08-14 04:09 UTC by Attila Mate
Modified: 2011-06-28 14:35 UTC (History)
2 users (show)

Clone Of:
Last Closed: 2011-06-28 14:35:33 UTC

Attachments (Terms of Use)

Description Attila Mate 2010-08-14 04:09:25 UTC
Description of problem: Unable to authenticate as client of captive portal wifi; e.g. unable to connect at Starbucks or at the New York Public Library. Wifi connection is clearly made (for example, DHCP installs /etc/resolv.conf; at Starbucks nslookup requests for domain name resolution are answered), but the login portal is never received (i.e., I never receive a Web page inviting "Starbucks login"). Login to unsecured wifi succeeds consistently. Problem is present both with Firefox and Seamonkey browsers.

Version-Release number of selected component (if applicable): Fedora 13, was upgraded as of August 7, 2010 (with "yum upgrade"). Kernel version

How reproducible: It happens all the time, that is, I am never receive the login portal Web page, even though wifi connection is always made.

Steps to Reproduce:
Actual results:

Expected results:

Additional info: My laptop is a Toshiba Satellite, A205-S50. Wireless Network Adapter is Atheros AR5001, though I fail to see how this would be related to the problem. I also did a Ubuntu Lucid Netbook Edition installation on an EeePC 1011HAB, where I did not have problems with captive portal authentication (both Firefox and Seamonkey is able to establish authentication).

   Actually, both Fedora 13 and Ubuntu Lucid (Ubuntu 10.4) seems to have a DHCP problem that I have a workaround for. For example, in Fedora 13, before a DHCP wifi connection is made, I replace the file /var/lib/dhclient/dhclient-wlan0.leases with a file that has as its only content

   interface "wlan0";

Before I started doing this, after a number of DHCP wifi connections to various
servers, no more DHCP leases could be obtained. I needed to add a similar fix in Ubuntu Lucid.

Comment 1 Bug Zapper 2011-06-01 11:27:36 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 2 Bug Zapper 2011-06-28 14:35:33 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.