Re: Daemon.log
Roy Marples
Tue Jun 25 07:49:30 2019
Hi Rob
On 25/06/2019 03:36, rob stone wrote:
You could add noipv6 or noipv6rs.
I think I've made enough changes to avoid these messages with a
default
config in the master branch of dhcpcd but I can't easily test it.
Are you able to get a wireshark or tcpdump of the RA so I can see
why
it's doing this please? From what I see nothing has a lifetime hence
the
messages.
Roy
I altered the conf file and added the noipv6rs option.
That has stopped the flooding of the "no routers" messages.
However, these messages are now being written to daemon.log:-
Jun 25 11:49:26 roblaptop dhclient[554]: DHCPREQUEST for 192.168.1.100
I don't support dhclient, it's not my software.
There seems to be a bit of a disconnect relating to network settings.
Some weeks ago, systemd started writing out a resolv.conf file without
the nameservers that I use. This was fixed via an include file with the
correct IP addresses and that fixed that particular issue.
NetworkManager writes a correct resolv.conf file into
/var/run/NetworkManager.
The contents of /etc/network/interfaces seems to be ignored and a dhcp
lease appears to be acquired via whatever is connected. So, if I'm in a
hotel somewhere and manage to overcome rfkill switch issues so as to
use their wi-fi, I'm able to connect even though there is no entry for
wlan0 in /etc/network/interfaces.
You'll have to goto your distro for support with NetworkManager and
SystemD. I don't use either of these.
One tip though - dhcpcd also ignores /etc/network/interfaces. That's a
Debian (and derivatives) specific file.
If you are looking for a GUI front end to dhcpcd, or just a simple
systray icon to let you know the state of the network, enter a PSK to
connect to a wireless network or setup a static IP address then please
look at the dhcpcd-ui project which I can help with as it goes hand in
hand with dhcpcd.
Roy
Archive administrator: postmaster@marples.name