Network weirdness with supernetted class C in prvate space.

CescoAiel

New member
Joined
Apr 11, 2023
Messages
2
I have a weirdness on the Steam Deck networking side I cannot explain. I am well versed in IP (and ICMP/TCP/UDP), networking (all OSI layers) and OSs (Windows, MacOS and misc Linuxes), but this one has me stumped...

My network is a subnet of the 10.0.0.0 Class A, but relativey speaking a supernetted Class C inside it.
For example (actual IPs are different, but this is adequate for demonstrating the issue)

Subnet: 10.10.164.0/23
Def GW: 10.10.164.254 (/23)
Steam Deck: 10.10.165.56 (/23)
DNS: 10.10.164.254

The Steam Deck can ping the whole subnet range, but can ony access over TCP the /24 subnet it's IP is in, so:
Ping 10.10.164.6 works, ssh 10.10.164.6 doesn't nor does https://10.10.164.6
Ping 10.10.165.55 works, as do ssh 10.10.165.55 and https://10.10.165.55
And (to add on to the confusion):
Ping 10.10.164.254 works, as do ssh 10.10.164.254 and https://10.10.164.254 (DNS lookups work as well!)

All other devices with IPs in the 10.10.165.0-254 range work fine and communicate with all other devices, wether they have a 10.10.164.x or 10.10.165.x address.

There are no firewall internally, only on the perimeter. Nor are there firewall on the hosts I am trying to reach, and as noted, other devices, regardless of IP, can successfully communicate.

It looks as if the Steam Deck is treating the network as if it has a /24 subnet address.

Any suggestions welcome!
 
Top Bottom