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:22] mcb30 |
cmd:ifconf [2014/08/15 14:51] mcb30 |
||
|---|---|---|---|
| Line 46: | Line 46: | ||
| * ''[[:cmd:route]]'' | * ''[[:cmd:route]]'' | ||
| * [[:cmd|List of all iPXE commands]] | * [[:cmd|List of all iPXE commands]] | ||
| + | |||
| + | ===== Build options ===== | ||
| + | |||
| + | The IPv6 protocol is available only when the build option ''[[:buildcfg:NET_PROTO_IPV6]]'' is enabled. | ||
| ===== Notes ===== | ===== Notes ===== | ||
| Line 53: | Line 57: | ||
| ''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 by default 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'' 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 dhcp | ||
