High pings again

[Sebby]

I'm on max, yet the IP of the first hop ends 99. Perhaps it's the other way?

[Rik]

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    25 ms    21 ms    21 ms  telehouse-gw4-lo2.idnet.net [212.69.63.99]
 3    26 ms    23 ms    21 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

 4    24 ms    25 ms    33 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
 5    24 ms    29 ms    34 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
 6    24 ms    25 ms    23 ms  www.idnet.net [212.69.36.10]

Trace complete.

The highlighted line will end in 99 or 100 for WBC, 101 or 102 for IPStream Connect.

[Rik]

I'm on max, yet the IP of the first hop ends 99. Perhaps it's the other way?

Shouldn't be, Seb, I'm getting 99 on WBC.

[Rik]

I'm on max, yet the IP of the first hop ends 99. Perhaps it's the other way?

Can you call support Seb.

[psp83]

ok, i powered off for 5mins while changing the plug, still looks like i'm not on the new hostlink.

Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  www.routerlogin.com [192.168.0.1]
  2    13 ms    13 ms    13 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
  3    13 ms    12 ms    13 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
  4    13 ms    13 ms    14 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    13 ms    13 ms    13 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6    14 ms    14 ms    14 ms  www.idnet.net [212.69.36.10]

Trace complete.

[Rik]

You're definitely on the hostlink, Paul, I'm trying to find out more.

[Sebby]

Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:

  1    63 ms    99 ms    99 ms  dsldevice.lan [192.168.1.254]
  2  2228 ms  2297 ms  2430 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
  3  2244 ms  1444 ms  2171 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4  2217 ms  1967 ms  1761 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5  2242 ms  2710 ms  3111 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6  3448 ms  2810 ms  2982 ms  www.idnet.net [212.69.36.10]

Trace complete.

[Rik]

 

Clearly something is not working as Simon expects, it's being investigated now.

[Sebby]

Better following a third PPP reboot:

Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:

  1    97 ms    99 ms    98 ms  dsldevice.lan [192.168.1.254]
  2   145 ms   205 ms   155 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
  3   151 ms   254 ms   163 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4   445 ms   225 ms   346 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5   197 ms   166 ms   177 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6   145 ms    93 ms    99 ms  www.idnet.net [212.69.36.10]

Trace complete.

[Ray]

This is what I'm getting after a router reboot.

Tracing route to idnet.net [212.69.36.10]
over a maximum of 30 hops:

 1    59 ms    99 ms    99 ms  speedtouch.lan [192.168.1.254]
 2    64 ms    16 ms    16 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
 3    16 ms    18 ms    16 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

 4    17 ms    35 ms    19 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
 5    17 ms    16 ms    17 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
 6    17 ms    17 ms    15 ms  www.idnet.net [212.69.36.10]

Trace complete.

[Rik]

Are those pings better, Ray?

[psp83]

mine hardly moves.. unlike that past few weeks.

C:\Users\Paul>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  www.routerlogin.com [192.168.0.1]
 2    13 ms    13 ms    12 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
 3    13 ms    13 ms    13 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
 4    13 ms    14 ms    13 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
 5    14 ms    13 ms    12 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
 6    14 ms    15 ms    14 ms  www.idnet.net [212.69.36.10]

Trace complete.


root@saturn:~# ping -c 20 www.idnet.net
PING www.idnet.net (212.69.36.10) 56(84) bytes of data.
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=1 ttl=59 time=12.9 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=2 ttl=59 time=13.0 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=3 ttl=59 time=12.4 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=4 ttl=59 time=12.9 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=5 ttl=59 time=12.5 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=6 ttl=59 time=12.2 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=7 ttl=59 time=12.4 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=8 ttl=59 time=12.4 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=9 ttl=59 time=12.2 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=10 ttl=59 time=12.9 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=11 ttl=59 time=13.2 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=12 ttl=59 time=12.4 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=13 ttl=59 time=12.5 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=14 ttl=59 time=12.7 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=15 ttl=59 time=13.4 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=16 ttl=59 time=12.7 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=17 ttl=59 time=12.7 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=18 ttl=59 time=13.0 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=19 ttl=59 time=12.3 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=20 ttl=59 time=12.2 ms

--- www.idnet.net ping statistics ---
20 packets transmitted, 20 received, 0% packet loss, time 19027ms
rtt min/avg/max/mdev = 12.240/12.693/13.499/0.348 ms

[Ray]

Are those pings better, Ray?

Around my normal, Rik.

[Dopamine]

If they said the new hostlink would 'arrive' on the 20th October (ie be delivered to them by BT) they are quite probably correct.  

What would you rather they do?  Have the hostlink delivered and then go live the same day without a period of testing?  Given the problems WBC has caused for everyone - not just iDNet - they would rightly be accused of crass stupidity.  

Looks like they can't win on this one.

How daft can you get? "What would you rather they do?"

I rather they tell me approximately when a fix might happen. If that's after ten days of testing, then tell me that the hostlink arrives on x so will solve problems on x + 10, not try to fool me into believing the fix will be sooner.

They hoped to stary moving people early this week, that was the last message Dopamine, if you had read through a few posts you would have seen Rik's post, the new link has to be tested, you cannot transfer thousands of customers and then go "oops it went wrong, guess we should have tested it" which would method you have preferred, no testing and maybe issues or a better new connection with backup? Yes the tested route I'm sure  

Same reply. Stupid comment.

[Rik]

Same reply. Stupid comment.

Unnecessarily abusive, Dopamine.

[juiceuk]

mine hardly moves.. unlike that past few weeks.

C:\Users\Paul>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  www.routerlogin.com [192.168.0.1]
 2    13 ms    13 ms    12 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
 3    13 ms    13 ms    13 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
 4    13 ms    14 ms    13 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
 5    14 ms    13 ms    12 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
 6    14 ms    15 ms    14 ms  www.idnet.net [212.69.36.10]

Trace complete.


root@saturn:~# ping -c 20 www.idnet.net
PING www.idnet.net (212.69.36.10) 56(84) bytes of data.
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=1 ttl=59 time=12.9 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=2 ttl=59 time=13.0 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=3 ttl=59 time=12.4 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=4 ttl=59 time=12.9 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=5 ttl=59 time=12.5 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=6 ttl=59 time=12.2 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=7 ttl=59 time=12.4 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=8 ttl=59 time=12.4 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=9 ttl=59 time=12.2 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=10 ttl=59 time=12.9 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=11 ttl=59 time=13.2 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=12 ttl=59 time=12.4 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=13 ttl=59 time=12.5 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=14 ttl=59 time=12.7 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=15 ttl=59 time=13.4 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=16 ttl=59 time=12.7 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=17 ttl=59 time=12.7 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=18 ttl=59 time=13.0 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=19 ttl=59 time=12.3 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=20 ttl=59 time=12.2 ms

--- www.idnet.net ping statistics ---
20 packets transmitted, 20 received, 0% packet loss, time 19027ms
rtt min/avg/max/mdev = 12.240/12.693/13.499/0.348 ms

Can I come and game at your house? lol. Those are some nice pings. I'll be happy when mine get back to the low twenties.

[Simon]

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    25 ms    21 ms    21 ms  telehouse-gw4-lo2.idnet.net [212.69.63.99]
  3    26 ms    23 ms    21 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4    24 ms    25 ms    33 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    24 ms    29 ms    34 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6    24 ms    25 ms    23 ms  www.idnet.net [212.69.36.10]

Trace complete.

The highlighted line will end in 99 or 100 for WBC, 101 or 102 for IPStream Connect.

Yeah, but some of them have been different to that.  Paul's (above) was [212.69.63.51].

[Simon]

Mine is currently:

Tracing route to idnet.com [212.69.36.10]
over a maximum of 30 hops:

  1     2 ms     1 ms    <1 ms  home [192.168.1.254]
  2    32 ms    33 ms    31 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3    32 ms    39 ms    33 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
  4    34 ms   305 ms   289 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    32 ms    33 ms    33 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6    32 ms    33 ms    33 ms  www.idnet.net [212.69.36.10]

Trace complete.

[Simon]

Oh, the penny's just dropped.  I'm on standard ADSL.   

[Tacitus]

How daft can you get? "What would you rather they do?"
I rather they tell me approximately when a fix might happen. If that's after ten days of testing, then tell me that the hostlink arrives on x so will solve problems on x + 10, not try to fool me into believing the fix will be sooner.

Given the vagaries of WBC and the problems iDNEt have had with BT, to give a firm date when all would be well would be asking for a fall.  They might perhaps have offered more information but given the problems they've had I can understand their reluctance to do so.

You are simply accusing them of ulterior motives which I very much doubt were there.  Your default assumption seems to be that everybody is dishonest - you shouldn't judge others by your own standards. 

[Rik]

Yeah, but some of them have been different to that.  Paul's (above) was [212.69.63.51].

I know, Simon's looking into it... Paul is definitely on the hostlink.

[Simon_idnet]

Seems that 20CN and 21CN report different addresses: 21CN connections show the L2TP Tunnel Endpoint and 20CN connections show the Loopback address.
S

[psp83]

old tracert :
Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  www.routerlogin.com [192.168.0.1]
  2   123 ms   113 ms   131 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3   166 ms   162 ms   145 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
  4   133 ms   134 ms   147 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5   145 ms   139 ms   152 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6   131 ms   135 ms   144 ms  www.idnet.net [212.69.36.10]

Trace complete.

Tonights:
Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  www.routerlogin.com [192.168.0.1]
  2    13 ms    12 ms    13 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
  3    13 ms    12 ms    13 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
  4    19 ms    13 ms    13 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    13 ms    13 ms    13 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6    14 ms    14 ms    13 ms  www.idnet.net [212.69.36.10]

Trace complete.

Tonights 2nd hop has a different IP address to my old one, so something has changed.

[Simon]

Following reboot:

Tracing route to idnet.com [212.69.36.10]
over a maximum of 30 hops:

 1     1 ms     1 ms     1 ms  home [192.168.1.254]
 2    32 ms    29 ms    29 ms  telehouse-gw4-lo2.idnet.net [212.69.63.99]
 3    30 ms    29 ms    31 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
 4    33 ms    31 ms    33 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
 5    33 ms    31 ms    31 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
 6    31 ms    32 ms    31 ms  www.idnet.net [212.69.36.10]

Trace complete.

So, am I now on the new hostlink?

[Tacitus]

Better check with support, Tac, in case something odd has happened, eg you re-connected to a central.

Apparently that is what happened Rik.  Actually Simon rang me before I was able to ring him.  After a few tests he established what was going on and forced a new session.  Following a router reboot my pings are now down in the normal range.

I don't know whether to put this in a separate thread, but to have the MD of your ISP ring you, since he had noticed my earlier comment on this forum regarding excessive pings is truly exemplary service.