Bug 114173 - dhclient couldn't get online with t-mobile hotspot at SFO
dhclient couldn't get online with t-mobile hotspot at SFO
Product: Red Hat Linux
Classification: Retired
Component: dhcp (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Walsh
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2004-01-23 11:39 EST by Need Real Name
Modified: 2007-04-18 13:02 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-04-06 19:32:21 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
stuff from /var/log/messages (34.12 KB, text/plain)
2004-01-23 11:42 EST, Need Real Name
no flags Details

  None (edit)
Description Need Real Name 2004-01-23 11:39:30 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031007

Description of problem:
I tried to use my buffalo-tech wifi card (which works fine in other
places) at a t-mobile hotspot in SFO airport.  It seemed to be talking
to the server but didn't accept any of the leases offered.

I will attach stuff from the messages file.

After the first failed attampt, the server wouldn't talk to me at all.
 Perhaps it thought I was just too stupid.

Version-Release number of selected component (if applicable):

How reproducible:
Didn't try

Steps to Reproduce:
1.Go to SFO airport
2.Set up wireless card to use DHCP
3.Insert it

Actual Results:  Didn't get a lease, couldn't get online

Expected Results:  Should have gotten online

Additional info:
Comment 1 Need Real Name 2004-01-23 11:42:58 EST
Created attachment 97213 [details]
stuff from /var/log/messages
Comment 2 Daniel Walsh 2004-04-06 19:32:21 EDT
No real way of figuring this out. 

Comment 3 John Flanagan 2004-12-21 14:42:06 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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