You are not logged in.

Pages: 1

#1 2022-10-14 18:10:20

technicap
Member
Registered: 2022-10-14
Posts: 54

[SOLVED]Strange Network connectivity problem

What do I mean by strange is that machine has connection to outside world ,which I tested by pinging 8.8.8.8, machine also doesn`t resolve domain names which I tested with
ping google.com . Device also doesn't have access to local network devices and router configuration page. On all other devices on my network there are no issues. Machine if connected to access point on my phone works perfectly fine .

Last edited by technicap (2022-10-15 19:53:28)

Offline

#2 2022-10-14 21:20:11

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,464

Re: [SOLVED]Strange Network connectivity problem

machine has connection to outside world ,which I tested by pinging 8.8.8.8, machine also doesn`t resolve domain names

So it's a DNS issue?

Device also doesn't have access to local network devices and router configuration page.

???

Please post the outputs of 

ip a
ip r
ping -c1 8.8.8.8
ping -c1 google.com
ping -c1 _gateway
resolvectl
find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#3 2022-10-15 10:29:49

technicap
Member
Registered: 2022-10-14
Posts: 54

Re: [SOLVED]Strange Network connectivity problem

output of 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: enp7s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 7c:d3:0a:81:2d:00 brd ff:ff:ff:ff:ff:ff
3: wlp0s20f3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether a4:c3:f0:48:86:ae brd ff:ff:ff:ff:ff:ff
    inet 192.168.100.6/24 brd 192.168.100.255 scope global dynamic noprefixroute wlp0s20f3
       valid_lft 86328sec preferred_lft 86328sec
    inet6 fe80::973c:2e69:9355:4f88/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
4: virbr3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 52:54:00:3f:31:76 brd ff:ff:ff:ff:ff:ff
    inet 10.0.2.2/24 brd 10.0.2.255 scope global virbr3
       valid_lft forever preferred_lft forever
5: virbr1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 52:54:00:3c:77:da brd ff:ff:ff:ff:ff:ff
    inet 192.168.100.1/24 brd 192.168.100.255 scope global virbr1
       valid_lft forever preferred_lft forever
6: virbr2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 52:54:00:a7:eb:38 brd ff:ff:ff:ff:ff:ff
7: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether 52:54:00:46:8c:16 brd ff:ff:ff:ff:ff:ff
    inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
       valid_lft forever preferred_lft forever
8: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default 
    link/ether 02:42:67:83:8c:0f brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever

output of ip r;

default via 192.168.100.1 dev wlp0s20f3 proto dhcp src 192.168.100.6 metric 600 
10.0.2.0/24 dev virbr3 proto kernel scope link src 10.0.2.2 linkdown 
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
192.168.100.0/24 dev virbr1 proto kernel scope link src 192.168.100.1 linkdown 
192.168.100.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.100.6 metric 600 
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown

output of ping -c1 8.8.8.8 :

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.

--- 8.8.8.8 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

output of ping -c1 google.com:

ping: google.com: Temporary failure in name resolution

output of  ping -c1 _gateway :

ping: _gateway: Temporary failure in name resolution

outoput of resolvectl :

Global
           Protocols: +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
    resolv.conf mode: foreign
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 (enp7s0)
Current Scopes: none
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 3 (wlp0s20f3)
    Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
         Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 192.168.100.5
       DNS Servers: 192.168.100.5

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

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

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

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

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

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

bluetooth.service                        | bluetooth.target.wants
cockpit.socket                           | sockets.target.wants
dbus-org.bluez.service                   | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.resolve1.service    | system
dbus-org.freedesktop.timesync1.service   | system
display-manager.service                  | system
docker.service                           | multi-user.target.wants
gcr-ssh-agent.socket                     | sockets.target.wants
getty@tty1.service                       | getty.target.wants
libvirtd-ro.socket                       | sockets.target.wants
libvirtd.service                         | multi-user.target.wants
libvirtd.socket                          | sockets.target.wants
lm_sensors.service                       | multi-user.target.wants
nbfc.service                             | multi-user.target.wants
NetworkManager.service                   | multi-user.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
ntpd.service                             | multi-user.target.wants
optimus-manager.service                  | graphical.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
systemd-timesyncd.service                | sysinit.target.wants
virtlockd.socket                         | sockets.target.wants
virtlogd.socket                          | sockets.target.wants
wireplumber.service                      | pipewire.service.wants
xdg-user-dirs-update.service             | default.target.wants

Sorry  if my post was too vague.
Thanks for replay.

Last edited by technicap (2022-10-15 15:53:52)

Offline

#4 2022-10-15 10:33:14

technicap
Member
Registered: 2022-10-14
Posts: 54

Re: [SOLVED]Strange Network connectivity problem

technicap wrote:

Device also doesn't have access to local network devices and router configuration page.

The router and that other local device refuse connection from my arch linux machine

Offline

#5 2022-10-15 13:25:41

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,464

Re: [SOLVED]Strange Network connectivity problem

Please edit your post and wrap the output in "code" tags, https://bbs.archlinux.org/help.php#bbcode

You have a lease on wlp0s20f3 via 192.168.100.0/24 - the problem is that there's a route for that segment that prefers virbr1 and that bridge has no carrier.

ping -I wlp0s20f3 -c1 8.8.8.8

Those bridges come from some VM configuration or maybe docker?
What's the point here and how do you configure them and the routing table?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#6 2022-10-15 15:58:18

technicap
Member
Registered: 2022-10-14
Posts: 54

Re: [SOLVED]Strange Network connectivity problem

virbr0 and virbr1 are probably coming from kvm ,but I'm not using them and I don't really know how to delete them . Routing table is auto-generated , I didn't touch it.

Offline

#7 2022-10-15 16:17:57

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,464

Re: [SOLVED]Strange Network connectivity problem

To establish a baseline, stop/disable libvirt and/or take down the network "virsh net-destroy default"
Make sure the bridges are gone from ip a and ip r

If the network functions properly afterwards, explain your KVM setup.
I do understand
10.0.2.0/24 dev virbr3 proto kernel scope link src 10.0.2.2 linkdown
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
and
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown

but
192.168.100.0/24 dev virbr1 proto kernel scope link src 192.168.100.1 linkdown
should not be there because of
192.168.100.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.100.6 metric 600

You can probably also just remove the former entry but it's likely better to figure why it's there and  prevent it.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#8 2022-10-15 16:59:17

technicap
Member
Registered: 2022-10-14
Posts: 54

Re: [SOLVED]Strange Network connectivity problem

virsh net-destroy default did got rid of virb0 but virbr1 is still there and when I  turn of libvirt the output of command ping -c1 8.8.8.8 is :

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=119 time=3.64 ms

--- 8.8.8.8 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 3.639/3.639/3.639/0.000 ms

Offline

#9 2022-10-15 17:06:27

technicap
Member
Registered: 2022-10-14
Posts: 54

Re: [SOLVED]Strange Network connectivity problem

My setup of kvm before was managed with virt-manager ,but recently It was broken  so switched to using virsh and virt-viewer. The only kvm vms that I'm aware of are from Whonix which I created using using their guide. Bridges virb2 and virb3 are used by Whonix. I might still have my old Windows vm ,but I'm new to using virsh so I only know how to start Whonix vms and check form running ones.

Offline

#10 2022-10-15 17:16:20

technicap
Member
Registered: 2022-10-14
Posts: 54

Re: [SOLVED]Strange Network connectivity problem

Ok ,so I deleted the virb0 network. I think it was created by virt-manager and since virt-manager isn't currently on my machine it probably did some weird thing . Now everything works.If something happense I will open another issue.
Thanks for help

Last edited by technicap (2022-10-15 17:16:52)

Offline

#11 2022-10-15 19:46:43

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,464

Re: [SOLVED]Strange Network connectivity problem

\o/

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

Pages: 1

Board footer

Powered by FluxBB