Cradlepoint MBR1400 for failover EDIT: Going with a peplink Balance 20

skyking

Lifer
Nov 21, 2001
22,635
5,743
146
I have a client who is in a one horse town when it comes to broadband. It is all DSL, and all down the same pipe no matter who the reseller is.
Have any of you used the cradlepoints connected to a verizon or other card for failover?
Verizon has it's own pipe, I confirmed that with traceroute and recent DSL failures. Verizon was up, the whole area was down due to some misguided backhoe work 100 miles away.
 
Last edited:

Gillbot

Lifer
Jan 11, 2001
28,830
17
81
I have a cradlepoint CTR350 with my blackberry and for grins, I hooked in my cable modem on the wan side for a failover test. Worked like a champ when I unplugged the cable modem. Blackberry connected right up and took over.
 

Gillbot

Lifer
Jan 11, 2001
28,830
17
81
Thank you sir! How has it been for reliability? longest uptime?

Honestly, I haven't tested it for uptime and reliability. I only used it for like an hour just to mess and see how well it worked, then I went back to my cable connection for better speed. I'll use it more when I travel, but I mainly got it for tethering to my blackberry so I can use it to connect my devices via Wi-Fi instead of hoping for a "secure/safe" Wi-Fi hot spot.

I was going to just grab a PHS300 but snagged this CTR350 from eBay for only $12 shipped. It has better features overall, but doesn't run on a battery like the PHS300 does, which really doesn't matter to me since I don't need the battery anyway.
 

skyking

Lifer
Nov 21, 2001
22,635
5,743
146
A quick update, I am going with a Peplink Balance 20 instead. I do not need another radio and it has a better feature set for what I am doing. Thanks again.
 

skyking

Lifer
Nov 21, 2001
22,635
5,743
146
thought I'd bring this up to date.
After a month of using the peplink 20, I'm not that impressed.
Issues:
1)It does not keep the 3G connected with any consistency. If I set it as "always on" both a verizon card and a sprint card would disconnect every 10 minutes to a couple of hours. Or 2 minutes. There was no rhyme or reason to it.
2) weak weak conventional network ports. I have a remote building on about 200' of cat5e, It has worked fine with a variety of network gear. I moved my network over there last night and tried to push internet back to the main building.
The peplink was not happy. no light, no traffic.
I had to go through another switch to make the jump.

All in all, I would give another company a try next time.
The good news is, the Ruckus wireless radios are the bomb!