Actually, let me explain that in laymans terms:

1) You have a long line, so as MrSaffron says, you can only expect a certain sync speed - which you get consistently. Also it explains the disconnects, as the quality is poor

2) Normally, the difference between 1.3mbs and 1.6 mbs would be unnoticeable.

3) BUT, if you get the *slow* IP you route to Germany and whatever. The speed is the same, it just is slower as the path is longer - example:

Suppose you drove to London at 60mph, the quickest route. Say it takes 6 hours. But what happens if you drive to London at 60mph but go to Bath, then to Dover, then up to London. That would take maybe 18 hours, but you are STILL going the same speed!

So really your speed isn't the issue here, but the route you get when connected.

Nick

I find the Techical knoledge on here is mind boggling!
How you find out all this information is amazing!
I assume that the deal from TalkTalk is, if the connection is cut another IP address is found to make a new connecton.
I am accepting that there is not a lot can be done although I also feel that, somewhere on the line there is a small problem which needs to be fixed.
I am not hoding my breath for this to happen.

It's normal operation, no fault. I guess due to all the acquisitions and take-overs of the network companies, talktalk are part of several networks - including one in Germany. Of course, due to the 1000's of Customers, they must have several DHCP server banks (which allocate IP's). So sometimes you get the DHCP server in Germany and sometimes you get the UK NTL DHCP server. This all depends on what the network loading is at the time, I guess.

I have never had a DHCP *DSL connection, only a static IP, so have not messed with such, but I am wondering if you could put in a fixed *route* in your router settings... but I don't know. Maybe someone here on DHCP can help with that.

Nick

Edited by deleted (Sat 09-Mar-13 09:59:31)

Nothing to do with Dhcp, a radius server in uk handles allocation and for redundancy talktalk will have several gateways so when you reconnect you may be on a physically different bit of network. This can happen even if you have a static ip.

I doubt they are routed via germany, just admin need to update the records for the old ip block.

As ipv4 blocks become more scarce look ups like this will become more confusing

It would explain why IP 91* is so slow (on data through-put) when the sync speeds are similar!

Nick

So would the more likely it is a different gateway hence different segment of their network

~ $ tracepath 91.18.162.154
~
 3:  lns13.the.dsl.enta.net                               31.848ms 
 4:  gi1-3.the.dist.dsl.enta.net                          31.213ms 
 5:  te2-2.telehouse-east3.dsl.enta.net                   31.381ms 
 6:  te5-2.telehouse-east.core.enta.net                   31.426ms 
 7:  te3-1.telecity-hex.core.enta.net                     31.523ms 
 8:  TenGigabitEthernet8-1.ar6.LON3.gblx.net              31.327ms 
 9:  ae3-20G.scr3.LON3.gblx.net                           33.980ms asymm 10 
10:  lag1.ar9.LON3.gblx.net                               31.825ms 
11:  80.150.168.97                                        34.612ms 
12:  hn-eb1-i.HN.DE.NET.DTAG.DE                           56.446ms asymm 13

It looks like it routes via Germany to me.

Nick

Which hops are german?

If I could pick a "Fixed Route" I would wait until a good one popped up!
I believe that Talk Talk have a LLU at the exchange and that they can actually alter the performance on the connection. Something to do with "Spreading the load">