exec
exec
PostsComments
UBUniversal Blue
Created by exec on 4/30/2025 in #🛟bazzite-help
Bazzite losing/dropping received packets to local networks that ubuntu wasn't?
So I recently swapped from Ubuntu to Bazzite (mostly because of snap finally enraging me for the last time). However, one thing I've been noticing is that for some reason Bazzite has been dropping packets- a lot of packets- received from some, but not all, local addresses. I THINK it might be a problem with how it's trying to route things, but I can't be sure, hence my question here. We have 4 devices in our network (there's a lot more than that, but this is a minimal example)- a router (192.168.1.1), our PC (192.168.1.244) and our destination address, a docker/portainer server (192.168.4.0/24, with the portainer server itself as 192.168.4.1/32) Pings from the PC to the router work fine, and vice versa. Pings from docker server to the router and PC work fine. But pings, ssh, and all general traffic from the PC to the docker server (and everything within it) are weird. If I set up a TCPdump on both the PC and the docker server, I can see my packets going out from the PC, received by the server, and the server responding. However, the TCPdump on the PC never sees the responding packets. I THINK there's a weird routing bug here- route -n gives: 
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.1     0.0.0.0         UG    100    0        0 enp6s0
192.168.1.0     0.0.0.0         255.255.255.0   U     100    0        0 enp6s0
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.1     0.0.0.0         UG    100    0        0 enp6s0
192.168.1.0     0.0.0.0         255.255.255.0   U     100    0        0 enp6s0
Is it trying to route anything that is 192.168.0.0/16 EXCEPT 192.168.1.0/24 over the router and then ditching the results because it's coming back not through the router or something? Even more interesting, a ping from the PC to the docker server has 100% packet loss... right up until it shows this sort of message:
580 replies