On Wed, 2009-07-15 at 09:20 -0400, Josh Luthman wrote:
Using the Winbox created a system script with these commands:
Edited/attached.
--
* Butch Evans * Professional Network Consultation*
*
-Original Message-
From: mikrotik-boun...@mail.butchevans.com
[mailto:mikrotik-boun...@mail.butchevans.com] On Behalf Of Josh Luthman
Sent: Friday, July 17, 2009 10:13 AM
To: Mikrotik discussions
Subject: Re: [Mikrotik] Exporting and Importing system scripts
Kristian - that perl code will same
Kristian - that perl code will same my life time and time again =)
I tried it on 2.9.50 and 2.9.51 and 3.22 and 3.13
Simple export then import (just system scripts) and they all complained
about the syntax.
Kevin's code would complain it already exists, so the syntax is definitely
understood.
, July 17, 2009 10:13 AM
To: Mikrotik discussions
Subject: Re: [Mikrotik] Exporting and Importing system scripts
Kristian - that perl code will same my life time and time again =)
I tried it on 2.9.50 and 2.9.51 and 3.22 and 3.13
Simple export then import (just system scripts) and they all
I still run the problem of putting these two scripts and two schedules on
each of my MikroTiks without copying/pasting for every single router...
Josh Luthman
Office: 937-552-2340
Direct: 937-552-2343
1100 Wayne St
Suite 1337
Troy, OH 45373
When you have eliminated the impossible, that which
You can FTP the files over or use drag and drop with Winbox. Are there any
other ways to transport the files?
Casey
-- next part --
An HTML attachment was scrubbed...
URL:
http://www.butchevans.com/pipermail/mikrotik/attachments/20090716/2102513f/attachment.html
Enviado el: jueves, 16 de julio de 2009 16:49
Para: Mikrotik discussions
Asunto: Re: [Mikrotik] Exporting and Importing system scripts
You can FTP the files over or use drag and drop with Winbox. Are there any
other ways to transport the files?
Casey
-- next part --
An HTML
I can FTP the rsc no problem. The problem is that I can't execute commands
(use the CLI) to make the system scripts.
A simple system script export file=test.rsc will render test.rsc useless (by
the same router that just exported it).
Josh Luthman
Office: 937-552-2340
Direct: 937-552-2343
1100
Yea I could see how that would happen. If you ran the commands:
export file=test
import test.rsc
You would get all kinds of errors. You would be re-adding all the same IPs
to the same interfaces. You would need to do it in this order.
export file=test
system reset-configuration
Between Josh and I we got it working. I'm going to post the code on a
wiki, after it's posted I'll updated this thread.
-Kevin
On Thu, Jul 16, 2009 at 11:00 AM, Josh
Luthmanj...@imaginenetworksllc.com wrote:
On my 3.22 x86 home router
[jluth...@uberpwnage] /interface wireless exp
I see no
I think I'm a bit late to the party, but here's the perl script that I
use to convert our MikroTik scripts from human-readable text files into
importable rsc files...
http://users.fire2wire.com/~khoff/txt2rsc.txt
Just rename it to txt2rsc.pl and call it like so...
perl ./txt2rsc somescript.txt
I don't believe the export output was meant to be pasted back into
another mikrotik, at least unmodified.
-Kevin
On Wed, Jul 15, 2009 at 12:03 AM, Vegard Svanbergveg...@svanberg.no wrote:
* Josh Luthman j...@imaginenetworksllc.com [2009-07-15 02:33]:
Has anyone tried importing a system
Firstly the order of items in an export is not ideal for an import.
You have to juggle sections around in a logical orderl pretend you are actually
typing the commands.
So effectively you need to remove all references to MAC addresses as this
buggers things up. Import the interface section
Specify a file name on the export. That way you aren't copying and
pasting. I think you can drag and drop files from Winbox right? Then
you can use a text editor to edit the file where needed.
Casey
On Wed, Jul 15, 2009 at 9:20 AM, Josh
Luthmanj...@imaginenetworksllc.com wrote:
Let me
Still doesn't do the import -
/import scripts.rsc
Opening script file scripts.rsc
Script file loaded successfullysyntax error (line 8 column 26)
Josh Luthman
Office: 937-552-2340
Direct: 937-552-2343
1100 Wayne St
Suite 1337
Troy, OH 45373
When you have eliminated the impossible, that which
@mail.butchevans.com
Subject: Re: [Mikrotik] Exporting and Importing system scripts
Still doesn't do the import -
/import scripts.rsc
Opening script file scripts.rsc
Script file loaded successfullysyntax error (line 8 column 26)
Josh Luthman
Office: 937-552-2340
Direct: 937-552-2343
1100 Wayne St
Suite 1337
Troy
j...@imaginenetworksllc.com
Date: Wed, 15 Jul 2009 20:20:35
To: Mikrotik discussionsmikrotik@mail.butchevans.com
Subject: Re: [Mikrotik] Exporting and Importing system scripts
Still doesn't do the import -
/import scripts.rsc
Opening script file scripts.rsc
Script file loaded
--
Regards
Hilton J Ralphs
Think Technologies
-Original Message-
From: Josh Luthman
Still doesn't do the import -
/import scripts.rsc
Opening script file scripts.rsc
On Wed, Jul 15, 2009 at 9:43 AM, Casey Mills wkm...@gmail.com wrote:
Specify a file name on the export. That way
Dude, just run the script, don't import anything.
Apologies for the earlier blank email, hit the send button on my phone by
mistake.
--
Regards
Hilton J Ralphs
Think Technologies
-Original Message-
From: Josh Luthman
Still doesn't do the import -
/import scripts.rsc
Opening script
Has anyone tried importing a system script before?
If I export, copy, paste and try to import I get errors on the source=
argument.
Josh Luthman
Office: 937-552-2340
Direct: 937-552-2343
1100 Wayne St
Suite 1337
Troy, OH 45373
When you have eliminated the impossible, that which remains, however
20 matches
Mail list logo
