cancel
Showing results for 
Search instead for 
Did you mean: 
1

Ask

2

Reply

3

Solution

Vodafone SureSignal suddenly stops working - traceroute shows it getting into VF's network

paulo.pinto
2: Seeker
2: Seeker

My SureSignal has been working fine. Suddenly, since last Tuesday 2nd November at around 11am, it stopped working. It's a SureSignal v3 and the red power light is flashing, and the two furthest right lights are stready orange.

 

I thought it was temporary so waited. No joy. Reset it (power on/off, reset button, reset button 10 seconds, reset button 20 seconds, reset button 30 seconds - all tried).

 

Spoke to Live Chat twice. The first time I was told it had been deregistered on the website (it hadn't, because I never did it), nevertheless they 're-added' it - still didn't work. Second time, they told me I needed to go into a shop and replace it. But a quick bit of network tracing showed me that it was working fine but seemed to be a connectivity problem.

 

Called 191, spoke to SureSignal expert and explained that I could see it was trying to establish a VPN session from my network trace, but was getting no response. I told him I did a traceroute and got see the packets getting to VF network, so there were no active blocks at least at the IP level. He said I needed to contact my ISP and tell them to allow VPN sessions.

 

Now VPN sessions are working as (IPSEC) as I use them for work, and have no problems. Ping vap.vodafone.co.uk and I get no replies. A traceroute shows the following:

 

traceroute to vap.vodafone.co.uk (212.183.133.177), 30 hops max, 60 byte packets

1  192.168.5.1 (192.168.5.1)  0.328 ms  0.309 ms  0.299 ms

2  * * *

3  172.16.27.136 (172.16.27.136)  8.131 ms  6.854 ms  7.431 ms

4  172.16.22.49 (172.16.22.49)  18.620 ms  17.761 ms  19.380 ms

5  172.16.24.172 (172.16.24.172)  8.520 ms  10.670 ms  9.605 ms

6  172.16.23.36 (172.16.23.36)  7.139 ms  6.546 ms  7.482 ms

7  172.16.22.224 (172.16.22.224)  3.321 ms  6.068 ms  4.842 ms

8  172.16.20.96 (172.16.20.96)  27.382 ms  28.025 ms  28.264 ms

9  172.16.25.23 (172.16.25.23)  30.354 ms  42.745 ms  42.349 ms

10  * * *

11  * * *

12  * * *

13  * * *

14  ae7-xcr2.lsw.cw.net (195.2.2.117)  1.987 ms  1.817 ms  1.798 ms

15  * * *

16  * * *

17  * * *

18  * * *

19  * * *

20  * * *

21  * * *

22  * * *

23  * * *

24  * * *

25  * * *

26  * * *

27  * * *

28  * * *

29  * * *

30  * * *

 

I hear mention of a 'whitelisting' requirement to sometimes get access. Is this still a thing? If not, anyone got any ideas? I'm pretty sure I don't need a new unit and there's something strange going on at the network level.

 

Thanks.

 

9 REPLIES 9

Rahim
Moderator (Retired)
Moderator (Retired)

@paulo.pinto Sorry for the delay in reaching your post. 

 

If you're still having trouble, please can you verify your serial number? 

 

Can you also verify that 212.183.133.177 is your IP address? 

 

If it is, then I can confirm it's within range on our Whitelist, therefore shouldn't be causing any issues. 

Hi Rahim,

 

No, 212.183.133.177 is the IP address of the VF server it is trying to connect to.  If you private message me I can send you my serial number and IP address.

 

Thanks,

Paulo

Rahim
Moderator (Retired)
Moderator (Retired)

@paulopinto I can confirm '212.183.133.177' is within range on our Whitelist. 

 

Please provide us with your serial number publicly, as we're unable to respond to messages sent to our personal inbox. 

Hi Rahim,

 

The IP address range from which I'm connecting is from Hyperoptic in the UK - 

 

https://apps.db.ripe.net/search/lookup.html?source=ripe&key=188.172.144.0%20-%20188.172.159.255&type...

 

The range is from 188.172.144.0 to 188.172.159.255

 

Can you check if this is in the whitelist? It may be a recent subnet re-allocation to Hyperoptic that may result in some form of geo-location based blocking.

Sukhi
Moderator (Retired)
Moderator (Retired)

@paulopinto I’ve requested this range to be added to our whitelist.

 

This should be done in the next 48 hours :Smiling:

Hi,

 

This still isn't working.

 

Can you confirm the range 188.172.144.0/20 (i.e. 188.172.144.1 to 188.172.159.254) has been added to the whitelist?

 

Thanks,

Paulo

Will
Moderator (Retired)
Moderator (Retired)

Hi @paulopinto

 

I've contacted the team again and asked them to check if they've added that range to the whitelist. Check again in 48 hours and let us know if it starts working.

Hi Will,

 

I can confirm this is now working!

 

Thank you all for the support on here. I have to admit I was at the point of changing providers after talking to your telephone and chat support teams, who denied that a whitelist existed and kept telling me to reboot my device, my phones, return to a shop etc...

 

You guys on here are great. I would suggest that you update the other support channels to make them aware of problems like this so that other customers who have these issues can get them solved quickly, rather than endless calls/chats over 2-3 weeks!

 

Thanks again!!

Rahim
Moderator (Retired)
Moderator (Retired)

@paulopinto We're delighted to hear your Sure Signal is up and running! 

 

We'll ensure this information is passed on to help with future cases. 

 

Thank you for your patience, and apologies for any inconvenience caused.