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
Date:Tue, 31 Jul 2018 23:49:18 +0700
From:Gua Chung Lim
Message-ID: <20180731164918.gb2...@gmail.com>
| So during office hours, I can't test NetBSD.
That's OK.
| I have to find the other ways around.
| I don't want bother you, indeed.
| My time and yours
Thank you for all your responses.
And sorry for my late reply.
At work I use FreeBSD.
I only use NetBSD at home (and at my own will).
So during office hours, I can't test NetBSD.
I can test NetBSD only at the night time (UTC+0700).
I can ssh from FreeBSD at work to NetBSD at home.
But I just can't
On 30/07/2018 15:38, Gua Chung Lim wrote:
So one of the changes in dhcpcd-7 was the default location of some
files, including the secret file which generates the SLAAC stable
private address. If you didn't change the location using postinstall(8)
before running dhcpcd it will have generated a
Date:Mon, 30 Jul 2018 21:38:01 +0700
From:Gua Chung Lim
Message-ID: <20180730143801.g...@gmail.com>
| > tcpdump -s 2000 -w DUMP-FILE -i wm0
| It gave me a binary log. But how to read it?
tdpdump -s 2000 -r DUMP-FILE (that was in the earlier message).
| >
Thanks for your kind responses.
> You'll get better information either by trawling syslog, or by adding
> `logfile /var/log/dhcpcd.log` to dhcpcd.conf.
% cat /var/log/dhcpcd.log
https://pastebin.com/VyJ5BXQc
> Is the DHCP server in the router?
Yes, it is. It's basically a home network.
(At work
On 29/07/2018 20:09, Robert Elz wrote:
Date:Sun, 29 Jul 2018 19:03:53 +0100
From:Roy Marples
Message-ID: <1718c621-40fe-cc05-5ec9-ee5f646de...@marples.name>
| > NetBSD 7 would have ignored the DHCP part, as there was no DHCPv6
| > client there
|
|
Date:Sun, 29 Jul 2018 19:03:53 +0100
From:Roy Marples
Message-ID: <1718c621-40fe-cc05-5ec9-ee5f646de...@marples.name>
| > NetBSD 7 would have ignored the DHCP part, as there was no DHCPv6
| > client there
|
| That's not true.
I phrased what I said badly.
On 29/07/2018 18:38, Robert Elz wrote:
Date:Sun, 29 Jul 2018 23:05:01 +0700
From:Gua Chung Lim
Message-ID: <20180729160500.ga3...@gmail.com>
| I don't suspect my router,
| I don't suspect dhcpcd
| I don't suspect name resolution
|
| Any ideas?
Date:Sun, 29 Jul 2018 23:05:01 +0700
From:Gua Chung Lim
Message-ID: <20180729160500.ga3...@gmail.com>
| I don't suspect my router,
| I don't suspect dhcpcd
| I don't suspect name resolution
|
| Any ideas?
First, stop not suspecting ... that is jumping
On 29/07/2018 17:05, Gua Chung Lim wrote:
Thanks for your kind response.
* Martin Husemann (mar...@duskware.de) wrote:
In the not working case, wm0 has:
inet6 2405:9800:b550:2939:f234:69d6:e0bf:8ebf/64 flags 0x0
inet6 2405:9800:b550:2939:8638:35ff:fe48:5720/128 flags 0x0
and it would
Thanks for your kind response.
* Martin Husemann (mar...@duskware.de) wrote:
> In the not working case, wm0 has:
>
> inet6 2405:9800:b550:2939:f234:69d6:e0bf:8ebf/64 flags 0x0
> inet6 2405:9800:b550:2939:8638:35ff:fe48:5720/128 flags 0x0
>
> and it would be good to understand where the
On 29/07/2018 09:06, Martin Husemann wrote:
In the not working case, wm0 has:
inet6 2405:9800:b550:2939:f234:69d6:e0bf:8ebf/64 flags 0x0
inet6 2405:9800:b550:2939:8638:35ff:fe48:5720/128 flags 0x0
and it would be good to understand where the second comes from.
Maybe add "-d" to
In the not working case, wm0 has:
inet6 2405:9800:b550:2939:f234:69d6:e0bf:8ebf/64 flags 0x0
inet6 2405:9800:b550:2939:8638:35ff:fe48:5720/128 flags 0x0
and it would be good to understand where the second comes from.
Maybe add "-d" to dhcpcd_flags in /etc/rc.conf and see what it
says?
* Gua Chung Lim (gua.chung...@gmail.com) wrote:
> > Oh, how many other hosts are on this LAN? (Regardless of
> > whether they support v6 or not.) One possibility for the issue
> > might be if the router thinks the LAN link is down when your
> > host is down, and drops the announcement of the
Thank you for your kindness in helping me.
* Robert Elz (k...@munnari.oz.au) wrote:
> | Long message does not interest people. :-p
>
> Often, true, but requiring going to look at an external web page will also
> discourage some people...It is a trade off.
Personally, I opt external links
Date:Sat, 28 Jul 2018 22:04:58 +0700
From:Gua Chung Lim
Message-ID: <20180728150458.ga1...@gmail.com>
| > If there is some other LL IPv6 on your net it might
| > be worth testing that one as well
| I have only one IPv6 network.
Oh, somehow I skipped that part.
Date:Sat, 28 Jul 2018 22:04:58 +0700
From:Gua Chung Lim
Message-ID: <20180728150458.ga1...@gmail.com>
| > ping6 fe80::1%wm0
| It still works pretty fine.
In general when using LL addresses, especially on a host with multiple
interfaces, you should always specify
Thank you very much for your kind response.
> If there is some other LL IPv6 on your net it might
> be worth testing that one as well
I have only one IPv6 network.
> Actually, is that exactly what you are typing ( "ping6 fe80::1" ) ?
ping6 -c 3 fe80::1
> If so, there's no interface specified,
Date:Sat, 28 Jul 2018 17:38:13 +0700
From:Gua Chung Lim
Message-ID: <20180728103813.ga...@gmail.com>
| I previously had rtsol in /etc/ifconfig.wm0 i.e.
|
| % cat /etc/ifconfig.wm0
| up
| !rtsol $int
Yes, rtsol was deleted, dhcpcd does that job now (Roy can
Thanks for your kind response, though I don't know much about what you are
explaining.
* Robert Elz (k...@munnari.oz.au) wrote:
> Just guessing, but this sounds to me like the "prohibiit sending from
> tentative addresses" BS that was added a while ago.
>
> I'd suspect that it goes something
Just guessing, but this sounds to me like the "prohibiit sending from
tentative addresses" BS that was added a while ago.
I'd suspect that it goes something like this ...
host boots, configures itself link-local addresses, and starts DaD
on them - addesses are tentative.
rtsol (v7) or dhcpcd
Thanks for your kind response.
>> % cat /etc/resolv.conf
>> # Generated by resolvconf
>> nameserver 192.168.1.1
>> nameserver fe80::1%wm0
>
> Based on these nameserver addresses, I'm assuming this is a host
> underneath another router you have?
Exactly, yes.
> If that's the case, it might be
On Fri, Jul 27, 2018 at 8:46 PM, Gua Chung Lim wrote:
> Scarcely, ping6 works at the first boot, while ping (IPv4) always works
> pretty fine. Mostly, I have to disconnect and re-connect the network 3-4
> times to have ping6 work. I haven't encountered this issue on netbsd-7.
>
> Related lines
Scarcely, ping6 works at the first boot, while ping (IPv4) always works pretty
fine. Mostly, I have to disconnect and re-connect the network 3-4 times to have
ping6 work. I haven't encountered this issue on netbsd-7.
Related lines in /etc/rc.conf...
# auto_ifconfig=YES
#wpa_supplicant=YES
Hi,
I have been using NetBSD 8.0 for a few days.
I found some inconsistency.
Sometimes I cannot ping6 anywhere.
But many times I can, and without touching any configuration.
Occasionally, I have to wait 10-15 minutes after boot,
in order to get access to IPv6 addresses.
Disabling NPF does not fix
29 matches
Mail list logo
