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
26-06-2015 04:13 PM
I found the problem was due to fragmentation of the return timing UDP packets from he vodafone servers to my VSS. This was a result of the PPPoE segment between the BT Infinity modem and my router, with the modem not returning a response to the server to reduce the MTU size. This meant the router blocked the fragmented UDP packets on it's WAN interface.
I resolved this by installing a Billion BiPAC 8800 VDSL router. This has a built-in VDSL modem, so does not implement a PPPoE segment. This avoids the fragmentation issue and my VSS works perfectly.
29-06-2015 09:51 AM
27-06-2015 04:22 PM
Thjanks for the advice. I have tried connecting at a neighbour's property... no joy. I also notice that sometimes when I do a reset the power light doesn't come on and after around 20 minutes of waiting I unpolug and plug it back in and then the power light comes on. Seems a bit 'iffy' to me, so I'm going to request a replacement or repair... what a pain 😕
26-06-2015 05:33 PM
using Airport Extreme on Plusnet fibre.
Thanks
Ed
Speed 31M Down:12M Up
Ping Couldn't run due to firewall
External IP 195.166.133.161
Serial 42151276542
Traceroute
traceroute to 212.183.133.177 (212.183.133.177), 64 hops max, 52 byte packets
1 10.0.1.1 (10.0.1.1) 1.250 ms 0.833 ms 0.684 ms
2 lo0.14.central14.ptn-bng01.plus.net (195.166.128.233) 20.833 ms 20.470 ms 20.479 ms
3 irb.14.ptw-cr01.plus.net (84.93.249.65) 21.130 ms
irb.14.ptw-cr02.plus.net (84.93.249.66) 21.046 ms
irb.14.ptw-cr01.plus.net (84.93.249.65) 21.064 ms
4 lndgw2.arcor-ip.net (195.66.224.124) 23.217 ms
ae2.ptw-cr01.plus.net (195.166.129.4) 20.955 ms 21.242 ms
5 lndgw2.arcor-ip.net (195.66.224.124) 23.625 ms 22.246 ms 23.008 ms
6 * 85.205.0.93 (85.205.0.93) 25.616 ms 22.440 ms
7 * * *
8 * * *
9 * * *
10 * * *
28-06-2015 09:20 AM
28-06-2015 10:47 AM - edited 28-06-2015 10:48 AM
@samsurfer Everything looks good from what you’ve provided.
I can see that you’ve last connected on the 25 June at 22:06.
Please try a different Ethernet cable and to ensure that all the following ports are open as follows:
Ports to be opened for forwarding
IP addresses to be allowed on the router & firewall
@webby10 Please try deregistering the Sure Signal and re-registering.
@edbond Please ensure that the following ports are open:
Ports to be opened for forwarding
IP addresses to be allowed on the router & firewall
I can see it's registered successfully on 25 June at 17:30, so once the above steps have been followed please perform a reset:
28-06-2015 01:06 PM
Hi Sarah
Thanks for getting back.
Wher you say...
quote>
IP addresses to be allowed on the router & firewall
<endquote
...I assume you mean 212.183.133.177 etc. Is that correct?
28-06-2015 01:18 PM
I think what she means is that you need to allow, on your router, the range of IP addresses provided
PWIAC
29-06-2015 08:13 AM
Hi drey_p
Thanks for the input.
I get that she wants those IP ranges allowed, but there are only three octets in each of those ranges aren't there? For example, the first range would be:
183.133.177 and 183.133.178 and 183.133.179
I may be really dumb here, but those aren't full IP addresses are they?
29-06-2015 10:08 AM - edited 29-06-2015 10:13 AM
Yes.
As before, stick 212. in front of what they quote, and again yes, the - and (resulting) 5th number denote an "address range".
It's best (in routers that are capable of this) to just allow all protocols from those addresses (and those only!) To pass unmolested to the internal fixed IP address that you allocated to your SureSignal. (You did assign or reserve it a fixed LAN address.)
I.e. Set up "address based" rules, not "protocol" or "port" based rules.
212.183.133.177 - 179 (three addresses)
212.183.133.181 - 182 (two addresses)
212.183.131.128 - 191 (sixty four addresses!)
(No one knows what 212.183.133.180 is, and why it's omitted.)
Setting up "protocol based" rules, can seriously ruin your day if you have other systems/services that use any of them, such as (but not only) many office vpn's for example, for outworkers etc to connect in with... Especially if you also have the utterly lame so called "Business Hub" from BT! Regards.
Dave B. (No affiliation to anyone, or anything.)