Bug 614860 - nmcli con up id "wireless" --timeout 10 continue connecting after timeout expiration
Summary: nmcli con up id "wireless" --timeout 10 continue connecting after timeout exp...
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: NetworkManager
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Dan Williams
QA Contact: desktop-bugs@redhat.com
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-15 12:21 UTC by Vladimir Benes
Modified: 2010-07-15 15:25 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2010-07-15 15:25:59 UTC


Attachments (Terms of Use)

Description Vladimir Benes 2010-07-15 12:21:41 UTC
Version-Release number of selected component (if applicable):
NetworkManager-0.8.1-2.el6.x86_64

How reproducible:


Steps to Reproduce:
1.execute nmcli con up id $your_network_profile --timeout 10 in console 

  
Actual results:
after timeuot expires connecting continues

Expected results:
if the timeout expires and error is shown you shouldn't have been connected to the desired network

Comment 1 Dan Williams 2010-07-15 15:25:59 UTC
Not exactly; the timeout just makes the client block until either (a) an error occurs, (b) the timeout is reached, or (c) the connection is successfully brought up.  It won't tell NM to *stop* connecting when the timeout is reached; it just makes nmcli exit instead of blocking for a long time.  --timeout allows callers of nmcli to bound their runtime in cases where NM may take a long time to acquire an IP address, like marginal wifi connections with bad DHCP servers where connections could take up to a minute or more.


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