Bug 444343 - have to dhclient wlan0 to connect at hotspots
Summary: have to dhclient wlan0 to connect at hotspots
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager   
(Show other bugs)
Version: 9
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2008-04-27 14:34 UTC by John Cox
Modified: 2014-12-22 15:57 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-07-14 17:52:22 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
log text (4.60 KB, text/plain)
2008-04-28 14:16 UTC, John Cox
no flags Details

Description John Cox 2008-04-27 14:34:45 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b5) Gecko/2008042509 Fedora/3.0-0.55.beta5.fc9 Firefox/3.0b5

Description of problem:
I have to dhclient wlan0 everytime I connect to a hotspot.
At home using WPA it works without this problem.
Is network manager not using dhclient corrrectly?

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

How reproducible:

Steps to Reproduce:
1.connect to a hotspot
2.no browser connection
3.enter dhclient wlan0 and connection works

Actual Results:
have to use dhclient to connect

Expected Results:
should connect without having to use dhclient wlan0

Additional info:
I see possible related bugs entered but I don't know which or if one of them is the same bug.

Comment 1 Dan Williams 2008-04-28 04:00:43 UTC
Can you attach your /var/log/messages from the time this happens so I can try to
figure out what's going on? Thanks!

Comment 2 John Cox 2008-04-28 14:16:50 UTC
Created attachment 303978 [details]
log text

This is my log.
I started up. wlan0 connected to hotspot but no internet. Ran dhclient wlan0
and then had internet access.

Comment 3 Bug Zapper 2008-05-14 10:15:34 UTC
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:

Comment 4 Jessica Sterling 2009-03-05 15:36:32 UTC
This bug has been triaged

Fedora Bugzappers volunteer triage team

Comment 5 Bug Zapper 2009-06-10 00:28:23 UTC
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  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 '9'.

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 9'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 9 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 6 Bug Zapper 2009-07-14 17:52:22 UTC
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 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.