websites not working [SOLVED]

jl2 · 2022-06-01 12:40:39

most websites do not work. some that work without problem:
- google.com
- archlinux.org
- lineageos.org

If i use ping on them:
--- google.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4007ms
rtt min/avg/max/mdev = 18.806/19.073/19.361/0.176 ms

If i use ping on github:
ping github.com
ping: connect: Network is unreachable

i haven't changed anything between them both.

it works on the live enviroment. i have systemd-networkd, systemd-resolved, ModemManager and iwd enabled.

Thanks for your help.

Last edited by jl2 (2022-06-02 12:45:31)

seth · 2022-06-01 13:13:55

Please post the actual output of

dig google.com
dig github.com
ping -c1 google.com
ping -c1 github.com

possibly some IPv6 ./. IPv4 situation.

Scimmia · 2022-06-01 13:15:09

First off, why are both iwd and systemd-networkd enabled?

Second, how did you configure systemd-resolved?

geopardo · 2022-06-01 22:42:57

same situation in past.. fake server.. and hijacked mail servers..
u must install arch connected only to kenerl.org and some ark worldwide servers..

i my case bbs.archlinux.or was defaced.. some code functions

@.. your case website offline is a good notice, u configured well arch linux network..

i told here, maybe there is ark fake servers and some bootnet inside us..

edit

try see status or
# systemctl start/enable systemd-resolved.service

Last edited by geopardo (2022-06-01 22:45:02)

jasonwryan · 2022-06-01 23:36:05

geopardo wrote:

same situation in past.. fake server.. and hijacked mail servers..
u must install arch connected only to kenerl.org and some ark worldwide servers..
i my case bbs.archlinux.or was defaced.. some code functions
@.. your case website offline is a good notice, u configured well arch linux network..
i told here, maybe there is ark fake servers and some bootnet inside us..

Don't post garbage like this.

jl2 · 2022-06-02 06:19:32

dig google.com:

 ; <<>> DiG 9.18.3 <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45249
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;google.com.                    IN      A

;; ANSWER SECTION:
google.com.             179     IN      A       216.58.212.142

;; Query time: 6 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Thu Jun 02 08:09:52 CEST 2022
;; MSG SIZE  rcvd: 55

dig github.com:

 ; <<>> DiG 9.18.3 <<>> github.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34647
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;github.com.                    IN      A

;; ANSWER SECTION:
github.com.             44      IN      A       140.82.121.3

;; Query time: 8 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Thu Jun 02 08:16:37 CEST 2022
;; MSG SIZE  rcvd: 55

ping -c1 google.com:

PING google.com(fra07s28-in-x200e.1e100.net (2a00:1450:4001:801::200e)) 56 data 
bytes
64 bytes from fra16s46-in-x0e.1e100.net (2a00:1450:4001:801::200e): icmp_seq=1 t
tl=118 time=10.3 ms

--- google.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 10.278/10.278/10.278/0.000 ms

ping -c1 github.com

ping: connect: Network is unreachable

seth · 2022-06-02 06:30:03

dig returns IPv4 from the localhost (resolved) but you're pinging IPv6 and gitub.com doesn't even get resolved.

resolvectl status
ip a; ip r
find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
cat /etc/nsswitch.conf

jl2 · 2022-06-02 12:45:12

thanks seth, installed dhcpcd, enabled it and it worked.

seth · 2022-06-02 13:43:06

dhcpcd will collide w/ systemd-networkd and possibly other services - there's a good chance you made a bad situation worse, just now the better™ tool wins the race.
Please post the output of the commands above if you don't want to run into more troubles down the road…

jl2 · 2022-06-03 15:40:18

resolvectl status:

Global
           Protocols: +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
    resolv.conf mode: stub
  Current DNS Server: 2606:4700:4700::1111#cloudflare-dns.com
Fallback DNS Servers: 1.1.1.1#cloudflare-dns.com 9.9.9.9#dns.quad9.net 8.8.8.8#dns.google
                      2606:4700:4700::1111#cloudflare-dns.com 2620:fe::9#dns.quad9.net
                      2001:4860:4860::8888#dns.google

Link 2 (enp2s0)
Current Scopes: none
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 4 (wlan0)
Current Scopes: LLMNR/IPv4 LLMNR/IPv6
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

ip a:

1: lo: <LOOPBACK,UP,LOWER_UP> 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: enp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether b0:5a:da:fe:a6:cb brd ff:ff:ff:ff:ff:ff
4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 94:65:9c:ed:45:ef brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.213/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0
       valid_lft 257333sec preferred_lft 224933sec
    inet6 2001:1715:4e3d:610:58d5:4191:d593:f059/128 scope global dynamic noprefixroute 
       valid_lft 3528sec preferred_lft 3528sec
    inet6 2001:1715:4e3d:610:8778:be8b:fb92:b5e/64 scope global dynamic mngtmpaddr noprefixroute 
       valid_lft 7180sec preferred_lft 3580sec
    inet6 fdaa:bbcc:ddee:0:3cb0:4134:c89:6329/64 scope global mngtmpaddr noprefixroute 
       valid_lft forever preferred_lft forever
    inet6 fe80::757e:6e82:4f9:dc29/64 scope link 
       valid_lft forever preferred_lft forever

ip r:

default via 192.168.1.1 dev wlan0 proto dhcp src 192.168.1.213 metric 3004 
192.168.1.0/24 dev wlan0 proto dhcp scope link src 192.168.1.213 metric 3004

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f:

dbus-org.freedesktop.ModemManager1.service | system
dbus-org.freedesktop.resolve1.service    | system
dhcpcd.service                           | multi-user.target.wants
dirmngr.socket                           | sockets.target.wants
display-manager.service                  | system
gcr-ssh-agent.socket                     | sockets.target.wants
getty@tty1.service                       | getty.target.wants
gnome-keyring-daemon.socket              | sockets.target.wants
gpg-agent-browser.socket                 | sockets.target.wants
gpg-agent-extra.socket                   | sockets.target.wants
gpg-agent-ssh.socket                     | sockets.target.wants
gpg-agent.socket                         | sockets.target.wants
iwd.service                              | multi-user.target.wants
ModemManager.service                     | multi-user.target.wants
p11-kit-server.socket                    | sockets.target.wants
pipewire-session-manager.service         | user
pipewire.socket                          | sockets.target.wants
pulseaudio.socket                        | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
systemd-resolved.service                 | sysinit.target.wants
wireplumber.service                      | pipewire.service.wants
xdg-user-dirs-update.service             | default.target.wants

cat /etc/nsswitch.conf

# Name Service Switch configuration file.
# See nsswitch.conf(5) for details.

passwd: files systemd
group: files [SUCCESS=merge] systemd
shadow: files systemd
gshadow: files systemd

publickey: files

hosts: mymachines resolve [!UNAVAIL=return] files myhostname dns
networks: files

protocols: files
services: files
ethers: files
rpc: files

netgroup: files

seth · 2022-06-03 16:18:22

Different from your OP, you're not running systemd-networkd… (nor networkmanager, for the records)
Since there's (only) a wifi connection, do you actually need https://wiki.archlinux.org/title/Mobile … demManager ?

jl2 · 2022-06-03 17:04:07

I removed systemd-networkd after this post:

Scimma wrote:

First off, why are both iwd and systemd-networkd enabled?

Why do you think i should have installed networkmanager?
Thanks again.

geopardo · 2022-06-04 03:14:51

Is strange dhcpcd problems , about post chroot arch linux installation..

i know during installation, always i install dhcpcd in chroot,
if u don't install dhcpcd package, maybe can be more problem post reboot..

PS
My problem was similar during a fresh linux install. with dhcpcd I was able to ping ..
but then I could not download the necessary packages, to continue the installation of the xorg server and the desktop.

I solved it by activating the resolvers and dhcpcd, consequently it worked properly.

# systemctl start/enable systemd-resolved.service
# cat /etc/dhcpcd.conf
# cat /etc/resolv.conf

On internet browsing can be also a proxy problems.. automatic/manual..

try see

Last edited by geopardo (2022-06-04 03:35:53)

seth · 2022-06-04 05:14:54

Disregard geopardos comment.

I didn't necessarily think that you were running NM, just pointing out that you were not (causing other collisions) and because it's often used along modemmanager.

On the subject: iwd primarily provides the carrier (the "wifi cable") and either dhcpcd or systemd-networkd or dhcpcd can obtain a lease on top of that.
However, if you https://wiki.archlinux.org/title/Iwd#En … figuration neither is necessary and will rather cause a race condition.

I suspect that originally systemd-networkd for whatever reason only provided you w/ an IPv6 lease.
Provide the updated outputs requested in #7 if the problem should re-surface.

geopardo · 2022-06-04 21:23:33

seth wrote:

Disregard geopardos comment.
I didn't necessarily think that you were running NM, just pointing out that you were not (causing other collisions) and because it's often used along modemmanager.
On the subject: iwd primarily provides the carrier (the "wifi cable") and either dhcpcd or systemd-networkd or dhcpcd can obtain a lease on top of that.
However, if you https://wiki.archlinux.org/title/Iwd#En … figuration neither is necessary and will rather cause a race condition.
I suspect that originally systemd-networkd for whatever reason only provided you w/ an IPv6 lease.
Provide the updated outputs requested in #7 if the problem should re-surface.

Yes, I took advantage at the last moment to ask for clarification.

Thank you so much Seth .. I will study this wiki page .. But can it be a security flaw in the linux system?

I need disable ipv6 ..

Last edited by geopardo (2022-06-04 21:27:41)

Slithery · 2022-06-04 21:54:13

geopardo wrote:

But can it be a security flaw in the linux system?
I need disable ipv6 ..

No.

geopardo · 2022-06-11 10:21:15

On fresh ark installation here the websites working , i having to open a new 3d maybe..
but there is a problem, on this arch linux: i can't debug proxy or for say analize internet traffic/connections..
wireshark working, well full working; but mitmproxy do no life signal.. same do fiddler..
what can be? or for better .. i try open a proper 3d?

Arch Linux

#1 2022-06-01 12:40:39

websites not working [SOLVED]

#2 2022-06-01 13:13:55

Re: websites not working [SOLVED]

#3 2022-06-01 13:15:09

Re: websites not working [SOLVED]

#4 2022-06-01 22:42:57

Re: websites not working [SOLVED]

#5 2022-06-01 23:36:05

Re: websites not working [SOLVED]

#6 2022-06-02 06:19:32

Re: websites not working [SOLVED]

#7 2022-06-02 06:30:03

Re: websites not working [SOLVED]

#8 2022-06-02 12:45:12

Re: websites not working [SOLVED]

#9 2022-06-02 13:43:06

Re: websites not working [SOLVED]

#10 2022-06-03 15:40:18

Re: websites not working [SOLVED]

#11 2022-06-03 16:18:22

Re: websites not working [SOLVED]

#12 2022-06-03 17:04:07

Re: websites not working [SOLVED]

#13 2022-06-04 03:14:51

Re: websites not working [SOLVED]

#14 2022-06-04 05:14:54

Re: websites not working [SOLVED]

#15 2022-06-04 21:23:33

Re: websites not working [SOLVED]

#16 2022-06-04 21:54:13

Re: websites not working [SOLVED]

#17 2022-06-11 10:21:15

Re: websites not working [SOLVED]

Board footer