Am Donnerstag, 29. August 2024, 20:31:10 CEST schrieb Tim Woodall:
> On Wed, 28 Aug 2024, Rainer Dorsch wrote:
> > In the systemd log, the first entry indicating network problems is that
> > the DNS server switches to another interface. But it could easily be a
> > consequence and not the cause of the issue:
> > 
> > Aug 28 06:57:54 h370 dhclient[1195]: DHCPREQUEST for 192.168.4.203 on
> > eno1.4 to 192.168.4.1 port 67
> > Aug 28 06:57:54 h370 dhclient[1195]: DHCPACK of 192.168.4.203 from
> > 192.168.4.1 Aug 28 06:57:54 h370 dnsmasq[2386]: reading /etc/resolv.conf
> > Aug 28 06:57:54 h370 dnsmasq[2386]: using nameserver 192.168.4.1#53
> > Aug 28 06:57:54 h370 dhclient[1195]: bound to 192.168.4.203 -- renewal in
> > 18265 seconds.
> 
> To me that looks like it's the DHCP request(renewal?) that is more
> likely breaking things. The DHCP server is presumably rewriting
> resolv.conf.
> 
> I have the following setting to stop dhcp changing resolv.conf:
> 
> $ cat /etc/dhcp/dhclient-enter-hooks.d/nodnsupdate
> make_resolv_conf() {
> 
> }
> 
> Don't know if that will fix your problem but it should hopefully stop
> those dnsmasq lines appearing in the log.
> 
> Does the problem definitely happen when the dhcp update happens or are
> these just the nearest logs?

Many thanks for your reply. I added the nodnsupdate configuration you 
suggested. But I should see now, if the problem comes back (unfortunately if 
happens in very irregular intervals). Do I need to restart a service that the 
change becomes effective?

I cannot tell if it happens when the dhcp update happens or if this was just a 
coincident (or if the network issue even triggered a dns update?). I can tell 
though that it by far happens not for every dhcp update, there are many more 
of them in the log. Therefore at least something else must happen as well.

I see a  number of active dhclients though

root         772  0.0  0.0   5872  3148 ?        Ss   Aug26   0:00 dhclient -4 
-v -i -pf /run/dhclient.eno1.pid -lf /var/lib/dhcp/dhclient.eno1.leases -I -df 
/var/lib/dhcp/dhclient6.eno1.leases eno1
root        1114  0.0  0.0   5872  3524 ?        Ss   Aug26   0:00 dhclient -4 
-v -i -pf /run/dhclient.eno1.3.pid -lf /var/lib/dhcp/dhclient.eno1.3.leases -I 
-df /var/lib/dhcp/dhclient6.eno1.3.leases eno1.3
root        1195  0.0  0.0   5872  3572 ?        Ss   Aug26   0:00 dhclient -4 
-v -i -pf /run/dhclient.eno1.4.pid -lf /var/lib/dhcp/dhclient.eno1.4.leases -I 
-df /var/lib/dhcp/dhclient6.eno1.4.leases eno1.4
root        1268  0.0  0.0   5868  3428 ?        Ss   Aug26   0:00 dhclient -4 
-v -i -pf /run/dhclient.eno1.6.pid -lf /var/lib/dhcp/dhclient.eno1.6.leases -I 
-df /var/lib/dhcp/dhclient6.eno1.6.leases eno1.6
root      377797  0.0  0.0   5848  3380 ?        Ss   Aug28   0:00 dhclient -4 
-v -i -pf /run/dhclient.br7.pid -lf /var/lib/dhcp/dhclient.br7.leases -I -df /
var/lib/dhcp/dhclient6.br7.leases br7
root      378009  0.0  0.0   5848  3560 ?        Ss   Aug28   0:00 dhclient -4 
-v -i -pf /run/dhclient.br2.pid -lf /var/lib/dhcp/dhclient.br2.leases -I -df /
var/lib/dhcp/dhclient6.br2.leases br2
root      378210  0.0  0.0   5848  3516 ?        Ss   Aug28   0:00 dhclient -4 
-v -i -pf /run/dhclient.br5.pid -lf /var/lib/dhcp/dhclient.br5.leases -I -df /
var/lib/dhcp/dhclient6.br5.leases br5

Many thanks again
Rainer

-- 
Rainer Dorsch
http://bokomoko.de/


Reply via email to