On Sat, 31 Dec 2016, atomicules wrote:
I use NetBSD on Linode, but still a XEN install (if it ain't broke,
don't fix it). All I do for ipv6 is:
I converted from Xen to KVM to get one of the free upgrades they
offered, I think it was for more RAM or something, but they required
changing the unde
I use NetBSD on Linode, but still a XEN install (if it ain't broke,
don't fix it). All I do for ipv6 is:
dhcpcd="YES"
ip6mode="autohost"
in rc.conf and this works automagically for me.
The only issue I have is dmesg gets spammed with:
"in6_ifadd: 2a01:7e00::f03c:91ff:fe70:e653 is already conf
Finally, I have used a new kernel and it works a little bit faster (90Mbits/sec
instead of 70Mbits/sec).
But after being able to play with the new kernel, I get a lot of trouble
with Windows 10 by transfering data (either by CIFS or FTP) and with all
OS (Linux, OpenBSD, NetBSD) on the router.
A
mpar...@bl.org (Michael Parson) writes:
>While I've got some free time over the holidays, I thought I'd go ahead
>and finally try to get my NetBSD/Linode going with its assigned IPv6.
>Linode tells me that my IPv6 IP is 2600:3c00::f03c:91ff:feae:c95d/64 and
>my default gateway should be fe80::1.
