DD thanks for the suggestion but ive definitely tried the no 'www' bit at the beginning. No speed-up software, im behind my linux firewall which is running slow-down software (
wondershaper) to alleviate for the upstream queing issue effecting cable/adsl modems worldwide (i do this so i can leech 24/7 and still get relatively low latency). you may notice the

on most of my postings, it is the linux mascot, Tux. Linux also rules along with Datsun 1200's.
BuRp newsflash i actually decided to try figure it out and just did, my firewall was dropping icmp packets (pings) from datsun1200.com (even though it NEver seemed to do that before a few weeks agO) so i made the certain changes to my iptables and now its all sweet. sorry for the ####talk i hadnt even intestigated it properly yet. datsuns rule computers suck.
hooray its working again
PING datsun1200.com (83.132.110.7): 56 data bytes
64 bytes from 83.132.110.7: icmp_seq=0 ttl=233 time=354.8 ms
64 bytes from 83.132.110.7: icmp_seq=1 ttl=233 time=360.6 ms
64 bytes from 83.132.110.7: icmp_seq=2 ttl=233 time=354.9 ms
i cant perform a complete traceroute to datsun1200.com, possibly it is behind a nat firewall like mine.. not sure.
still pretty slow but thats cuz our australian sourced packets have to travel across around 20 router hops before they reach netcabo.pt where datsun1200.com seems to be .. even from connect.com's fibre backbone does this slow ping exist. damn slow internet in 2004, wait 5-10 years and it will rock.
ang94541, the reason is says it took >1 second to load page is that this forum is dynamic and it took the webserver (the computer on which datsun1200.com data is located) that long to compile the page before sending it out to your web browser. also interesting what you say about the 21 hops, it seems strange it is 20+ hops from AU as well as US.. see below the out put of my traceroute.. interesting to compare the two..
bullshit isnt it..
Quote:
Page took 0.634447 seconds to load.
animal:~# traceroute datsun1200.com
traceroute to datsun1200.com (83.132.110.7), 30 hops max, 38 byte packets
1 10.128.204.1 (10.128.204.1) 6.036 ms 11.877 ms 7.064 ms
2 61.9.193.3 (61.9.193.3) 7.827 ms 10.367 ms 8.360 ms
3 GigabitEthernet3-1.pic1.Sydney.telstra.net (139.130.94.93) 13.856 ms 46.085 ms 8.259 ms
4 GigabitEthernet11-1.ken-core4.Sydney.telstra.net (203.50.12.117) 7.444 ms 8.067 ms 7.183 ms
5 10GigabitEthernet3-0.pad-core4.Sydney.telstra.net (203.50.6.86) 10.253 ms 6.972 ms 7.496 ms
6 GigabitEthernet2-2.syd-core01.Sydney.net.reach.com (203.50.13.38) 14.799 ms 7.339 ms 7.706 ms
7 i-12-1.wil-core02.net.reach.com (202.84.144.65) 164.850 ms 194.147 ms 164.976 ms
8 i-6-2.wil04.net.reach.com (202.84.251.186) 168.866 ms 194.580 ms 164.747 ms
9 teleglobe.wil04.net.reach.com (134.159.63.202) 173.446 ms 195.585 ms 172.635 ms
10 if-6-0.core2.laa.Teleglobe.net (209.58.85.14) 174.175 ms 217.941 ms 173.632 ms
11 if-3-2.mcore3.laa.teleglobe.net (216.6.84.21) 271.091 ms 270.155 ms 271.836 ms
12 if-4-0.mcore3.njy.teleglobe.net (216.6.84.2) 270.893 ms 270.796 ms 271.505 ms
13 if-5-0.core2.njy.teleglobe.net (216.6.57.38) 263.607 ms 276.598 ms 264.328 ms
14 if-2-0.core2.mia.teleglobe.net (64.86.138.113) 271.288 ms 271.695 ms 270.865 ms
15 if-5-0.core1.mia.Teleglobe.net (64.86.83.189) 270.780 ms 270.590 ms 271.714 ms
16 ix-1-0.core1.mia.Teleglobe.net (207.45.197.202) 347.798 ms 347.877 ms 348.871 ms
17 lisbon2-br1-p20.cprm.net (195.8.0.90) 371.617 ms 410.212 ms 372.354 ms
18 netcabo1.cprm.net (195.8.10.198) 428.469 ms 380.011 ms 371.102 ms
19 ge-4-1.cr01pc01.netcabo.net (212.113.161.209) 347.482 ms 376.163 ms 348.472 ms
20 ge-wan3-2.cr01pc08.netcabo.net (212.113.160.57) 339.374 ms 339.982 ms 339.808 ms
21 a212-113-162-67.netcabo.pt (212.113.162.67) 347.995 ms 348.850 ms 347.948 ms
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *