Differences

This shows you the differences between two versions of the page.

Link to this comparison view

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:50]
mcb30
Line 53: Line 53:
 ''​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
Line 62: Line 62:
     :retry     :retry
     ifconf -c dhcp && isset ${filename} || goto retry     ifconf -c dhcp && isset ${filename} || goto retry
 +
 +===== Build options =====
 +
 +The IPv6 protocol is available only when the build option ''​[[:​buildcfg:​NET_PROTO_IPV6]]''​ is enabled.
  
cmd/ifconf.txt ยท Last modified: 2021/01/26 17:34 by mcb30
Recent changes RSS feed CC Attribution-Share Alike 4.0 International Driven by DokuWiki
All uses of this content must include an attribution to the iPXE project and the URL https://ipxe.org
References to "iPXE" may not be altered or removed.