Plusnet - New Network

[#1]

What traceroute are you doing/using?

[#2]

I'm using the HE tools app running on my iPod touch but I don't see why it would matter. What's your thinking?

[#3]

I was thinking you might have been doing the traceroute the wrong way around such as when done from a website.

I think it's the router that will have the correct IP address for the other end of its PPP link, a traceroute may show all sorts of different things or nothing at all. The router will be doing its connectivity check by pinging the IP address at the remote end of its PPP link, this check will fail if it doesn't respond to pings. I don't know why your traceroute shows you something different, but this will be unrelated to the reason that the router's connectivity check fails.

Edit: 195.166.130.254 does respond to pings, so perhaps the router's connectivity check is just broken.

[#4]

Well the gateway checker with trace over @ usertools gives out the same results (in reverse of course) as my traceroute.

In the past router and traceroute have always given the same IP for the gateway. Something has changed with regards to BT routing as the first host reported in the tg582n log is no longer mentioning anything about BT or Birmingham (could still be located there but not seeing anything in the host name, don't recognise it).

Last thing to try out, I guess, is to try another router, see what gateway server IP it gets. Grr... A bit of a pain to do, will try it sometime.

[#5]

Try another traceroute program. I'd actually expect the reverse traceroute to look different to the outbound one.

[#6]

Sorry, meant not exactly the same but same for last few hops, which is what we are looking at.

Different traceroute program will result in the same as before.

It's the gateway IP shown in the router that is plainly wrong. None of the checks show it anywhere else.

[#7]

Could you give us the full output of the checks you're doing? There's no possibility for the IP address that the router displays to be wrong. The router establishes a PPP connection between two IP addresses, the IP address at your end being your WAN IP address, and the IP address at the remote end being the gateway.

[#8]

Well you say there's no possibility but that's what it is appearing to be. I'll have to check the routing tables on the tg582n (not that easy to read on a small screen).

Anyway, here's one traceroute, no formatting tools available on this mobile safari so may look out of line.
traceroute to ntp.plus.net (10.6.159.212)...
Loss% Sent Last Avg Best Worst Stddev
1 192.168.1.254 0.00% 3 43.39 42.34 40.77 43.39 1.38
2 410.xe-2-2-0.central10.psb-bng03.plus.net (84.93.253.112) 0.00% 3 40.73 40.87 40.22 41.67 0.74
3 411.be7.psb-ir01.plus.net (84.93.253.115) 0.00% 3 58.55 56.88 55.87 58.55 1.45
4 cdns02.plus.net (212.159.6.10) 0.00% 3 55.58 55.42 55.04 55.63 0.32

[#9]

Is the gateway showing as 195.166.130.254 for you?  If so, mines's the same.  I'm using a TPLink TD-W9980 though.

I think they are different interfaces on the same router though if you look at the DNS for them.  They are both on central10.psb-bng03.plus.net.

[#10]

First couple of hops are an L2TP tunnel so you're not seeing the full picture from the traceroute. The router isn't wrong, it's just showing you interfaces the traceroute isnt.

[#11]

Ah, thanks for the clarification @bobpullen
So it seems the "connectivity check" (on the tg582n at least) is always going to fail with this new setup?

[#12]

---

@RPMozley wrote:
Anyway, here's one traceroute, no formatting tools available on this mobile safari so may look out of line.
traceroute to ntp.plus.net (10.6.159.212)...
Loss% Sent Last Avg Best Worst Stddev
1 192.168.1.254 0.00% 3 43.39 42.34 40.77 43.39 1.38
2 410.xe-2-2-0.central10.psb-bng03.plus.net (84.93.253.112) 0.00% 3 40.73 40.87 40.22 41.67 0.74
3 411.be7.psb-ir01.plus.net (84.93.253.115) 0.00% 3 58.55 56.88 55.87 58.55 1.45
4 cdns02.plus.net (212.159.6.10) 0.00% 3 55.58 55.42 55.04 55.63 0.32

---

Was the above a copy & paste from somewhere?  Note the IP address for ntp.plus.net is 'presented' as D.C.B.A not A.B.C.D - looks like a bug in the tool you are using.

[#13]

---

@bobpullen wrote:
First couple of hops are an L2TP tunnel so you're not seeing the full picture from the traceroute. The router isn't wrong, it's just showing you interfaces the traceroute isnt.

---

It may be true that packets go through an L2TP tunnel to get to Plusnet, but does that actually explain the observations? Haven't the packets already entered and exited the L2TP tunnel by the time they have reached 195.166.130.254? I thought L2TP was also used on the "old" network.

[#14]

@Townman That line isn't shown in the app's interface. Looks like it gets added when exporting the traceroute. I didn't think to check that closely as at first glance it looked ok, so thanks for pointing it out. Will see if I can contact Hurricane Electric about that, if they're still developing the app.