I don´t speak english very well, and i will try explain my questions.
I want to Known if i can use any type of “joke” or “metacharacter” like * to do a “find” in a script to “ip firewall mangle”
And the other question is about run a script store. How i can see the output of a script store in /system/script.
Many thanks and best regards
I want to Known if i can use any type of “joke” or “metacharacter” like * to do a “find” in a script to “ip firewall mangle”
If you want to “find” all entries, you can just write “/ip firewall mangle find” (without further seach parameters) - this will find all entries.
And the other question is about run a script store. How i can see the output of a script store in /system/script.
If you have scripts started by the scheduler, netwatch or the like and want to observe their output, you have to make them send the output somewhere, as you don’t see the “put” console output.
You could log to the system log (with the “:log” command), or you could send an e-mail - this depends on what you really want to achieve.
Best regards,
Christian Meis
About the question of the output, any problema. If i cant take the output of the script when i run it, i will send to the syslog. But i thought that i can take the output to console when i run it in a telnet session.
And the other question, that is a NOT,no?? There aren´t a joke to do a multiple select.
The idea is with a find, in a mangle, select by two criteriars:
i can do:
ip firewall mangle find new-connection-mark=TGO-PEPE
but i can´t do:
ip firewall mangle find new-connection-mark=TGO*
best regards
You could use the “:put” command to write something to the console. When the script is run from a scheduler task or something like that, this output is simply lost (but doesn’t do any harm).
Regarding find: I think a wildcard “find” is not possible. You could try to “find” according to some other parameters. You could for example give every mangle rule in your example the (same) command “TGO” and the “find” for that comment (“/ip firewall mangle find comment=TGO”).
Does that help you?
Best regards,
Christian Meis