11-04-2012 04:12 PM - last edited on 11-04-2012 04:53 PM by Lee
Dave you've not even bothered to reply to mine from last week! This is beyond the pale, a device you should really be hiring out for free to those with contracts above a certain amount. I think a twee to 6000 is about to go out about how poor this is and will no longer spread, at least in this tech age we have the tools and power to complain publiclly properly.
11-04-2012 05:49 PM
Right, it's working, here's how:
INSTRUCTIONS TO SET UP VSS FOR technicolor beBoxV2 (Thompson/Alcatel TG582n)
1. Log in to your router's admin control panel
2. Enable UPnP (aka Game Mode)
3. Create a new firewall profile (you can't edit the default ones)
4. Add the list of IP addresses from the original post into your new firewall profile
5. Set up a new port forwarding profile
6. Add the list of ports from the original post into your port forwarding profile
7. Assign your port forwarding profile to your VSS
8. Telnet into your router and run the following command: ids config state=disabled
9. Reboot your router
10. Reboot your VSS
11. Leave the VSS for a long time, over night or something. If you've done it right your signal light will be on. When you make a call your phone light will come on.
11-04-2012 05:52 PM - edited 11-04-2012 05:53 PM
The new bit of information I found which wasn't mentioned was that my router has a built in "Intrusion Detection System" which was blocking the VSS and can only be enabled using a Telnet command.
I've no idea how peeps are supposed to figure this out on their own. I have 1st class degree in internet computing and it took me days to get to the bottom of it. Sad times.
11-04-2012 05:55 PM
Thanks for your posts. I'm sorry to hear that you're all affected by the steady red light issue.
@ realdannys - I'm sorry, I'm certain that Dave never meant to ignore you. If you're referring to the IP question then this is 126.96.36.199. Also, we do support the VSS. It's just that there are outside factors such as ISP's and routers that we've got no control over. In your own words: " they cannot offer support on a device they didnt make...".
@ billysielu - I've just seen your post come into the thread. Thanks for confirming you're up and running, and for sharing the working instructions for the benefit of others with the same setup.
@mrblack - Thanks for your post. I have forced a resync of your unit. Please could you factory reset the device and let me know how you get on? Your trace route looks fine as do your speeds. It seems the VPN has dropped for some reason and the resync may help to kick it back into life.
@ notsosure - Thanks for confirming the factory reset didn't work. Please could you and any other users still affected by this issue after a reset, try the VSS on an alternate connection? Looking at your VSS, it connected to our servers this morning at 03.24 so I can confirm your external IP is on the whitelist.
@ SJWS - Thanks to you too for coming back to us. Your VSS has failed to create a new VPN to our servers. Could you try the VSS on another connection for me?
11-04-2012 10:24 PM
I don't have access to an alternate connection. If my VSS is connecting to your servers then it sounds like a problem either on your side or a firewall rule on my side blocking incoming data. However, my VSS is set as the default DMZ and I have disabled DOS attack filters too. In effect I've stripped apart all filters yet it still fails to work.
I appreciate there are lots of variables for you guys to deal with i.e. different ISPs and different routers. However, is it safe to assume that only some cases succeed and in the majority there are compatibility issues? i.e the VSS is not fit for general public sales.
11-04-2012 11:51 PM
Thanks for the response. Yes, both of the SS had one constant orange and one randomly flashing green led on. My new IP address is 188.8.131.52. In order to try and narrow down the issues, I currently only have one SS ( serial 40120543554 ) connected, direct to my router, with all other hardware ( wired and wireless ) powered down. Have also rebooted router and SS in all sorts of orders and combinations - still no joy
12-04-2012 06:55 PM
I have to disagree with your comment about the VSS not being fit for purpose. There are many thousands of users who do not frequent this forum who are using the device without issue.
Your VSS once again connected with our servers last night at 23:07 so it's set up correctly as far as I can tell. Have you tried turning off your firewall?
Also, are you using the supplied BT equipment?
You could also try completely de-registering the VSS and re-registering it to see if it will pick up a fresh connection. Failing that I could arrange for a possible replacement with no guarantee it will work since we're so far unable to establish if your current device is faulty.
Could you possibly provide me with your external IP as this is what I need to check on the whitelist?
Cheers to you both,
12-04-2012 09:32 PM
Glad to hear the SS is fit for purpose, that is why I asked the question; "s it safe to assume that only some cases succeed and in the majority there are compatibility issues?".
If it is working for the vast majority, then it sounds like it is specific to the routers (unlikely ISPs unless international IP's issued). As I mentioned in my original post, I am an advanced IT user - I troubleshoot and repair hardware and software issues and these network issues sound router related. I will try and switch routers - I am not using the BT HomeHub due to its rubbish port forwarding capability. However, I will check if the SS works on it and report back. Perhaps my Netgear is the culprit.
13-04-2012 06:04 PM
Thank you for your post and please keep us updated.
I have checked and can see the IP is on the whitelist.
It would appear that something since the change has tripped this up, please can you temporarily disable your firewalls and let us know how you get on.
The final step before we look at our device options would be to ask to try the device on a different connection to see if you are still experiencing the same issues.
Please let me know your findings.
13-04-2012 06:24 PM
Hi Dave CD,
I have tried this with the firewall off and still no joy. I dont have another connection I can try it on, unfortunaltely.
BT sent me another router this morning ( that has more configureable logging ) I have set that up, forwarded the ports etc etc and the logs are showing that the pings on all ports are being passed to the SS2, but that's where they stop !
One change, since I installed the new router, the SS2 is constantly flashing the two white lights ( before this would happen for 10 mins and then revert to red light only ) the two white lights have now been flashing for some hours - is this progress ?
14-04-2012 02:20 PM
14-04-2012 02:33 PM
No, no joy. The lights flashed for some hours but then the box resorted to the dreaded red light only.
I've been speaking to BT again this morning and they came up with an interesting point. If, the Sure Signal 2 is making the connection to your servers via VPN, why do we have to forward any ports at all. Surely everything is negotiated by the SS VPN ? (which would explain why, initially both of my SS2 boxes just worked - with no ports forwarded at all )
Is there any way you can tell me when either of my boxes communicated with your servers in any shape or form ?
I have now plugged both SS back in and they are both sitting with red light only.
I am rapidly giving up on this - is there any way I can escalate the problem ?
14-04-2012 04:01 PM
I have tried to connect my new Sure Signal but am getting the red light only after the flashing light for about 5 hours or so.
The serial number is 40113102608 and the router is a BT Home Hub 2. Please can you advise if there has been any connection received at your end.
14-04-2012 04:54 PM
Chalk me up as one of the latest people to have a problem setting up their femtocell. When I first turned it on, it sat there with the double-flash for quite a while, and I figured it was downloading firmware or something, so I left for a while. I came back home about five hours later to see that it was still flashing. I gave it another half hour or so, making a total of around seven hours, before I unplugged it and plugged it back in again. Now I get the flashing for a few minutes, followed by just the steady power light. I have ensured that UPnP is enabled, and I have also poked holes in the firewall for ports 8, 50, 123, 500, and 4500 on both TCP and UDP (hopefully this won't interfere with my work VPN, but I haven't gotten around to trying that, yet). Here is various and sundry other information I've seen requested on other forum posts to help out:
Model: 9361 Home Cell V2-V
Serial No: 40120127846
Internally assigned IP address: 192.168.1.13
Sky Broadband Router
External IP: 184.108.40.206
Network Type: MER
Firewall Rules: TCP/UDP Ports 8, 50, 123, 500, 4500 routed to 192.168.1.13
Tracing route to 220.127.116.11 over a maximum of 30 hops
1 2 ms 1 ms 1 ms myrouter.home [192.168.1.1]
2 37 ms 36 ms 39 ms 5e0d6dbe.bb.sky.com [18.104.22.168]
3 35 ms 35 ms 34 ms 10.245.202.81
4 45 ms 43 ms 45 ms te0-1-0-2.er11.thlon.ov.easynet.net [22.214.171.124]
5 44 ms 44 ms 42 ms LNDGW2.arcor-ip.net [126.96.36.199]
6 41 ms 43 ms 41 ms 188.8.131.52
7 * * * Request timed out.
...and so on up to 30 hops...
The results are virtually identical for 184.108.40.206 and for 220.127.116.11.
Any help you could provide would be greatly appreciated. Thanks.
14-04-2012 06:48 PM
This last week has been a nightmare with SS. Problems started last Tuesday when I got a new HTC One X, micro sim, with the same phone number.
It would not connect to the SS at all. Old phone with new PAYG SIM was having troubles being registering through the web. That was eventually fixed with some help from one of the Vodafone people on here. Still no joy with the main phone though.
I went round a cycle of de-register SS, re-register SS, still with the same end result, everything working except one phone. With hindsight I should have stopped at this point because it has all gone downhill since then.
Eventually one of the "Specialists" on the Vodafone helpline told me to do a factory reset on the SS. After that had been done, it was goodnight Vienna. I have never been able to make a connection at all since then - I get the dreaded solid red light and nothing else.
Some basic facts
SS Serial No: 40112437260
External IP Address: 18.104.22.168
ISP : BT Infinity
Router : Netgear WNDR3700 and BT HomeHub 3 (both configured correctly, although had always been quite OK on uPnP before)
Speedtest: Ping 26 ms. Down 37.48 Mbps Up 8.15 Mbps
Traceroute output looks OK too
Tracing route to 22.214.171.124 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms READYSHARE [192.168.1.254]
2 8 ms 8 ms 8 ms 126.96.36.199
3 9 ms 8 ms 9 ms 188.8.131.52
4 13 ms 13 ms 13 ms 184.108.40.206
5 13 ms 13 ms 13 ms 220.127.116.11
6 14 ms 14 ms 14 ms 18.104.22.168
7 14 ms 14 ms 13 ms acc1-10GigE-0-7-0-4.bm.21cn-ipp.bt.net [22.214.171.124]
8 24 ms 23 ms 23 ms core1-te0-15-0-0.ealing.ukcore.bt.net [126.96.36.199]
9 22 ms 22 ms 22 ms peer1-xe1-0-0.telehouse.ukcore.bt.net [188.8.131.52]
10 24 ms 31 ms 24 ms LNDGW2.arcor-ip.net [184.108.40.206]
11 22 ms 22 ms 22 ms 220.127.116.11
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.
In fact my router even logged some successful inbound packets from one of the Vodafone servers during one of my many attempts to get this &^%%* device to connect again
- [LAN access from remote] from 18.104.22.168:4500 to 192.168.1.218:4500, Saturday, April 14,2012 14:44:30
- [LAN access from remote] from 22.214.171.124:4500 to 192.168.1.218:4500, Saturday, April 14,2012 16:15:58
15-04-2012 09:35 AM
Another frustrated new user here. I registered my VSS V2 S/N 40120954967 early yesterday afternoon. All I seem to get is 10 minutes of the System and Phome lights flashing before it resorts to a steady red power light. I have gone some way through setting up Port Forwarding on my BT Home Hub 2 but, and I suspect that this is the big but, it doesnt look as if the HH2 is allocating an IP address. Any help/guidance would be very much appreciated.
15-04-2012 12:33 PM
My suresignal has been playing up for a while now where it shows a full signal and will send/recieve texts but no calls. Usually after a reset it comes back within 10 mins to an hour; however yesterday I had to switch off my router (seperate circuit) for some maintenance at home and since then no matter what I do the suresignal only has the power light lit, sometimes with a slow flashing no.2 light.
My internet connection is running fine at 6.4 meg down/0.4 meg up as usual and ports 50,123,500 & 4500 are all forwarded to the suresignal on a fixed ip.
My ISP is Zen and I'm on a netgear DGN2200
I cannot ping or run a traceroute to the address listed elswhere in this thread as I get a "general failure" on both - all other pings and traceroutes work fine so I am guessing this is a vodafone server issue?
My suresignal serial is 21224713541
Please can someone look into what's going on and let me know?!