Steamos cant ping

[apoyusiken]

So i can connect to internet and no real problems but should i fix it? I can ping local devices but no remote ips. My dns conf was smt like 127.1.0.53, i changed it to 8.8.8.8 and i tried some stuff but no luck.

[Needfuldoer]

Make sure your default gateway and netmask are set properly. Gateway should be your router's IP address, and if your network is like almost everyone else's then your netmask should be 255.255.255.0 (or /24 in that nomenclature). Without that, your PC won't be able to reach outside its local subnet.

 

Honestly, just turn on DHCP and leave it on. It's easier to let the router figure out addresses by itself.

[apoyusiken]

10 minutes ago, Needfuldoer said:

Make sure your default gateway and netmask are set properly. Gateway should be your router's IP address, and if your network is like almost everyone else's then your netmask should be 255.255.255.0 (or /24 in that nomenclature). Without that, your PC won't be able to reach outside its local subnet.

 

Honestly, just turn on DHCP and leave it on. It's easier to let the router figure out addresses by itself.

yea so im connected to a router with dhcp off which is connected to a modem with dhcp on

[Needfuldoer]

5 minutes ago, apoyusiken said:

yea so im connected to a router with dhcp off which is connected to a modem with dhcp on

No, on your client device running SteamOS. If it has DHCP enabled then it should "just work" and get all the IP settings it needs.

 

Make sure your device running SteamOS has a valid default gateway and netmask (subnet mask) set.

[apoyusiken]

2 hours ago, Needfuldoer said:

No, on your client device running SteamOS. If it has DHCP enabled then it should "just work" and get all the IP settings it needs.

 

Make sure your device running SteamOS has a valid default gateway and netmask (subnet mask) set.

well idk abt that but i just use a static ip and it has subnet and stuff

[Needfuldoer]

12 minutes ago, apoyusiken said:

well idk abt that but i just use a static ip and it has subnet and stuff

There's your problem.

 

Use DHCP on your SteamOS machine.

[apoyusiken]

27 minutes ago, Needfuldoer said:

There's your problem.

 

Use DHCP on your SteamOS machine.

but i tried auto ip too and no luck. 

[Nayr438]

I am assuming you edited "/etc/resolv.conf". 127.0.0.53 normally points to systemd-resolved and this file should be overwritten when resolved gets restarted.

you can check this by running "ls -l /etc/resolv.conf" which probably symlinks to "/run/systemd/resolve/stub-resolv.conf" and checking "systemctl status system-resolved"
If this is the case you can view your current dns information with "resolvectl status"

 

If you are using NetworkManager you can define the DNS in it's network config, alternatively if the directory is editable you can define a dns dropin file, https://wiki.archlinux.org/title/Systemd-resolved#Manually and restart systemd-resolved. "systemctl restart systemd-resolved"

 

I'm not familiar with SteamOS so I am not sure what gets exposed, to my understanding it does ship KDE Plasma which means you should be able to define the DNS in System Settings -> Networking.

[apoyusiken]

1 hour ago, Nayr438 said:

I am assuming you edited "/etc/resolv.conf". 127.0.0.53 normally points to systemd-resolved and this file should be overwritten when resolved gets restarted.

you can check this by running "ls -l /etc/resolv.conf" which probably symlinks to "/run/systemd/resolve/stub-resolv.conf" and checking "systemctl status system-resolved"
If this is the case you can view your current dns information with "resolvectl status"

 

If you are using NetworkManager you can define the DNS in it's network config, alternatively if the directory is editable you can define a dns dropin file, https://wiki.archlinux.org/title/Systemd-resolved#Manually and restart systemd-resolved. "systemctl restart systemd-resolved"

 

I'm not familiar with SteamOS so I am not sure what gets exposed, to my understanding it does ship KDE Plasma which means you should be able to define the DNS in System Settings -> Networking.

so the problem is it couldnt resolve dns, deeper than resolv.conf. thx it explains some stuff.

 

I will try your suggestions but my main question is should i fix this at all? so far its not causing any problems as far as i see but you never know