Unable to connect to devuan laptop server on local network

nuclearkev · 2025-07-02 19:27:26

Hi all,

I've run into a issue with my current Devuan install on my laptop. When trying to use a program called "qrcp" I found that I was unable to connect to the server that was created in order to do the file transfer. I did a little testing and if I spin up an nginx server, I have the same issue. I also found that I am unable to ping the address of the laptop as well. After even more digging I found that there were certain machines that I was unable to ping _from_ the devuan laptop (making the request while on the laptop pinging outward) namely my actual home server, my phone, and my TVs but I was able to ping everything else.

I've checked for firewalls, iptables, subnet issues, tried joining to different wifis, etc. but nothing seems to fix this issue. Does anyone have any idea what could be causing this?

PS: I do have internet connection although I recently broke NetworkManager in the process of debugging... xD

ralph.ronnquist · Yesterday 02:13:12

Does the router isolate between wireless hosts and wired hosts?

nuclearkev · Yesterday 14:13:12

Nope, if I boot into a liveCD I can ping and ssh to the server without a problem. I haven't tried starting up a server on the livecd, however.

chris2be8 · Yesterday 16:24:03

Here are a few thing to check:

How are the systems connected to your network?
If any systems are connected wirelessly check they are connected to *your* router, not one belonging to a neightbour. That has been known.
If the laptop also has an ethernet port try connecting it to your router with an ethernet cable. Does that change the symptoms?

What are the symptoms of ping not working? Replace target with the name of the system you are trying to reach below (server, laptop, etc):
host target - does this return the servers IP address?
traceroute target - how many hops away is the server?
ping target - what does it say?
ssh -v target - some systems don't respond to ping but will allow a ssh connection. The -v will make ssh show how far it gets.

I hope that gives you some help.

nuclearkev · Yesterday 17:06:33

host target - does this return the servers IP address?
traceroute target - how many hops away is the server?
ping target - what does it say?
ssh -v target - some systems don't respond to ping but will allow a ssh connection. The -v will make ssh show how far it gets.

$ host 192.168.1.4
Host 4.1.168.192.in-addr.arpa. not found: 3(NXDOMAIN)

$ traceroute 192.168.1.4
traceroute to 192.168.1.4 (192.168.1.4), 30 hops max, 60 byte packets
 1  * * *
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

$ ping 192.168.1.4
PING 192.168.1.4 (192.168.1.4) 56(84) bytes of data.

`ping` never stops...

$ ssh -v samba@192.168.1.4
OpenSSH_9.2p1 Debian-2+deb12u6, OpenSSL 3.0.16 11 Feb 2025
debug1: Reading configuration data /home/kev/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files
debug1: /etc/ssh/ssh_config line 21: Applying options for *
debug1: Connecting to 192.168.1.4 [192.168.1.4] port 22.
debug1: connect to address 192.168.1.4 port 22: Connection timed out
ssh: connect to host 192.168.1.4 port 22: Connection timed out

When I run those on a computer that can connect to the server obvious ping gets a response in like 12ms, traceroute returns something immediately, and ssh asks for the password. The only one that is the same is when I use `host'. I get the same response.

ralph.ronnquist · Yesterday 22:28:14

Yes it sounds like the installation (not liveCD) has something wrong.

Does it have a firewall? e.g. does iptables-save report something; (or if you use nftables there would be a similar command among its programs). And use ip6tables-save for ipv6 rules. (I'm not sure about the nftables commands)

Is the interface up? ifconfig wlan0 would be the easiest, if you have net-tools installed. An you'd also check with ip link show dev wlan0 and ip address show dev wlan0. The ip command comes from the iproute2 package.

Is there a default route? ip route show ... and checking ipv6: ip -6 route show

Hmm but if understand right, the laptop does have other internet access... anyhow, please include the outputs of those commands and we'll see if there's something to see there.

nuclearkev · Today 02:08:17

iptables-save:

# Generated by iptables-save v1.8.9 (nf_tables) on Thu Jul  3 22:03:48 2025
*mangle
:PREROUTING ACCEPT [0:0]
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:POSTROUTING ACCEPT [0:0]
:LIBVIRT_PRT - [0:0]
-A POSTROUTING -j LIBVIRT_PRT
-A LIBVIRT_PRT -o virbr0 -p udp -m udp --dport 68 -j CHECKSUM --checksum-fill
COMMIT
# Completed on Thu Jul  3 22:03:48 2025
# Generated by iptables-save v1.8.9 (nf_tables) on Thu Jul  3 22:03:48 2025
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:LIBVIRT_FWI - [0:0]
:LIBVIRT_FWO - [0:0]
:LIBVIRT_FWX - [0:0]
:LIBVIRT_INP - [0:0]
:LIBVIRT_OUT - [0:0]
:ts-forward - [0:0]
:ts-input - [0:0]
-A INPUT -j LIBVIRT_INP
-A INPUT -j ts-input
-A FORWARD -j LIBVIRT_FWX
-A FORWARD -j LIBVIRT_FWI
-A FORWARD -j LIBVIRT_FWO
-A FORWARD -j ts-forward
-A OUTPUT -j LIBVIRT_OUT
-A LIBVIRT_FWI -d 192.168.122.0/24 -o virbr0 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A LIBVIRT_FWI -o virbr0 -j REJECT --reject-with icmp-port-unreachable
-A LIBVIRT_FWO -s 192.168.122.0/24 -i virbr0 -j ACCEPT
-A LIBVIRT_FWO -i virbr0 -j REJECT --reject-with icmp-port-unreachable
-A LIBVIRT_FWX -i virbr0 -o virbr0 -j ACCEPT
-A LIBVIRT_INP -i virbr0 -p udp -m udp --dport 53 -j ACCEPT
-A LIBVIRT_INP -i virbr0 -p tcp -m tcp --dport 53 -j ACCEPT
-A LIBVIRT_INP -i virbr0 -p udp -m udp --dport 67 -j ACCEPT
-A LIBVIRT_INP -i virbr0 -p tcp -m tcp --dport 67 -j ACCEPT
-A LIBVIRT_OUT -o virbr0 -p udp -m udp --dport 53 -j ACCEPT
-A LIBVIRT_OUT -o virbr0 -p tcp -m tcp --dport 53 -j ACCEPT
-A LIBVIRT_OUT -o virbr0 -p udp -m udp --dport 68 -j ACCEPT
-A LIBVIRT_OUT -o virbr0 -p tcp -m tcp --dport 68 -j ACCEPT
-A ts-forward -i tailscale0 -j MARK --set-xmark 0x40000/0xff0000
-A ts-forward -m mark --mark 0x40000/0xff0000 -j ACCEPT
-A ts-forward -s 100.64.0.0/10 -o tailscale0 -j DROP
-A ts-forward -o tailscale0 -j ACCEPT
-A ts-input -s 100.125.212.88/32 -i lo -j ACCEPT
-A ts-input -s 100.115.92.0/23 ! -i tailscale0 -j RETURN
-A ts-input -s 100.64.0.0/10 ! -i tailscale0 -j DROP
-A ts-input -i tailscale0 -j ACCEPT
-A ts-input -p udp -m udp --dport 49412 -j ACCEPT
COMMIT
# Completed on Thu Jul  3 22:03:48 2025
# Generated by iptables-save v1.8.9 (nf_tables) on Thu Jul  3 22:03:48 2025
*nat
:PREROUTING ACCEPT [0:0]
:INPUT ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:POSTROUTING ACCEPT [0:0]
:LIBVIRT_PRT - [0:0]
:ts-postrouting - [0:0]
-A POSTROUTING -j LIBVIRT_PRT
-A POSTROUTING -j ts-postrouting
-A LIBVIRT_PRT -s 192.168.122.0/24 -d 224.0.0.0/24 -j RETURN
-A LIBVIRT_PRT -s 192.168.122.0/24 -d 255.255.255.255/32 -j RETURN
-A LIBVIRT_PRT -s 192.168.122.0/24 ! -d 192.168.122.0/24 -p tcp -j MASQUERADE --to-ports 1024-65535
-A LIBVIRT_PRT -s 192.168.122.0/24 ! -d 192.168.122.0/24 -p udp -j MASQUERADE --to-ports 1024-65535
-A LIBVIRT_PRT -s 192.168.122.0/24 ! -d 192.168.122.0/24 -j MASQUERADE
-A ts-postrouting -m mark --mark 0x40000/0xff0000 -j MASQUERADE
COMMIT
# Completed on Thu Jul  3 22:03:48 2025

ip6tables-save

# Generated by ip6tables-save v1.8.9 (nf_tables) on Thu Jul  3 22:04:56 2025
*mangle
:PREROUTING ACCEPT [0:0]
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:POSTROUTING ACCEPT [0:0]
:LIBVIRT_PRT - [0:0]
-A POSTROUTING -j LIBVIRT_PRT
COMMIT
# Completed on Thu Jul  3 22:04:56 2025
# Generated by ip6tables-save v1.8.9 (nf_tables) on Thu Jul  3 22:04:56 2025
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:LIBVIRT_FWI - [0:0]
:LIBVIRT_FWO - [0:0]
:LIBVIRT_FWX - [0:0]
:LIBVIRT_INP - [0:0]
:LIBVIRT_OUT - [0:0]
:ts-forward - [0:0]
:ts-input - [0:0]
-A INPUT -j LIBVIRT_INP
-A INPUT -j ts-input
-A FORWARD -j LIBVIRT_FWX
-A FORWARD -j LIBVIRT_FWI
-A FORWARD -j LIBVIRT_FWO
-A FORWARD -j ts-forward
-A OUTPUT -j LIBVIRT_OUT
-A ts-forward -i tailscale0 -j MARK --set-xmark 0x40000/0xff0000
-A ts-forward -m mark --mark 0x40000/0xff0000 -j ACCEPT
-A ts-forward -o tailscale0 -j ACCEPT
-A ts-input -s fd7a:115c:a1e0::1f01:d459/128 -i lo -j ACCEPT
-A ts-input -i tailscale0 -j ACCEPT
-A ts-input -p udp -m udp --dport 36783 -j ACCEPT
COMMIT
# Completed on Thu Jul  3 22:04:56 2025
# Generated by ip6tables-save v1.8.9 (nf_tables) on Thu Jul  3 22:04:56 2025
*nat
:PREROUTING ACCEPT [0:0]
:INPUT ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:POSTROUTING ACCEPT [0:0]
:LIBVIRT_PRT - [0:0]
:ts-postrouting - [0:0]
-A POSTROUTING -j LIBVIRT_PRT
-A POSTROUTING -j ts-postrouting
-A ts-postrouting -m mark --mark 0x40000/0xff0000 -j MASQUERADE
COMMIT
# Completed on Thu Jul  3 22:04:56 2025

ifconfig wlan0:

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.17  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::d563:fbff:19fc:a534  prefixlen 64  scopeid 0x20<link>
        ether 2c:9c:58:29:10:6f  txqueuelen 1000  (Ethernet)
        RX packets 3734036  bytes 5142519247 (4.7 GiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1041488  bytes 206972980 (197.3 MiB)
        TX errors 0  dropped 37 overruns 0  carrier 0  collisions 0

ip link show dev wlan0:

 ip link show dev wlan0
2: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
    link/ether 2c:9c:58:29:10:6f brd ff:ff:ff:ff:ff:ff

ip address show dev wlan0:

2: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 2c:9c:58:29:10:6f brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.17/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0
       valid_lft 86132sec preferred_lft 75332sec
    inet6 fe80::d563:fbff:19fc:a534/64 scope link noprefixroute
       valid_lft forever preferred_lft forever

ip route show:

default via 192.168.1.1 dev wlan0 proto dhcp src 192.168.1.17 metric 3002
192.168.1.0/24 dev wlan0 proto dhcp scope link src 192.168.1.17 metric 3002

ip -6 route show:

fe80::/64 dev wlan0 proto kernel metric 1024 pref medium

I think that's everything! (everything seems normal to me...)

PS: i have a tailscale vpn hence the tailscale0 dev

Last edited by nuclearkev (Today 02:09:15)

ralph.ronnquist · Today 05:33:31

Yeah; almost all the iptables rules concerns accepting packets in circumstances, which are kind of useless rules when policy is "accept". However since they don't interfere they can be ignored. And in any case they shouldn't concern wlan0 traffic.

But that virtbr0 bridge might have networking impact. What's your output of brctl show? And ifconfig virtbr0?

I suppose the problem(s) you talk about concern the main host and network 192.168.1.0/24; not any qemu virtual machine?

The officially official Devuan Forum!

#1 2025-07-02 19:27:26

Unable to connect to devuan laptop server on local network

#2 Yesterday 02:13:12

Re: Unable to connect to devuan laptop server on local network

#3 Yesterday 14:13:12

Re: Unable to connect to devuan laptop server on local network

#4 Yesterday 16:24:03

Re: Unable to connect to devuan laptop server on local network

#5 Yesterday 17:06:33

Re: Unable to connect to devuan laptop server on local network

#6 Yesterday 22:28:14

Re: Unable to connect to devuan laptop server on local network

#7 Today 02:08:17

Re: Unable to connect to devuan laptop server on local network

#8 Today 05:33:31

Re: Unable to connect to devuan laptop server on local network

Board footer