FTTC - Vodafone Suresignal IP Problems?

[#1]

FYI
Mine is working fine and I'm on Fibre.
Ian

[#2]

Quote from: hiflier

Mine is working fine and I'm on Fibre.

Thanks Ian. Would you mind running a trace route to 212.183.133.177 if you're able to and have a moment?
In that case, anyone from Plusnet able to advise?  Don't seem to be able to reach the Vodafone Suresignal servers currently and from checking the Vodafone forums it sounds like I'm not the only one with a problem at the moment.
timstephenson@MacBook-Pro ~ $ traceroute 212.183.133.177
traceroute to 212.183.133.177 (212.183.133.177), 64 hops max, 52 byte packets
1  bthomehub (192.168.100.254)  1.832 ms  1.993 ms  1.622 ms
2  lo0.11.central11.ptn-bng01.plus.net (195.166.128.229)  11.802 ms  12.250 ms  12.330 ms
3  irb.11.ptw-cr02.plus.net (84.93.249.18)  12.312 ms  40.274 ms
    irb.11.ptw-cr01.plus.net (84.93.249.17)  11.756 ms
4  ae2.ptw-cr01.plus.net (195.166.129.4)  41.649 ms  12.543 ms
    lndgw2.arcor-ip.net (195.66.224.124)  13.998 ms
5  lndgw2.arcor-ip.net (195.66.224.124)  15.617 ms  14.636 ms  15.023 ms
6  * * 85.205.0.93 (85.205.0.93)  19.855 ms
7  * * *
8  * * *
9  * * *
10  * * *
11  * * *
12  * * *
13  * * *

[#3]

I am getting an incomplete trace route that stops at the same point as yours, and pinging that IP address fails.
However, my Suresignal is working ok.
Ian

[#4]

That traceroute looks normal to me. From what I can gather the Vodafone servers don't respond to ICMP packets. There's a thread I've been involved with over on Voda's forums here that I'd expect to be alive with complaints if there was a wider problem.
I'd try and reach out to Vodafone if I were you and get them to check things from their side.
Also, make sure the Plusnet Firewall is disabled.

[#5]

Thanks Bob.
Are there any differences in how traffic is routed or filtered between ADSL & FTTC connections? Might be sheer coincidence but can't help to come back to the fact that the SS was working fine when our line was connected to ADSL, and now can't connect following the switch to fibre...
Have reached out to Vodafone; not being particularly helpful at the moment but will see how that progresses.

[#6]

Two factors have changed - Your router and your IP address (assuming you don't have a static address)
Double check your HH5 configuration and try visiting http://www.iplocation.net/ to see if your current IP address is registered as being in the UK (Some of the IP ranges that PN use are incorrectly listed in geolocation databases).  You should be able to change your IP address, if needed, by disconnecting your router. If you're using the HH5 as both the modem and the router don't disconnect it too often though or the VDSL kit in the cabinet may decrease your line speed.

[#7]

Hi, same router & same  IP (static) - had been running the HH5 for a couple of weeks on ADSL without any problems...

[#8]

Quote from: TimStephenson

Are there any differences in how traffic is routed or filtered between ADSL & FTTC connections?

Nothing significant, certainly not when it comes to the Plusnet network. When using FTTC, you're relying on PPPoE rather than PPPoA, and the MTU is a tad lower I believe, but if either were a significant problem then I'd expect to have seen more examples of a similar thing happening.

[#9]

Thanks Bob - working on getting Vodafone to assist at the moment.. they seem to run out of technical expertise after "reset your SureSignal" however!
Ah well..

[#10]

Just to update in case it helps someone, after wasting maybe 2-3 days time troubleshooting this with a HomeHub5; I ran out of patience and replaced the Homehub5.
No idea if it's the specific combination of FTTC, SureSignal v2 & using the VDSL modem incorporated in the HomeHub5 TypeA, but something seems to be fundamentally broken somewhere.  No amount of tinkering with port forwarding, Port Clamping, uPNP or DMZ configuration helped and Vodafone had all but run out of ideas.
I replaced the HH5 with a Billion BiPac 8800AXL;  plugged in & configured the router; connected the SureSignal, and about half an hour later it had automatically configured itself and was up and running.
No special configuration, port forwarding, messy SureSignal specific setup or anything similar was needed...!