Suresignal has a habit of dying

[planetf1]

I have a Sure Signal v2

I've recently moved but the same issue occured in both locations.

Sure Signal will work great for a few days up to a week or two, and then will stop working. Neither of the white lights will be lit, and it's no longer broadcasting a 3G signal. This of course then means my vodafone signal is dodgy or non existant (the reason I got a SS).

Frustratingly when this happens the SS doesn't appear to recover automaticlly - it requires me to pull the power and re-insert. Much of the time it then starts up ok within 10-20 minutes, though at times (like tonight) it may sit there for hours not working.

My suspicion is that I am seeing two seperate issues here
 a) The firmware on the SS v2 I have is not smart enough to reconnect automatically in all error cases

 b) The back-end vodafone systems supporting SS are not entirely reliable.

this is of course rather frustrating. so

i) are other people seeing similar issues - a general ss infrastructure issue

ii) or is this likely to be a flaw only applying to the ss2 ?

iii) or perhaps just specific ss2 firmware (update please)

iv) ISP related

I am using BT Infinity with HomeHub 3A. The actual connection is rock solid (I use it all day) though it's always possible it's a combination of the SS and BT HH for example timing connections out. That being said as a typical configuration the SS should be able to handle any such errors - at least recovering automatically.

[planetf1]

SS still "dead" this morning.

Have now done then 30s reset so will see if this helps....

[planetf1]

still down 😞

[planetf1]

Double checked upnp settings on HH3a earlier -- re-enabled port clamping (it had worked without this) and rebooted - no difference a few hours later.

I've not put hardcoded port rules in yet

Is there any kind of outage on the SS environment? 

[Ben_H]

Hi planetf1,

Can you follow the Sure Signal Troubleshooting Guide and post the results either here or on the page you're directed to? There's no outage at present but I'm confident we can sort yours out with the right details.

Cheers, Ben

[planetf1]

thanks - I switched thread. Reposting here instead to followup

Thanks

My unit is SN 40113161927 & is a v2 (9361 home cell v2-v)

Speedtest gives around 30/7 Mbs

ping is around 33 ms +/- 4ms - however from last test the kitter and higher latency is only on the PC (connected to router via powerline, whilst suresignal is direct connect)

traceroute isn't completing:

C:\sgs3> tracert 212.183.133.177

Tracing route to cluster4.vap.vodafone.co.uk [212.183.133.177]
over a maximum of 30 hops:

1 4 ms 5 ms 4 ms BTHUB3 [192.168.1.254]
2 22 ms 18 ms 21 ms 217.32.141.4
3 22 ms 18 ms 24 ms 217.32.140.222
4 29 ms 27 ms 24 ms 217.41.216.130
5 36 ms 34 ms 44 ms 31.55.164.51
6 29 ms 65 ms 24 ms 31.55.164.107
7 27 ms 25 ms 26 ms acc1-10GigE-0-3-0-3.bm.21cn-ipp.bt.net [109.159.248.114]
8 32 ms 33 ms 35 ms core2-te0-15-0-17.ilford.ukcore.bt.net [109.159.248.42]
9 29 ms 29 ms 33 ms peer1-xe0-1-0.telehouse.ukcore.bt.net [109.159.254.132]
10 33 ms 33 ms 36 ms lndgw2.arcor-ip.net [195.66.224.124]
11 36 ms 34 ms 35 ms 85.205.116.10
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.

Trace complete.

can't get to the other two either -- though it may just be they don't respond to pings...

> cluster4.vap.vodafone.co.uk
Server: pls-use-9-0-138-50.portsmouth.uk.ibm.com
Address: 9.64.162.21

Non-authoritative answer:
Name: cluster4.vap.vodafone.co.uk
Addresses: 212.183.133.178
212.183.133.179
212.183.133.177

> quit

C:\Users\Nigel>ping 212.183.133.178

Pinging 212.183.133.178 with 32 bytes of data:
Control-C
^C
C:\Users\Nigel>ping 212.183.133.179

Pinging 212.183.133.179 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 212.183.133.179:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

[planetf1]

I should add I've not setup port forwarding as I also make use of other sw/tools that may use some of the same ports -- for example I use multiple VPNs for work -- so I can't place the VSS in a dmz nor explicitly use port forwarding to that address. I didn't have "port clamping" set either though have now enabled that.

I've actually never setup port forwarding for the VSS, it's always worked - well to a point. The original reason for this post was that periodically it loses connectivity - but mostly a reboot fixes it. I was trying to get to the bottom of that when co-incidentally it now seems to not recover after a power cycle.

[Retired-Kay]

Hi planetf1, 

We have a statement regarding this issue here. I'd recommend subscribing to that thread for any updates. 

I have resynced your device for you as it hasn't updated since the 21st so please perform a factory reset:-

Hold down the reset button until all the lights show/flash (about 30 seconds)
Keeping the reset button held down, remove then re-insert the power lead.
Once all lights display release the reset button.
The Sure Signal will come online in around 1 hour.

Due to the issues in the statement I can't guarantee this will work but we hope to have an update shortly. 

Thanks, 

Kay

[planetf1]

Thanks, just done another full reset now so hoping this helps.

[planetf1]

Ok - the SS is now back on-line again. thanks.