sorry if this is the wrong place to post this.

Recently i switched to steam os on my pc, installed battle net and everything went smoothly. I played in beta and i dont have issue but when i play on live my ping would shoot to 1000 to 4000. and it only smooth on the first 10 minutes or so. I dont know what else i should do so any help is appreciated.

things i tried

restarting.

Im using starlink so i tried to relocate the dish.

turning off firewall in my asus modem

turning off firewall in my pc

turning on and off qos

turning on and off ipv6

changing poton

I tried several ping checker and in my browser everything seem normal

  • Jo Miran@lemmy.mlEnglish
    2·
    2 hours ago

    Have you figured out how to reach the Linux desktop yet? Once you do, all you need to do is open a terminal and type

    tracert <your_wow_server_address>
    • wopalopa@lemmy.worldOPEnglish
      1·
      1 hour ago

      whats the difference between this and ping? i tried ping and it showed normal ms.

      I’m still figuring out how to install trace because right now it says something about my pgp signsture is corrupted, so still working on that

      • Jo Miran@lemmy.mlEnglish
        1·
        56 minutes ago

        I am not sure what you are doing but you should not have to install tracert/traceroute as it is in the same utility family as ping.

        Ping tells you the response time between you and your end point. Tracert outputs the response information of every hop along the way to your end point. It helps you pinpoint where the failure is along the way.

        • ikidd@lemmy.dbzer0.comEnglish
          3·
          36 minutes ago

          traceroute is a separate package from iputils on Arch.

          tracepath would be included though. mtr is better than both for tracking down packet loss.

          • Jo Miran@lemmy.mlEnglish
            2·
            34 minutes ago

            This is just a guess, but turnoff ipv6 and try running the game that way. It might be a network issue rather than a Linux compatibility issue.