In reply to a post by Alucidnation:

How many hops should i let the trace route perform?

I only get the three and then all i get are *

It may be a Ubiquiti problem. See here where somebody has similar problems.

Unless you have more obvious signs of trouble (like being unable to access web sites), or a burning desire for tracert to work, I would be tempted to ignore it.

Ping and traceroute are useful tools but sometimes do not work. Responding to them is often deliberately disabled as they can be used to cause trouble, or temporarily ignored if something is overloaded.

That's the point though, the ISPs need to pull finger to make it so that more and more users CAN access them. Because increasingly it'll be hard to obtain IPv4 addresses for hosting new services etc. I speculate web hosting companies will start adding a surcharge for IPv4 but not charging for IPv6.

It also makes the interesting point: can an IPv4 ISP still say they're providing internet access when they don't have IPv6?

In reply to a post by blueacid:

I speculate web hosting companies will start adding a surcharge for IPv4 but not charging for IPv6.

That's already started, I know of one VPS provider that includes 4.3 billion IPv6 addresses free of charge with each server, but charges a £2 a month for one IPv4 address.

Could that be why I've had continual disconnections/re-connections today ?

In reply to a post by jchamier:

Windows since 2000, Mac OS from the same time, Linux forever, iOS and Android and Windows Phone all have supported IPv6.
Its just the ISPs we are waiting on.

That's a ridiculous load of twaddle. Support for IPv6 is certainly not as complete as you make out in the Operating Systems, especially going back as far as Windows 2000.

Neither is router support commonplace, far far far from it.

Whilst it is "ridiculous" that we're still in this situation, that IS the situation. Pretending IPv6 adoption is anywhere near ubiquitous at OS or Router level is crazy.

Heck, I'm STILL waiting for quite a few major connectivity providers who connect our datacentre facilities to get with the programme, let alone consumer ISPs.

In reply to a post by MrTAToad2:

Could that be why I've had continual disconnections/re-connections today ?

Funny you mention that, I'm seeing a few PlusNet lines bouncing up and down continually.

Issues with configuring EU equipment are irrelevant. Enabling IPv6 on a network doesn't mean everyone has to use it and if the EU's equipment isn't configured for IPv6 it just won't be used and they will carry on using IPv4. As no router ever supplied by Plusnet has ever been configured for IPv6 only geeks who knew what they were doing would pick it up from the beginning.

Going beyond that, if they'd said the new network is IPv6 ready but we won't be turning it on for a few weeks because of the points you've made, that would be fine. But no, they've said "no timescale" - that is pretty terrible.

Edited by jelv (Sat 09-Jan-16 19:21:57)

My traceroute is now :

1 4 ms 3 ms 4 ms BThomehub.home [192.168.1.254]
2 11 ms 14 ms 13 ms lo0-central10.pcl-ag03.plus.net [195.166.128.184]
3 11 ms 10 ms 10 ms link-a-central10.pcl-gw01.plus.net [212.159.2.168]
4 12 ms 11 ms 13 ms xe-10-2-0.pcl-cr01.plus.net [212.159.0.200]
5 11 ms 10 ms 10 ms po2.pcl-gw01.plus.net [195.166.129.41]
6 13 ms 12 ms 10 ms FWDR-10.FWDR-6.FWDR-159.FWDR-212 [212.159.6.10]

which looks like the new system

When asked

In reference to community.plus.net/forum/index.php/topic,147447.msg1298316.html#msg...:

Does the new network support IPv6 (and if not, why not)?

they (eventually) replied:

In reference to community.plus.net/forum/index.php/topic,147447.msg1298330.html#msg...:

Not yet. We don't currently have any time scale for this. We don't have any further comments on this at the moment.

In reply to a post by Alucidnation:

In reply to a post by ChrisAO:

Try doing a tracert to ntp.plus.net I think you will find it obvious when/if you have moved.

Just done that and got......................
Invalid traceroute data ( 9 * * te2-1-4.ptw-ssw01.plus.net (195.166.129.157) 13.230 ms !A)

Are you still getting that? Is it consistent?
Apart from which, posting the whole tracert maybe significant.
Bob said here that all tracert's would be similar to the one's posted previously.