02-04-2012 03:38 PM
Can one of the support team advise whether the Sure Signal Network Setup Guide has been updated since it's v1 - as available through the SureSignal website.
We've currently got 2 SureSignal's on our corporate network, one of which hasn't made a connection to Vodafone's systems in weeks (mildly annoying but not really a problem), the other (which is now a problem) dropped its connection at the end of last week. We've run through the troubleshooting guides, reset the devices on a few occasions & I've de/re-registered one of them with no apparent success. While I can "see" the devices on our network and see them trying to connect to Vodafone they just don't want to get the secure connection up and running.
Within the Network Setup Guide v1 the only IP addresses we need to make sure are allowed through our security systems are in the 212.183.x.x range. A bit of work tracing messages from the SureSignal boxes on our network shows that they are trying to connect to a different series of (Vodafone) IP addresses, hence the query. So, If there is an updated network setup guide available, or just an updated list of IP addresses that the SureSignal's try to contact, it would be appreciated.... or if someone needs to resync/straighten our two devices out, that'd also be appreciated!
Solved! See solution
04-04-2012 08:05 AM
Thanks for your post here and welcome to the Vodafone eForum from all of the team.
When it comes to the setup of the two versions of the Sure Signal, the process is the same however; it is only the troubleshooting guides that are slightly different for each version of Sure Signal.
So that we can help you with your query please can you let me know what light sequence you are seeing on each Sure Signal and also let me know the serial numbers so I can check the registrations for you.
04-04-2012 05:46 PM
The two devices are serials 21196851048 & 21232183018 & are both the earlier version of the device. Both are showing just the power light permanently on (as they still are after resets), internet (@) light occasionally slow flashing & the bottom light occasionally slow flashing as well.
05-04-2012 09:30 AM
I have had a support call logged with our Firewall Vendor.
This might help, equally well it might not.
We have a watchguard firewall. See below for working/not working configs.
1. ADSL - MODEM - FIREWALL PPPoE - SureSignal = Doesnt work
2. ADSL - ROUTER PPPoA - Firewall - works
What I have found through the help somewhere else on this site is that MTU has something to do with it. I have altered how our connections work when using option 1 (my preferred choice as less config if adsl modem goes faulty) and now have a working sure signal.
Might be of use, I spent a month on it........
10-04-2012 11:02 AM
OK, have run through the Troubleshooting and as you may guess, the 2 devices are still misbehaving and stuck on solid power light, with occasional bursts of flashing from light 2 & 4 (separately).
Physical connections to the devices are fine & general internet access is also OK, the SureSignal has a valid IP address and I can see it on our network. It's had a couple of days since it's last reset, I've not seen any sign of planned maintenance to affect service, I've removed and re-registered it (last week) and that went as smoothly as when I originally ran through this and our firewall is setup the same way (specifically including the IP addresses and ports noted) as it was when they went in months ago and were working.
My problem appears to be that the SureSignal serial 211968851048 was actually trying to establish a VPN connection with hostname "cluster12.vap.vodafone.co.uk" on IP addresses 188.8.131.52/178/179 (as seen from some network debug tools) rather than the addresses noted in the troubleshooting or network setup guide. Hence my original query to see if the network setup guide was still correct or had been added to.... Our firewall isn't setup to allow a connection to those addresses, hence the VPN connection won't get going.
Hi Rich, I kinda wish that ADSL was involved here, it'd simplify things a lot compared to the pretty huge network the VSS's are attached to!
10-04-2012 12:11 PM
Well, 88.82.13.* is a valid VF address range, and if SSs are now attempting to open VPNs through servers within that range I suspect that you'd better allow that too.
The original set-up guide is certainly out of date - VF have added much more capacity / many more servers since then - and the two lists contained within the troubleshooting area are different, though I suspect that the actual IP requirements for V1 and V2 SSs are identical.
I don't have the network monitoring capability to check what my SS is actually doing here - I'm running entirely plug-and-play - so I can't help much more I'm afraid. But if VF have updated the ranges that are being used, it might be a good idea [for VF] to update the requirements lists for those who do need to forward ports.
10-04-2012 05:03 PM
I agree with your comments & am pretty sure they will be correct. I'm not likely to get our security team to buy into such changes without confirmation from Vodafone that this is actually correct though.....
Any assistance from VF eforum staff would be appreciated!
11-04-2012 02:32 PM - edited 11-04-2012 02:32 PM
13-04-2012 11:23 AM
Ok, not exactly the positive confirmation I was expecting 'cos I'm still not quite sure what to make of the last response!
Given a lack of solid info & hoping our devices aren't trying to connect to some random site somewhere, we've added the following addresses into our firewall rules and the SS boxes made the VPN connection and came back to life soon afterwards. The additional IP addersses (and DNS names) I've spotted from a bit of investigation are:
cluster12.vap.vodafone.co.uk - 184.108.40.206, 220.127.116.11 & 18.104.22.168 - which is what ours have been trying to connect to.
cluster14.vap.vodafone.co.uk - 22.214.171.124, 126.96.36.199 & 188.8.131.52 - which I've spotted in our DNS cache but I don't think we've tried connecting to ...
Until next time!