John Andersen wrote:
On 04/01/2016 10:55 AM, Anton Aylward wrote:
On 04/01/2016 01:35 PM, Dave Howorth wrote:
Anyway, it looks like wicked.service, SuSEfirewall2_init.service, and dev-disk-by\x2duuid* are the culprits in some way. wicked.service is perhaps only guilty by association?
Forget the disk startup; that's a given, there may be a unit that takes care of disk startup delays that is responsible; or perhaps disk startup is responsible. My machine takes longer to do the fsck'ing and the tmp file cleaning.
Do you need the firewall on the PC?
I have a firewall in my router/switch (which also has a VPN gateway, but that's beside the point).
Please do try without the firewall and without wiked and using static addresses and see if its any different.
I got to my setup having experimented with a lot of other ways of doing things.
Actually, I suspect that wicked is trying to bring up both interfaces as that time. A typical DHCP request takes something like +275ms, but if it is setting up a wifi, for which there is no reachable accesspoint, that process can take a lot longer.
There is just about no way you could extend a dhcp request to chew up 18 seconds and still SUCCEED!
I agree. Here's the log from the dhcp exchange when my wife (her iphone) came home today: Apr 1 19:29:08 dresden dhcpd: DHCPDISCOVER from 84:b1:53:e5:b0:8c (Nadine) via eth0 Apr 1 19:29:09 dresden dhcpd: DHCPOFFER on 192.168.7.69 to 84:b1:53:e5:b0:8c (Nadine) via eth0 Apr 1 19:29:10 dresden dhcpd: DHCPREQUEST for 192.168.7.69 (192.168.2.137) from 84:b1:53:e5:b0:8c (Nadine) via eth0 Apr 1 19:29:10 dresden dhcpd: DHCPACK on 192.168.7.69 to 84:b1:53:e5:b0:8c (Nadine) via eth0 Less than 2 seconds. The 192.168.7.x range is reserved for all unknown devices, including our own mobiles and such. -- Per Jessen, Zürich (11.6°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org