From: grinch@somewhere.net   
      
   On 14/03/2023 11:56, Don Spam's Reckless Son wrote:   
   > grinch wrote:   
   >> On 13/03/2023 22:50, Carlos E.R. wrote:   
   >>> On 2023-03-13 14:45, Malcolm wrote:   
   >>>> On Mon, 13 Mar 2023 13:13:59 +0000   
   >>>> grinch  wrote:   
   >>>>   
   >>>>> I am seeing public ipv4 addresses in my eth0 settings .It configured   
   >>>>> to use 1.1.1.1 and 1.1.0.1   
      
      
   >>>>>   
   >>>>> I am a retired network engineer so I understand how cloudflare itself   
   >>>>> works but it is very difficult to get an accurate answer to my   
   >>>>> question.   
   >   
   >>   
   >>>   
   >> As per my yesterdays post which appears to have been lost in this group .   
   >>   
   >> The latest tumbleweed update has fixed the issue so it was a bug/feature.   
   >>   
      
      
   > I don't use Tumbleweed but can't imagine an update changing   
   > configuration settings in that way (unless the previous version was   
   > totally broken and incapable of reading config files successfully).   
      
      
   It now follows the firewalls dhcp4/6 settings as does everything else on   
   the network and there have been no changes/reboots made to the firewall.   
      
   All my other OS 15.4 Linux boxes and android devices on the network,   
   work properly DNS wise as they have always done.   
      
   Even when I added the DNS servers manually it still used the same   
   settings,that what was worrying me.   
      
   Next little project is to create a Firewall DNS allow rule for   
   cloudflare and my ISP's ipv4/6 DNS servers only then put a firewall deny   
   DNS/log the rule after it so I can see if it happens again.   
      
     My guess would be something external to your machine, although a failure   
   > of ee-maj-in-eyshun on my part is always on the cards.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)