Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie

Prob with gaming on 2meg IBB with perfect pings

  • 26-06-2005 6:36pm
    #1
    jesus_thats_gre
    Registered Users, Registered Users 2 Posts: 17,441 ✭✭✭✭


    Hi Lads

    This is pissing me off like no other but its hard to prove..

    I am experiencing problems with packet loss and choke when playing online games. Specifically CS: Source..

    I play mainly on the IOA server, 82.138.226.130, and my ping times are pretty much perfect. See below:

    C:\Documents and Settings\Luke>ping 82.138.226.130 -n 100

    Pinging 82.138.226.130 with 32 bytes of data:

    Reply from 82.138.226.130: bytes=32 time=24ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=24ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=27ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=21ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=25ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=26ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=25ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=24ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=24ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=24ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=23ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=26ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=25ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=29ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=25ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=24ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=29ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=22ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=26ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=27ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=24ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=24ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=26ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=25ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=24ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=26ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=22ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=25ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=27ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=25ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=27ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=28ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=24ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=26ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=27ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=25ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=25ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=27ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=24ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=27ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=27ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=26ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=28ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=25ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=27ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=24ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=25ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=26ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=28ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=24ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=25ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=27ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=26ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=25ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=25ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=24ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=24ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=27ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=26ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=23ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=26ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=25ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=27ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=26ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=30ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=22ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=23ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=22ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=24ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=22ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=24ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=26ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=26ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=25ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=24ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=28ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=24ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=24ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=26ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=25ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=22ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=25ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=24ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=25ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=27ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=24ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=23ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=26ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=22ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=23ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=24ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=22ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=23ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=24ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=23ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=21ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=25ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=23ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=23ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=25ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=25ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=24ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=25ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=26ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=26ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=24ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=24ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=27ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=25ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=22ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=26ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=22ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=23ms TTL=120
    Reply from 82.138.226.130: bytes=32 time=21ms TTL=120

    Ping statistics for 82.138.226.130:
    Packets: Sent = 114, Received = 114, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 21ms, Maximum = 30ms, Average = 24ms




    Now as you can see, when I do a ping test through DOS there is no packet loss at all.. However, when I am playing CS and have the net graph enabled, I can see conserable packet loss and choke..

    See attached screenshots showing loss and choke..

    My rates in CS are default.. So I dont have a clue how to prove it to IBB...


    Is there any Ping Monitor that will ping an IP more than once a second, i.e. at a similar rate to what CS would?


Comments

  • #2
    Simi
    Registered Users, Registered Users 2 Posts: 1,874 ✭✭✭Simi


    Is this actually affecting gameplay or is it just annoying u to see packet loss? TBH unless its 100times worse than what u have in the screenshots then u have nothing to complain about.


  • #3
    juliuspret
    Closed Accounts Posts: 458 ✭✭juliuspret


    jesus_thats_gre

    What CPU/GFX Card have you as those FPS numbers are pretty high?


  • #4
    Sparky
    Registered Users, Registered Users 2 Posts: 22,231 ✭✭✭✭Sparky


    juliuspret wrote:
    jesus_thats_gre

    What CPU/GFX Card have you as those FPS numbers are pretty high?

    I think i may be using his inspiron XPS


  • #5
    jesus_thats_gre
    Registered Users, Registered Users 2 Posts: 17,441 ✭✭✭✭jesus_thats_gre


    Using a 2.0 GHz Centrino, 2 GB Ram and a 6800 Ultra...

    Its causing me to warp all over the shop... Its totally ****ing up BF2..

    If it didnt affect gameply i wouldnt care.


  • #6
    angelofdeath
    Closed Accounts Posts: 2,148 ✭✭✭angelofdeath


    try changing your rates, rate 18000, cl_updaterate 80, cl_cmdrate 80


  • Advertisement
  • #7
    jesus_thats_gre
    Registered Users, Registered Users 2 Posts: 17,441 ✭✭✭✭jesus_thats_gre


    I tried with with that and its worse to be honest..

    The level basically shudders as i move.. as if it was a bad frame rate but i am hitting near 100fps..


  • #8
    jesus_thats_gre
    Registered Users, Registered Users 2 Posts: 17,441 ✭✭✭✭jesus_thats_gre


    Actually seems to have eased. WIll keep an eye on it..


  • #9
    elexes
    Registered Users, Registered Users 2 Posts: 4,471 ✭✭✭elexes


    jesus_thats_gre wrote:
    Actually seems to have eased. WIll keep an eye on it..


    rate 17000 60 60

    works a treat for me


  • #10
    Mutant_Fruit
    Closed Accounts Posts: 4,943 ✭✭✭Mutant_Fruit


    Dos pings are fine, so it isn't a latency related issue. You have no packetloss... so thats not it.

    Are you playing over a wireless link? Also, as for rates, try something not so high.... rate 20000, cl_updaterate 35, cl_cmdrate 35. an extremely high updaterates can pose problems if you have limited upload speed... but not if you have IBB.

    TBH it sounds much more like a server issue than an IBB issue. Try different servers to see if they experience the same issues.

    Have you changed your MTU settings recently, or applied any TCP/IP tweakers/optimisers? IF you have ever used em, undo their changes.


  • #11
    Steffano2002
    Registered Users, Registered Users 2 Posts: 5,918 ✭✭✭Steffano2002


    I have similar problems with Call of Duty but I think in my case it is due to my crappy IBB connection.

    Here's a ping test of my CoD server in France:

    C:\Documents and Settings\Stéphane>ping 85.12.140.120 -n 100

    Pinging 85.12.140.120 with 32 bytes of data:

    Reply from 85.12.140.120: bytes=32 time=101ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=23ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=29ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=28ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=31ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=41ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=27ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=25ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=67ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=22ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=24ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=25ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=24ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=67ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=171ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=22ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=25ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=23ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=27ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=54ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=46ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=22ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=21ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=71ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=73ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=42ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=22ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=23ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=23ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=23ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=22ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=129ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=26ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=29ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=101ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=23ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=23ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=21ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=25ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=22ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=37ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=59ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=25ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=28ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=43ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=31ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=22ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=24ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=24ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=24ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=31ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=25ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=22ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=33ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=26ms TTL=53
    Request timed out.
    Reply from 85.12.140.120: bytes=32 time=28ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=146ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=25ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=33ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=80ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=22ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=26ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=22ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=28ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=27ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=39ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=25ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=23ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=23ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=24ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=21ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=23ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=23ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=25ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=22ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=23ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=24ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=24ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=22ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=24ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=27ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=25ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=22ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=24ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=26ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=27ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=24ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=38ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=25ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=44ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=28ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=41ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=24ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=27ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=26ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=26ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=32ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=26ms TTL=53
    Reply from 85.12.140.120: bytes=32 time=25ms TTL=53

    Ping statistics for 85.12.140.120:
    Packets: Sent = 100, Received = 99, Lost = 1 (1% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 21ms, Maximum = 171ms, Average = 34ms

    I actually had to turn off my lagometer as playing with it and seeing the amount of packets lost was making me sick...

    Do any of you know of any commands/settings I could use to imrpove on the above pings? Here's what I'm playing with at the moment:

    /cl_maxpackets 100
    /snaps 40
    /rate 12500

    Thank you in advance for your help! ;)


  • Advertisement
  • #12
    jesus_thats_gre
    Registered Users, Registered Users 2 Posts: 17,441 ✭✭✭✭jesus_thats_gre


    I want a ping tester that will send and rec as many packets per second as CS would.. Sending 1 packet a second through DOS does for 200 minutes is the equivelent of a second in CS.. So 1 packet missing i DOS in 2 minutes is 1 a second in CS.. This is not good..


  • #13
    jesus_thats_gre
    Registered Users, Registered Users 2 Posts: 17,441 ✭✭✭✭jesus_thats_gre


    Mutant_Fruit wrote:
    Dos pings are fine, so it isn't a latency related issue. You have no packetloss... so thats not it.

    Are you playing over a wireless link? Also, as for rates, try something not so high.... rate 20000, cl_updaterate 35, cl_cmdrate 35. an extremely high updaterates can pose problems if you have limited upload speed... but not if you have IBB.

    TBH it sounds much more like a server issue than an IBB issue. Try different servers to see if they experience the same issues.

    Have you changed your MTU settings recently, or applied any TCP/IP tweakers/optimisers? IF you have ever used em, undo their changes.


    It happens on all servers in all games....

    Happens regardless of rates I have. With 2mb up and down I should not be getting choke. I have not changed any TCP settings.


  • #14
    Mutant_Fruit
    Closed Accounts Posts: 4,943 ✭✭✭Mutant_Fruit


    Get ping plotter. Set it to ping boards.ie.

    It'll then send a ping packet to each hop on the way to boards.ie, thus allowing you to see exctly where the prob is.


  • #15
    Steffano2002
    Registered Users, Registered Users 2 Posts: 5,918 ✭✭✭Steffano2002


    Mutant_Fruit wrote:
    Get ping plotter. Set it to ping boards.ie.

    It'll then send a ping packet to each hop on the way to boards.ie, thus allowing you to see exctly where the prob is.

    Ping Plotter is very good indeed Mutant! Thanks a million! ;)

    I downloaded it and tried it here at work and I'll be doing the same this evening at home to see where my IBB connection is bugging.

    Thanks again!


  • #16
    jesus_thats_gre
    Registered Users, Registered Users 2 Posts: 17,441 ✭✭✭✭jesus_thats_gre


    Can you set it to send multiple requests per second, i.e. something similar to the traffic that CS would create..


  • #17
    Mutant_Fruit
    Closed Accounts Posts: 4,943 ✭✭✭Mutant_Fruit


    As far as i know it can only send one packet per hop per second. (i.e. each hop on the way to the destination will recieve a ping packet every second).

    If theres' 7 hops, there will be 7 packets sent per second.

    EDIT: I'm getting packetloss from:
    hosting365. IPs: 82.195.128.1 (1% loss), 82.195.128.7 (3% loss)
    boards.ie (2% loss)
    IBB: all fine up til their router to the net, at 62.231.52.157 (1% loss).


  • #18
    jesus_thats_gre
    Registered Users, Registered Users 2 Posts: 17,441 ✭✭✭✭jesus_thats_gre


    hmmmm will have to have a nosey with that app and see what I can find so.. thanks dawg..


  • #19
    jesus_thats_gre
    Registered Users, Registered Users 2 Posts: 17,441 ✭✭✭✭jesus_thats_gre


    I finally got around to giving ping plotter a go and have got some interesting results...


    I got it to keep pinging the last node I go through before leaving IBB;s network to get the internet..


    C:\Documents and Settings\Luke>tracert www.boards.ie

    Tracing route to www.boards.ie [82.195.136.36]
    over a maximum of 30 hops:

    1 <1 ms <1 ms <1 ms 192.168.1.1
    2 2 ms 3 ms 2 ms DN02-fe-1-3-1-160-3rock.irishbroadband.ie [62.231.57.129]
    3 3 ms 3 ms 3 ms 62.231.52.186
    4 3 ms 3 ms 3 ms DN42-as1-0-ibis-access.irishbroadband.ie [62.231.52.134]
    5 4 ms 3 ms 4 ms DN42-ae0-50-ibis-gw.irishbroadband.ie [62.231.52.157]
    6 15 ms 14 ms 14 ms panama-inex.hosting365.ie [193.242.111.87]
    7 6 ms 6 ms 7 ms corerouter1.hosting365.ie [82.195.128.7]
    8 7 ms 6 ms 6 ms boards.ie [82.195.136.36]

    Trace complete.




    So I basically got it to ping all the hops up to 62.231.52.157



    The results conclusively proof that the probles I have been experiencing are occuring on IBB's network but not over the wireless link as I originally thought.


    I have attached an image showing up to 10% packet loss on this hop alone...


  • #20
    Mutant_Fruit
    Closed Accounts Posts: 4,943 ✭✭✭Mutant_Fruit


    Yup, that more than likely means they are heavily congested on that section, and are too damn lazy to upgrade the router there, or buy more bandwidth (not sure which is needed).

    Could you ring IBB, speak to a manager person, and ask for their email and send them that (while on the phone to them). Ask for it to be fixed. If they fob you off with some excuse, i'll ring em too, and get a few others to ring aswell if we can.

    Its rediculous that they can let that link feck up, thats their most important link!

    EDIT: Could you redo that with at least 300 pings, for a more consistant view. You say 10% loss... but thats only 3 packets.

    EDIT2: If you eradicate the packetloss in IBB's network, you'd probably find packetloss would vanish from the later hops.


  • #21
    Steffano2002
    Registered Users, Registered Users 2 Posts: 5,918 ✭✭✭Steffano2002


    Here's mine:

    PingPlotter%20Screenshot%20www.boards.ie.JPG

    I'm not very good with Tracerts and it's the first time I've used PingPlotter. Does the above show properly how crap my IBB connection is?


  • Advertisement
  • #22
    DemonOfTheFall
    Closed Accounts Posts: 2,279 ✭✭✭DemonOfTheFall


    Did you turn on/off interp or interpolate or any of those things? They make u warp around the shop like mad (Well they do for me anyway).


  • #23
    Steffano2002
    Registered Users, Registered Users 2 Posts: 5,918 ✭✭✭Steffano2002


    DemonOfTheFall wrote:
    Did you turn on/off interp or interpolate or any of those things? They make u warp around the shop like mad (Well they do for me anyway).
    What's that now? :confused:


  • #24
    Mutant_Fruit
    Closed Accounts Posts: 4,943 ✭✭✭Mutant_Fruit


    stef, what you do now is you email that to IBB WHILE on the phone the the guy you're emailing it to. Preferably NOT a normal grunt on tech support, try get to a manager. Then tell them you want it fixed, and you want it fixed now. Give em an ultimatum.

    Everyone with problems should email the same guy, and theaten the same thing. i.e. cancelling direct debit and demanding a refund on previous months. If its a manager/supervisor type person, they might actually get something done for you.

    And don't ring the 1850 number or whatever it is, ring the 01 number thats their headoffice and ask to speak to a manager/supervisor.


  • #25
    DemonOfTheFall
    Closed Accounts Posts: 2,279 ✭✭✭DemonOfTheFall


    Interp and interpolate change the settings with how the game predicts movement and that sort of stuff. If you havent changed em then nevermind tho


  • #26
    jesus_thats_gre
    Registered Users, Registered Users 2 Posts: 17,441 ✭✭✭✭jesus_thats_gre


    Whats the default settings, just so I can check...


  • #27
    Steffano2002
    Registered Users, Registered Users 2 Posts: 5,918 ✭✭✭Steffano2002


    Mutant_Fruit wrote:
    stef, what you do now is you email that to IBB WHILE on the phone the the guy you're emailing it to. Preferably NOT a normal grunt on tech support, try get to a manager. Then tell them you want it fixed, and you want it fixed now. Give em an ultimatum.

    Everyone with problems should email the same guy, and theaten the same thing. i.e. cancelling direct debit and demanding a refund on previous months. If its a manager/supervisor type person, they might actually get something done for you.

    And don't ring the 1850 number or whatever it is, ring the 01 number thats their headoffice and ask to speak to a manager/supervisor.
    Well they're sending an engineer over on Monday to replace my radio with a newer one which has a lower frequency... If this fails to resolve EVERY SINGLE problem I've had for the past 2 months, I'll do what you said above.

    Do you have that 01 number handy Mutant_Fruit? Thanks a million! ;)


  • #28
    Steffano2002
    Registered Users, Registered Users 2 Posts: 5,918 ✭✭✭Steffano2002


    DemonOfTheFall wrote:
    Interp and interpolate change the settings with how the game predicts movement and that sort of stuff. If you havent changed em then nevermind tho
    Are you talking about timenudge? I don't think that will help at all... It would if I had a consistent ping of let's say 150ms. But my ping is up and down (30ms to 350ms) all the time...


  • #29
    Mutant_Fruit
    Closed Accounts Posts: 4,943 ✭✭✭Mutant_Fruit


    Steffano2002 wrote:
    Do you have that 01 number handy Mutant_Fruit? Thanks a million! ;)
    Tel: +353 1 481 8400

    Its the only one i ever ring :P


Advertisement