On Wed, 2011-08-03 at 00:09 -0700, Adam Williamson wrote: > On Tue, 2011-08-02 at 17:12 -0400, Bill McGonigle wrote: > > On 08/01/2011 07:25 PM, Adam Williamson wrote: > > > It seems like there's <SOMETHING> which has to happen after > > > wake before NM even attempts to re-establish a connection, and that's > > > the longest delay, at least for me. Anyone know what that something is, > > > and whether it can be optimized? > > > > I don't know what your networks look like, but are you perhaps seeing > > the delay in (not)discovering IPv6 on an IPv4-only network? My wife's > > f15 machine was doing this on our home network and I just disabled IPv6 > > in the connection definition and it got much faster. Not sure if that's > > a good default behavior given typical use cases. > > I doubt it. I don't think the <SOMETHING> is inherently networking. I > think it's something that has to clear before NM even kicks in. I should > check the log timestamps to make sure, though. The Ubuntu NM maintainer has posted a WIP patch that makes NM say it's connected immediately if at least one of IPv4 or IPv6 completes. Currently if both are enabled, NM won't say it's connected until both are done (and result in either success or failure). That at least speeds up the perceived connection speed, which isn't a bad thing. Dan > -- > Adam Williamson > Fedora QA Community Monkey > IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora > http://www.happyassassin.net > -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
