Posts by nuclearkev

nuclearkev · Other Issues

But, does your latop invent new macaddress when it reboots?

Unless this is the Devuan default, then no. It is a fully encrypted disk but I doubt that's related.

Did you check whether arp messages are received on the laptop (from any problem device)?

Nope, if I watch for arp messages while attempting to ping from my phone nothing ever shows up. However, if I boot into a liveCD with the same IP (192.168.1.17) I do get the arp messages and the ping works.

At any rate, since this seems to only happen on this current Devuan install I'll likely try a reinstall and see if that fixes it. Even the distro I had on this laptop before this one didn't have the issue so I'm assuming it's something that got messed up during installation or a bug.

nuclearkev · Other Issues

Well, now we're really stuck. Seems that overnight things have "resolved" between the server and the laptop. I'm able to ping it and it can ping me. Also, my other system is able to ping and connect to an example HTTP server on the laptop. While this might seem like the entire thing is fixed, it isn't. I still can't ping my phone, my wife's phone and my digital picture frame (which is just a raspberry pi). My phone and the picture frame both can't ping the laptop. Basically the same situation but with different devices. While I generally don't ever need to ping these or ssh out into them it still shows there is a problem. I can't get any information from my phone as I don't have the device rooted. I can, however, maybe get something from the picture frame. It's an old first generation RPI but we'll see what I get.

nuclearkev · Other Issues

I believe netbsd uses pf (maybe short for packet filter?) for firewalling...

pf(4) was deprecated. We now use the shiny new (since NetBSD 8 that is...) npf(7) xD Anyways, when I run npfctl show, which will show the current filter state and config I get:

# filtering:    inactive
# config:      empty

Regardless, I don't think that it has anything to do with the server as no systems on the entire network can ping the laptop. Even if I open a hotspot on my phone, join it along with another computer/phone I can't ping it.

I would guess netbsxd has different commands for sysctl too(?)

To be frank, I don't actually know the freelist.org(?)/linux sysctl program pretty much at all. Giving the man page for the linux sysctl and it looks completely different than the NetBSD one. If you tell me what I need to look for I can probably find it, however.

I just did another test where I booted into a liveCD of a different distro on the laptop and I was able to ping the server and I was able to ping the laptop (booted into the liveCD) from another computer. What was particularly important about this test was that the IP address of the liveCD was 192.168.1.17. I think this pretty much rules out that it's a router or a server issue. Seems to me that there might be a bug in the devuan network stack?

nuclearkev · Other Issues

The server runs NetBSD so I'm not sure how the linux routing tables look in comparison:

Internet:
Destination Gateway Flags Refs Use Mtu Interface
default 192.168.1.1 UG - - - genet0
127/8 localhost UGRS - - 33624 lo0
localhost lo0 UHl - - 33624 lo0
192.168.1/24 link#1 UC - - - genet0
192.168.1.4 link#1 UHl - - - lo0
192.168.1.10 18:58:80:62:72:0a UHL - - - genet0
192.168.1.1 80:cc:9c:27:e6:31 UHL - - - genet0
192.168.1.7 3c:22:fb:13:ce:50 UHL - - - genet0
192.168.1.25 32:4c:ba:00:4b:cd UHL - - - genet0
192.168.1.27 58:96:1d:f6:e5:19 UHL - - - genet0
192.168.1.17 2c:9c:58:29:10:6f UHL - - - genet0
192.168.1.16 e2:5e:09:96:f2:ad UHL - - - genet0

There is also a ipv6 table as well, if you need it.

EDIT: I ran netstat -r (to view the routing tables) when I was attempting to ping the server from the laptop. Hence why we see the 192.168.1.17 in the table. If I'm not pinging it, I don't see the IP in the table.

nuclearkev · Other Issues

ow about ping -n 9.9.9.9 from the laptop; does that get proper response? This test is only for verifying that packets from the laptop can go to and from the router. If that is the case, you will need to reconsider the router configuration.

Yes, works fine.

no that's not ping reqeust or response; that's ssh packets.

Haha, my mistake. I mistook 27 for 17 as the laptop's address is currently 192.168.1.17. I'll try it again.

listening on genet0, link-type EN10MB (Ethernet), capture size 262144 bytes
02:05:47.900289 IP 192.168.1.17 > 192.168.1.4: ICMP echo request, id 29541, seq 1, length 64
02:05:48.913712 IP 192.168.1.17 > 192.168.1.4: ICMP echo request, id 29541, seq 2, length 64
02:05:49.995650 IP 192.168.1.17 > 192.168.1.4: ICMP echo request, id 29541, seq 3, length 64
02:05:50.924072 IP 192.168.1.17 > 192.168.1.4: ICMP echo request, id 29541, seq 4, length 64
02:05:51.925312 IP 192.168.1.17 > 192.168.1.4: ICMP echo request, id 29541, seq 5, length 64
02:05:52.957950 IP 192.168.1.17 > 192.168.1.4: ICMP echo request, id 29541, seq 6, length 64
02:05:53.964533 IP 192.168.1.17 > 192.168.1.4: ICMP echo request, id 29541, seq 7, length 64
02:05:54.988505 IP 192.168.1.17 > 192.168.1.4: ICMP echo request, id 29541, seq 8, length 64

nuclearkev · Other Issues

since you don't have the same issues when using a _livecd/dvd/usb_ (no tailscale)
you'll need to know what tailscale has done and that might depend on how you installed tailscale.

No, it still happens when I turn off tailscale completely. It is possible that maybe tailscale broke something during installation as is suggested with the script you posted.

Sorry, I'm not sure why I assumed that orbi32 was the actual router name, it isn't. It's this one: https://www.netgear.com/support/product/rbr750/

Is there any pattern to which systems respond to ping from the laptop. Eg does it work for systems connected wirelessly but not ones with a wired connection? Do their IP addresses have any pattern (eg 192.168.1,* work but 192.168.0.* don't)?

The entire network is on 192.168.1.*, so I'm not sure about your second question. The only pattern that I see (that isn't really a pattern) is that 2 out of the 4-5 devices that I can't ping run NetBSD. However, I am able to ping my NetBSD laptop. Both of the other NetBSD systems are plugged into Ethernet. That being said, we'd almost have a pattern except for the fact that the rest of the devices that I can't ping both are linux systems (or so I assume) as one is my android phone and the other is out LG webOS TV, which back in the Palm/HP days ran linux. I can't remember what the last one is but there's a 99% chance it's a linux system.

Does the laptop respond to pings from other systems? If so does it respond to all the systems you can ping from?

Nope. None of the systems that the laptop can ping can ping it back. This was also seen when my friends came over for a LAN party and I attempted to use the laptop as the host... No one could connect. 2 of them were using macOS, 1 windows, and 1 linux (nixOS).

Are you able to run tcpdump on the server?

Yes, I was able to. I can't easily get you the log of the output but I can clearly see the ping making it to the server from and then the server responding to the ping. Here's what it kinda looks like:

${date} IP 192.168.1.27.65531 > 192.168.1.4.ssh: Flags [P.], seq 8065.8191, ack 110932, win 4197, optinos [nop,nopTS val 343 ecr342], langth 36
${date} IP 192.168.1.4.ssh > 192.168.1.27.65531: Flags [P.], seq 110932:110968, ack 81801, win 4197, options [nopnop,TS val 342 ecr 343]

From what I can tell, the ping is making it to the server but the server is failing to reply. Which tells me that there is something wrong with how this laptop is receiving data! We might be on to something...

nuclearkev · Other Issues

tcpdump -n -i wlan0:

# tcpdump -n -v -i wlan0
tcpdump: listening on wlan0, link-type EN10MB (Ethernet), snapshot length 262144 bytes
20:10:48.743087 IP (tos 0x0, ttl 64, id 25025, offset 0, flags [DF], proto TCP (6), length 52)
    192.168.1.17.36766 > 104.16.50.19.443: Flags [.], cksum 0x233f (correct), ack 1665082714, win 588, options [nop,nop,TS val 1363393373 ecr 1212045043], length 0
20:10:48.777528 IP (tos 0x0, ttl 57, id 35831, offset 0, flags [DF], proto TCP (6), length 52)
    104.16.50.19.443 > 192.168.1.17.36766: Flags [.], cksum 0x8700 (correct), ack 1, win 18, options [nop,nop,TS val 1212090104 ecr 1363257809], length 0
20:10:49.255596 IP (tos 0x0, ttl 57, id 60465, offset 0, flags [DF], proto TCP (6), length 112)
    172.65.251.78.443 > 192.168.1.17.47346: Flags [P.], cksum 0xed3e (correct), seq 955205532:955205592, ack 1284422278, win 18, options [nop,nop,TS val 3232343497 ecr 412434261], length 60
20:10:49.255663 IP (tos 0x0, ttl 64, id 5844, offset 0, flags [DF], proto TCP (6), length 52)
    192.168.1.17.47346 > 172.65.251.78.443: Flags [.], cksum 0xff8c (correct), ack 60, win 484, options [nop,nop,TS val 412437104 ecr 3232343497], length 0
20:10:50.790436 IP (tos 0x0, ttl 64, id 59205, offset 0, flags [DF], proto TCP (6), length 52)
    192.168.1.17.39750 > 172.65.251.78.443: Flags [.], cksum 0x19bd (correct), ack 228135339, win 529, options [nop,nop,TS val 412438639 ecr 1391551095], length 0
20:10:50.814412 IP (tos 0x0, ttl 57, id 33060, offset 0, flags [DF], proto TCP (6), length 52)
    172.65.251.78.443 > 192.168.1.17.39750: Flags [.], cksum 0xa414 (correct), ack 1, win 18, options [nop,nop,TS val 1391596149 ecr 412424215], length 0
20:10:51.727210 IP (tos 0x0, ttl 57, id 33061, offset 0, flags [DF], proto TCP (6), length 52)
    172.65.251.78.443 > 192.168.1.17.39750: Flags [.], cksum 0xa089 (correct), ack 1, win 18, options [nop,nop,TS val 1391597057 ecr 412424215], length 0
20:10:51.727266 IP (tos 0x0, ttl 64, id 59206, offset 0, flags [DF], proto TCP (6), length 52)
    192.168.1.17.39750 > 172.65.251.78.443: Flags [.], cksum 0x6615 (correct), ack 1, win 529, options [nop,nop,TS val 412439575 ecr 1391596149], length 0
20:10:51.907521 IP (tos 0x0, ttl 64, id 4838, offset 0, flags [DF], proto TCP (6), length 106)
    192.168.1.17.50164 > 100.25.231.167.443: Flags [P.], cksum 0x6f3e (correct), seq 3746156203:3746156257, ack 4139603484, win 594, options [nop,nop,TS val 1122466613 ecr 2945544234], length 54
20:10:51.938482 IP (tos 0x0, ttl 54, id 29344, offset 0, flags [DF], proto TCP (6), length 52)
    100.25.231.167.443 > 192.168.1.17.50164: Flags [.], cksum 0xaca1 (correct), ack 54, win 10, options [nop,nop,TS val 2945551923 ecr 1122466613], length 0
20:10:51.938487 IP (tos 0x0, ttl 54, id 29345, offset 0, flags [DF], proto TCP (6), length 108)
    100.25.231.167.443 > 192.168.1.17.50164: Flags [P.], cksum 0x0200 (correct), seq 1:57, ack 54, win 10, options [nop,nop,TS val 2945551923 ecr 1122466613], length 56
20:10:51.938577 IP (tos 0x0, ttl 64, id 4839, offset 0, flags [DF], proto TCP (6), length 52)
    192.168.1.17.50164 > 100.25.231.167.443: Flags [.], cksum 0xaa02 (correct), ack 57, win 594, options [nop,nop,TS val 1122466644 ecr 2945551923], length 0
20:10:52.198691 IP (tos 0x0, ttl 57, id 60466, offset 0, flags [DF], proto TCP (6), length 112)
    172.65.251.78.443 > 192.168.1.17.47346: Flags [P.], cksum 0xb705 (correct), seq 60:120, ack 1, win 18, options [nop,nop,TS val 3232346442 ecr 412437104], length 60
20:10:52.198762 IP (tos 0x0, ttl 64, id 5845, offset 0, flags [DF], proto TCP (6), length 52)
    192.168.1.17.47346 > 172.65.251.78.443: Flags [.], cksum 0xe850 (correct), ack 120, win 484, options [nop,nop,TS val 412440047 ecr 3232346442], length 0
20:10:54.886602 IP (tos 0x0, ttl 64, id 62607, offset 0, flags [DF], proto TCP (6), length 52)
    192.168.1.17.44746 > 3.142.111.40.443: Flags [.], cksum 0x6069 (correct), ack 2333624532, win 562, options [nop,nop,TS val 1813428550 ecr 1821735859], length 0
20:10:54.927044 IP (tos 0x0, ttl 54, id 47536, offset 0, flags [DF], proto TCP (6), length 52)
    3.142.111.40.443 > 192.168.1.17.44746: Flags [.], cksum 0xe769 (correct), ack 1, win 9, options [nop,nop,TS val 1821780914 ecr 1813415022], length 0
20:10:55.196061 IP (tos 0x0, ttl 57, id 60467, offset 0, flags [DF], proto TCP (6), length 112)
    172.65.251.78.443 > 192.168.1.17.47346: Flags [P.], cksum 0x0b29 (correct), seq 120:180, ack 1, win 18, options [nop,nop,TS val 3232349439 ecr 412440047], length 60
20:10:55.196140 IP (tos 0x0, ttl 64, id 5846, offset 0, flags [DF], proto TCP (6), length 52)
    192.168.1.17.47346 > 172.65.251.78.443: Flags [.], cksum 0xd0aa (correct), ack 180, win 484, options [nop,nop,TS val 412443044 ecr 3232349439], length 0
20:10:56.632241 IP (tos 0x0, ttl 64, id 17912, offset 0, flags [DF], proto ICMP (1), length 84)
    192.168.1.17 > 192.168.1.4: ICMP echo request, id 31691, seq 1, length 64
20:10:57.639033 IP (tos 0x0, ttl 64, id 18102, offset 0, flags [DF], proto ICMP (1), length 84)
    192.168.1.17 > 192.168.1.4: ICMP echo request, id 31691, seq 2, length 64
20:10:58.194712 IP (tos 0x0, ttl 57, id 60468, offset 0, flags [DF], proto TCP (6), length 112)
    172.65.251.78.443 > 192.168.1.17.47346: Flags [P.], cksum 0xe2c3 (correct), seq 180:240, ack 1, win 18, options [nop,nop,TS val 3232352439 ecr 412443044], length 60
20:10:58.194758 IP (tos 0x0, ttl 64, id 5847, offset 0, flags [DF], proto TCP (6), length 52)
    192.168.1.17.47346 > 172.65.251.78.443: Flags [.], cksum 0xb8ff (correct), ack 240, win 484, options [nop,nop,TS val 412446043 ecr 3232352439], length 0
20:10:58.304784 IP (tos 0x0, ttl 116, id 63454, offset 0, flags [DF], proto TCP (6), length 316)
    44.217.82.191.443 > 192.168.1.17.44580: Flags [P.], cksum 0xb07e (correct), seq 2230164430:2230164694, ack 2561276881, win 502, options [nop,nop,TS val 887979639 ecr 3349870077], length 264
20:10:58.307235 IP (tos 0x0, ttl 64, id 5862, offset 0, flags [DF], proto TCP (6), length 87)
    192.168.1.17.44580 > 44.217.82.191.443: Flags [P.], cksum 0x21eb (correct), seq 1:36, ack 264, win 586, options [nop,nop,TS val 3349895111 ecr 887979639], length 35
20:10:58.309945 IP (tos 0x0, ttl 64, id 5863, offset 0, flags [DF], proto TCP (6), length 189)
    192.168.1.17.44580 > 44.217.82.191.443: Flags [P.], cksum 0xe88d (correct), seq 36:173, ack 264, win 586, options [nop,nop,TS val 3349895114 ecr 887979639], length 137
20:10:58.334722 IP (tos 0x0, ttl 116, id 63455, offset 0, flags [DF], proto TCP (6), length 52)
    44.217.82.191.443 > 192.168.1.17.44580: Flags [.], cksum 0xfa39 (correct), ack 36, win 502, options [nop,nop,TS val 887979673 ecr 3349895111], length 0
20:10:58.339108 IP (tos 0x0, ttl 116, id 63456, offset 0, flags [DF], proto TCP (6), length 52)
    44.217.82.191.443 > 192.168.1.17.44580: Flags [.], cksum 0xf9a8 (correct), ack 173, win 502, options [nop,nop,TS val 887979678 ecr 3349895114], length 0
20:10:58.339108 IP (tos 0x0, ttl 116, id 63457, offset 0, flags [DF], proto TCP (6), length 386)
    44.217.82.191.443 > 192.168.1.17.44580: Flags [P.], cksum 0x13ad (correct), seq 264:598, ack 173, win 502, options [nop,nop,TS val 887979679 ecr 3349895114], length 334
20:10:58.340815 IP (tos 0x0, ttl 64, id 5864, offset 0, flags [DF], proto TCP (6), length 185)
    192.168.1.17.44580 > 44.217.82.191.443: Flags [P.], cksum 0xe742 (correct), seq 173:306, ack 598, win 586, options [nop,nop,TS val 3349895145 ecr 887979679], length 133
20:10:58.409424 IP (tos 0x0, ttl 116, id 63458, offset 0, flags [DF], proto TCP (6), length 52)
    44.217.82.191.443 > 192.168.1.17.44580: Flags [.], cksum 0xf76f (correct), ack 306, win 502, options [nop,nop,TS val 887979749 ecr 3349895145], length 0
20:10:58.663249 IP (tos 0x0, ttl 64, id 18123, offset 0, flags [DF], proto ICMP (1), length 84)
    192.168.1.17 > 192.168.1.4: ICMP echo request, id 31691, seq 3, length 64
20:10:59.687272 IP (tos 0x0, ttl 64, id 18351, offset 0, flags [DF], proto ICMP (1), length 84)
    192.168.1.17 > 192.168.1.4: ICMP echo request, id 31691, seq 4, length 64
20:11:00.711207 IP (tos 0x0, ttl 64, id 18581, offset 0, flags [DF], proto ICMP (1), length 84)
    192.168.1.17 > 192.168.1.4: ICMP echo request, id 31691, seq 5, length 64
20:11:01.031155 IP (tos 0x0, ttl 64, id 38269, offset 0, flags [DF], proto TCP (6), length 52)
    192.168.1.17.45048 > 199.38.181.93.443: Flags [.], cksum 0xe0b3 (correct), ack 1497312991, win 544, options [nop,nop,TS val 422296097 ecr 3405324441], length 0
20:11:01.031177 IP (tos 0x0, ttl 64, id 28649, offset 0, flags [DF], proto TCP (6), length 52)
    192.168.1.17.56982 > 136.243.229.210.443: Flags [.], cksum 0x0948 (correct), ack 1388748959, win 669, options [nop,nop,TS val 244205800 ecr 2818394054], length 0
20:11:01.070600 IP (tos 0x0, ttl 52, id 36605, offset 0, flags [DF], proto TCP (6), length 52)
    199.38.181.93.443 > 192.168.1.17.45048: Flags [.], cksum 0xe0ad (correct), ack 1, win 506, options [nop,nop,TS val 3405356528 ecr 422264053], length 0
20:11:01.169045 IP (tos 0x0, ttl 47, id 58448, offset 0, flags [DF], proto TCP (6), length 52)
    136.243.229.210.443 > 192.168.1.17.56982: Flags [.], cksum 0x6d37 (correct), ack 1, win 501, options [nop,nop,TS val 2818441074 ecr 244067829], length 0
20:11:01.192713 IP (tos 0x0, ttl 57, id 60469, offset 0, flags [DF], proto TCP (6), length 112)
    172.65.251.78.443 > 192.168.1.17.47346: Flags [P.], cksum 0x24a2 (correct), seq 240:300, ack 1, win 18, options [nop,nop,TS val 3232355439 ecr 412446043], length 60
20:11:01.192748 IP (tos 0x0, ttl 64, id 5848, offset 0, flags [DF], proto TCP (6), length 52)
    192.168.1.17.47346 > 172.65.251.78.443: Flags [.], cksum 0xa155 (correct), ack 300, win 484, options [nop,nop,TS val 412449041 ecr 3232355439], length 0
20:11:01.295215 IP (tos 0x0, ttl 64, id 21742, offset 0, flags [DF], proto TCP (6), length 91)
    192.168.1.17.40360 > 142.250.65.234.443: Flags [P.], cksum 0xbcfd (correct), seq 3850104891:3850104930, ack 2123159421, win 490, options [nop,nop,TS val 3931268794 ecr 3966737308], length 39
20:11:01.295366 IP (tos 0x0, ttl 64, id 21743, offset 0, flags [DF], proto TCP (6), length 76)
    192.168.1.17.40360 > 142.250.65.234.443: Flags [FP.], cksum 0xe494 (correct), seq 39:63, ack 1, win 490, options [nop,nop,TS val 3931268794 ecr 3966737308], length 24
20:11:01.341922 IP (tos 0x0, ttl 118, id 43826, offset 0, flags [none], proto TCP (6), length 52)
    142.250.65.234.443 > 192.168.1.17.40360: Flags [.], cksum 0x7987 (correct), ack 64, win 1044, options [nop,nop,TS val 3966786976 ecr 3931268794], length 0
20:11:01.341923 IP (tos 0x0, ttl 118, id 43827, offset 0, flags [none], proto TCP (6), length 52)
    142.250.65.234.443 > 192.168.1.17.40360: Flags [F.], cksum 0x7986 (correct), seq 1, ack 64, win 1044, options [nop,nop,TS val 3966786976 ecr 3931268794], length 0
20:11:01.593324 IP (tos 0x0, ttl 118, id 43828, offset 0, flags [none], proto TCP (6), length 52)
    142.250.65.234.443 > 192.168.1.17.40360: Flags [F.], cksum 0x788e (correct), seq 1, ack 64, win 1044, options [nop,nop,TS val 3966787224 ecr 3931268794], length 0
20:11:01.593386 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 52)
    192.168.1.17.40360 > 142.250.65.234.443: Flags [.], cksum 0x798e (correct), ack 2, win 490, options [nop,nop,TS val 3931269092 ecr 3966787224], length 0
20:11:01.734909 IP (tos 0x0, ttl 64, id 18586, offset 0, flags [DF], proto ICMP (1), length 84)
    192.168.1.17 > 192.168.1.4: ICMP echo request, id 31691, seq 6, length 64
20:11:01.798639 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.1.4 tell 192.168.1.17, length 28
20:11:01.801672 ARP, Ethernet (len 6), IPv4 (len 4), Reply 192.168.1.4 is-at d8:3a:dd:6d:93:f6, length 46
20:11:01.907084 IP (tos 0x0, ttl 64, id 4840, offset 0, flags [DF], proto TCP (6), length 106)
    192.168.1.17.50164 > 100.25.231.167.443: Flags [P.], cksum 0x363c (correct), seq 54:108, ack 57, win 594, options [nop,nop,TS val 1122476612 ecr 2945551923], length 54
20:11:01.938095 IP (tos 0x0, ttl 54, id 29346, offset 0, flags [DF], proto TCP (6), length 108)
    100.25.231.167.443 > 192.168.1.17.50164: Flags [P.], cksum 0x4379 (correct), seq 57:113, ack 108, win 10, options [nop,nop,TS val 2945561923 ecr 1122476612], length 56
20:11:01.938152 IP (tos 0x0, ttl 64, id 4841, offset 0, flags [DF], proto TCP (6), length 52)
    192.168.1.17.50164 > 100.25.231.167.443: Flags [.], cksum 0x5b75 (correct), ack 113, win 594, options [nop,nop,TS val 1122476643 ecr 2945561923], length 0
20:11:02.055096 IP (tos 0x0, ttl 64, id 64519, offset 0, flags [DF], proto TCP (6), length 52)
    192.168.1.17.57298 > 54.161.152.147.443: Flags [.], cksum 0xd83d (correct), ack 123684684, win 569, options [nop,nop,TS val 2710411598 ecr 2034596087], length 0
20:11:02.086265 IP (tos 0x0, ttl 55, id 25475, offset 0, flags [DF], proto TCP (6), length 52)
    54.161.152.147.443 > 192.168.1.17.57298: Flags [.], cksum 0xc4b2 (correct), ack 1, win 442, options [nop,nop,TS val 2034626294 ecr 2710320985], length 0
20:11:02.759217 IP (tos 0x0, ttl 64, id 18780, offset 0, flags [DF], proto ICMP (1), length 84)
    192.168.1.17 > 192.168.1.4: ICMP echo request, id 31691, seq 7, length 64
20:11:03.079137 IP (tos 0x0, ttl 64, id 889, offset 0, flags [DF], proto TCP (6), length 52)
    192.168.1.17.55828 > 104.16.51.19.443: Flags [.], cksum 0x38eb (correct), ack 2534177017, win 633, options [nop,nop,TS val 842729842 ecr 960225257], length 0
20:11:03.106880 IP (tos 0x0, ttl 57, id 64820, offset 0, flags [DF], proto TCP (6), length 52)
    104.16.51.19.443 > 192.168.1.17.55828: Flags [.], cksum 0x4bfb (correct), ack 1, win 17, options [nop,nop,TS val 960270314 ecr 842549450], length 0
20:11:03.782955 IP (tos 0x0, ttl 64, id 18865, offset 0, flags [DF], proto ICMP (1), length 84)
    192.168.1.17 > 192.168.1.4: ICMP echo request, id 31691, seq 8, length 64
20:11:04.190508 IP (tos 0x0, ttl 57, id 60470, offset 0, flags [DF], proto TCP (6), length 112)
    172.65.251.78.443 > 192.168.1.17.47346: Flags [P.], cksum 0x3a58 (correct), seq 300:360, ack 1, win 18, options [nop,nop,TS val 3232358435 ecr 412449041], length 60
20:11:04.190574 IP (tos 0x0, ttl 64, id 5849, offset 0, flags [DF], proto TCP (6), length 52)
    192.168.1.17.47346 > 172.65.251.78.443: Flags [.], cksum 0x89af (correct), ack 360, win 484, options [nop,nop,TS val 412452039 ecr 3232358435], length 0
20:11:04.199871 IP (tos 0x0, ttl 64, id 4842, offset 0, flags [DF], proto TCP (6), length 108)
    192.168.1.17.50164 > 100.25.231.167.443: Flags [P.], cksum 0x475a (correct), seq 108:164, ack 113, win 594, options [nop,nop,TS val 1122478905 ecr 2945561923], length 56
20:11:04.267768 IP (tos 0x0, ttl 54, id 29347, offset 0, flags [DF], proto TCP (6), length 52)
    100.25.231.167.443 > 192.168.1.17.50164: Flags [.], cksum 0x4b95 (correct), ack 164, win 10, options [nop,nop,TS val 2945564253 ecr 1122478905], length 0
20:11:04.806976 IP (tos 0x0, ttl 64, id 18981, offset 0, flags [DF], proto ICMP (1), length 84)
    192.168.1.17 > 192.168.1.4: ICMP echo request, id 31691, seq 9, length 64
20:11:05.831165 IP (tos 0x0, ttl 64, id 19237, offset 0, flags [DF], proto ICMP (1), length 84)
    192.168.1.17 > 192.168.1.4: ICMP echo request, id 31691, seq 10, length 64
20:11:06.855179 IP (tos 0x0, ttl 64, id 19340, offset 0, flags [DF], proto ICMP (1), length 84)
    192.168.1.17 > 192.168.1.4: ICMP echo request, id 31691, seq 11, length 64
20:11:07.086573 IP (tos 0x0, ttl 57, id 33062, offset 0, flags [DF], proto TCP (6), length 52)
    172.65.251.78.443 > 192.168.1.17.39750: Flags [.], cksum 0x2889 (correct), ack 1, win 18, options [nop,nop,TS val 1391612417 ecr 412439575], length 0
20:11:07.086626 IP (tos 0x0, ttl 64, id 59207, offset 0, flags [DF], proto TCP (6), length 52)
    192.168.1.17.39750 > 172.65.251.78.443: Flags [.], cksum 0x2a15 (correct), ack 1, win 529, options [nop,nop,TS val 412454935 ecr 1391596149], length 0
20:11:07.174680 IP (tos 0x0, ttl 64, id 52447, offset 0, flags [DF], proto TCP (6), length 52)
    192.168.1.17.49234 > 44.205.171.153.443: Flags [.], cksum 0x8a89 (correct), ack 3026662997, win 614, options [nop,nop,TS val 3566144646 ecr 1673664397], length 0
20:11:07.190730 IP (tos 0x0, ttl 57, id 60471, offset 0, flags [DF], proto TCP (6), length 112)
    172.65.251.78.443 > 192.168.1.17.47346: Flags [P.], cksum 0xf561 (correct), seq 360:420, ack 1, win 18, options [nop,nop,TS val 3232361437 ecr 412452039], length 60
20:11:07.190775 IP (tos 0x0, ttl 64, id 5850, offset 0, flags [DF], proto TCP (6), length 52)
    192.168.1.17.47346 > 172.65.251.78.443: Flags [.], cksum 0x7201 (correct), ack 420, win 484, options [nop,nop,TS val 412455039 ecr 3232361437], length 0
20:11:07.210311 IP (tos 0x0, ttl 54, id 2663, offset 0, flags [DF], proto TCP (6), length 52)
    44.205.171.153.443 > 192.168.1.17.49234: Flags [.], cksum 0x9f60 (correct), ack 1, win 11, options [nop,nop,TS val 1673709451 ecr 3565963789], length 0
20:11:07.879252 IP (tos 0x0, ttl 64, id 19516, offset 0, flags [DF], proto ICMP (1), length 84)
    192.168.1.17 > 192.168.1.4: ICMP echo request, id 31691, seq 12, length 64
20:11:08.902989 IP (tos 0x0, ttl 64, id 19702, offset 0, flags [DF], proto ICMP (1), length 84)
    192.168.1.17 > 192.168.1.4: ICMP echo request, id 31691, seq 13, length 64
^C
72 packets captured
72 packets received by filter
0 packets dropped by kernel

The router is a Netgear ORBI32, firmware version 7.2.7.15_5.1.16. I don't really think it's the router because the IP of the laptop has changed over the many days I've looked into this. Originally I was 192.168.1.20, then 6, and now 17. Unless there is something doing it based on MAC address.

EDIT: the server's address is 192.168.1.4

EDIT 2: The number of connected devices isn't the problem either. If I boot into a liveCD of another distro (in my case I used gentoo), I can ping the server and I can be pinged no issue.

nuclearkev · Other Issues

How are the systems connected to your network? Please answer for both the laptop and the server,

17 devices are on the network. The laptop and server are on the same network. The home server doesn't currently have any active connections as it's used for backups and streaming mostly. Neither are being used at the moment.

If any systems are connected wirelessly check they are connected to *your* router, not one belonging to a neightbour. That has been known.

Yes, they're on the same network. In other words, I can ping most devices on the network. Only the few mentioned can't be ping by the laptop only. From what I can tell, no one on the network can ping the laptop either.

If the laptop also has an ethernet port try connecting it to your router with an ethernet cable.

Sadly, it doesn't. I don't have a USB-ethernet cable either.

Sorry for missing these earlier!

EDIT: missed some info

nuclearkev · Other Issues

No problem pingging:

# ping -n 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=23.0 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=20.9 ms

ebtables-save returns nothing.

There are no shared ethernet addresses on my router from what I can tell,

nuclearkev · Other Issues

Oddly enough, if I attempt to remove the bridge with brctl delbr it claims that the bridge doesn't exist...

nuclearkev · Other Issues

Yeah, no virtual machines involved.

ifconfig virtbr0:

# ifconfig virtbr0
virtbr0: error fetching interface information: Device not found

brctl show:

# brctl show
bridge name     bridge id               STP enabled     interfaces
virbr0          8000.5254001b4e3b       yes

nuclearkev · Other Issues

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

nuclearkev · Other Issues

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.

nuclearkev · Other Issues

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.

nuclearkev · Other Issues

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

The officially official Devuan Forum!

#1 Re: Other Issues » Unable to connect to devuan laptop server on local network » 2025-07-08 13:02:47

#2 Re: Other Issues » Unable to connect to devuan laptop server on local network » 2025-07-07 13:29:33

#3 Re: Other Issues » Unable to connect to devuan laptop server on local network » 2025-07-07 01:35:52

#4 Re: Other Issues » Unable to connect to devuan laptop server on local network » 2025-07-07 00:35:01

#5 Re: Other Issues » Unable to connect to devuan laptop server on local network » 2025-07-06 02:08:47

#6 Re: Other Issues » Unable to connect to devuan laptop server on local network » 2025-07-06 00:29:00

#7 Re: Other Issues » Unable to connect to devuan laptop server on local network » 2025-07-05 00:14:32

#8 Re: Other Issues » Unable to connect to devuan laptop server on local network » 2025-07-04 16:26:42

#9 Re: Other Issues » Unable to connect to devuan laptop server on local network » 2025-07-04 15:29:02

#10 Re: Other Issues » Unable to connect to devuan laptop server on local network » 2025-07-04 13:32:31

#11 Re: Other Issues » Unable to connect to devuan laptop server on local network » 2025-07-04 13:31:02

#12 Re: Other Issues » Unable to connect to devuan laptop server on local network » 2025-07-04 02:08:17

#13 Re: Other Issues » Unable to connect to devuan laptop server on local network » 2025-07-03 17:06:33

#14 Re: Other Issues » Unable to connect to devuan laptop server on local network » 2025-07-03 14:13:12

#15 Other Issues » Unable to connect to devuan laptop server on local network » 2025-07-02 19:27:26

Board footer