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
    ·
    21 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
      3
      ·
      21 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
        ·
        20 hours 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
          3
          ·
          20 hours 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
            6
            ·
            19 hours 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 hours 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
        ·
        21 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
          3
          ·
          edit-2
          18 hours ago

          SteamOS 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

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

            thank you so much for the detailed guide.

            i tried traceroute 1.1.1.1, i dont think i see any weird thing.

            but when i do traceroute the wow server it suddenly stop midway and displaying *** until it stopped

            • BCOVertigo@piefed.world
              link
              fedilink
              English
              arrow-up
              3
              ·
              18 hours ago

              If you can traceroute to some unrelated cloudflare dns server like 1.1.1.1, then the problem seems likely to be outside your machine, outside your home network, and then we scrutinize what hop it’s failing at to see if we can rule things out further. (I’m making assumptions obviously, this is just how I’d think about it.)

              Maybe that’s your ISP, or something in a data center with a hostname related to wow itself?

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

                i tried the mtr thing, is it okay for me to show it? it looks like there some kind of problem after it hopped outside of the country (im assuming because i see singapore and japan) the rest is ips that im not sure what it is or how to check where is it

                just to be sure i tried using different network (thethering from my phone) and still same result

                • BCOVertigo@piefed.world
                  link
                  fedilink
                  English
                  arrow-up
                  2
                  ·
                  17 hours ago

                  What traceroute and mtr have told us is that ICMP echo requests (called a ping) don’t get there reliably, but that can happen for multiple reasons. Maybe a server along the path doesn’t feel like passing your ping along and drops it. There’s a point in their machinery which blizzard doesn’t want you peeking past, and other companies might have their own reasons even if the route is healthy.

                  A friend says the game has two network sockets that have individual pings (latency measure this time not echo) and you can see them by hovering your mouse over the indicator. Which is it that’s misbehaving?

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

                    i see, so there is a chance that something is wrong with my machine or isp that makes them do that?

                    i do tried tethering from my phone, same result.

                    yeah it has home and world ping. iirc home handle about chat stuff and world is character stuff. both has high ping. sometimes one is wildly higher than the other sometimes both