Bug 146450 - Network install boot disk: DHCP timeout too long
Summary: Network install boot disk: DHCP timeout too long
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Installation (show other bugs)
Version: Beta 2
Hardware: i686 Other
: P5 - None : Enhancement (vote)
Target Milestone: ---
Assignee: Peter Poeml
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-28 16:11 UTC by Olav Reinert
Modified: 2006-02-01 11:10 UTC (History)
1 user (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Olav Reinert 2006-01-28 16:11:28 UTC 
The boot disk used to do a network install of SUSE Linux 10.1 correctly detects my two network interfaces, eth0 and eth1. It also tries to configure them both using DHCP, which is fine, too. But the timeout for the DHCP requests is way too long, about 1 minute I guess - 5-10 seconds would be more appropriate at this stage, I think.

Otherwise, an unnecessary delay of 1 minute is introduced for each network interface on the machine that isn't configurable by DHCP.

How about performing DHCP requests on all relevant interfaces in parallel?
Comment 1 Michael Gross 2006-01-30 15:03:50 UTC 
Could be seen else in larger/slower networks, but 1 minute seems a bit long indeed. Redirecting as enhancement to the maintainer.
Comment 2 Peter Poeml 2006-01-31 17:24:05 UTC 
Steffen? Do you think 1 minute is too long? Should we reduce the timeout
to 30 seconds maybe?
Comment 3 Steffen Winterfeldt 2006-02-01 11:10:57 UTC 
It was set to 60s on request because is was really required in large
network setups. Use dhcptimeout=foo if you want to shorten it.