Re: ipv4_prefer

[mlh%goathill.org@localhost (MLH)]

MLH wrote:
> Jonathan A. Kollasch wrote:
> > On Mon, Apr 29, 2024 at 02:16:13PM -0400, MLH wrote:
> > > ifconfig :
> > > re0: flags=0x8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> > >         capabilities=0x3f80<TSO4,IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx,TCP4CSUM_Tx>
> > >         capabilities=0x3f80<UDP4CSUM_Rx,UDP4CSUM_Tx>
> > >         enabled=0
> > >         ec_capabilities=0x3<VLAN_MTU,VLAN_HWTAGGING>
> > >         ec_enabled=0
> > >         address: (xx:xx:xx:xx:xx:xx)
> > >         media: Ethernet autoselect (1000baseT full-duplex)
> > >         status: active
> > >         inet6 (fe80::xxxx:xxxx:xxxx:xx%re0/64) flags 0 scopeid 0x1
> > >         inet6 ::1000/128 flags 0
> > 
> > Has "::1000/128" been redacted?  Because it looks bogus if it isn't.
> 
> No. I didn't change that.
> 
> I am using dhcpcd and maybe that isn't getting set up correctly
> but --inform6 just returns with "sending commands to dhcpcd
> process/send OK" and nothing else.  I will try '--waitip=6' to
> dhcpcd commands and see what happens there.

Same :
inet6 fe80:: (redacted but looks good)
inet6 ::1000/128 flags 0

dhcpcd issued a bunch of ipv6 stuff on startup that indicated all
was fine but it didn't go into dmesg or a logfile that I can find
and it appeared to wait a bit until an ipv6 addr was satisfied.