When I run a traceroute to www.idnet.net I get this
Traceroute has started...
traceroute to www.idnet.net (212.69.36.10), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 3.027 ms 2.498 ms 3.041 ms
2 telehouse-gw2-lo1.idnet.net (212.69.63.51) 19.074 ms 18.782 ms 23.541 ms
3 telehouse-gw3-g0-1-400.idnet.net (212.69.63.243) 17.776 ms 18.943 ms 30.355 ms
4 redbus-gw2-fa1-1-1003.idnet.net (212.69.63.1) 29.359 ms 22.929 ms 21.344 ms
5 redbus-gw1-fa2-0-300.idnet.net (212.69.63.225) 23.872 ms 19.863 ms 27.341 ms
6 * * *
7 * * *
8 * * *
As you can see it just looses it, but to any other site is fine like the bbc.co.uk site for instance.
Traceroute has started...
traceroute to www.bbc.net.uk (212.58.244.70), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 5.546 ms 4.178 ms 5.137 ms
2 telehouse-gw2-lo1.idnet.net (212.69.63.51) 19.808 ms 18.324 ms 19.642 ms
3 telehouse-gw5-e4-400.idnet.net (212.69.63.245) 16.016 ms 19.569 ms 18.898 ms
4 rt-lonap-b.thdo.bbc.co.uk (193.203.5.91) 19.111 ms 19.255 ms 19.369 ms
5 212.58.238.149 (212.58.238.149) 20.249 ms 16.387 ms 19.968 ms
6 212.58.239.62 (212.58.239.62) 19.318 ms 16.252 ms 19.941 ms
7 212.58.251.44 (212.58.251.44) 15.479 ms 15.430 ms 16.384 ms
8 bbc-vip115.telhc.bbc.co.uk (212.58.244.70) 18.980 ms 18.803 ms 18.926 ms
I can ping idnet fine
Ping has started...
PING www.idnet.net (212.69.36.10): 56 data bytes
64 bytes from 212.69.36.10: icmp_seq=0 ttl=59 time=15.781 ms
64 bytes from 212.69.36.10: icmp_seq=1 ttl=59 time=15.601 ms
64 bytes from 212.69.36.10: icmp_seq=2 ttl=59 time=20.837 ms
64 bytes from 212.69.36.10: icmp_seq=3 ttl=59 time=20.394 ms
64 bytes from 212.69.36.10: icmp_seq=4 ttl=59 time=20.575 ms
64 bytes from 212.69.36.10: icmp_seq=5 ttl=59 time=17.948 ms
64 bytes from 212.69.36.10: icmp_seq=6 ttl=59 time=19.634 ms
64 bytes from 212.69.36.10: icmp_seq=7 ttl=59 time=20.366 ms
64 bytes from 212.69.36.10: icmp_seq=8 ttl=59 time=19.552 ms
64 bytes from 212.69.36.10: icmp_seq=9 ttl=59 time=20.265 ms
--- www.idnet.net ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 15.601/19.095/20.837/1.868 ms
So what's happening :dunno:
I really don't know, Gary:
tracert www.idnet.net
Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:
1 <1 ms <1 ms 1 ms 192.168.1.254
2 14 ms 13 ms 13 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 14 ms 15 ms 13 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 14 ms 13 ms 14 ms redbus-gw2-fa1-1-1003.idnet.net [212.69.63.1]
5 15 ms 15 ms 13 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 14 ms 13 ms 13 ms www.idnet.net [212.69.36.10]
Trace complete.
Quote from: Rik on Dec 29, 2010, 11:30:49
I really don't know, Gary:
tracert www.idnet.net
Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:
1 <1 ms <1 ms 1 ms 192.168.1.254
2 14 ms 13 ms 13 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 14 ms 15 ms 13 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 14 ms 13 ms 14 ms redbus-gw2-fa1-1-1003.idnet.net [212.69.63.1]
5 15 ms 15 ms 13 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 14 ms 13 ms 13 ms www.idnet.net [212.69.36.10]
Trace complete.
Odd Rik, if I leave it it will just keep going by 12 I got bored. Surely this is not right? Unless its an oddity of OS X but then why is it fine on all other sites?
No problem here either, Gary.
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
Tracing route to idnet.net [212.69.36.10]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms VIGOR.router [192.168.1.1]
2 11 ms 12 ms 11 ms telehouse-gw4-lo2.idnet.net [212.69.63.99]
3 11 ms 13 ms 11 ms telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
4 12 ms 13 ms 12 ms redbus-gw2-fa1-1-1003.idnet.net [212.69.63.1]
5 12 ms 13 ms 12 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
6 12 ms 12 ms 11 ms www.idnet.net [212.69.36.10]
Trace complete.
If you can reach it, I wouldn't worry. It's possible the power outage at Letchworth is affecting it, but it should also affect me.
It times out to O2 as well, but to the forum its fine :dunno:
traceroute has started...
traceroute to www.idnetters.co.uk (212.69.36.28), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 5.181 ms 4.245 ms 4.973 ms
2 telehouse-gw2-lo1.idnet.net (212.69.63.51) 18.757 ms 20.059 ms 20.200 ms
3 telehouse-gw3-g0-1-400.idnet.net (212.69.63.243) 19.717 ms 18.925 ms 15.549 ms
4 redbus-gw2-fa1-1-1003.idnet.net (212.69.63.1) 20.669 ms 19.073 ms 19.874 ms
5 redbus-gw1-fa2-0-300.idnet.net (212.69.63.225) 20.093 ms 18.320 ms 16.244 ms
6 hosting2.idnet.net (212.69.36.28) 19.210 ms !Z 18.926 ms !Z 16.179 ms !Z
I really don't know, Gary. Why were you running a trace anyway, had you had performance problems or been unable to reach IDNet.
Quote from: Rik on Dec 29, 2010, 11:43:11
I really don't know, Gary. Why were you running a trace anyway, had you had performance problems or been unable to reach IDNet.
Been having some DNS issues (idnet dns) with sites not resolving, like google now and then, and a few others, very intermittent and always during the day, so I was doing a bit of trouble shooting.
Edit, also if I let the wizzard on my router set the connection up now and then it says PPPoE which is odd and I get that odd gateway ending in 99 as well. Tried the spare router and same thing.
I'm still on the Norton dns servers. Gary, not had any problems with those.
It's working OK from my folks TT line.
C:\Users\Glenn>tracert www.idnet.net
Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 22 ms 22 ms 22 ms 78.149.32.1
3 31 ms 30 ms 31 ms 62.24.254.224
4 31 ms 29 ms 28 ms gig-14-1-4001-rtr002.man.opaltelecom.net [62.24.
254.225]
5 31 ms 30 ms 30 ms xe-10-0-0-rt001.bir.as13285.net [78.151.225.71]
6 36 ms 36 ms 36 ms xe-11-2-0-rt001.man.as13285.net [62.24.240.0]
7 38 ms 37 ms 38 ms xe-11-1-0-rt001.sov.as13285.net [62.24.240.14]
8 43 ms 43 ms 44 ms host-78-144-1-134.as13285.net [78.144.1.134]
9 47 ms 42 ms 41 ms host-78-144-0-176.as13285.net [78.144.0.176]
10 40 ms 38 ms 38 ms telehouse-gw.idnet.net [195.66.224.181]
11 43 ms 41 ms 41 ms redbus-gw2-fa1-1-1003.idnet.net [212.69.63.1]
12 43 ms 43 ms 43 ms redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
13 38 ms 38 ms 37 ms www.idnet.net [212.69.36.10]
Times out for me too. Ping is fine, albeit a little slow.
[ted@MDK2010 ~]$ su
Password:
[root@MDK2010 ted]# traceroute www.idnet.net
traceroute to www.idnet.net (212.69.36.10), 30 hops max, 60 byte packets
1 homeportal (192.168.1.254) 15.546 ms 15.404 ms 15.428 ms
2 homeportal (192.168.1.254) 15.420 ms 15.403 ms 15.133 ms
3 telehouse-gw2-lo1.idnet.net (212.69.63.51) 36.461 ms 36.362 ms 40.074 ms
4 telehouse-gw3-g0-1-400.idnet.net (212.69.63.243) 42.134 ms 43.771 ms 43.756 ms
5 redbus-gw2-fa1-1-1003.idnet.net (212.69.63.1) 48.034 ms 49.824 ms 51.560 ms
6 redbus-gw1-fa2-0-300.idnet.net (212.69.63.225) 53.948 ms 31.521 ms 31.508 ms
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
[root@MDK2010 ted]#
Quote from: Ray on Dec 29, 2010, 11:48:07
I'm still on the Norton dns servers. Gary, not had any problems with those.
I do with youtube, Ray, it slows videos down for me, I have seen a few othesr with Norton DNS have that issue, normally I can play a 1080P music video with no issue but with Norton DNS it always does that round dot loading thing for ages and stutters during playback, hence I went back to IDnets.
Quote from: Ted on Dec 29, 2010, 11:50:43
Times out for me too. Ping is fine, albeit a little slow.
[ted@MDK2010 ~]$ su
Password:
[root@MDK2010 ted]# traceroute www.idnet.net
traceroute to www.idnet.net (212.69.36.10), 30 hops max, 60 byte packets
1 homeportal (192.168.1.254) 15.546 ms 15.404 ms 15.428 ms
2 homeportal (192.168.1.254) 15.420 ms 15.403 ms 15.133 ms
3 telehouse-gw2-lo1.idnet.net (212.69.63.51) 36.461 ms 36.362 ms 40.074 ms
4 telehouse-gw3-g0-1-400.idnet.net (212.69.63.243) 42.134 ms 43.771 ms 43.756 ms
5 redbus-gw2-fa1-1-1003.idnet.net (212.69.63.1) 48.034 ms 49.824 ms 51.560 ms
6 redbus-gw1-fa2-0-300.idnet.net (212.69.63.225) 53.948 ms 31.521 ms 31.508 ms
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
[root@MDK2010 ted]#
That's what happens to me if I leave it, Ted. Are you on Adsl max or ASdsl2+ Ted? same with Glenn and Ray, could that be an issue?
Noticed linux traceroute does this but windows tracert does not.
>traceroute 212.69.36.10
traceroute to 212.69.36.10 (212.69.36.10), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 0.374 ms 0.313 ms 0.331 ms
2 telehouse-gw2-lo1.idnet.net (212.69.63.51) 42.739 ms 44.068 ms 46.701 ms
3 telehouse-gw3-g0-1-400.idnet.net (212.69.63.243) 47.641 ms 50.033 ms 51.686 ms
4 redbus-gw2-fa1-1-1003.idnet.net (212.69.63.1) 56.087 ms 57.278 ms 58.236 ms
5 redbus-gw1-fa2-0-300.idnet.net (212.69.63.225) 59.632 ms 61.798 ms 63.965 ms
6 * * *
Not checked bbc yet
ADSL Max here, Gary.
Quote from: davej99 on Dec 29, 2010, 11:56:02
Noticed linux traceroute does this but windows tracert does not.
Could be the same with OS X 10.6.5 then I guess. Really odd. Cheers ray, I'll see how it goes and have a natter with support next week. That sounds so odd....Next week :sigh:
Next year. ;)
Quote from: Rik on Dec 29, 2010, 12:11:01
Next year. ;)
indeed, sadly I can see a move from Idnet next year, purely based on cost, Idnet for me is no longer good value with no chance of WBC or FTTC in the near future, and now they are more limited in what they can do test wise as well on your line the premium is seeing less tempting, no reflection on Idnet at all though, will have to see what happens with providers come early next year, and if (blood out of stone) I can get Kijomo to reply to an email for cost for a WiFi installation of their service, they just seem to be a void to contact, but offer FTTC speeds for not much more than I pay now for adsl max
Quote from: Gary on Dec 29, 2010, 11:52:39
That's what happens to me if I leave it, Ted. Are you on Adsl max or ASdsl2+ Ted? same with Glenn and Ray, could that be an issue?
I'm on max, Gary.
Can't really see why Linux would be an issue, traceroutes to idnet are usually ok.
Did a tracerout from the router directly. was the same.
traceroute 212.69.36.10 with 64 packetsize
1: telehouse-gw2-lo1.idnet.net (212.69.63.51) 36 ms
2: telehouse-gw3-g0-1-400.idnet.net (212.69.63.243) 30 ms
3: redbus-gw2-fa1-1-1003.idnet.net (212.69.63.1) 33 ms
4: redbus-gw1-fa2-0-300.idnet.net (212.69.63.225) 33 ms
5: * *
6: * *
7: * *
8: * *
9: * *
10: * *
11: * *
12: * *
13: * *
Quote from: Ted on Dec 29, 2010, 12:22:14
I'm on max, Gary.
Can't really see why Linux would be an issue, traceroutes to idnet are usually ok.
Did a tracerout from the router directly. was the same.
traceroute 212.69.36.10 with 64 packetsize
1: telehouse-gw2-lo1.idnet.net (212.69.63.51) 36 ms
2: telehouse-gw3-g0-1-400.idnet.net (212.69.63.243) 30 ms
3: redbus-gw2-fa1-1-1003.idnet.net (212.69.63.1) 33 ms
4: redbus-gw1-fa2-0-300.idnet.net (212.69.63.225) 33 ms
5: * *
6: * *
7: * *
8: * *
9: * *
10: * *
11: * *
12: * *
13: * *
That cuts out your OS then Ted, Ill try that.
I still wonder whether the power issues at Letchworth are affecting some people, but why it should be selective I can't explain.
Quote from: Rik on Dec 29, 2010, 12:24:33
I still wonder whether the power issues at Letchworth are affecting some people, but why it should be selective I can't explain.
The wonders of the net, Rik, my neighbour lost power last week in a powercut and we did not even though our power hiccuped, who knows the secrets of a cr@ppy utility like BT or the national grid/local wiring.
It shouldn't affect the routing though, I wouldn't have thought.
Quote from: Rik on Dec 29, 2010, 12:34:44
It shouldn't affect the routing though, I wouldn't have thought.
Had the same from my router as well, weird. Oh well not a lot to be done for now. At least it works. :fingers:
Quote from: Gary on Dec 29, 2010, 12:23:24
That cuts out your OS then Ted, Ill try that.
If the router uses busybox it will use a linux command from the GUI. Certainly traceroute as opposed to windows tracert can give the problem. Cannot say if this always gives the problem. There are many trace route type programs and I understand they are not all the same in the way they work.
Quote from: davej99 on Dec 29, 2010, 12:50:24
If the router uses busybox it will use a linux command from the GUI.
Yes, never thought of that.
Rik, could you run a traceroute from your 2700 and see what hapens?
Is this another example of Windows perhaps showing things to be something they are not i.e the traceroute to IDNet will not complete on other OSs and the disparency in ping times between XP and the rest.
The Letchworth power issue only affects our 01462 480092 incoming number (due to our ISDN30 & PBX being hosted there) and a few very old websites (classic ASP) - no ADSL traffic goes anywhere near Letchworth.
Quote from: Rik on Dec 29, 2010, 11:35:59
If you can reach it, I wouldn't worry. It's possible the power outage at Letchworth is affecting it, but it should also affect me.
Thanks, Martin.
I also have the same problem when using xUbuntu using the default traceroute options
traceroute www.idnet.net
traceroute to www.idnet.net (212.69.36.10), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 11.612 ms 11.748 ms 11.870 ms
2 telehouse-gw4-lo2.idnet.net (212.69.63.99) 29.708 ms 29.839 ms 30.021 ms
3 telehouse-gw3-g0-1-400.idnet.net (212.69.63.243) 30.221 ms 30.350 ms 30.439 ms
4 redbus-gw2-fa1-1-1003.idnet.net (212.69.63.1) 39.126 ms 39.232 ms 39.360 ms
5 redbus-gw1-fa2-0-300.idnet.net (212.69.63.225) 37.916 ms 38.114 ms 38.246 ms
6 * * *
7 * * *
8 * * *
9 * * *
If however I force the linux traceroute command to use ICMP I get
traceroute www.idnet.net -I
traceroute to www.idnet.net (212.69.36.10), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 9.545 ms 9.787 ms *
2 * * *
3 * * *
4 * * *
5 * * *
6 * www.idnet.net (212.69.36.10) 43.566 ms 43.631 ms
If I then restrict the number of simultaneous probe packets I get the expected results
traceroute www.idnet.net -I -N 1
traceroute to www.idnet.net (212.69.36.10), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 9.582 ms 6.426 ms 10.505 ms
2 telehouse-gw4-lo2.idnet.net (212.69.63.99) 29.142 ms 29.713 ms 30.416 ms
3 telehouse-gw3-g0-1-400.idnet.net (212.69.63.243) 29.264 ms 29.673 ms 30.396 ms
4 redbus-gw2-fa1-1-1003.idnet.net (212.69.63.1) 29.247 ms 29.629 ms 30.431 ms
5 redbus-gw1-fa2-0-300.idnet.net (212.69.63.225) 29.217 ms 29.773 ms 30.402 ms
6 www.idnet.net (212.69.36.10) 29.233 ms 29.319 ms 29.800 ms
Quote from: mchunt_idnet on Dec 29, 2010, 15:13:46
I also have the same problem when using xUbuntu using the default traceroute options
traceroute www.idnet.net
traceroute to www.idnet.net (212.69.36.10), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 11.612 ms 11.748 ms 11.870 ms
2 telehouse-gw4-lo2.idnet.net (212.69.63.99) 29.708 ms 29.839 ms 30.021 ms
3 telehouse-gw3-g0-1-400.idnet.net (212.69.63.243) 30.221 ms 30.350 ms 30.439 ms
4 redbus-gw2-fa1-1-1003.idnet.net (212.69.63.1) 39.126 ms 39.232 ms 39.360 ms
5 redbus-gw1-fa2-0-300.idnet.net (212.69.63.225) 37.916 ms 38.114 ms 38.246 ms
6 * * *
7 * * *
8 * * *
9 * * *
If however I force the linux traceroute command to use ICMP I get
traceroute www.idnet.net -I
traceroute to www.idnet.net (212.69.36.10), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 9.545 ms 9.787 ms *
2 * * *
3 * * *
4 * * *
5 * * *
6 * www.idnet.net (212.69.36.10) 43.566 ms 43.631 ms
If I then restrict the number of simultaneous probe packets I get the expected results
traceroute www.idnet.net -I -N 1
traceroute to www.idnet.net (212.69.36.10), 30 hops max, 60 byte packets
1 192.168.0.1 (192.168.0.1) 9.582 ms 6.426 ms 10.505 ms
2 telehouse-gw4-lo2.idnet.net (212.69.63.99) 29.142 ms 29.713 ms 30.416 ms
3 telehouse-gw3-g0-1-400.idnet.net (212.69.63.243) 29.264 ms 29.673 ms 30.396 ms
4 redbus-gw2-fa1-1-1003.idnet.net (212.69.63.1) 29.247 ms 29.629 ms 30.431 ms
5 redbus-gw1-fa2-0-300.idnet.net (212.69.63.225) 29.217 ms 29.773 ms 30.402 ms
6 www.idnet.net (212.69.36.10) 29.233 ms 29.319 ms 29.800 ms
Just using the -I switch (Use ICMP ECHO for probes) works for me, without limiting the amount of probe packets sent.
[root@MDK2010 ted]# traceroute www.idnet.net -I
traceroute to www.idnet.net (212.69.36.10), 30 hops max, 60 byte packets
1 homeportal (192.168.1.254) 6.830 ms 6.830 ms 6.815 ms
2 telehouse-gw2-lo1.idnet.net (212.69.63.51) 56.054 ms 56.103 ms 65.995 ms
3 telehouse-gw3-g0-1-400.idnet.net (212.69.63.243) 67.845 ms 67.886 ms 77.608 ms
4 redbus-gw2-fa1-1-1003.idnet.net (212.69.63.1) 93.440 ms 95.538 ms 95.581 ms
5 redbus-gw1-fa2-0-300.idnet.net (212.69.63.225) 79.591 ms 84.030 ms 85.572 ms
6 www.idnet.net (212.69.36.10) 85.565 ms 68.795 ms 70.787 ms
Just ran a tracert on my daughters Vista laptop "cough, spit" and it completed with no issue.
Would appear to be a "unix" anomaly! :o
I won't bother then, Ted. ;) Thanks for the info, Martin. :thumb:
Thanks Martin, I suppose if we need to remember to use the switches.