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

  • wopalopa@lemmy.worldOP
    link
    fedilink
    English
    arrow-up
    3
    ·
    2 hours ago

    sorry im linux noob, how to do traceroute?

    I’m on steamos. so i think its arch based

    • Jo Miran@lemmy.ml
      link
      fedilink
      English
      arrow-up
      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.worldOP
        link
        fedilink
        English
        arrow-up
        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.ml
          link
          fedilink
          English
          arrow-up
          1
          ·
          42 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.com
            link
            fedilink
            English
            arrow-up
            3
            ·
            22 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.ml
              link
              fedilink
              English
              arrow-up
              2
              ·
              19 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.

      • wopalopa@lemmy.worldOP
        link
        fedilink
        English
        arrow-up
        2
        ·
        2 hours ago

        so is it like a program? i tried to install it but i cant because apparently steamos is read only.

        then i disable it, then it asked something something keyring, i did some key init thing, and retry installing traceroute. it said something about import pgp key and its been like that for a bit now.

        • BCOVertigo@piefed.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          16 minutes ago

          Steam is an immutable OS so many changes will be overwritten at your next update, but you can always pull a tool down temporarily, or keep a script saved on your desktop!

          Pop the hood open

          sudo steamos-readonly disable Pacman is a package manager you’ll have on steamos/arch. Refresh pacman keys and resync database. sudo pacman-key --init

          sudo pacman-key --populate

          sudo pacman -Syy Install the tool you want (traceroute) sudo pacman -S traceroute Close it up again until your next change sudo steamos-readonly enable

          Once you’re in a position to use traceroute you can just follow it with an IP or a domain.

          traceroute 1.1.1.1

          It will check each step (hop) along the networking path path between you and that target with details like the round trip time a message took to go there and back to you. Look for a hop where the latency gets bad and stays that way for the rest if the hops like a clog in a pipe. If you don’t see that you’ll probably want to examine with some other tools like mtr that go into more depth. https://man.archlinux.org/man/mtr.8.en