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

Nabs
17: Community Champion
17: Community Champion

Hi Craig Brass,

 

It looks like you ahve posted all the info required. one of the Vodafone Team should pick up this thread and be able to pass on the details to the network team.

 

Sit tight, they are a small team so may take a little while to get to this post but they will get here.

grolschuk
Community Champion (Retired)
Community Champion (Retired)
I am not sure if the new SureSignal2 boxes handle this any better, but we were tying to get our original devices connected to a non /24 subnet and failed after weeks of configuration changes and calls to tech support.

As there were no IP Config pages for it, everything had to be assigned by DHCP... connecting to a 'home' ADSL modem worked fine. Putting on our public address range did not.
It will be interesting to see if this now a supported setup.

Hi

I have the same problem and my business is suffering as our mobile will not work any longer with suresignal boxes because of the ip range with our new service provider

any news please :smileysad:

Retired-George
Moderator (Retired)
Moderator (Retired)

Hi craigbrass,

 

Firstly, a very warm welcome to the eForum :).

 

As this IP range was previously registered in the USA, then the chances are that it's not allowed through our firewall. I've fired an email across to the Sure Signal team so that this can be added to the whitelist. I'll let you know when I've heard back.

 

Kind Regards,

 

George.

Any update? There are a few of our customers using these SureSignal boxes...

Well done very good

Hey craigbrass,

 

I'm afraid we've not heard anything yet so I've sent a follow up to George's email.

 

I'll come back as soon as I hear anything.

 

Cheers,

 

Lee

Hi Tech team
Have you forgot about us poor souls :Sad_face:

Hi Guys,

 

Unfortunately we still don't have an update on this for you however we will continue to chase our support teams for an update.

 

James