I have a scenario where I need to export all the IP's from ether2 to a file? Something similar to this put with an export command:
pr file="Ether2" where interface="ether2"
The above yields a text file with the IP's but I need it where I can import it to another router?
Joe
Re: export ip addresses from particular interface
I think you cant export only specific ips, but you can do workaround something like script below:
Code: Select all
{
:local content ""
:local ip;
/file print file=ip
:foreach i in=[/ip address find interface="ether2"] do={
:set ip [/ip address get $i address];
:set content ("$content\r\n/ip address add address=$ip interface=ether2);
}
/file set ip.txt contents=$content;
}
Re: export ip addresses from particular interface
/ip address print file=ip where interface=ether2
Re: export ip addresses from particular interface
This command will print the table of IPs on ether2, and it is not importable configuration./ip address print file=ip where interface=ether2
Re: export ip addresses from particular interface
You can use on the source box:
/ip address export file=ipadd
and this on the destination box:
/ip address import file=ipadd
Getting the file from one to the other is the trick. It may require an local net tftp server, or the like, to relay the files. You could probably do the same with a text file like the suggestions above, and use the tftp server to relay that text file, and "import" with a script.
/ip address export file=ipadd
and this on the destination box:
/ip address import file=ipadd
Getting the file from one to the other is the trick. It may require an local net tftp server, or the like, to relay the files. You could probably do the same with a text file like the suggestions above, and use the tftp server to relay that text file, and "import" with a script.
Re: export ip addresses from particular interface
but that will get all the ip addresses that are on all interfaces - OP specifically asked for a way to get addresses of one interface.
Re: export ip addresses from particular interface
That is why I put the reference to the previous post. It may be better to use a script to generate a text file, then move it to the new machine, and use another script to install it there.
To me, the challenge is not getting or setting the /ip address of the interface. I can do that in my sleep. It is getting it from one machine to the other.
BTW, see my post in the Beta forum. sftp would be nice, along with the RB433V.
To me, the challenge is not getting or setting the /ip address of the interface. I can do that in my sleep. It is getting it from one machine to the other.
BTW, see my post in the Beta forum. sftp would be nice, along with the RB433V.
-
-
breno.vale
just joined
- Posts: 6
- Joined:
Re: export ip addresses from particular interface
mrz,
i need find and export ip adress and acess list from wlan1 for exemple, I do not know how. My version is 2.9.50
I wish it were possible to explain the controls of the export.
Best Regards.
Breno Vale
Brazil
i need find and export ip adress and acess list from wlan1 for exemple, I do not know how. My version is 2.9.50
I wish it were possible to explain the controls of the export.
Best Regards.
Breno Vale
Brazil
Re: export ip addresses from particular interface
I am already waiting for the tftp, so I have been practicing. Here is the script for the source MT box:
EDIT: This is an array - to - CSV file converter.
Move the file ipaddlist.txt from the source MT box to the target MT box
Here is the code on the second MT box:
EDIT: This is a CSV file - to array converter.
Before you have this set your ip addresses, I would test this for a while to insure it does what you want. Let me know if I made any errors or typos. I tested all except assigning the ip addresses to the interface.
Keeping with standards, the ipaddlist.txt file is a CSV list.
ADD: The test was putting 3 sets of ip addresses (10.0.1.1/24, 10.0.2.1/24, and 10.0.3.1/24) on ether3, then running both routines, and
:env pri
ADD: The script no longer aborts if the CSV file does not exist. It will log it.
EDIT: This is an array - to - CSV file converter.
Code: Select all
:global ipadd [/ip address find interface=wlan1]
:global ipaddlist ""
:foreach i in=$ipadd do={
:local ipstr [/ip address get $i address]
:if ( [:len $ipaddlist] = 0) do={
:set ipaddlist ([:toarray $ipstr])
} else={
:set ipaddlist ($ipaddlist + [:toarray $ipstr])
}
}
{ /file print file=ipaddlist count-only }
{ /file set ipaddlist.txt contents=$ipaddlist }
Here is the code on the second MT box:
EDIT: This is a CSV file - to array converter.
Code: Select all
:global ipadd2 ""
:global ipaddlist2 ""
:local curpos 0
:local newpos 0
:local filearray [/file find name=ipaddlist.txt]
:if ([:len $filearray] > 0) do={
:set ipaddlist2 [/file get $filearray contents]
} else={
:log info "file ipaddlist.txt does not exist"
}
:if ([:len $ipaddlist2] > 0) do={
:set newpos [:find $ipaddlist2 "," $curpos]
:while ($newpos > 0) do={
:if ([:len $ipadd2] = 0) do={
:set ipadd2 ([:toarray [:pick $ipaddlist2 $curpos $newpos]])
} else={
:set ipadd2 ($ipadd2 + [:toarray [:pick $ipaddlist2 $curpos $newpos]])
}
:set curpos ($newpos + 1)
:set newpos [:find $ipaddlist2 "," $curpos]
}
:if ([:len $ipadd2] = 0) do={
:set ipadd2 ([:toarray [:pick $ipaddlist2 $curpos [:len $ipaddlist2]]])
} else={
:set ipadd2 ($ipadd2 + [:toarray [:pick $ipaddlist2 $curpos [:len $ipaddlist2]]])
}
:foreach i in=$ipadd2 do={
{ /ip address add address=$i interface=wlan1 }
}
}
Keeping with standards, the ipaddlist.txt file is a CSV list.
ADD: The test was putting 3 sets of ip addresses (10.0.1.1/24, 10.0.2.1/24, and 10.0.3.1/24) on ether3, then running both routines, and
:env pri
ADD: The script no longer aborts if the CSV file does not exist. It will log it.
Re: export ip addresses from particular interface
To move from system to system is as simple as dragging the file you created from the file list in one winbox interface to the file list in the other system's winbox and then run the import command.
Hope this helps.
Rod
I love drag-n-drop!!!
Hope this helps.
Rod
I love drag-n-drop!!!
Re: export ip addresses from particular interface
Then I guess if the script interpreter could use Winbox, that would be great! 
MikroTik has made me lazy! I used to log in to every box to see if it is up and running. What a hassle! Now a script does it at 2AM and emails me the results.
I used to log in to check the voltage on my solar powered units. Now a script keeps a record of the voltage every hour, and email me those at 11PM, unless the voltage drops below 12.5 volts, then it emails me every hour.
What part of those can Winbox do?
MikroTik has made me lazy! I used to log in to every box to see if it is up and running. What a hassle! Now a script does it at 2AM and emails me the results.
I used to log in to check the voltage on my solar powered units. Now a script keeps a record of the voltage every hour, and email me those at 11PM, unless the voltage drops below 12.5 volts, then it emails me every hour.
What part of those can Winbox do?
Re: export ip addresses from particular interface
The export script worked as expected, but the import did not work.
Accuses syntax error:
[admin@MK02] > :if ([:len $ipaddlist2] > 0) do={
{... :set newpos [:find $ipaddlist2 "," $curpos]
syntax error (line 2 column 10)
[admin@MK02] >
:set curpos ($newpos + 1)
syntax error (line 8 column 14)
[admin@MK02] > :set newpos [:find $ipaddlist2 "," $curpos]
syntax error (line 1 column 14)
Accuses syntax error:
[admin@MK02] > :if ([:len $ipaddlist2] > 0) do={
{... :set newpos [:find $ipaddlist2 "," $curpos]
syntax error (line 2 column 10)
[admin@MK02] >
:set curpos ($newpos + 1)
syntax error (line 8 column 14)
[admin@MK02] > :set newpos [:find $ipaddlist2 "," $curpos]
syntax error (line 1 column 14)