cancel
Showing results for 
Search instead for 
Did you mean: 
1

Ask

2

Reply

3

Solution

SureSignal Not Working on our IP Range

craigbrass
4: Newbie

Hello,

 

We are a wireless and fibre optic broadband ISP that has recently started connecting customers to one of our networks. When connecting one customer, we tried to move over their SureSignal box to our connection but it is refusing to connect to your systems.

 

The range is 149.5.110.0/23 (149.5.110.1-149.5.111.254).

 

I think I know what the problem is. These IPs only were recently put in our name by Cogent and previously showed up as being in the USA. WHOIS now shows as being in the UK :-

- - - - - - - -

[root@gandalf ~]# whois 149.5.110.1
[Querying whois.arin.net]
[Redirected to rwhois.cogentco.com:4321]
[Querying rwhois.cogentco.com]
[rwhois.cogentco.com]
%rwhois V-1.5:0010b0:00 rwhois.cogentco.com
149.5.110.1
network:ID:NET4-95056E0017
network:Network-Name:NET4-95056E0017
network:IP-Network:149.5.110.0/23
network:Tech-Contact:ZC108-ARIN
network:Updated:2011-11-03 13:07:44
network:Updated-by:Bill Garrison

- - - - - - - -

 

All that I get is a red light on the newer style SureSignal device.

 

Can one of the staff here please speak to your network guys to get this range updated ASAP please?

 

Trace Route just in case :-

- - - - - - - -

Tracing route to 212.183.133.181 over a maximum of 20 hops

 1    5ms    5ms    5ms    10.0.0.1
 2 16ms    6ms    6ms    149.6.10.25
 3 11ms 10ms 10ms    130.117.1.165
 4 11ms 12ms 12ms    130.117.50.217
 5 13ms 11ms 13ms    154.54.57.61
 6 13ms 18ms 12ms    64.208.110.109
 7 12ms 14ms 12ms    67.17.72.22
 8 31ms 30ms 28ms    67.17.78.13
 9 29ms 28ms 29ms    64.213.33.210
10 47ms 47ms 48ms    85.205.116.6
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.

Trace complete.

- - - - - - - -

 

Best Regards,

Craig Brass

44 REPLIES 44

Hi craigbrass,

 

From what I can see, the entire range is on the whitelist.

 

If there are any particular examples within the range that you are having trouble with please let me know so we can get them checked in more detail for you.

 

However, the issues that they are having may also be down to firewall or port settings on the routers causing the Sure Signal to be unable to create the required VPN connection.

 

James

Thanks for the reply James. 192.175.42.20 is one user in particular who is having problems.

Hi craigbrass,

 

I have just checked this for you and this particular IP address is fine and on the whitelist.

 

Due to this it would lead me to believe that the issue is either to do with the internet connection (speed or ping) or the setup that they are using.

 

Can you confirm that there isn’t anything in the network firewall that is stopping these from connecting?

 

Are you able to test the Sure signals away from your network on a different connection to verify that it is definitely not a faulty Sure Signal that is causing the issue?

 

James

185.149.208.0/22 is also not working. Can you add please?

Mark
Community Manager
Community Manager

@craigbrass

 

I've checked the IP address provided (185.149.208.0/22) unfortunately, the address has been listed in an incorrect format. Please re-confirm the address so we can request it's added to our whitelist.

 

Thanks.