Greg Troxel writes:
> * drop ip6mode=autohost from rc.conf, so that the default of host
> applies. On any interface you want a v6 automatic address, run
> dhcpcd. This should just work and you should have useful logs in
> /var/log/messages if not.
>
> So basically those last 4 lines
On Mon, Jan 28, 2019 at 5:23 PM Jan Danielsson
wrote:
>
> Hello,
>
>I have a vague memory of having read that IPv6 autoconfiguration has
> changed in NetBSD 8. Something along the line of "rtadvd is dead, now
> dhcpcd is the way to go". Am I remembering correctly? If so; has
> anyone
Jan Danielsson writes:
>I have a vague memory of having read that IPv6 autoconfiguration has
> changed in NetBSD 8. Something along the line of "rtadvd is dead, now
> dhcpcd is the way to go". Am I remembering correctly? If so; has
> anyone written a migration guide?
What you said isn't
Hello,
I have a vague memory of having read that IPv6 autoconfiguration has
changed in NetBSD 8. Something along the line of "rtadvd is dead, now
dhcpcd is the way to go". Am I remembering correctly? If so; has
anyone written a migration guide?
--
Kind Regards,
Jan
I remember having problems sometimes ago when my NetBSD machines were
around 8.99.25 or so (my timeserver is an RPI Model B still on
8.99.2). I haven't had these problems for a while, but all my -current
machines are on 8.99.32.
Chavdar
On Mon, 28 Jan 2019 at 15:51, Patrick Welche wrote:
>
>
Hello,
https://wiki.netbsd.org/amazon_ec2/amis/ currently lists NetBSD 7.0 as
the latest version for which there are AWS EC2 AMIs available. Is that
correct, or are there any official NetBSD 8.0 images available?
-Jan
Just noticed (NetBSD-8.99.26/amd64):
ntpd[1575]: kernel reports TIME_ERROR: 0x4041: Clock Unsynchronized
This is after a ntpdate which succeeded in catching up the 3/4 hour
that clock was behind by. I haven't seen this error before...
Is ACPI-Fast a good choice? (I didn't choose...)
# sysctl
