Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
cmd:ifconf [2014/08/15 14:51] mcb30 |
cmd:ifconf [2021/01/26 17:34] mcb30 |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| ===== Synopsis ===== | ===== Synopsis ===== | ||
| - | ifconf [--configurator <configurator>] [<interface>] [<interface>...] | + | ifconf [--configurator <configurator>] [--timeout <timeout>] [<interface>...] |
| ===== Examples ===== | ===== Examples ===== | ||
| Line 35: | Line 35: | ||
| If no configurators are explicitly specified, iPXE will try all available configurators. | If no configurators are explicitly specified, iPXE will try all available configurators. | ||
| + | |||
| + | A configuration timeout can be specified (in milliseconds) using the ''%%--timeout%%'' option. | ||
| ===== Command status ===== | ===== Command status ===== | ||
| Line 66: | Line 68: | ||
| :retry | :retry | ||
| ifconf -c dhcp && isset ${filename} || goto retry | ifconf -c dhcp && isset ${filename} || goto retry | ||
| + | |||
| + | Where possible, iPXE will automatically detect switches that are not yet forwarding packets (e.g. because the switch is configured to use spanning tree, or 802.1x port authentication, or 802.3ad link aggregation), and will extend the configuration timeout period as needed. | ||
