Ask
Reply
Solution
10-01-2013 03:46 PM - last edited on 14-07-2014 05:29 PM by Jenny
This thread has been created to discuss and troubleshoot the version 3 Sure Signal when the light sequence is as follows:
Cause
This light sequence indicates the Sure Signal's not active and it has been unable to authenticate on the Vodafone network
Troubleshooting
Please restart your Sure Signal. If the symptoms continue please add the following details to this thread:
Traceroute command:
On a PC:
On a Mac:
This will help us get the quickest possible resolution for you.
Thanks
LeeH
06-05-2015 12:59 PM
Hi @loncam
Thanks for that.
As the IP isn't showing as approved, I've passed this on to see if it can be added. We'll post back with the outcome.
Cheers,
Ben
26-05-2015 01:49 PM
@Ben_H
Do you if the IP 192.52.162.29 was ever added to the approved list?
Thanks
26-05-2015 03:13 PM
@Ioncam
That IP (192.52.162.29) is not a RIPE managed address. Vodafone might have "a bit of a policy issue" adding that to the whitelist.
Is your ISP not able to grant you an IP that checks out in the RIPE database, to being located in the UK?
https://apps.db.ripe.net/search/query.html
Regards.
Dave B.
(Not part of Vodafone.)
08-05-2015 12:12 PM - edited 09-05-2015 09:47 PM
Vodafone Sure Signal V3Trouble Shooting
My Sure Signal has been working for a couple of years. Two days ago it stopped working. I checked on MyVodafone and found the registration details had gone. I reregistered the Sure Signal. MyVodafone now says the Sure Signal is ACTIVE, but it still doesn't work. I've tried resetting it a number of times.
I'd be grateful for some technical support to get it working again. Here is my troubleshooting information...
Model:
Light Sequence:
Your speed test results from here:
Your ping test results from here:
Your external IP address from here:
RIPE Database search results:
Your Sure Signal serial number:
The results of a traceroute:
Tracing route to cluster4.vap.vodafone.co.uk [212.183.133.177]
over a maximum of 30 hops:
1 4 ms 4 ms 287 ms home.gateway.home.gateway [192.168.200.254]
2 34 ms 33 ms 33 ms lo0_ecldsl-bba1.gs1.eclipse.net.uk [82.153.1.65]
3 35 ms 34 ms 34 ms 86.54.135.72
4 806 ms 36 ms 36 ms lndgw2.arcor-ip.net [195.66.224.124]
5 37 ms 36 ms 40 ms 85.205.0.93
6 * * * Request timed out.
... " " " " " "
30 * * * Request timed out.
Trace complete.
09-05-2015 09:45 PM - edited 09-05-2015 09:46 PM
The light sequence on the Sure Signal has changed now. It has become:
It's been like this for about 24 hours now. I can't find a troubleshooting guide for this one.
10-05-2015 11:41 AM
Hello My Friends in Problem
Power = flashing
Internet = OFF
Service = steady orange
Users = steady orange
This means that your S.Sig.v3 (perhaps opthers) has failed to connecto to the V'fone server because the V'fone server cannot or will not recognise your device.
CURE = action by a human (rare creature) at V'fone server center to press buttons.
@Black Knight
Your question is easy.
Power = steady
Internet = silver pulsating slowly
Service = OFF
Users = OFF
Your S.Sig. is trying to connect to V'fone server (and is being ignored if it has been like this for several hours) It may even crash back to the original fault state.
CIRE = see CURE above!!
My S.Sigv3 has been like this for one week, to the hour.
V'fone has resolutely ignored the problem.
HEEEEELLLLLPPPPP
a.t.b.
D.Lox.
10-05-2015 12:16 PM - edited 10-05-2015 03:50 PM
@dmlox Thanks for your suggestions. I think you are right. When I do a pathping to the Sure Signal server I get these results:
Update: Oops, that was the wrong server. Here is the right server (same outcome)...
C:\>pathping 212.183.133.177
Tracing route to cluster4.vap.vodafone.co.uk [212.183.133.177]
over a maximum of 30 hops:
0 LOGI26 [192.168.200.126]
1 home.gateway.home.gateway [192.168.200.254]
2 lo0_ecldsl-bba7.th.eclipse.net.uk [82.153.1.69]
3 91.85.10.97
4 86.54.135.173
5 fe6-17-core4.th.eclipse.net.uk [212.104.128.243]
6 vl-38.lon-th1cr.spn.kcom.com [86.54.183.249]
7 lndgw2.arcor-ip.net [195.66.224.124]
8 85.205.0.93
9 * * *
Computing statistics for 200 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 LOGI26 [192.168.200.126]
0/ 100 = 0% |
1 42ms 0/ 100 = 0% 0/ 100 = 0% 192.168.200.254
0/ 100 = 0% |
2 56ms 0/ 100 = 0% 0/ 100 = 0% lo0_ecldsl-bba7.th.eclipse.net.uk [82.153.1.69]
0/ 100 = 0% |
3 72ms 0/ 100 = 0% 0/ 100 = 0% 91.85.10.97
0/ 100 = 0% |
4 59ms 1/ 100 = 1% 1/ 100 = 1% 86.54.135.173
0/ 100 = 0% |
5 68ms 0/ 100 = 0% 0/ 100 = 0% fe6-17-core4.th.eclipse.net.uk [212.104.128.243]
0/ 100 = 0% |
6 67ms 0/ 100 = 0% 0/ 100 = 0% vl-38.lon-th1cr.spn.kcom.com [86.54.183.249]
0/ 100 = 0% |
7 76ms 0/ 100 = 0% 0/ 100 = 0% lndgw2.arcor-ip.net [195.66.224.124]
100/ 100 =100% |
8 --- 100/ 100 =100% 0/ 100 = 0% 85.205.0.93
Trace complete.
Between hop 7 and 8 100% of packets are being lost. IMO this looks like a firewall at Vodafone is blocking my Sure Signal/IP. I expect this means my Sure Signal/IP has erroneously been put on a blocking list by Vodafone.
Like you say, it needs a PERSON at Vodafone to PRESS THE BUTTON to UNBLOCK my Sure Signal/IP, PLEASE :robothappy:
Sure Signal serial number:
IP address:
10-05-2015 12:25 PM
G’mornin’ V’fone
For one week, to the hour, our S.Sig.v3 has displayed these symptoms.
For nearly two years it has provided no problems at all.
On the few occasions when we have had electricity glitches the S.Sig has always regained service within 10 mins. As it ‘should’.
Every several hours it can fall back into fault status “flashing, off, orange, orange “ It usually restarts attempts to re-connect:- “steady, pulsating silver, off, off”.
Previous posts in this thread tell me that this is because the V’fone server does not recognise the connection request, for various reasons. The cure for this is that someone at Vodafone must press buttons to re-establish the connection.
Please do this to:
S.Sig.v3
Name: pwvss2012
Ser. No. 40132605193
Ext I.P. 37.72.114.62 = NYNet.
I am getting fed up with pinging, speedneting and tracerting when the results have always been consistently within the parameters set by V’fone.
Fault for this kind of problem lies not with the kit but with those who write the software which runs it. To write a routine which will re-capture a connection which has, for external reasons, failed is easy, within my engineering experience, and avoids the need for human intervention.
Please press the buttons.
a.t.b.
D.Lox
10-05-2015 09:17 PM - edited 10-05-2015 10:28 PM