aboutsummaryrefslogtreecommitdiffstats
path: root/bridge-port-to-default
AgeCommit message (Collapse)AuthorFilesLines
2020-01-01update copyright for 2020Gravatar Christian Hesse1-1/+1
2019-06-26bridge-port-to-default: handle special value 'dhcp-client'...Gravatar Christian Hesse1-5/+17
... which disables the bridge port, but enables a dhcp client.
2019-06-25bridge-port-to-default: get bridge port values into arrayGravatar Christian Hesse1-8/+7
2019-01-04global: variable names are CamelCaseGravatar Christian Hesse1-15/+15
___ _ ___ __ / _ )(_)__ _ / _/__ _/ /_ / _ / / _ `/ / _/ _ `/ __/ /____/_/\_, / /_/ \_,_/\__/ _ __ /___/ _ __ | | / /___ __________ (_)___ ____ _/ / | | /| / / __ `/ ___/ __ \/ / __ \/ __ `/ / | |/ |/ / /_/ / / / / / / / / / / /_/ /_/ |__/|__/\__,_/_/ /_/ /_/_/_/ /_/\__, (_) /____/ RouterOS has some odd behavior when it comes to variable names. Let's have a look at the interfaces: [admin@MikroTik] > / interface print where name=en1 Flags: D - dynamic, X - disabled, R - running, S - slave # NAME TYPE ACTUAL-MTU L2MTU 0 RS en1 ether 1500 1598 That looks ok. Now we use a script: { :local interface "en1"; / interface print where name=$interface; } And the result... [admin@MikroTik] > { :local interface "en1"; {... / interface print where name=$interface; } Flags: D - dynamic, X - disabled, R - running, S - slave # NAME TYPE ACTUAL-MTU L2MTU 0 RS en1 ether 1500 1598 ... still looks ok. We make a little modification to the script: { :local name "en1"; / interface print where name=$name; } And the result: [admin@MikroTik] > { :local name "en1"; {... / interface print where name=$name; } Flags: D - dynamic, X - disabled, R - running, S - slave # NAME TYPE ACTUAL-MTU L2MTU 0 RS en1 ether 1500 1598 1 S en2 ether 1500 1598 2 S en3 ether 1500 1598 3 S en4 ether 1500 1598 4 S en5 ether 1500 1598 5 R br-local bridge 1500 1598 Ups! The filter has no effect! That happens whenever the variable name ($name) matches the property name (name=). And another modification: { :local type "en1"; / interface print where name=$type; } And the result: [admin@MikroTik] > { :local type "en1"; {... / interface print where name=$type; } Flags: D - dynamic, X - disabled, R - running, S - slave # NAME TYPE ACTUAL-MTU L2MTU Ups! Nothing? Even if the variable name ($type) matches whatever property name (type=) things go wrong. The answer from MikroTik support (in Ticket#2019010222000454): > This is how scripting works in RouterOS and we will not fix it. To get around this we use variable names in CamelCase. Let's hope Mikrotik never ever introduces property names in CamelCase... *fingers crossed*
2019-01-02update copyright for 2019Gravatar Christian Hesse1-1/+1
2018-10-25bridge-port-to-default: delay only when requiredGravatar Christian Hesse1-3/+5
2018-10-25bridge-port-to-default: delay for global-configGravatar Christian Hesse1-0/+3
All scripts scheduled with "start-time=startup interval=0" start simultaneously, thus racing on global variables. So delay for a second and give global-config time to finish.
2018-10-25bridge-port-to-default: drop unused code, :toarray strips itselfGravatar Christian Hesse1-3/+0
2018-10-25bridge-port-to-default: fix variable nameGravatar Christian Hesse1-1/+1
2018-10-04bridge-port-to-default: strip leading blank from commentGravatar Christian Hesse1-0/+3
2018-10-04bridge-port-to-default: support different configurationsGravatar Christian Hesse1-10/+18
Just add something like this to your bridge ports: comment="default:br-ext,alt:br-intern"
2018-09-27start scripts with a magic token / shebangGravatar Christian Hesse1-1/+1
2018-08-27rename ethernet-to-default -> bridge-port-to-defaultGravatar Christian Hesse1-0/+18
generated by cgit v1.2.3-54-g00ecf (git 2.44.0) at 2024-04-29 19:34:45 +0000