Ask
Reply
Solution
06-10-2010
02:19 PM
- last edited on
14-07-2014
03:42 PM
by
Jenny
We’ve created this thread to help with an issue that some people find during setup.
This issue has the following symptoms:
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:
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:
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
09-04-2011 03:10 PM
Hi trickster,
Thanks for posting. From looking at those screenshots, you don't appear to have port 500 listed but you've got port 8 listed twice. Can you try removing one of the Port 8 entries and replacing it with Port 500 (UDP)? Let me know if that makes any difference.
Isca, if it's suddenly stopped working then we may need to try a resync on the server. Please reply to the email I've just sent you and we'll be in touch as soon as we can.
jdanbreeze, I think we're going to need to take a closer look at yours too. Reply to the email I've sent you and we'll be in touch as soon as we can.
George
eForum Team
09-04-2011 05:41 PM
Hi George/eForum Team,
would that be port 500 UDP inbound, outbound or both?
If you check my first post to this forum, you'll see I *had* configured port 500, but since that didn't work, I was directed to the 5th post which doesn't include port 500! and had two entries for port 8.
We just keep going round in circles...
So, to keep you happy I will add both an inbound and outbound port 500 UDP, reset the VSS and wait another 48 hours...
09-04-2011 06:01 PM
Actually George, there already is a standard service defined in my NetGear DGN1000 ("VPN-IPSEC") which is for port 500, UDP (see attached screenshot).
So, when you look at the original services settings, you'll find that there is already a firewall rule allowing UDP traffic outbound on port 500 from my VSS to 212.183.133.177-212.183.133.182.
For completeness, since you didn't mention it specifically, I've added an inbound rule using the same service, see the updated attached list of firewall rules.
Now to reboot the router and reset the VSS...
10-04-2011 03:42 PM
10-04-2011 10:09 PM
Hi Benj/eForum Team,
OK, so I added another firewall rule for port 500, TCP, inbound and outbound, reset the router, and reset the VSS.
The first packet out of the VSS once it starts communicating is a UDP Packet - Source:192.168.1.11,500 Destination:212.183.133.178,500 - [VPN-IPSEC rule match].
However, if I try and tracert or pathping this address, there is a 100% packet loss inside Vodafone's own network and so the VSS can't ever get to the destination address!
C:\tracert 212.183.133.178
Tracing route to 212.183.133.178 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 25 ms 25 ms 25 ms 213.1.113.132
3 27 ms 26 ms 26 ms 213.1.120.14
4 33 ms 32 ms 32 ms 213.1.78.42
5 33 ms 32 ms 32 ms 213.1.79.2
6 32 ms 32 ms 32 ms 87.237.20.244
7 36 ms 36 ms 34 ms bundle-ether1.lontr1.London.opentransit.net [193.251.255.101]
8 45 ms 44 ms 44 ms xe-0-0-1-0.ffttr2.Frankfurt.opentransit.net [193.251.129.41]
9 120 ms 50 ms 50 ms tengige0-3-0-0.ffttr1.FrankfurtAmMain.opentransit.net [193.251.242.254]
10 47 ms 46 ms 45 ms te4-4-10g.ar4.fra3.gblx.net [64.208.110.225]
11 63 ms 62 ms 63 ms VODAFONE-LTD.TenGigabitEthernet7-1.ar6.LON3.gblx.net [64.214.144.122]
12 * * * Request timed out.
13 * * * Request timed out.
etc.
C:\pathping 212.183.133.178
Tracing route to host212-183-133-178.uk.access.vodafone.net [212.183.133.178] over a maximum of 30 hops:
0 [192.168.1.3]
1 192.168.1.1
2 213.1.113.132
3 213.1.120.14
4 213.1.78.42
5 213.1.79.2
6 87.237.20.244
7 bundle-ether1.lontr1.London.opentransit.net [193.251.255.101]
8 xe-0-0-1-0.ffttr2.Frankfurt.opentransit.net [193.251.129.41]
9 tengige0-1-5-0.ffttr1.FrankfurtAmMain.opentransit.net [193.251.129.34]
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 300 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 [192.168.1.3] 0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1 0/ 100 = 0% |
2 25ms 0/ 100 = 0% 0/ 100 = 0% 213.1.113.132 0/ 100 = 0% |
3 29ms 0/ 100 = 0% 0/ 100 = 0% 213.1.120.14 0/ 100 = 0% |
4 --- 100/ 100 =100% 100/ 100 =100% 213.1.78.42 0/ 100 = 0% |
5 --- 100/ 100 =100% 100/ 100 =100% 213.1.79.2 0/ 100 = 0% |
6 35ms 0/ 100 = 0% 0/ 100 = 0% 87.237.20.244 0/ 100 = 0% |
7 36ms 0/ 100 = 0% 0/ 100 = 0% bundle-ether1.lontr1.London.opentransit.net [193.251.255.101] 0/ 100 = 0% |
8 49ms 0/ 100 = 0% 0/ 100 = 0% xe-0-0-1-0.ffttr2.Frankfurt.opentransit.net [193.251.129.41] 0/ 100 = 0% |
9 51ms 0/ 100 = 0% 0/ 100 = 0% tengige0-1-5-0.ffttr1.FrankfurtAmMain.opentransit.net [193.251.129.34] 0/ 100 = 0% |
10 55ms 0/ 100 = 0% 0/ 100 = 0% te4-4-10g.ar4.fra3.gblx.net [64.208.110.225] 0/ 100 = 0% |
11 63ms 0/ 100 = 0% 0/ 100 = 0% VODAFONE-LTD.TenGigabitEthernet7-1.ar6.LON3.gblx.net [64.214.144.122] 100/ 100 =100% |
12 --- 100/ 100 =100% 0/ 100 = 0% [0.0.0.0]
Trace complete.
The same is true of all of the other addresses I've been asked to create firewall rules for on the router, namely 212.183.133.177 - 212.183.133.183.
So, VF, can you explain the reason why this is happening and if there is a problem with the VF network that is preventing my VSS from working?
The two IP addresses shown in the pathping above which show 100% packet loss before getting to the Vodafone network belong to BT - 213.1.78.42 and 213.1.79.2. Is there anything in these that needs investigation, since after them, pathping is able to continue to Vodafone?
Richard
15-12-2014 01:17 PM
OK, here we go.
I have a VSS mark 1. It's been working flawlessly for about 9 months and has suddenly decided to revert to just a steady power light.
I've been through the recommended trouble shooting steps as requested, so I have:
1. Checked the ethernet cable fine
2. Checked Internet Connection - fine
3. Checked Speed - 25 Mbps
4. Checked IP address issued - yes it is.
5. Checked MTU - was set to 1480. Setting to 1500 makes no difference.
6. Have hard reset the VSS several times.
So, as requested, the serial No is:
21196982876
My router is a TP Link
N600 Wireless Dual Band Gigabit ADSL2+ Modem Router
Model No. TD-W8980
Its configured as wireless router only, as we have had Plusnet FTTC since Sept, so there is Plusnet supplied fibre modem to which the router is attached.
I've also run a trace route with the following result:
Traceroute to 212.183.133.177 (212.183.133.177), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 3.974 ms 2.254 ms 2.275 ms
2 lo0.10.central10.ptw-bng02.plus.net (195.166.130.203) 27.980 ms 28.928 ms 27.915 ms
3 irb.10.ptw-cr02.plus.net (84.93.249.2) 28.030 ms
irb.10.ptw-cr01.plus.net (84.93.249.1) 30.923 ms
irb.10.ptw-cr02.plus.net (84.93.249.2) 28.431 ms
4 lndgw2.arcor-ip.net (195.66.224.124) 31.409 ms 34.800 ms
ae2.ptw-cr01.plus.net (195.166.129.4) 59.235 ms
5 85.205.0.93 (85.205.0.93) 30.482 ms
lndgw2.arcor-ip.net (195.66.224.124) 31.039 ms 29.727 ms
6 85.205.0.93 (85.205.0.93) 29.513 ms * *
7 * * *
8 * * *
9 * * *
1
I look forward to hearing from you.
Best regards
19-12-2014 10:45 AM
Hi @Buckham
I'm sorry for the delay in replying.
Please can you supply your IP address?
Your Sure Signal connected to our servers last night.
Please see the following port numbers that need to be forwarded to your Sure Signal's internal IP address.
Ports and Protocols:
Hi @runrep
I'm pleased things are sorted for you.
Thanks,
Ian
19-12-2014 12:04 PM - edited 19-12-2014 12:07 PM
I have copy and paste this from my own thread but as it seems no VF personnel is actively looking at individual thread so here we go and hopefully I will get some attentions:
My SSV1 has stop working, i have had a vodafone tech guy on the phone instructing me to test the unit without success, he suggests i try asking here so...
i have just renewed 2 contracts and then the sure signal goes down, I haven't been able to buy a new one from any of your stores near by so I am in a bit of a trouble, if I can't get it to work then I will have to cancel the 2 contracts within the 14 days cooling period, end date is 26th friday and that thursday 25th and friday 26th being holiday too....
anyway....
serial number: 21231090248
ip:212.159.113.119
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\>tracert 212.183.133.177
Tracing route to cluster4.vap.vodafone.co.uk [212.183.133.177]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.1
2 32 ms 31 ms 32 ms lo0-central10.pcl-ag01.plus.net [195.166.128.182
]
3 149 ms 138 ms 72 ms link-a-central10.pcl-gw01.plus.net [212.159.2.16
0]
4 100 ms 97 ms 74 ms xe-10-0-0.pcl-cr01.plus.net [212.159.0.192]
5 54 ms 53 ms 60 ms ae1.ptw-cr01.plus.net [195.166.129.0]
6 32 ms 35 ms 34 ms lndgw2.arcor-ip.net [195.66.224.124]
7 32 ms 34 ms 34 ms 85.205.0.93
8 * * * Request timed out.
9 * * * Request timed out.
20-12-2014 01:13 PM
After the umpteenth hard reset it's now decided to start working again. You can't live with it sometimes, but then you can't live without a signal....#miracle
21-12-2014 02:01 PM
Hi @ramontam,
Please try a reset of the Sure Signal by following the steps below:
Thanks,
Matt B