Welcome to Vodafone Community
We're a UK ISP who were recently assigned new IP ranges by RIPE and have noticed that customers on our new IP ranges are unable to use their Sure signal devices. This is presumably because our new IP's are being firewalled by yourselves. We have verified this by routing the same devices over our previous ranges, which enables them to connect fine.
If possible can you forward this range onto the relevent department or provide me with the details for somebody at Vodafone we can contact regarding this.
The affected range is 188.8.131.52/16
Sorry to jump on this thread, but could a mod also check if the following UK range is allowed?
184.108.40.206 - 220.127.116.11
Please add the above if it is not allowed currently.
Can somebody please provide an update on this? I'm a Business customer with multiple connections spending a considerable monthly amount in a complete signal not-spot. Being unable to use Sure Signal properly is extremely inconvenient.
I simply cannot get the Sure Signal to connect when using the IPs in the range 18.104.22.168 - 22.214.171.124. All other potential problems have been eliminated so I really need to know if this range is blocked and, if it is, if it can be opened up ASAP.
There's far too little information available about Sure Signal. Great when it's working, but when it's not troubleshooting is like a game of pin the tail on the donkey.
Our business is migrating to secure networks.
Please can the following be added:
Dear Team ?
Have written twice, now thrice, previously - no answer given to date. Not complaining if this is the level of service customers are supposed to expect. Other companies provide 'signal boost' and unfortunatly my voda contract is now up for grabs.
Am unable to connect over the company acces points which may need authorising:
126.96.36.199 - range
188.8.131.52 - range
If anyone at vodafone paying attention a response would be appreciated.
I've requested all of the above IP ranges to be checked against our whitelist and then added if required. At present I don't have a timescale for this as we're still ironing out an official process for this type of query. As soon as we know more though, we'll let you know.