Comment # 45 on bug 1188949 from Raija Ruuska

(In reply to Vladislav Milenin from comment #43)
> (In reply to Jonathan Kang from comment #42)
> > (In reply to Vladislav Milenin from comment #41)
> > > Created attachment 854023 [details]
> > > dhclient log
> > > 
> > > When executing the command "dhclient -v -d eth0" nothing happens and "Device
> > > "eth0" does not exist." is output. My network is called enp2s0, as the
> > > system automatically named it during installation. In the command, I changed
> > > "eth0" to "enp2s0" and it was executed correctly.
> > 
> > Yep. Use your ethernet interface name instead.
> > 
> > The log shows that dhclient still cannot get an reply from DHCP server. It
> > didn't
> > even get an DHCPOFFER this time.
> 
> I've run out of ideas what it could be. Most likely, this is a unique bug on
> my configuration, which cannot be reproduced by anyone else. At the moment,
> as a solution, I use the dhcp=internal parameter from comment#7 and it works
> fine all the time.

I have a brand new mini PC ASUS ExpertCenter PN52 and I have the same problem.
The network disconnects every few days. I have not noticed the same error in
another mini PC (Intel��� NUC Kit NUC8i7BEH). Both computers have the same
software Tumbleweed 20221202.