The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
The Guiding Principles and New Rules document is now in effect.

Networking Madness...

buzzard0627buzzard0627 Registered User regular
edited April 2008 in Help / Advice Forum
So due to one of my cats chewing fetish, I have had to go wireless as much as possible in my home. Since then, my latency has jumped a bit (mainly noticeable when playing WoW). I would like it to drop back down, but I have to stay wireless. Here are the technical details:

Network Setup:
I have ATT Uverse (love it btw). Everything originates at their box which doubles as my wireless gateway (802.11n). I have a cable box hardwired into the router via ethernet. On the other side of the apartment, I have a wireless bridge connected to a router at my desk that connects another cable box and my desktop to the network. I have connectivity on everything just fine.

Any ideas as to what I could do differently to boost my network performance? I am considering just going wireless from the pc directly, but I hesitant to spend the cash unless i know it will help. The cable box near my desk has to be hardwired either coax or ethernet cable.

Thanks

buzzard0627 on

Posts

  • ScrubletScrublet Registered User regular
    edited April 2008
    Solution: Get rid of the cat.

    Seriously though, I'm confused about the need for a bridge and two routers. If you could condense that all into one router you'd probably see some improvements.

    Scrublet on
    subedii wrote: »
    I hear PC gaming is huge off the coast of Somalia right now.

    PSN: TheScrublet
  • buzzard0627buzzard0627 Registered User regular
    edited April 2008
    The bridge only has 1 ethernet port on it so i used an old router to plug it into that. It isn't doing true routing, just acting like a switch. When I plugged directly into the bridge with the PC, I did not see any improvements, so the "switch" is not the issue.

    buzzard0627 on
  • PirateJonPirateJon Registered User regular
    edited April 2008
    Ping the wireless gateway from the WoW box. What's the ping time? It should be under 4 or 5 ms.

    PirateJon on
    all perfectionists are mediocre in their own eyes
  • TofystedethTofystedeth Registered User regular
    edited April 2008
    Raise your stuff off the floor, and run your cables along walls and door frames?

    Tofystedeth on
    steam_sig.png
  • buzzard0627buzzard0627 Registered User regular
    edited April 2008
    I will check the ping to the gateway when I get home.

    Can't really raise it off the floor - I'd have to run it along the ceiling and I would be in the same boat I was before. The cable I had before was run under the carpet and it was chewed at the exit point.

    buzzard0627 on
  • amateurhouramateurhour One day I'll be professionalhour The woods somewhere in TennesseeRegistered User regular
    edited April 2008
    I don't know about cats, but sprinkling a little cayenne pepper or some vet reccomended solution on the cable ends usually stops the chewing problem for dogs, along with some catnip toys and disciplinary measures (for the cat).

    I'm assuming you've tried all of that though

    amateurhour on
    are YOU on the beer list?
  • DrFrylockDrFrylock Registered User regular
    edited April 2008
    What kind of bridge is it?

    DrFrylock on
  • buzzard0627buzzard0627 Registered User regular
    edited April 2008
    It is a WGA600N. It was about the only thing I could find for 802.11n that wasn't too overpriced.

    buzzard0627 on
  • buzzard0627buzzard0627 Registered User regular
    edited April 2008
    Pinged the gateway:
    Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
    Reply from 192.168.1.254: bytes=32 time=2ms TTL=255
    Reply from 192.168.1.254: bytes=32 time=1ms TTL=255
    Reply from 192.168.1.254: bytes=32 time=1ms TTL=255
    Reply from 192.168.1.254: bytes=32 time=1ms TTL=255
    Reply from 192.168.1.254: bytes=32 time=1ms TTL=255
    Reply from 192.168.1.254: bytes=32 time=1ms TTL=255
    Reply from 192.168.1.254: bytes=32 time=1ms TTL=255
    Reply from 192.168.1.254: bytes=32 time=1ms TTL=255
    Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
    Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
    Reply from 192.168.1.254: bytes=32 time=1ms TTL=255
    Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
    Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
    Reply from 192.168.1.254: bytes=32 time<1ms TTL=255
    Reply from 192.168.1.254: bytes=32 time<1ms TTL=255

    judging from that I am assuming that it's not the bridge, correct?

    buzzard0627 on
  • DrFrylockDrFrylock Registered User regular
    edited April 2008
    Run some traceroutes to the servers to which you have high latency and see where the latency picks up.

    DrFrylock on
Sign In or Register to comment.