Page 1 of 1
Command line update 3.x key to 4.x key
Posted: Thu Jun 03, 2010 5:46 pm
by ejmerkel
I am batch programming a bunch of 411's and upgrading them from 3.x to 4.x during the process. After the unit reboots, it will automatically connect to the Internet.
My question is, is there a way to automate the license update from 3.x to 4.x via the command line without logging into Winbox?
Thanks,
Eric
Re: Command line update 3.x key to 4.x key
Posted: Fri Jun 04, 2010 11:11 am
by sergejs
Currently there is no way to do it by script.
Re: Command line update 3.x key to 4.x key
Posted: Fri Jun 04, 2010 11:23 am
by normis
This is not possible, because the update is not done by RouterOS, but by Winbox from the PC. Router doesn't need internet connectivity to do the update,.
Re: Command line update 3.x key to 4.x key
Posted: Fri Jun 04, 2010 12:26 pm
by ejmerkel
I assumed it needed internet access because when I do the updates via winbox it resolves the mikrotik.com site and pulls the new license. How is this done offline?
Re: Command line update 3.x key to 4.x key
Posted: Fri Jun 04, 2010 4:13 pm
by fewi
The client running Winbox pulls the license data from mikrotik.com, _NOT_ the router. So you could have a laptop dual homed on the wire and wireless, with an internet connection on the wireless and a standalone router - and update the license. But because the client itself pushes the license you cannot script the license upgrade process. There is no process in the router itself that can upgrade a license from the router.
Re: Command line update 3.x key to 4.x key
Posted: Fri Jun 04, 2010 4:33 pm
by ejmerkel
Makes sense. Thanks for clarifying that!
Re: Command line update 3.x key to 4.x key
Posted: Sun Jun 06, 2010 11:37 pm
by changeip
sounds like a nice addition to the dude... this will be a major issue once routerboard licenses are required to be renewed (is that going to happen?)
Re: Command line update 3.x key to 4.x key
Posted: Mon Jun 07, 2010 7:36 am
by normis
sounds like a nice addition to the dude... this will be a major issue once routerboard licenses are required to be renewed (is that going to happen?)
it's already needed if you want to upgrade to v4 and have a 1234-123 type SoftID.