NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
AC800S Compatibility with Netgear Cradle DC112A
I have recently puchased the new AC800S (Optus) and I needed to boost the Wifi and the LTE signal so I puchased a DC112A (Firmware V1.0.0.30_1.0.60) which said it was compatable with most Aircards – However i'm aware this is a brand new Aircard. I've plugged the aircard into the dock and it seems to boost the 4G+ however it doesn't seem to intergrate at all with the Wifi capabilities with the dock. I checked for new Firmware updates for the DC112A however it says nothing is available. Any advice? Is there a way I can force them to pair or force it to use the Aircard's internet? Any help would be most appreciated.
Hi everbody, I can confirm that the cradle now works with the AC800s. A software update arrived today for the AC800s and straight after the update I put it in the cradle and all lights are green. Works great!
Good luck!
33 Replies
Does it actually work with AC800S?
Does anyone know how to setup?
Thanks
yes this aircard should work with the dock.
DarrenM
I know that it should work, however it doesn't work.
The Aircard doesn't recognise the base at all or bridge the wifi networks. It simply uses it as a charging station & potentially the LTE antenna works but I can't confirm this. Hopefully a fireware update will be out soon for either device.Hi DarrenM,
Do you have any more information on when the new firmware may be coming?
I also have the same AC800S OPTUS AIRCARD and Netgear DC112A Cradle. I have the same issue that the cradle wont recognise the Aircard.
It would be nice if Netgear would comment on our problems with compatability of the 800S ans DC112A cradle.
Will you be dipporting the combination? If yes when can we expect the upgraded firmware.
Will both devices need firmware upgrades?
Do you only support Telsta with your DC112A and not allowed to support Optus?
Thanks
I just bought the AC800s as well, and would like to buy something to boost the wifi signal at home. The dc112a cradle sounds perfect, but it seems like it doesn't support AC800s?
Hopefully a firmware update comes out soon, coz I'm ready to buy this cradle.
- Any updates on this? I have an AC800S and would like to buy the cradle but want to ensure it works...
No mate - I didn't see a Firmware update to get it working. It had no compatibility last time I checked with no updates to the Aircard from Optus or from Netgear. Also noticed that the cradle firmware update system is a little rubbish and couldn't autocheck for new firmware - but I couldn't see firmware on any other Netgear sites.
Hi everbody, I can confirm that the cradle now works with the AC800s. A software update arrived today for the AC800s and straight after the update I put it in the cradle and all lights are green. Works great!
Good luck!
^ Oh wow, thanks Roccas for the update. So it is increasing both the 4G signal and the Wifi output correctly?
Guess I'll be ordering the cradle now!
Everything is working good. I just changed the settings on the AC800s to automatic for the cradle on the 192.168.5.1 web page before I put it on the cradle. All good!!
Does anyone have any idea where this update is coming from?
It isn't on the netgear support site. https://www.netgear.com/support/download/
One idea, if someone has the cradle working and an alternate internet route:
1. Configure the cradle to use 4G as fail-over.
2. Connect the cradle WAN to a PC.
3. Configure the PC to forward the ethernet from the cradle to an ethernet port with internet access (use masquerade or similar)
4. Run wireshark on the PC.
5. From the AC800s, check for software updates.
6. Review wireshark capture to identify the server it is communicating with.
Other observations from this cradle enabling firmware (NTG9X40C_11.14.08.31 r5419 ntgrbc-fwbuild4 2017/09/19 17:07:28):
Ubuntu now connects via USB port, previously the kernel baulked after the modem failed to respond to U1/U2 Power Management request.
With the new firmware, U1/U2 Power Management is still not implemented but the driver load continues. Possibly why the linux operated cradle couldn't connect to it.
Also with the previous firmware (NTG9X40C_11.14.08.17 r5297 ntgrbc-fwbuild4 2017/03/02 18:39:45):
AT commands could be issued by TELNET on 192.168.1.1:5510 (Non standard telnet port)
NVRAM was accessible using Qualcomm's QPST tool on 192.168.1.1:5511
With the new firmware the AT commands are still available at 5510 but the QPST access either isn't at 5511 or we need to knock somewhere else first.
TCP & UDP port scans fail to identify 5510 but do identify ports 53, 80 & 45179. 53 is DNS and 80 is the modem's web page, I haven't worked out what 45179 does but QPST won't connect to it.
