Ask
Reply
Solution
31-10-2011 08:00 AM - edited 31-10-2011 08:06 AM
Hi,
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 31.205.0.0/16
Thanks,
Jamie
26-03-2016 11:36 AM
@gommog - Please get back to us with the following information.
VSS Traceroute command
On a PC:
This will help us get the quickest possible resolution for you.
04-04-2016 03:25 PM
@Jenny
Thanks for your response but i've already included most of this information in post number 71 of this thread. As i've mentioned before we have a 50 Mbps leased line so no problems at all with out internet connection. Here are the results of the traceroute:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\gary.omalley>tracert 212.183.133.177
Tracing route to 212.183.133.177 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms csfw1.dca-design.com [192.168.10.250]
2 383 ms 158 ms 6 ms ser037528.ixhs.uk.exponential-e.net [5.148.142.1
7]
3 6 ms 5 ms 5 ms 2-1-2.cr01.ixhs.uk.exponential-e.net.london1.lev
el3.net [212.113.15.238]
4 6 ms 5 ms 6 ms xe-10-0-1.edge3.london1.level3.net [212.113.15.2
37]
5 6 ms 6 ms 6 ms 195.50.118.230
6 11 ms 6 ms 5 ms ae22-xcr1.lns.cw.net [195.2.30.61]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
As you can see traffic stops being passed at 195.2.30.61, this is a vodafone owned IP address so i'd suggest a problem with your internal routing and you need to get your network team involved. Thanks
05-04-2016 05:33 PM
I’ve just checked and I can see that your IP address still isn’t on our whitelist.
I’m sorry about the time that it’s taking for this to process.
I’ve chased the team responsible and will get in touch as soon as it’s done.
06-04-2016 08:59 AM
@Wayne
Is there much point doing this as the team responsbile for this will probably lie to you.
@Chazzd
You were certain this was checked
@DaveCD
You double checked this and was told our addresses were on the whitelist.
Now either all 3 of you lied to me or you're being given duff information from whichever team is responsible for this. This isn't the first time this has happened, the last time this happened to me was 5 years ago. This shows vodafone are doing nothing to recify this and don't care about me as a customer. If you'd like to send me a formal apology and something to compensate me for all the time i've wasted with this i'll consider resigning our vodafone contract in a few months, if not hello EE. You can find my email address in my account.
06-04-2016 12:14 PM
I’ve heard back from the team we escalated this to. They’ve confirmed that the IP addresses are on the whitelist, it just wasn’t updated on the database that we check. This has now been updated.
Traffic will stop at 192.2.30.61, as we block ICMP packets from entering our internal network.
Can you please let me know your Sure Signal serial number?
06-04-2016 12:16 PM
@Wayne
Thanks for the response, the serial number of the sure signal we're testing is 42152744084 but we have others that aren't working also.
08-04-2016 07:40 PM
Your Sure Signal’s aren’t making a connection to our servers at all.
There is nothing further we can check from our end here.
You’ll need to speak to your ISP for further assistance with this.
09-04-2016 03:29 PM - edited 09-04-2016 06:34 PM
I have tried everything else and so I thought I would check this. We are using a Sure Signal 1, port forwarding has been set, but it shows a power light, with the '@' light flashing. Eventually the '@' light goes steady and the 4th 'tick' light flashes for around 30/40 seconds. All the lights go out and the power light comes back on, the lights then cycle from top to bottom and then the whole cycle repeats. We are BT customers and our public IP address is in the 86.136.XXX.XXX range, can somebody tell me if this range is on your white list. Thanks
11-04-2016 08:42 AM
@Wayne
Great plan Wayne but what exactly should i ask my ISP? They're not blocking any traffic as the traceroute clearly shows traffic is reaching vodafone. Maytbe i should ask them if they have any experience with Vodafone's sure signal devices as vodafone themselves don't seem to.
I'm sorry Wayne but this is a complete cop out and the fact you're asking me to contact my ISP shows you have no understanding of how these devices work and how to troubleshoot them.
12-04-2016 11:07 AM - edited 12-04-2016 11:48 AM
Hello, is there anybody there that can help with my post????
I've completed a tracert....
Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Users\Mike>tracert 212.183.133.17
Tracing route to 212.183.133.17 over a maximum of 30 hops
1 <1 ms 1 ms 1 ms BThomehub.home
2 9 ms 10 ms 9 ms 217.32.145.2
3 9 ms 9 ms 10 ms 217.32.145.46
4 14 ms 13 ms 14 ms 212.140.235.202
5 13 ms 13 ms 13 ms 217.41.169.191
6 14 ms 14 ms 13 ms 213.120.179.83
7 15 ms 13 ms 13 ms acc2-xe-1-3-0.sf.21cn-ipp.bt.net [109.159.251.203]
8 20 ms 22 ms 22 ms core1-te-0-13-0-10.ilford.ukcore.bt.net [109.159.251.191]
9 20 ms 19 ms 20 ms peer1-xe10-0-0.redbus.ukcore.bt.net [62.6.200.81]
10 23 ms 21 ms 18 ms 195.66.224.209
11 20 ms 19 ms 20 ms 85.205.0.93
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
Can't understand why this ends at Vodafone in Germany (Dusseldorf)??????
Hope this helps you guys to sort this problem, thanks...