On Sat, Mar 06, 2021 at 04:09:50PM +0000, Raf Czlonka wrote: > On Sat, Mar 06, 2021 at 08:59:16AM GMT, Florian Obser wrote: > > your interface is not "UP" > > > > > lladdr f0:de:f1:77:c2:c8 > > > index 6 priority 0 llprio 3 > > > trunk: trunkproto failover > > > iwn0 port active > > > em0 port master > > > groups: trunk egress > > > media: Ethernet autoselect > > > status: active > > > > > > ifconfig trunk0 inet autoconf > > > > 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.
I had actually forgotten about dhclient's behaviour when I commited dhcpleased. All my hostname.if(5) files have "up" or "down" as the last line. Years ago I was bitten by the parent interface of a vlan interface not being up and spending half a day debugging it... I learned my lesson and try to be explicit. -- I'm not entirely sure you are real.
