While that would normally be true it won’t work for hAP lites from some versions of RouterOS (particularly 6.47.9). Somewhere in the 6.47s the OS started using too much RAM to be able to leave enough space for the upgrade image. The official response from Mikrotik is to NetInstall and with luck from 6.47.10 it will again fit. As far as I saw the hAP lite was the only affected device so it must be a combination of CPU arch and memory size being just a little too small. Cheers, Andrew
On 10 Aug 2021, at 11:58 am, Mike Everest <mike@duxtel.com> wrote:
Although hAP-lite does not have sufficient storage for the upgrade image, you can use 'upload' button on files menu which stores the file in volatile mem (just make sure to reboot not power cycle to install it ;) or use 'check for upgrades' on system->packages page.
Cheers! : )
-----Original Message----- From: Public [mailto:public-bounces@talk.mikrotik.com.au] On Behalf Of Andrew Radke Sent: Monday, 9 August 2021 1:38 PM To: kauer@nullarbor.com.au; MikroTik Australia Public List <public@talk.mikrotik.com.au> Subject: Re: [MT-AU Public] hAP Lite not hAP-pening...
Hi Karl,
The hAP lite doesn’t have enough space to upgrade to newer RouterOS from a few of the 6.47.x versions. You can reinstall via NetInstall to 6.47.10 and apparently there is just enough space to go up from there.
We only had two of them on our network and after arguing with them for a bit it was cheaper to swap them for hAP ac lites instead. As a bonus the hAP lites are good as test devices and an occasional net install for an upgrade is not an issue when it’s on my desk instead of a couple of hours away.
Cheers, Andrew
On 9 Aug 2021, at 6:31 am, Karl Auer <kauer@nullarbor.com.au> wrote:
I have a hAP Lite (RB941-2nD-TC). I went to upload an NPK file and found that I couldn't. scp fails with various errors, mostly "temporarily unavailable", and only about three-quarters of the file is copied. This is with a direct connection to a laptop.
The same cable works fine with other MikroTiks, the problem happens with other cables, the problem happens on ports 2,3 and 4, and the problem persists after a configuration reset. The problem is completely repeatable. The connection is not a complete failure - I can for example log in to the device over a cable and configure it.
It's a cheap device, so I don't want to spend too much time on it, but if this is a known issue with a quick fix it'd be nice :-)
Regards, K.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~
Karl Auer (kauer@nullarbor.com.au) work +61 2 64957435 http://www.nullarbor.com.au mobile +61 428 957160
GPG fingerprint: 9FB6 C08F 91CB 5093 30EF 3E2F 8C94 EEBD 117C 4A10 Old fingerprint: CF68 0C56 EEE4 CC19 28D4 03B3 BCE0 E800 E31F 7254
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com. au
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au
_______________________________________________ Public mailing list Public@talk.mikrotik.com.au http://talk.mikrotik.com.au/mailman/listinfo/public_talk.mikrotik.com.au