Jump to content
SAU Community

Recommended Posts

quick... post your ping times...

here's one for ya... i'll tracert www.telstra.com

1 40 ms 40 ms 40 ms lns-1.pacific.net.au [203.9.190.190]

2 40 ms 40 ms 40 ms f1-0-100.mel001.pacific.net.au [210.23.140.249]

3 200 ms 180 ms 191 ms a1-0-3.syd008.pacific.net.au [210.23.140.106]

4 140 ms 170 ms 170 ms ATM8-0-0-7.ken12.Sydney.telstra.net [139.130.4.185]

5 130 ms 140 ms 181 ms GigabitEthernet3-0.ken-core4.Sydney.telstra.net [203.50.12.153]

6 160 ms 150 ms 141 ms GigabitEthernet1-1.pit1.Sydney.telstra.net [203.50.13.2]

7 160 ms 151 ms 150 ms pitt-tcom-r01 [139.130.185.254]

8 190 ms 171 ms 160 ms 144.135.19.10

And here's my ping...

Pinging www.telstra.com [144.135.19.10] with 32 bytes of data:

Reply from 144.135.19.10: bytes=32 time=190ms TTL=249

Reply from 144.135.19.10: bytes=32 time=130ms TTL=249

Reply from 144.135.19.10: bytes=32 time=121ms TTL=249

Reply from 144.135.19.10: bytes=32 time=110ms TTL=249

Now show me yours...

I'm on Pacific Internet ADSL 256/64

Link to comment
https://www.sau.com.au/forums/topic/17124-howdyyy-people/#findComment-354356
Share on other sites

HAHAHAHAHA oh god that sucks ass.

GO ADSL! :O

i dont even use up my 3GB plan.

tracert www.telstra.com

Tracing route to www.telstra.com [144.135.18.10]

over a maximum of 30 hops:

1 17 ms 9 ms 9 ms 10.37.0.1

2 10 ms 9 ms 9 ms meb1-pos3-3.gw.optusnet.com.au [198.142.192.17]

3 25 ms 25 ms 24 ms pos0-0-0.mn1.optus.net.au [202.139.18.5]

4 23 ms 23 ms 23 ms Pos-5-1-0.lon42.Melbourne.telstra.net [139.130.6.25]

5 24 ms 23 ms 23 ms GigabitEthernet3-0.win-core1.Melbourne.telstra.net [203.50.79.129]

6 23 ms 23 ms 23 ms Pos2-0.ken-core4.Sydney.telstra.net [203.50.6.165]

7 24 ms 23 ms 23 ms GigabitEthernet1-1.pit1.Sydney.telstra.net [203.50.13.2]

8 25 ms 23 ms 29 ms pitt-tcom-r01 [139.130.185.254]

9 67 ms 37 ms 24 ms 144.135.18.10

Trace complete.

ping www.telstra.com

Pinging www.telstra.com [144.135.18.10] with 32 bytes of data:

Reply from 144.135.18.10: bytes=32 time=33ms TTL=245

Reply from 144.135.18.10: bytes=32 time=25ms TTL=245

Reply from 144.135.18.10: bytes=32 time=24ms TTL=245

Reply from 144.135.18.10: bytes=32 time=24ms TTL=245

Ping statistics for 144.135.18.10:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 24ms, Maximum = 33ms, Average = 26ms

Link to comment
https://www.sau.com.au/forums/topic/17124-howdyyy-people/#findComment-354361
Share on other sites

woops... forgot that I was downloading some MP3's... my bad... I'll update when i'm done downloading.

I also noticed that my tracert to telstra goes to syd and then comes back to melb, wheras u'rs stays in melb... quite odd..

Link to comment
https://www.sau.com.au/forums/topic/17124-howdyyy-people/#findComment-354368
Share on other sites

75? pffft i pay 50 a month

and like i said... i dont use 3GB and i like to be able to doanload something in half an hour... not 2 days.

256 plan... AHAHAHA yeah a whole 28kb/s as apposed to 400+

Link to comment
https://www.sau.com.au/forums/topic/17124-howdyyy-people/#findComment-354551
Share on other sites

Tracing route to www.telstra.com [144.135.18.10]

over a maximum of 30 hops:

1 * * * Request timed out.

2 13 ms 13 ms 12 ms 203.89.203.1

3 13 ms 12 ms 13 ms cr1.mel.vnet.net.au [203.89.200.2]

4 13 ms 13 ms 12 ms ibr02-g6-0.mlbn01.globalcenter.net.au [64.15.32.

17]

5 26 ms 27 ms 27 ms 203-134-48-153.cust.mel.iprimus.net.au [203.134.

48.153]

6 26 ms 26 ms 25 ms vl044.sw02.mel.iprimus.net.au [203.134.50.13]

7 28 ms 26 ms 26 ms 203.134.50.18

8 18 ms 15 ms 21 ms Pos6-0-0.lon20.Melbourne.telstra.net [139.130.19

3.101]

9 28 ms 16 ms 15 ms GigabitEthernet3-0.win-core1.Melbourne.telstra.n

et [203.50.79.129]

10 28 ms 28 ms 28 ms Pos2-0.ken-core4.Sydney.telstra.net [203.50.6.16

5]

11 30 ms 30 ms 32 ms GigabitEthernet1-1.pit1.Sydney.telstra.net [203.

50.13.2]

12 32 ms 27 ms 28 ms pitt-tcom-r01 [139.130.185.254]

13 96 ms 37 ms 30 ms 144.135.18.10

Trace complete.

Link to comment
https://www.sau.com.au/forums/topic/17124-howdyyy-people/#findComment-354587
Share on other sites

1 .5 ms 1 ms 3 ms 10.37.0.1

2 1 ms 1.5 ms 3 ms meb1-pos3-3.gw.optusnet.com.au [198.142.192.17]

3 1 ms 2 ms 4 ms pos0-0-0.mn1.optus.net.au [202.139.18.5]

4 3 ms 5 ms 9 ms Pos-5-1-0.lon42.Melbourne.telstra.net [139.130.6.25]

5 2 ms 3 ms 7 ms GigabitEthernet3-0.win-core1.Melbourne.telstra.net [203.50.79.129]

6 3 ms 4 ms 6 ms Pos2-0.ken-core4.Sydney.telstra.net [203.50.6.165]

7 11 ms 13 ms 12 ms GigabitEthernet1-1.pit1.Sydney.telstra.net [203.50.13.2]

8 1 ms 6 ms 9 ms pitt-tcom-r01 [139.130.185.254]

9 4 ms 15 ms 17 ms 144.135.18.10

Link to comment
https://www.sau.com.au/forums/topic/17124-howdyyy-people/#findComment-354720
Share on other sites

Pinging www.telstra.com [144.135.18.10] with 32 bytes of data:

Reply from 144.135.18.10: bytes=32 time=165ms TTL=241

Reply from 144.135.18.10: bytes=32 time=234ms TTL=241

Reply from 144.135.18.10: bytes=32 time=150ms TTL=241

Reply from 144.135.18.10: bytes=32 time=173ms TTL=241

Ping statistics for 144.135.18.10:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 150ms, Maximum = 234ms, Average = 180ms

Don't Laugh!

Link to comment
https://www.sau.com.au/forums/topic/17124-howdyyy-people/#findComment-358116
Share on other sites

and now my goddamn traceroute

farkkkkout.

traceroute to www.telstra.com (144.135.18.10), 30 hops max, 40 byte packets

1 FastEthernet6-0.civ-service1.Canberra.telstra.net (203.50.1.65) 0.439 ms 0.395 ms 0.408 ms

2 GigabitEthernet3-0.civ-core2.Canberra.telstra.net (203.50.10.129) 0.661 ms 0.35 ms 0.412 ms

3 GigabitEthernet2-2.dkn-core1.Canberra.telstra.net (203.50.6.126) 0.562 ms 0.479 ms 0.569 ms

4 Pos4-0.ken-core4.Sydney.telstra.net (203.50.6.121) 4.674 ms 4.721 ms 4.647 ms

5 GigabitEthernet1-1.pit1.Sydney.telstra.net (203.50.13.2) 4.815 ms 4.764 ms 4.773 ms

6 pitt-tcom-r01 (139.130.185.254) 4.829 ms * 4.844 ms

7 * * *

8 * * *

9 pitt-tcom-r01 (139.130.185.254) 4.93 ms * 5.043 ms

10 * * *

11 * pitt-tcom-r01 (139.130.185.254) 5.006 ms *

12 pitt-tcom-r01 (139.130.185.254) 5.028 ms * *

13 pitt-tcom-r01 (139.130.185.254) 5.044 ms * 4.912 ms

14 * * *

15 pitt-tcom-r01 (139.130.185.254) 4.907 ms * 4.879 ms

16 * * *

17 pitt-tcom-r01 (139.130.185.254) 4.888 ms * *

18 pitt-tcom-r01 (139.130.185.254) 5.004 ms * *

19 pitt-tcom-r01 (139.130.185.254) 4.877 ms * 4.909 ms

20 * * pitt-tcom-r01 (139.130.185.254) 4.971 ms

21 * pitt-tcom-r01 (139.130.185.254) 4.885 ms *

22 pitt-tcom-r01 (139.130.185.254) 4.926 ms * 4.819 ms

23 * * *

24 * * pitt-tcom-r01 (139.130.185.254) 4.972 ms

25 * pitt-tcom-r01 (139.130.185.254) 5.025 ms *

26 pitt-tcom-r01 (139.130.185.254) 4.991 ms * 4.974 ms

27 * pitt-tcom-r01 (139.130.185.254) 4.891 ms *

28 * pitt-tcom-r01 (139.130.185.254) 4.978 ms *

29 * pitt-tcom-r01 (139.130.185.254) 4.881 ms *

30 pitt-tcom-r01 (139.130.185.254) 4.969 ms * 5.065 ms

still not there, farkkk

Link to comment
https://www.sau.com.au/forums/topic/17124-howdyyy-people/#findComment-358117
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Similar Content

  • Latest Posts

    • This. The R34 handbrake icon DOES come up when the brake fluid level is low. You might be sitting right on that threshhold. I have been down this diagnosis path and this was the solution (and it was pretty much as full as your picture is to begin with).
    • Unfortunately the cavaet to that is that while any scan tool should be able to read the code, the workshop will need a consult plug to OBD socket adapter. You don't have a location on your profile, where are you based?
    • @Haggerty this is your red flag. In MAP based ECU's the Manifold pressure X RPM calculation is how the engine knows it is actually...running/going through ANY load. You are confusing the term 'base map' with your base VE/Fuel table. When most people say 'base map' they mean the stock entire tune shipped with the ECU, hopefully aimed at a specific car/setup to use as a base for beginning to tune your specific car. Haltech has a lot of documentation (or at least they used to, I expect it to be better now). Read it voraciously.
    • I saw you mention this earlier and it raised a red flag, but I couldn't believe it was real. Yes, the vacuum signal should vary. It is the one and only load signal from the engine to the ECU, and it MUST vary. It is either not connected or is badly f**ked up in some way.
    • @Haggerty you still haven't answered my question.  Many things you are saying do not make sense for someone who can tune, yet I would not expect someone who cannot tune to be playing with the things in the ECU that you are.  This process would be a lot quicker to figure out if we can remove user error from the equation. 
×
×
  • Create New...