Sure Signal- Power Light on Red and flashing first light- nothing else

[RachRich160]

Our Sure Signal has been working fine until last week, now the red light is on and the first light is flashing.

I have just called through to Vodafone who told me i they would send me a text with what to do, to call BT and ask them to check the ports, i did this and they said they do not support this?!!

So, now i am stuck! What should I do?

Would a firewall block access to Sure Signal?

Thanks

Rachel

[nathanrh14]

some more info:

sudo nmap 212.183.133.177 -Pn -sU -sS -sV -p50,4500,500,123,53,80,82,8,1723

Starting Nmap 5.21 ( http://nmap.org ) at 2014-06-26 00:43 BST
Nmap scan report for cluster4.vap.vodafone.co.uk (212.183.133.177)
Host is up.
PORT STATE SERVICE VERSION
8/tcp filtered unknown
50/tcp filtered re-mail-ck
53/tcp filtered domain
80/tcp filtered http
82/tcp filtered xfer
123/tcp filtered ntp
500/tcp filtered isakmp
1723/tcp filtered pptp
4500/tcp filtered sae-urn
8/udp open|filtered unknown
50/udp open|filtered re-mail-ck
53/udp open|filtered domain
80/udp open|filtered http
82/udp open|filtered xfer
123/udp open|filtered ntp
500/udp open|filtered isakmp
1723/udp open|filtered unknown
4500/udp open|filtered nat-t-ike

Service detection performed. Please report any incorrect results at http://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 83.73 seconds

traceroute 212.183.133.177
traceroute to 212.183.133.177 (212.183.133.177), 30 hops max, 60 byte packets
1 dsldevice.lan (192.168.1.254) 5.992 ms 6.417 ms 6.413 ms
2 62.208.14.22 (62.208.14.22) 27.543 ms 31.120 ms 29.700 ms
3 62.208.12.33 (62.208.12.33) 32.538 ms 36.151 ms 34.099 ms
4 62.208.14.99 (62.208.14.99) 38.025 ms 39.719 ms 41.922 ms
5 62.208.15.21 (62.208.15.21) 43.702 ms 45.565 ms 47.355 ms
6 xe-10-0-0-xcr1.lnd.cw.net (166.63.168.197) 50.512 ms 37.145 ms 40.193 ms
7 ae15-xcr1.lns.cw.net (195.2.30.114) 42.353 ms 30.135 ms 18.956 ms
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

[nathanrh14]

Why is no one replying? 

[grolschuk]

The forum team generally take 24-48 hours to reply to new questions and pick up additions to existing threads.

Since you have already provided the info, they may already be looking at it, or you still may be in the queue.

From your 1st message it seems to suggest the suresignal used to work but has stopped?

Has anything changed in your network setup? new ISP? new router?

[nathanrh14]

Hi grolschuk, no change, just stopped working, like a lot of people despite the product being named Sure Signal the box generally crashes about once a week - not exactly reliable/sure!

We just unplug it leave it for a minute then plug it back in when it's crashed.

Now the flashing first light never goes steady...

To be asked to perform a traceroute by Vodafone and find Vodafone claim anything network related should be directed to BT is just ridiculous, if anything network related should be directed to BT, why are Vodafone requesting customer to run traceroute?

This product is pretty poor and the support leaves much to be desired in my experience so far...

[grolschuk]

The trace route is going to make sure that DNS is resolving ok and your network is pointing to the right destination, and also check the response times along the way, as a slow hop could mess things up.

I look after just over 20 of these ranging from the original #####, through to the newer SS3, and find mostly they are fairly stable once up and running.

They don't like overheating, so if in a warm place/direct sunlight that may cause it to fall over more than it should.

Also, I have found that due to the encrypted link back to vodafone being a secure vpn tunnel, if the router you are using is vpn aware and can terminate connections itself, it sometimes tries to do that rather than passing the traffic onto the suresignal.

BT routers have an option called Port Clamping to get around this, others sometimes have VPN Passthrough.

But as yours has been working in the past, the above probably isn't relevant.

Hopefully the tech team can take a look at your box when it last reported in, and and offer some help.

[Retired-Matt_B]

Hi nathanrh14,

I've checked your Sure Signal and can see that it's not on the latest firmware. As such, I've requested for the Sure Signal to be updated.

Please leave it switched on and do not reset it for the next 24 hours.

After this time, unplug the Sure Signal and plug it back in, you should then see an active connection.

Thanks,

Matt B

[LeonardScott]

I am experiencing exactly the same problem as other people. The power light is sold and the first light is flashing slowly and nothing else. I am using a BT Homehub 3 and I have even moved the Suresignal into the DMZ and nothing changes. I have even disbaled the homehub firewall but that made not difference either.

Your speed test results from here. Download speed 5.62 Upload speed 0.89 

Results - http://www.speedtest.net/my-result/3589476058

Your ping test results from here. Packet Loss 0% Ping 36ms Jitter 7ms http://www.pingtest.net/result/100624551.png
Your external IP address from here. 81.151.246.90

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 2 ms 4 ms BThomehub.home [192.168.1.254]
2 12 ms 10 ms 10 ms 217.32.142.193
3 13 ms 10 ms 10 ms 217.32.142.222
4 18 ms 16 ms 15 ms 212.140.206.226
5 19 ms 15 ms 17 ms 31.55.165.35
6 18 ms 16 ms 16 ms 31.55.165.107
7 18 ms 16 ms 15 ms acc1-10GigE-2-3-0.mr.21cn-ipp.bt.net [109.159.25
0.94]
8 25 ms 29 ms 29 ms core2-te0-13-0-13.ilford.ukcore.bt.net [109.159.
250.44]
9 26 ms 23 ms 23 ms peer2-xe2-1-0.telehouse.ukcore.bt.net [109.159.2
54.142]
10 27 ms 25 ms 24 ms t2c3-xe-1-1-2-0.uk-lon1.eu.bt.net [166.49.211.18
0]
11 26 ms 23 ms 23 ms 166-49-211-254.eu.bt.net [166.49.211.254]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Your Sure Signal serial number:4214605180

[Retired-Matt_B]

Hi LeonardScott,

Could you let me know the Sure Signal serial number again please?

The one you've provided is showing up as invalid.

Thanks,

Matt B

[RachRich160]

Hi,

Here are my results:

Speed Test Results:

Ping: 13ms

Download Speed: 4.69 Mbps

Upload Speed: 0.38 Mbps

IP Address is: 86.133.177.81

Serial Number: 40132745908

VSS Traceroute command:

In attachments. As couldnt paste.

Still experiencing the same problems.

Thanks

[LeonardScott]

Hi Matt_B

Thanks for the prompt responce, in the meantime I contined to work at the problem.

The probem turned out to be with the BT Homehub, since it is a 3A I found that I had to use a few tricks on it as I did when I was setting up a webcam earlier in the year.

In this case I had to remove all my previous settings for port forwarding, as I found that it was co-opting preset rules into the user defined rules even though I did not set them. I then configured the Suresignal DHCP on the BT HomeHub (version 3A) to a single DHCP IP address that it would reuse.[BT Homehubs have a fixed up range running from .9X to 2XX]

I then set VPN port clamping on in the BT HomeHub and then set a single port forwarding rule up for the Vss authentication with all the relevent TCP and UDP ports.

UDP 4500- 4500  to 4500 - 4500

UDP 500 - 500 to 500 - 500

UDP 123 - 123 to 123 - 123

UDP 8 - 8 to 8 - 8

Any 50 - 50 to 50 - 50 

Any 1723 - 1723 to 1723 - 1723

About 3 minutes after I started the rule. The SureSignal changed to a Steady Power light with the two lights on solid as well. The only time I have had since then is when BT themselves had connection issues.