From: none@nowhere.net   
      
   On 10/11/22 10:47 AM, Marco Moock wrote:   
   > On 11 Oct 2022 10:45:53 -0400 wAYNE  wrote:   
   >   
   >> Any suggestions welcome.  Everything had been working fine until this   
   >> morning.   
   >   
   > Post the output of   
   >   
   > ip a   
   > resolvectl   
   > cat /etc/resolv.conf   
   >   
   > When the connection is established and the question mark is there.   
   >   
      
      
   ip a   
      
   1: lo:  mtu 65536 qdisc noqueue state UNKNOWN   
   group default qlen 1000   
        link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00   
        inet 127.0.0.1/8 scope host lo   
           valid_lft forever preferred_lft forever   
        inet6 ::1/128 scope host   
           valid_lft forever preferred_lft forever   
   2: enp9s0:  mtu 1500 qdisc fq_codel   
   state UP group default qlen 1000   
        link/ether 00:23:ae:31:df:70 brd ff:ff:ff:ff:ff:ff   
        inet 192.168.1.224/24 brd 192.168.1.255 scope global dynamic   
   noprefixroute enp9s0   
           valid_lft 563sec preferred_lft 563sec   
        inet6 fe80::db86:de8c:8266:76/64 scope link noprefixroute   
           valid_lft forever preferred_lft forever   
   3: wlp12s0:  mtu 1500 qdisc noop state DOWN group   
   default qlen 1000   
        link/ether 0c:60:76:66:f6:c4 brd ff:ff:ff:ff:ff:ff   
      
      
      
      
      
   resolvectl   
      
               Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported   
   resolv.conf mode: stub   
      
   Link 2 (enp9s0)   
        Current Scopes: DNS   
             Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS   
   DNSSEC=no/unsupported   
   Current DNS Server: 192.168.1.1   
           DNS Servers: 192.168.1.1   
            DNS Domain: fios-router.home   
      
   Link 3 (wlp12s0)   
   Current Scopes: none   
         Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS   
   DNSSEC=no/unsupported   
      
      
      
      
   cat /etc/resolv.conf   
      
      
   # This is /run/systemd/resolve/stub-resolv.conf managed by   
   man:systemd-resolved(8).   
   # Do not edit.   
   #   
   # This file might be symlinked as /etc/resolv.conf. If you're looking at   
   # /etc/resolv.conf and seeing this text, you have followed the symlink.   
   #   
   # This is a dynamic resolv.conf file for connecting local clients to the   
   # internal DNS stub resolver of systemd-resolved. This file lists all   
   # configured search domains.   
   #   
   # Run "resolvectl status" to see details about the uplink DNS servers   
   # currently in use.   
   #   
   # Third party programs should typically not access this file directly,   
   but only   
   # through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a   
   # different way, replace this symlink by a static file or a different   
   symlink.   
   #   
   # See man:systemd-resolved.service(8) for details about the supported   
   modes of   
   # operation for /etc/resolv.conf.   
      
   nameserver 127.0.0.53   
   options edns0 trust-ad   
   search fios-router.home   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)