I Believe there is a bug in version 3.x (tested in v 3.9), while exporting configuration in queues simple if there are any queues with unlimited settings in Burst Limit or Burst threshold or 0 in seconds this is what's gets exported:

add burst-limit=/1536000 burst-threshold=/256000 burst-time=/32s comment="" \
direction=both disabled=no dst-address=0.0.0.0/0 interface=all \
limit-at=256000/256000 max-limit=512000/512000 name="Global Forwarding @ \
ITC - 512K" parent=none priority=5 queue=default/default \
target-addresses=12.52.84.35/32 total-queue=default

As you can see:
burst-limit=/1536000
burst-threshold=/256000
burst-time=/32s

If you copy paste this exported queue simple and paste it into a routeros your gone a have three errors ... I don't know but this might be a bug in the exporting engine.

There is another bug/error in exporting engine:

If you /ip firewall layer7-protocol
then export file=l7p for example and later you copy paste that into another router you will end with a bunch of errors because Mikrotik is confusing symbol \ with the \ contained in the regular expressions of the L7 protocols.

Any comments about this? Am I wrong?

Best Regards

Jorge Boardman

Jorge,

Do you have any idea how many "bug" topics you have started? Starting to wonder about user error, seriously!

Jorge,

Do you have any idea how many "bug" topics you have started? Starting to wonder about user error, seriously!

Yes, three (including this one) for RouterOS and one for The Dude...

From those, one for RouterOS turned to be actually a bug (bios), and the one for The dude was and still a bug.

I really do not understand the point of your comment, but I can assure you, I do not post in this forum without a reason, I am NOT a Mikrotik expert but I have been using it probably for the last 7 - 8 years, and I have installed and keep running probably more than 200 systems with RouterOS.

But, yes you are right, it can be an user error. Since I am not such an expert, if I found something that's unusual or beyond my limited knowledge, I post that here... mainly for three reasons:

1- Feedback that may help RouterOS people.
2- Help fellow forum readers
3- Learn

But, jwcn if you really think I am waiting somebody else's time ... I am sorry .... I'm sorry for my lack of knowledge, I am an electronics and communications engineer but when I was in school the most advanced computer was an apple II with barely or no networking, from that point till today everything I have learned has been by myself, so sorry for my lack of knowledge.

I do not want to sound rude but If you do not like what I post ..... PLEASE DO NOT READ IT...

Regarding this issue, I don't know but exporting a simple queue and copy paste it causing an error it is a bug to me.

Best Regards
Ing. Jorge E. Boardman
http://www.laredonet.com
MEXICO

it probably is a bug, email details with a supout to support at mikrotik.com.

Sam

CONFIRMED BUG - as of v3.x beta!

I have spent many hours testing exports and scripts on MT and I can confirm 100% that it is a BUG but very easy to solve.

For those who haven't noticed since v3.x MT has strictened syntax so if you try to for example it won't do anything, but will do the trick.

Same thing apllies to queues, so if you have: will FAIL and this is ACTUAL EXPORT from v3.7 on RB333, but will WORK every time.

So, guys from MT please make command syntax even more strict so that users must enter [variable_name]="[parameter]" for EVERY variable and implement that in EXPORT command.

The only bugs I find are on my dog.... maybe I'm just too stupid...

I just do a backup off the old stuff and restore on the new stuff (ie: RB600 from RB500) and haven't had ONE issue...

Like I said - maybe a little dim.... but thing I can tell you is I DO NOT go LOOKING for the tinyest weeenyest little bug in ROS everytime a version hits the scene... btw - those fancy xxCO boxes you can buy come with a MANUAL on how to circumvent the KNOWN bugs... sheeesh!!!!
Give me ROS on a RB anyday... OK back to the dog....

T

The only bugs I find are on my dog.... maybe I'm just too stupid...

I just do a backup off the old stuff and restore on the new stuff (ie: RB600 from RB500) and haven't had ONE issue...

Like I said - maybe a little dim.... but thing I can tell you is I DO NOT go LOOKING for the tinyest weeenyest little bug in ROS everytime a version hits the scene... btw - those fancy xxCO boxes you can buy come with a MANUAL on how to circumvent the KNOWN bugs... sheeesh!!!!
Give me ROS on a RB anyday... OK back to the dog....

T

Yes please go back to your dog...

He made a valid point...

He made a valid point...

What's new in 3.10:

*) added Multilink PPP to PPPoE client - just specify multiple interfaces
to enable it;
*) added ability to add dynamicly PPTP, L2TP & PPPoE client addresses
to firewall address-list, specified in ppp profile,
or via RADIUS in Mikrotik:19;
*) added address-list attribute support in user-manager;
*) added fan control for RB433;
*) console:
fixed 'interface wireless print detail', now shows the same output as
'interface wireless print basic';
fixed print to file, now writes complete contents, fixed resource leak;
show name of running scripts in '/system script job', update
'last-started' value;
could not use item names for '/interface ovpn-server' and
'/interface ovpn-client', fixed;
fixed problems with export:
some settings were not included in full export, such as
'/interface wireless nstreme');
some settings had duplicate entries with an error, such as
'/system ntp client' when ntp package was enabled;
long parameter values were incorrectly split across multiple lines;
export now quotes all values that are split across multiple lines, it
also adds line split before all newline characters, which improves
readability of exported script sources;


Thanks

He made a valid point...

What's new in 3.10:

*) added Multilink PPP to PPPoE client - just specify multiple interfaces
to enable it;
*) added ability to add dynamicly PPTP, L2TP & PPPoE client addresses
to firewall address-list, specified in ppp profile,
or via RADIUS in Mikrotik:19;
*) added address-list attribute support in user-manager;
*) added fan control for RB433;
*) console:
fixed 'interface wireless print detail', now shows the same output as
'interface wireless print basic';
fixed print to file, now writes complete contents, fixed resource leak;
show name of running scripts in '/system script job', update
'last-started' value;
could not use item names for '/interface ovpn-server' and
'/interface ovpn-client', fixed;
fixed problems with export:
some settings were not included in full export, such as
'/interface wireless nstreme');
some settings had duplicate entries with an error, such as
'/system ntp client' when ntp package was enabled;
long parameter values were incorrectly split across multiple lines;
export now quotes all values that are split across multiple lines, it
also adds line split before all newline characters, which improves
readability of exported script sources;


Thanks

Like I said.... give me RB anyday...

You could of course revert to 10x price xxxCO product - where you require a PhD to operate the stuff..!!! Nah.. ROS rocks..

T