Forum Debian Users Gang

 #dig www.yahoo.com
# time curl -Iv https://www.yahoo.com
*   Trying 87.248.100.215:443...
*   Trying 2a00:1288:110:c305::1:8001:443...
* Immediate connect fail for 2a00:1288:110:c305::1:8001: Network is unreachable
*   Trying 2a00:1288:110:c305::1:8000:443...
* Immediate connect fail for 2a00:1288:110:c305::1:8000: Network is unreachable
* Connected to www.yahoo.com (87.248.100.215) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256
* ALPN, server accepted to use h2
* Server certificate:
*  subject: C=US; ST=California; L=Sunnyvale; O=Oath Holdings Inc.; CN=yahoo.com
*  start date: May  2 00:00:00 2023 GMT
*  expire date: Oct 25 23:59:59 2023 GMT
*  subjectAltName: host "www.yahoo.com" matched cert's "*.yahoo.com"
*  issuer: C=US; O=DigiCert Inc; OU=www.digicert.com; CN=DigiCert SHA2 High Assurance Server CA
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x55a51387cfc0)
> HEAD / HTTP/2
> Host: www.yahoo.com
> user-agent: curl/7.74.0
> accept: */*
> 
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* Connection state changed (MAX_CONCURRENT_STREAMS == 100)!
< HTTP/2 200 
HTTP/2 200 
< date: Mon, 14 Aug 2023 21:15:52 GMT
date: Mon, 14 Aug 2023 21:15:52 GMT
< strict-transport-security: max-age=31536000
strict-transport-security: max-age=31536000
< server: ATS
server: ATS
< cache-control: no-store, no-cache, max-age=0, private
cache-control: no-store, no-cache, max-age=0, private
< content-type: text/html
content-type: text/html
< content-language: en
content-language: en
< expires: -1
expires: -1
< content-security-policy: frame-ancestors 'self' https://*.builtbygirls.com https://*.rivals.com https://*.engadget.com https://*.intheknow.com https://*.autoblog.com https://*.techcrunch.com https://*.yahoo.com https://*.aol.com https://*.huffingtonpost.com https://*.oath.com https://*.search.yahoo.com https://*.pnr.ouryahoo.com https://pnr.ouryahoo.com https://*.search.aol.com https://*.search.huffpost.com https://*.onesearch.com https://*.verizonmedia.com https://*.publishing.oath.com https://*.autoblog.com; sandbox allow-forms allow-same-origin allow-scripts allow-popups allow-popups-to-escape-sandbox allow-presentation; report-uri https://csp.yahoo.com/beacon/csp?src=ats&site=frontpage&region=US&lang=en-US&device=desktop&yrid=6q631m1idl6c8&partner=;
content-security-policy: frame-ancestors 'self' https://*.builtbygirls.com https://*.rivals.com https://*.engadget.com https://*.intheknow.com https://*.autoblog.com https://*.techcrunch.com https://*.yahoo.com https://*.aol.com https://*.huffingtonpost.com https://*.oath.com https://*.search.yahoo.com https://*.pnr.ouryahoo.com https://pnr.ouryahoo.com https://*.search.aol.com https://*.search.huffpost.com https://*.onesearch.com https://*.verizonmedia.com https://*.publishing.oath.com https://*.autoblog.com; sandbox allow-forms allow-same-origin allow-scripts allow-popups allow-popups-to-escape-sandbox allow-presentation; report-uri https://csp.yahoo.com/beacon/csp?src=ats&site=frontpage&region=US&lang=en-US&device=desktop&yrid=6q631m1idl6c8&partner=;
< x-frame-options: SAMEORIGIN
x-frame-options: SAMEORIGIN
< x-xss-protection: 1; mode=block
x-xss-protection: 1; mode=block
< referrer-policy: no-referrer-when-downgrade
referrer-policy: no-referrer-when-downgrade
< x-content-type-options: nosniff
x-content-type-options: nosniff
< content-length: 12
content-length: 12

< 
* Connection #0 to host www.yahoo.com left intact

real    0m17.226s
user    0m0.039s
sys    0m0.005s

$ dig www.yahoo.com

; <<>> DiG 9.16.42-Debian <<>> www.yahoo.com
;; global options: +cmd
;; connection timed out; no servers could be reached

$ time curl -Iv https://www.yahoo.com
* Could not resolve host: www.yahoo.com
* Closing connection 0
curl: (6) Could not resolve host: www.yahoo.com

real    0m40.120s
user    0m0.016s
sys    0m0.021s

nslookup yahoo.com
;; Got SERVFAIL reply from 8.8.8.8, trying next server
Server:        8.8.4.4
Address:    8.8.4.4#53

** server can't find yahoo.com: SERVFAIL

nslookup -debug yahoo.com
;; connection timed out; no servers could be reached

dig example.com

; <<>> DiG 9.16.42-Debian <<>> example.com
;; global options: +cmd
;; connection timed out; no servers could be reached

nmcli dev connect wlp5s0
nmcli device wifi connect ...... password ........
sudo wpa_supplicant -i wlx502b73a51266 -c etc/wpa_supplicant/wpa_supplicant.conf -B

cat /etc/resolv.conf
# Generated by NetworkManager
search localdomain
nameserver 8.8.8.8
nameserver 8.8.4.4

systemctl status wpa_supplicant
[sudo] password for mark: 
● wpa_supplicant.service - WPA supplicant
     Loaded: loaded (/lib/systemd/system/wpa_supplicant.service; enabled; vendo>
     Active: active (running) since Thu 2023-08-17 10:27:26 IST; 4min 53s ago
   Main PID: 730 (wpa_supplicant)
      Tasks: 1 (limit: 9297)
     Memory: 4.8M
        CPU: 112ms
     CGroup: /system.slice/wpa_supplicant.service
             └─730 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant

wpa_cli status