Bug 790989 - FC16 - 5 seconds added to any network connection
Summary: FC16 - 5 seconds added to any network connection
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 16
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-15 21:31 UTC by eisenhowerj
Modified: 2013-02-13 13:52 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 13:52:51 UTC
Type: ---


Attachments (Terms of Use)

Description eisenhowerj 2012-02-15 21:31:33 UTC
Description of problem:
Compared to my OSX machine, any connections using tcp/network takes an extra 5 seconds to connect.  After it connects, I don't see any lagging

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


How reproducible:
Every. time.

Steps to Reproduce:
1.ssh remotehost
2.curl remotehttpd
3.
  
Actual results:
On FC16:
$ time curl google.com
...snip...

real	0m5.034s
user	0m0.002s
sys	0m0.002s
$ time ssh remote.host.com exit

real	0m5.435s
user	0m0.009s
sys	0m0.004s


On OSX:
$ time curl google.com
...snip...

real	0m0.033s
user	0m0.004s
sys	0m0.004s
$ time ssh remote.host.com exit

real	0m0.494s
user	0m0.018s
sys	0m0.016s





Expected results:
5 seconds is too long. I can understand some differences but this is unusable.

Additional info:

Both OSX ad FC16 are attached to the same switch and are running 100/Full.

Comment 1 Jirka Klimes 2012-09-06 12:52:00 UTC
I'd say that it can be caused by resolving domain names.
It could be bad DNS configuration or a bug in resolving domain names.

Do you experience the lag if you use IP instead of domain name?

To debug further, more information are needed:
* cat /etc/resolv.conf
* do you use IPv4, IPv6 or both

Also would you run the command through strace and see where it may hang?
$ strace ssh remote.host.com exit

What about 'dig google.com'?

Comment 2 Fedora End Of Life 2013-01-16 13:11:17 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 '16'.

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 16'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 16 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, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

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: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Fedora End Of Life 2013-02-13 13:52:54 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.