My Arch Linux is unreachable by local networks

zettomon · 2023-11-09 15:06:31

I have three devices: 2 Wireless (Arch Linux and Windows), 1 LAN (Windows)

I recently switched my ISP so the new ISP setup a new home router

My Arch Linux is hosting SMB Share, so it's crucial for me to be able to access it

However, all the devices (Even my phone) are intra-reachable, except my Arch Linux

Arch linux can't even reach other devices at the Layer 3 Level (Can't even ping them whereas other WiFi devices can ping the LAN devices and vice versa)

I've disabled both ufw and iptables in case they're interfering with the device.

Only the router and the internet can be pinged. However, visiting router via a browser doesn't show the router's configuration page, instead it just shows some web server with "This works" testing page. (But this is no longer working after disabling the arch's apache2 service, so it's probably me? and the 192.168.1.1 is having conflicting IP address with the device itself or something from the past that I can't seem to remember or I don't know I've been here for like hours my head hurts)

This could be the NAT problem but I can't seem to find it and the other wireless Windows devices are fine so I thought it was the Arch problem.

I can only see traffic of my Arch device going towards 224.0.0.251 multicast on Wireshark. (I've installed Avahi and enabled/started its services, but still no luck)

/etc/resolv.conf shows "search hgu_lan" nameserver <my router's ip>
I cannot access the websites, but I could if I just changed to static DNS (But still the LAN is inaccessible and this is not what I want)

Pinging from LAN to Arch Device says "Request timed out" while pinging from Arch to LAN says "Destination Host Unreachable"

My laptop just works fine at work, so it's probably the new home router, and I'm unfamiliar with home routers, and this router is weird, probably some modded one by the ISP. So, what am I missing here?

twelveeighty · 2023-11-09 16:43:10

What local subnet did your ISP configure on the new router? You're going to have to share some details on the local subnet of the router and the local config on your Arch machine, otherwise there's not a lot we can do to help. For example, it's possible (but unlikely) that the ISP only set up ipv6, not ipv4, which could explain your problems, but without actual data, it's hard to analyze.

zettomon · 2023-11-09 17:10:45

twelveeighty wrote:

What local subnet did your ISP configure on the new router? You're going to have to share some details on the local subnet of the router and the local config on your Arch machine, otherwise there's not a lot we can do to help. For example, it's possible (but unlikely) that the ISP only set up ipv6, not ipv4, which could explain your problems, but without actual data, it's hard to analyze.

IPv6 is disabled
The local subnet is 192.168.1.0/24
The router is 192.168.1.1
The router is probably configured to be in GPON network
The Arch is 192.168.1.100
The LAN PC is 192.168.1.103
The other Wireless Device is 192.168.1.102
My phone is probably something like 192.168.1.101 I guess.

Everything can be pinged each other (The wired devices, the wireless devices)
It's just the Arch system
The Arch just has NetworkManager setup on Hyprland with stuffs
I ran the wireshark on the Arch laptop, and it only has traffic to 224.0.0.251, querying for Multicast-DNS, but failing miserably I guess
I do have Avahi-daemon service installed and enabled, but is left untouched

seth · 2023-11-09 20:26:23

The Arch just has NetworkManager setup on Hyprland with stuffs

Pinging from LAN to Arch Device says "Request timed out" while pinging from Arch to LAN says "Destination Host Unreachable"

Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Please post the output of

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

Also the output of

ip a; ip r

on the arch system and please detail whether your tests have been to ping by IP or by hostname.

zettomon · 2023-11-10 02:53:27

seth wrote:

The Arch just has NetworkManager setup on Hyprland with stuffs
Pinging from LAN to Arch Device says "Request timed out" while pinging from Arch to LAN says "Destination Host Unreachable"
Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855

Sorry, I went dizzy, tired, shameful, and done yesterday for not being able to solve it.

seth wrote:

Please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.st

Here is my journal output -> http://0x0.st/HtG6.txt
Please only take the logs from yesterday (9th November, 2023), I'm at work today, so the logs afterwards shouldn't have anything related.

seth wrote:

Please post the output of

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

Here is the output of the above command

avahi-daemon.service                     | multi-user.target.wants
avahi-daemon.socket                      | sockets.target.wants
bluetooth.service                        | bluetooth.target.wants
cups.path                                | multi-user.target.wants
cups.service                             | multi-user.target.wants
cups.service                             | printer.target.wants
cups.socket                              | sockets.target.wants
dbus-org.bluez.service                   | system
dbus-org.freedesktop.Avahi.service       | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.timesync1.service   | system
docker.service                           | multi-user.target.wants
gcr-ssh-agent.socket                     | sockets.target.wants
getty@tty1.service                       | getty.target.wants
mariadb.service                          | multi-user.target.wants
NetworkManager.service                   | multi-user.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
nmb.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
smb.service                              | multi-user.target.wants
snmpd.service                            | multi-user.target.wants
sshd.service                             | multi-user.target.wants
systemd-timesyncd.service                | sysinit.target.wants
vmware-networks-server.service           | multi-user.target.wants
vmware.service                           | multi-user.target.wants
vmware-workstation-server.service        | multi-user.target.wants
wireplumber.service                      | pipewire.service.wants
xdg-user-dirs-update.service             | default.target.wants

Also the output of
ip a; ip r
on the arch system and please detail whether your tests have been to ping by IP or by hostname.

The output of ip a; ip r can't be captured at this moment as I'm at work right now.
The ping tests had been by IPv4 themselves, the ping could only reach an IP what seemed to be the router (But visiting the IP address on the web browser gave me the local Apache server rather than the router's config page by itself so I was thinking I was having IP conflicts with some stuffs, but I could go to the internet by IP address like pinging google's DNS.
And oh wait, I just noticed something, one of my bridge interface does actually have IP conflict with my new IP subnet assigned, the previous ISP was using 192.168.100.0/24 so I guess it was the reason why my arch was working okay.

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 noprefixroute
       valid_lft forever preferred_lft forever
2: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether c4:b3:01:ac:34:86 brd ff:ff:ff:ff:ff:ff
    inet 192.168.10.26/24 brd 192.168.10.255 scope global dynamic noprefixroute wlp3s0
       valid_lft 603559sec preferred_lft 603559sec
    inet6 fe80::eb7e:5fa2:a86:cded/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
3: br-f42b6cb1a16c: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:1a:e7:fe:4d brd ff:ff:ff:ff:ff:ff
    inet 172.20.0.1/16 brd 172.20.255.255 scope global br-f42b6cb1a16c
       valid_lft forever preferred_lft forever
4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:0d:70:33:34 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
5: br-3dbe276ee575: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:08:05:57:c0 brd ff:ff:ff:ff:ff:ff
    inet 172.27.0.1/16 brd 172.27.255.255 scope global br-3dbe276ee575
       valid_lft forever preferred_lft forever
6: br-6195ec8f1a60: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:5f:3f:86:5a brd ff:ff:ff:ff:ff:ff
    inet 172.22.0.1/16 brd 172.22.255.255 scope global br-6195ec8f1a60
       valid_lft forever preferred_lft forever
7: br-6cec0cac2569: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:dc:d2:f7:f4 brd ff:ff:ff:ff:ff:ff
    inet 172.24.0.1/16 brd 172.24.255.255 scope global br-6cec0cac2569
       valid_lft forever preferred_lft forever
8: br-946c780046a1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:32:d1:c5:86 brd ff:ff:ff:ff:ff:ff
    inet 172.18.0.1/16 brd 172.18.255.255 scope global br-946c780046a1
       valid_lft forever preferred_lft forever
9: br-e8b66bbda1b4: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:af:c5:bd:35 brd ff:ff:ff:ff:ff:ff
    inet 172.25.0.1/16 brd 172.25.255.255 scope global br-e8b66bbda1b4
       valid_lft forever preferred_lft forever
10: br-92f3c04c9ef5: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:40:2d:5d:6c brd ff:ff:ff:ff:ff:ff
    inet 172.23.0.1/16 brd 172.23.255.255 scope global br-92f3c04c9ef5
       valid_lft forever preferred_lft forever
11: br-b396cb899696: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:8c:35:a6:ff brd ff:ff:ff:ff:ff:ff
    inet 172.26.0.1/16 brd 172.26.255.255 scope global br-b396cb899696
       valid_lft forever preferred_lft forever
12: br-e9def8e13d30: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:76:70:0c:22 brd ff:ff:ff:ff:ff:ff
    inet 172.19.0.1/16 brd 172.19.255.255 scope global br-e9def8e13d30
       valid_lft forever preferred_lft forever
13: br-f3b9a2cbbc17: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:5d:4e:69:78 brd ff:ff:ff:ff:ff:ff
    inet 172.21.0.1/16 brd 172.21.255.255 scope global br-f3b9a2cbbc17
       valid_lft forever preferred_lft forever
14: br-ffdd7efe3097: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
    link/ether 02:42:6e:5a:13:1f brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.1/24 brd 192.168.1.255 scope global br-ffdd7efe3097
       valid_lft forever preferred_lft forever

I'll mark this as solved if this was the problem when I get back home. Thank you, good sirs!!

Arch Linux

#1 2023-11-09 15:06:31

My Arch Linux is unreachable by local networks

#2 2023-11-09 16:43:10

Re: My Arch Linux is unreachable by local networks

#3 2023-11-09 17:10:45

Re: My Arch Linux is unreachable by local networks

#4 2023-11-09 20:26:23

Re: My Arch Linux is unreachable by local networks

#5 2023-11-10 02:53:27

Re: My Arch Linux is unreachable by local networks

Board footer