Back to Help and Support
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
1

Ask

2

Reply

3

Solution

VSS1 not working since ISP change

shgoodman
4: Newbie

‎17-01-2017 09:42 AM

Hi,

 

Please can you check what's up with my VSS? It has not worked since changing ISP on Friday. I've completed the template below.

 

Thanks.

 

Stephen

 

 

----------------------------------------------TEMPLATE--------------------------------------------

 

The issue you’re experiencing:

 

I changed ISP on Friday and my router changed to a Meraki MX60. I’ve opened the required ports and I got an email from VF on Saturday night saying that you had seen a location change. I went into the portal and reset the postcode. When I do a packet trace I can see communication between the VSS and the NTP server and to another server: cluster13.vap.vodafone.co.uk. See trace below.

 

I therefore know that my VSS is connected to the internet and communicating with VF’s servers but I am not getting any service.

 

What light sequence you're seeing:

 

Power light is on and steady. Service light flashes slowly four or five times every ten minutes or so.


Speed test results: Download = 38.25Mbps, Upload 9.95Mbps

My external IP address: 81.149.149.240

 

My Sure Signal serial number: 21196773366

 

The results of a traceroute.

 

traceroute to 212.183.133.177 (212.183.133.177), 30 hops max, 38 byte packets

 1  host81-134-160-1.in-addr.btopenworld.com (81.134.160.1)  9.394 ms  8.785 ms  8.917 ms

 2  213.120.178.141 (213.120.178.141)  9.535 ms  9.395 ms  9.439 ms

 3  213.120.177.98 (213.120.177.98)  9.682 ms  9.782 ms  10.192 ms

 4  213.120.178.67 (213.120.178.67)  10.180 ms  12.599 ms  9.785 ms

 5  217.41.168.107 (217.41.168.107)  10.903 ms  10.956 ms  10.133 ms

 6  acc1-10GigE-0-7-0-5.l-far.21cn-ipp.bt.net (109.159.249.86)  9.737 ms  109.159.249.114 (109.159.249.114)  10.474 ms  acc1-10GigE-0-7-0-4.l-far.21cn-ipp.bt.net (109.159.249.74)  10.278 ms

 7  core3-te0-10-0-26.faraday.ukcore.bt.net (109.159.249.53)  10.338 ms  core3-te0-0-0-19.faraday.ukcore.bt.net (109.159.249.43)  10.058 ms  core4-te0-10-0-18.faraday.ukcore.bt.net (109.159.249.9)  10.262 ms

 8  213.121.193.199 (213.121.193.199)  11.005 ms  host213-121-193-189.ukcore.bt.net (213.121.193.189)  10.692 ms  10.772 ms

 9  t2c3-et-7-3-0-0.uk-lon1.eu.bt.net (166.49.211.230)  10.100 ms  t2c3-et-3-1-0-0.uk-lon1.eu.bt.net (166.49.211.236)  10.938 ms  t2c3-et-7-3-0-0.uk-lon1.eu.bt.net (166.49.211.230)  10.442 ms

10  166-49-211-254.eu.bt.net (166.49.211.254)  10.358 ms  10.268 ms  10.872 ms

11  *  *  *

 

Packet trace results

 

 

09:35:41.446648 IP 192.168.128.12.10232 > 208.67.222.222.53: 17334+ A? cluster13.vap.vodafone.co.uk. (46)

09:35:41.462446 IP 208.67.222.222.53 > 192.168.128.12.10232: 17334 3/0/0 A 88.82.13.175, A 88.82.13.168, A 88.82.13.172 (94)

09:35:41.469544 IP 192.168.128.12.12060 > 208.67.222.222.53: 2981+ A? initial-ipsecrouter.vap.vodafone.co.uk. (56)

09:35:41.480063 IP 208.67.222.222.53 > 192.168.128.12.12060: 2981 5/0/0 A 212.183.131.131, A 212.183.133.179, A 88.82.13.179, A 88.82.13.171, A 212.183.131.139 (136)

09:35:41.491723 IP 192.168.128.12.10749 > 208.67.222.222.53: 33514+ A? cluster13.vap.vodafone.co.uk. (46)

09:35:41.501751 IP 208.67.222.222.53 > 192.168.128.12.10749: 33514 3/0/0 A 88.82.13.168, A 88.82.13.172, A 88.82.13.175 (94)

09:35:41.507181 IP 192.168.128.12.12135 > 208.67.222.222.53: 21612+ A? cluster13.vap.vodafone.co.uk. (46)

09:35:41.518938 IP 208.67.222.222.53 > 192.168.128.12.12135: 21612 3/0/0 A 88.82.13.168, A 88.82.13.172, A 88.82.13.175 (94)

09:35:41.525599 IP 192.168.128.12.11459 > 208.67.222.222.53: 22580+ A? initial-ipsecrouter.vap.vodafone.co.uk. (56)

09:35:41.536332 IP 208.67.222.222.53 > 192.168.128.12.11459: 22580 5/0/0 A 212.183.131.131, A 212.183.133.179, A 88.82.13.179, A 88.82.13.171, A 212.183.131.139 (136)

 

09:36:00.723941 IP 192.168.128.12.500 > 88.82.13.172.500: isakmp: parent_sa ikev2_init[I]

09:36:00.737935 IP 88.82.13.172.500 > 192.168.128.12.500: isakmp: parent_sa ikev2_init[R]

09:36:01.567742 IP 192.168.128.12.4500 > 88.82.13.172.4500: NONESP-encap: isakmp: child_sa  ikev2_auth[I]

09:36:05.570572 IP 192.168.128.12.4500 > 88.82.13.172.4500: NONESP-encap: isakmp: child_sa  ikev2_auth[I]

 

----------------------------------------------TEMPLATE END--------------------------------------------

0 Thanks
2 REPLIES 2

Carly
Moderator (Retired)
Moderator (Retired)

‎17-01-2017 03:07 PM

@shgoodman

 

It looks like your Sure Signal's last contacted us on Saturday, although it hasn't done since.

 

I've now resynced it for you, please wait six hours then restart your phone in range of the Sure Signal.

 

Let us know how you get on.

0 Thanks

shgoodman
4: Newbie
In response to Carly

‎18-01-2017 02:14 PM

Thanks.

 

Closing the loop on this. It turns out that there is a limitation on my router which means I cannot open ports 500 and 4500 for the VSS. I've gone back to my old router and all is working now again.

0 Thanks