cancel
Showing results for 
Search instead for 
Did you mean: 
1

Ask

2

Reply

3

Solution

Flashing/steady power light, no other lights lit

Retired-George
Moderator (Retired)
Moderator (Retired)

We’ve created this thread to help with an issue that some people find during setup.

 

This issue has the following symptoms:

 

  • The power light either constantly flashes or remains steady
  • No other lights flash or light up

 

Please note that whether the power light is flashing or remains steady, this still points to the same issue - the Sure Signal hasn't established a connection to the internet.

 

The only difference is that if the light’s steady, then the Sure Signal has previously downloaded a profile from the server, if it's flashing then it hasn't.

 

Troubleshooting steps:

 

Check the physical connection between your Sure Signal and the router/modem.

In order to work, the Sure Signal needs to be connected to a spare Ethernet port on your router or modem, or a Hub/Switch that is connected to an internet gateway.

 

In some cases, it’s possible for an Ethernet cable to be faulty, in which case it may not allow your router and Sure Signal to talk to each other.

 

To verify that the Ethernet cable works, check the lights at the back of your Sure Signal where the cable is plugged in.

 

There should be a link light on permanently which indicates that an electrical circuit has been established through the cable.

 

There should also be a light which flashes whenever data is being passed through the cable. If either the data light or the link light do not come on, this could indicate a problem with the cable itself. Please try a spare cable, or plug the cable into a different port on your router/modem.

 

Check that you’ve got an active internet connection.
Make sure you can connect to the internet on another device, such as your PC or phone. If you can’t connect, this indicates a problem with your router or your Internet Service Provider (ISP).

 

We recommend rebooting the router to see if this then allows you to connect to the internet.

 

Reboot your router/modem:

 

  1. Turn off your router or modem at the wall for 10 seconds and then turn it back on
  2. Wait for the lights on your modem/router to indicate that an internet connection has been established
  3. Press the reset button on the Sure Signal

 

Check that your Sure Signal has been assigned an internal IP address by your router.

The Sure Signal must be assigned an internal IP address by your router. If your router supports DHCP (Dynamic Host Configuration Protocol), this must be enabled, as doing so will enable the router to assign an IP address to your Sure Signal automatically.


For more instructions on how to do this, please check your router manual, or contact your ISP or router manufacturer.

 

If your router or network configuration doesn’t allow DHCP, you’ll need to assign a static IP address to your Sure Signal's MAC Address by using your router's configuration panel. Please contact your ISP or router manufacturer for instructions on how to do this. The MAC address can be found on the sticker at the back of the Sure Signal.

 

BT Infinity customers.

If you’re a BT Infinity customer, you’ll need to log into your router admin page and select port clamping.

 

Once this has been selected please restart your router and Sure Signal.

 

Check your MTU settings.

Log into your router admin page and find the location of the MTU field. This varies depending on the make and model so you’ll need to look for it.

 

Change the value of the MTU size to 1500.

 

Log out of the router, this will usually result in a reboot.

 

Perform a reset of the Sure Signal:

 

  1. Hold in the reset button until all lights go solid
  2. Pull the power lead out with the reset button still pushed in
  3. Continue to hold down the reset button and reconnect the power lead
  4. Wait for all lights to come on and then release the reset button

 

The Sure Signal will now try to contact the network and download its profile. This can take up to 6 hours.

 

Post your router/ISP details and Sure Signal serial number.

If you’ve done all of the above, or you’re struggling with configuring your router, please post your router's make and model number below. Please also include your Sure Signal serial number and the name of your ISP.

 

We find that other users of the same router will usually be able to share tips with you, to get things working.

 

We’ll also attempt to help with this, but due to the number of different manufacturers and models, it is not always possible. We don’t officially support any form of router configuration, so we’ll always recommend contacting your router manufacturer or ISP for assistance first.

 

Thanks,

 

Jenny

1,304 REPLIES 1,304

Hi Lee/VSS eforum,

 

I *have* been in touch with Orange, my new ISP, but their stock response is that "they do not block anything", and that I can find the answers to my problems "by searching in Google", so they have been absolutely no use whatsoever. If Vodafone have no way of remotely testing my VSS, then I cannot go back to Orange and tell them that they are actually blocking something, without an understanding of what that might be. For instance, once I reset the VSS, I can see that it is initially trying to communicate with 212.183.133.181 and 212.183.131.133 on port 123, then after a while, to 212.183.133.177, 212.183.133.178 and 212.183.133.179 on port 500. However, at no time does it *receive* anything from any of these or any other IP addresses on the ports I have been asked to forward to the VSS (8, 50, 123, 500 & 4500).

 

So does this mean that Orange is blocking traffic from these IP addresses to my VSS, or does Vodafone use other IP addresses to communicate back to the VSS once it has initially communicated with the above addresses?

 

I don't know, but there should be someone in Vodafone who can tell me what the expected communication sequence *should* be, so I can go back to Orange with a cast iron explanation of what should happen then at least I can get them to look at this seriously. Or at least try and ping my external router IP address on the above ports from a valid Vodafone IP address to test that Orange is actually blocking or doing something with this traffic.

 

C'mon Vodafone, I know this problem is not of your making, but we've invested in your technology, so please help out!

 

 

Hi mck2011,

 

Firstly I would like to wish you a very warm welcome to the eForum.

 

I have look into MERE just, but there isn't much about this technoligy anywhere at the moment, except on a few forums. I have had this raised to a few network experts to get a better opinion and will post back on this thread as soon as know any more about it.

 

Hi trickster,

 

From what you are saying here, it sounds like the ports aren't forwarding correctly. There is a very good post on the first page of this thread expelling what to do. It's the 5th post. Let us know if that resolves the issue.

 

Woody

eForum team

I’ve had a Vodafone Sure Signal box since last year – a device which was working fine up until three weeks ago.

Just before Christmas we changed our broadband provider from Orange to Sky, but this did not have any immediate effect on the Sure Signal box and it continued to work as normal.

A fortnight ago, all of the lights on the Sure Signal box went off apart from the top light, which started to continually flash, and everybody’s mobile phone signal disappeared (we have four Vodafone users in our house).

On initial contact with Vodafone, they suggested that I reset the Sure Signal box, which I did, reset my router, which I did, and gave out some quite obvious instructions like checking all of the connections and making sure everything was plugged in properly.

After all of this had failed to work, I was transferred to their second-line support team, who used a remote accessing system to look at my computer (an iMac) and check my router settings.

My router (a D-Link DSL-2640S) showed that the Sure Signal box was detected in the ‘attached devices’ section and it was deemed that the fault was with the Sure Signal box and a new one was ordered.

The new box arrived the very next day and I immediately registered it on the ‘my account’ section of the Vodafone website and made sure it was all plugged in and ready to go.

After 24 hours, the box remained in the same state as its predecessor (the top light flashing on and off and all other lights off). After another phone call to Vodafone, I was then told that it could take up to 48 hours to start working and was instructed to reset the box and wait.

Another 24 hours passed, with the box still in the same state, so once again I rang Vodafone (each time having to explain the issue from the beginning) and after going through all of the obvious checks once more, I was again transferred to their second-line support team.

They informed me that a certain number of ports on my router needed to be opened to make the Sure Signal box work and directed me to a port forwarding website which gave clear instructions on how to do this.

Using my router settings, I then proceeded to open ports 8, 50, 123, 500 and 4500 as instructed and made sure all of the ports were listed as ‘allowed’ in my firewall and security settings. I also assigned an IP address to my Sure Signal box.

I then waited another 24 hours to see if that would do the trick and – you guessed it – nothing happened. So yet another phone call to Vodafone was made and once again I was passed on to the second-line support team.

They had another remote look at my computer – at the settings that I’d changed and the ports that I’d opened – and said I’d done everything correctly. On that basis, they put the fault down to another faulty Sure Signal box and ordered a second replacement.

So I then received a second, brand new Sure Signal box which I registered on my account but, once again, I was stuck with the exact same issue. The top light on the box was flashing and nothing else.

It is not the router that is at fault. I checked the issue with Sky and at present we have an iMac, a Sky HD+ box, a Sony Bravia television and at least four wireless devices hooked up to the router and all are working fine.

The router detected the new Sure Signal box in the ‘attached devices’ section but to no avail, so I put in one final, lengthy call to Vodafone's support team. After a 35-minute call, it was deemed that I had another faulty Sure Signal box, except this time they wanted me to send them the box in a pre-paid envelope (which hasn't arrived yet) so they can have a look at it.

I then did something called a path-ping on Vodafone's request, which showed that my connection is being blocked. It timed out instantly and lost 100% of the data packets that were sent.

I rang my ISP earlier today and they were very vague in their knowledge of such issues. However, they did say that my connection uses PPPoA and that the router uses a dynamic IP address.

Something somewhere has changed in the last few weeks and the problem clearly isn't with my router because it is working fine with everything else. 

I feel as if I have exhausted every avenue. I have even tried using different ethernet cables and switching the cables around on the router, but to no avail.

I have reached the end of the line with this device plus it costs me every time I ring Vodafone’s 08700 number from my landline because (obviously) I can’t get a signal on my mobile.

Is there anything that anyone can think of that might rectify this situation and get the Sure Signal box working again? I cannot face another gruelling (and expensive) conversation explaining this all over again.

Any help would be greatly appreciated.

 

Hi Danny

 

I have exactly the same symptoms but a different router/ISP

 

VF have replaced the Box, but no joy, I have also configured the port forwarding etc

 

Very Frustrating - I have noted that when I reset the box, the power light stays solid for about 30 seconds with some associated network activity.

 

Also I tried the pingpath and it did work but took sometime - I have included it, can you confirm I used the right IP address?

 

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.


C:\Users\Administrator>pathping 212.183.133.177

Tracing route to host212-183-133-177.uk.access.vodafone.net [212.183.133.177]
over a maximum of 30 hops:
  0  IBM-S1HD2QV58DD.home.gateway [192.168.1.110]
  1     *     home.gateway.home.gateway [192.168.1.254]
  2  213.1.113.12
  3  213.1.118.62
  4  213.1.78.2
  5  213.1.79.22
  6  87.237.20.244
  7  bundle-ether1.lontr1.London.opentransit.net [193.251.255.101]
  8  xe-1-1-0-0.ffttr2.Frankfurt.opentransit.net [193.251.240.105]
  9  tengige0-10-4-0.ffttr1.FrankfurtAmMain.opentransit.net [193.251.129.38]
 10  te4-4-10g.ar4.fra3.gblx.net [64.208.110.225]
 11  VODAFONE-LTD.TenGigabitEthernet7-1.ar6.LON3.gblx.net [64.214.144.122]
 12     *        *        *
Computing statistics for 275 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           IBM-S1HD2QV58DD.home.gateway [192.
168.1.110]
                                1/ 100 =  1%   |
  1    4ms     1/ 100 =  1%     0/ 100 =  0%  home.gateway.home.gateway [192.168
.1.254]
                                0/ 100 =  0%   |
  2   14ms     1/ 100 =  1%     0/ 100 =  0%  213.1.113.12
                                0/ 100 =  0%   |
  3   20ms     1/ 100 =  1%     0/ 100 =  0%  213.1.118.62
                                0/ 100 =  0%   |
  4  ---     100/ 100 =100%    99/ 100 = 99%  213.1.78.2
                                0/ 100 =  0%   |
  5  ---     100/ 100 =100%    99/ 100 = 99%  213.1.79.22
                                0/ 100 =  0%   |
  6   23ms     2/ 100 =  2%     1/ 100 =  1%  87.237.20.244
                                0/ 100 =  0%   |
  7   23ms     2/ 100 =  2%     1/ 100 =  1%  bundle-ether1.lontr1.London.opentr
ansit.net [193.251.255.101]
                                0/ 100 =  0%   |
  8   41ms     1/ 100 =  1%     0/ 100 =  0%  xe-1-1-0-0.ffttr2.Frankfurt.opentr
ansit.net [193.251.240.105]
                                0/ 100 =  0%   |
  9   37ms     1/ 100 =  1%     0/ 100 =  0%  tengige0-10-4-0.ffttr1.FrankfurtAm
Main.opentransit.net [193.251.129.38]
                                0/ 100 =  0%   |
 10   90ms     1/ 100 =  1%     0/ 100 =  0%  te4-4-10g.ar4.fra3.gblx.net [64.20
8.110.225]
                                0/ 100 =  0%   |
 11   51ms     1/ 100 =  1%     0/ 100 =  0%  VODAFONE-LTD.TenGigabitEthernet7-1
.ar6.LON3.gblx.net [64.214.144.122]

Trace complete.

Thanks

 

Neil

Hi guys,

 

danny0191, I can definitely understand your frustration here. The fact that you've had three different Sure Signals would lead me to believe the issue lies with your ISP or router though. I don't suppose you still have the router from your Orange connection? If so, I'd recommend using this instead to see if it makes any difference. If it doesn't, or you're unable to check, then I'd strongly recommend taking this issue further with Sky.

 

nsimmo, thanks for posting. You've performed the pathping to the correct IP address here. It does look like there are packet failures before the data hits Vodafone though. As such, I'd recommend contacting your ISP.

 

George

eForum Team

Hi, I have put a firewall log on all inbound and outbound traffic from my SureSignal and its not getting any response from 212.183.133.178:500 and if I ping it I don't get a response either - is this a VF problem or an Orange problem?

 

  Mar 30 15:02:32 home user.info kernel: PacketFilter: Forward UDP packet from [br0] 192.168.1.200:500 to 212.183.133.178:500
  Mar 30 15:02:36 home user.info kernel: PacketFilter: Forward UDP packet from [br0] 192.168.1.200:500 to 212.183.133.178:500
  Mar 30 15:02:48 home user.info kernel: PacketFilter: Forward UDP packet from [br0] 192.168.1.200:10008 to 135.245.1.1:33435
  Mar 30 15:02:48 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:48 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 135.245.1.1
  Mar 30 15:02:48 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:48 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 135.245.1.1
  Mar 30 15:02:49 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:49 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 213.1.113.12
  Mar 30 15:02:49 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:49 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 135.245.1.1
  Mar 30 15:02:49 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:49 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 135.245.1.1
  Mar 30 15:02:49 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:49 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 213.1.113.12
  Mar 30 15:02:49 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:49 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 135.245.1.1
  Mar 30 15:02:50 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:50 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 135.245.1.1
  Mar 30 15:02:50 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:50 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 213.1.113.12
  Mar 30 15:02:50 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:50 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 135.245.1.1
  Mar 30 15:02:50 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:50 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 135.245.1.1
  Mar 30 15:02:50 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:50 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 213.1.113.12
  Mar 30 15:02:51 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:51 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 135.245.1.1
  Mar 30 15:02:51 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:51 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 135.245.1.1
  Mar 30 15:02:51 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:51 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 213.1.113.12
  Mar 30 15:02:51 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:51 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 135.245.1.1
  Mar 30 15:02:51 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:51 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 135.245.1.1
  Mar 30 15:02:52 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:52 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 213.1.113.12
  Mar 30 15:02:52 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:52 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 135.245.1.1
  Mar 30 15:02:52 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:52 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 135.245.1.1
  Mar 30 15:02:52 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:52 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 213.1.113.12
  Mar 30 15:02:52 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:52 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 135.245.1.1
  Mar 30 15:02:53 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:53 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 135.245.1.1
  Mar 30 15:02:53 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:53 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 213.1.113.12
  Mar 30 15:02:53 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:53 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 135.245.1.1
  Mar 30 15:02:53 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:53 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 135.245.1.1
  Mar 30 15:02:53 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:54 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 213.1.113.12
  Mar 30 15:02:54 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:54 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 135.245.1.1
  Mar 30 15:02:54 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:54 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 135.245.1.1
  Mar 30 15:02:54 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:54 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 213.1.113.12
  Mar 30 15:02:54 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:54 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 135.245.1.1
  Mar 30 15:02:54 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:55 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 135.245.1.1
  Mar 30 15:02:55 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:55 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 213.1.113.12
  Mar 30 15:02:55 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:55 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 135.245.1.1
  Mar 30 15:02:55 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:55 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 135.245.1.1
  Mar 30 15:02:55 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:55 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 213.1.113.12
  Mar 30 15:02:55 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:56 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 135.245.1.1
  Mar 30 15:02:56 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:56 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 135.245.1.1
  Mar 30 15:02:56 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:56 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 213.1.113.12
  Mar 30 15:02:56 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:56 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 135.245.1.1
  Mar 30 15:02:56 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:56 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 135.245.1.1
  Mar 30 15:02:56 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:57 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 213.1.113.12
  Mar 30 15:02:57 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:57 home user.info kernel: PacketFilter: Forward UDP packet from [br0] 192.168.1.200:500 to 212.183.133.178:500
  Mar 30 15:02:57 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 135.245.1.1
  Mar 30 15:02:57 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:57 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 135.245.1.1
  Mar 30 15:02:57 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:57 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 213.1.113.12
  Mar 30 15:02:57 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:57 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 135.245.1.1
  Mar 30 15:02:57 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:58 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 135.245.1.1
  Mar 30 15:02:58 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:58 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 213.1.113.12
  Mar 30 15:02:58 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:58 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 135.245.1.1
  Mar 30 15:02:58 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:58 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 135.245.1.1
  Mar 30 15:02:58 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:58 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 213.1.113.12
  Mar 30 15:02:58 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:59 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 135.245.1.1
  Mar 30 15:02:59 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:59 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 135.245.1.1
  Mar 30 15:02:59 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:59 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 213.1.113.12
  Mar 30 15:02:59 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:59 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 135.245.1.1
  Mar 30 15:02:59 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:02:59 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 135.245.1.1
  Mar 30 15:02:59 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:03:00 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 213.1.113.12
  Mar 30 15:03:00 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:03:00 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 135.245.1.1
  Mar 30 15:03:00 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:03:00 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 135.245.1.1
  Mar 30 15:03:00 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:03:00 home user.info kernel: PacketFilter: Forward ICMP packer from [br0] 192.168.1.200 to 213.1.113.12
  Mar 30 15:03:00 home user.info kernel: PacketFilter: Forward ICMP packer from [ppp_0_0_38_1] 213.1.113.12 to 192.168.1.200
  Mar 30 15:03:20 home user.info kernel: PacketFilter: Forward UDP packet from [br0] 192.168.1.200:500 to 212.183.133.178:500
  Mar 30 15:04:02 home user.info kernel: PacketFilter: Forward UDP packet from [br0] 192.168.1.200:500 to 212.183.133.178:500
  Mar 30 15:05:24 home user.info kernel: PacketFilter: Forward UDP packet from [br0] 192.168.1.200:500 to 212.183.133.178:500
  Mar 30 15:05:28 home user.info kernel: PacketFilter: Forward UDP packet from [br0] 192.168.1.200:500 to 212.183.133.178:500
  Mar 30 15:05:35 home user.info kernel: PacketFilter: Forward UDP packet from [br0] 192.168.1.200:500 to 212.183.133.178:500
  Mar 30 15:05:48 home user.info kernel: PacketFilter: Forward UDP packet from [br0] 192.168.1.200:500 to 212.183.133.178:500
  Mar 30 15:06:11 home user.info kernel: PacketFilter: Forward UDP packet from [br0] 192.168.1.200:500 to 212.183.133.178:500
  Mar 30 15:06:53 home user.info kernel: PacketFilter: Forward UDP packet from [br0] 192.168.1.200:500 to 212.183.133.178:500
  Mar 30 15:08:15 home user.info kernel: PacketFilter: Forward UDP packet from [br0] 192.168.1.200:500 to 212.183.133.178:500
  Mar 30 15:08:19 home user.info kernel: PacketFilter: Forward UDP packet from [br0] 192.168.1.200:500 to 212.183.133.178:500
  Mar 30 15:08:26 home user.info kernel: PacketFilter: Forward UDP packet from [br0] 192.168.1.200:500 to 212.183.133.178:500
  Mar 30 15:08:39 home user.info kernel: PacketFilter: Forward UDP packet from [br0] 192.168.1.200:500 to 212.183.133.178:500
  Mar 30 15:09:02 home user.info kernel: PacketFilter: Forward UDP packet from [br0] 192.168.1.200:500 to 212.183.133.178:500
  Mar 30 15:09:44 home user.info kernel: PacketFilter: Forward UDP packet from [br0] 192.168.1.200:500 to 212.183.133.178:500

I'm working at home today and noticed my SS has stopped working (after 6 months of working fine).

Steady power light.

Lights on on the Ethernet port (green steady, orange blinking)

I followed the intructions at the start of this post - no joy.

Logging into the router shows the SS in the Attached Devices as having an IP.

 

Router = Netgear DG834G

SS

 

Is there somebody I can phone?

 

Mark

 

nsimmo,

 

have you been able to resolve your issue with the VSS + Orange broadband successfully?

 

I have been trying to get this to work for me for weeks and after replacements and resets, port forwards and telephone calls, I am no further than when I started. :Sad_face:

 

Your firewall logs at least show that your getting responses from VF servers to your VSS. Mine only show traffic from my VSS to VF servers, so I had put this down to Orange blocking the traffic from VF to me, but until I can get someone from VF to test this, how would I know?

Woody/eForum team,

 

I had already set up port forwarding, as described in my first post on this forum (Re: Sure Signal - Flashing/Steady Power Light, No ... - ( 14-03-2011 06:01 PM ), including the screen shots of the router settings so that VF could take a look and comment on them since it still wasn't work then or now.

 

I have looked at post 5 in this forum and I'm not 100% sure of the instructions because the person isn't using the same router as me (a NETGEAR DGN1000, again as described in my first post and not an Orange LIVEBOX as in the 5th post), but I have tried, as directed, to remove the existing port forwarding rules I had set up, and use the ones from the 5th post (see attached new port forwarding rules and router settings).

 

Woody/eForum team, can you take a look at these and tell me categorically if these settings are correct, please.

 

Unfortunately, the issue is still the same - the VSS is still not working and only the flashing the power light is lit, after a reset, and leaving for 48 hours, of course.

 

In the firewall logs, there is plenty of traffic from the VSS to VF (to 212.183.133.177, 212.183.133.178, 212.183.133.179  on port 500), but nothing from VF to the VSS on any of the forwarded ports.

 

I am curious as to why I do not see any traffic from VF servers to my VSS and was wondering if VF could try and test this connectivity for me so I can go to ORANGE and give them the exact problem to solve.

 

 

Dear Technical team

I posted here two days ago (on the other thread) about the loss of signal to our Vodafone Gateway (pre-dates Sure Signal gadget). We had really poor responses to our numerous phone calls to Vodafone (I spent a whole day trying to resolve it), twice whilst we were trying to politely explain the problem the phone was put down on us (presumably we were taking up too much contact time with the phone operatives) and we were then given a ridiculous explanation of "insufficient upload speed" from BT, our ISP. I called BT and they were incredulous, they said we had an upload speed of 448, not the 0.31 stated by someone in your second line technical support team. We have used this Gateway for over two years and absolutely nothing has changed in respect of our internet provider or our internet usage, and our internet is working perfectly. We got BT to check that the ports were open etc etc, still no signal.

So what happens now? Are we going to be left like this, with no phone in a rural area, when we have clients trying to call us? After over 20 years of being with Vodafone with an expensive monthly contract (same applies to my partner), we will definitely be going elsewhere as soon as our contract terms are up. We have had the worst customer service I can remember from any provider of any service.

At the end of my day of phone calls, I asked for someone to call me so that i could make a complant - and guess what, no-one has bothered to do so. It's a disgrace, Vodafone, you've had many thousands of pounds from us over the years and when we need some help we are just ignored.