Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
cmd:ifconf [2014/01/29 14:17] mcb30 |
cmd:ifconf [2014/01/29 14:22] mcb30 |
||
|---|---|---|---|
| Line 52: | Line 52: | ||
| ''ifconf'' will not automatically close all other network interfaces before starting to attempt automatic configuration. If you have already opened other network interfaces, then you may wish to execute ''[[:cmd:ifclose]]'' before executing ''ifconf''. | ''ifconf'' will not automatically close all other network interfaces before starting to attempt automatic configuration. If you have already opened other network interfaces, then you may wish to execute ''[[:cmd:ifclose]]'' before executing ''ifconf''. | ||
| + | |||
| + | ''ifconf'' will succeed if **any** configurator manages to successfully obtain a configuration. If you want to ensure that both DHCP and IPv6 have succeeded, then you must use each configurator explicitly: | ||
| + | |||
| + | ifconf -c dhcp | ||
| + | ifconf -c ipv6 | ||
| Automatic configuration via DHCP will succeed if it manages to obtain an IP address. If you are using a ProxyDHCP server to provide a boot filename, then you may wish to keep retrying DHCP until it obtains a response from the ProxyDHCP server as well as obtaining the IP address from the DHCP server. You can do this using a script fragment such as: | Automatic configuration via DHCP will succeed if it manages to obtain an IP address. If you are using a ProxyDHCP server to provide a boot filename, then you may wish to keep retrying DHCP until it obtains a response from the ProxyDHCP server as well as obtaining the IP address from the DHCP server. You can do this using a script fragment such as: | ||
| :retry | :retry | ||
| - | ifconf && isset ${filename} || goto retry | + | ifconf -c dhcp && isset ${filename} || goto retry |
