Raf Czlonka <[email protected]> wrote:

> >     ifconfig trunk0 up
> > 
> > should make it go. There is currently a discussion going on if
> > ifconfig(8) should implicitly bring interfaces up, until that is
> > settled you either need ifconfig $IF up or add "up" to your
> > hostname.if(5) file.
> 
> FWIW, I've made the same mistake thinking that "inet autoconf" and
> "dhcp" are functionally equivalent.
> 
> I based the assumption both on the commit message[0]:
> 
>       The flag can be set by "ifconfig $if inet autoconf" or by
>       adding "inet autoconf" to /etc/hostname.if. An existing
>       "dhcp" line should be removed.
> 
> i.e. no mention of additional "up"; and the fact that "up" is already
> implied when "dhcp" is being used.

Also, no mention that the sun makes the day brighter.

> I can understand both sides to the argument, i.e. on the one hand
> you can configure several interfaces without bringing any of them
> up; or why would you configure an interface if you don't want to
> use it, not to mention one command less to run or one less option
> to use in hostname.if(5), on the other.
> 
> [0] https://marc.info/?l=openbsd-cvs&m=161435621007396&w=2

I had a hostname.if file with "description something", and it didn't
bring the interface up.

You going to explain to me why "description something" shouldn't bring
the interface up, but "inet autoconf" should?

     autoconf        Set the AUTOCONF4 or AUTOCONF6 flag on the interface,
                     depending on address_family.  slaacd(8) automatically
                     configures IPv6 addresses for interfaces with AUTOCONF6
                     set.

                     dhclient(8) only configures interfaces with AUTOCONF4
                     set.

The ifconfig man page says "inet autoconf" sets a flag.   It does not say
"sets the flag and brings the interface up".  You want to argue against
the documented behaviour?

It is the dhclient *program*, activated by the "dhcp" word parsed by netstart,
which brings the interface up, and operates unlike anything else in the system.
What we want in the future when "autoconf" becomes the norm is hard to tell,
but "inet6 autoconf" does not bring the interface up either.

Reply via email to