i tied that before but couldnt fiure out what was wrong. directory listing shows “forbidden”. not helpful neither
For stable release, you can see the “directory listing”
https://mikrotik.com/download/archive
If you want to download it directly using a version name from RouterOS, this may help:
:global dlros do={
:local lver "7.11.2"
:local larch "arm64"
:if ([:typeof $1]="str") do={
:set lver $1
:if ([:typeof $arch]="str") do={
:set larch $arch
}
}
:local curl "https://download.mikrotik.com/routeros/$lver/routeros-$lver-$larch.npk"
:put $curl
/tool fetch url=$curl
}
$dlros 7.12beta1 arch=arm
In the new /terminal/ask, I’ve notice the preinput= is included in the returned value. I’m not sure when this changed… I get preinput= is the what appears on same line before input (and prompt= is above the input). But the “question” (e.g. what’s in preinput=) should not be in the response string IMO. e.g.
:global askbug [/terminal/ask "Should the preinput= be included in return?" preinput="I think no. Bug? "]
Should the preinput= be included in return?
I think no. Bug? > YES
:put $askbug
I think no. Bug? YES
Here just the “YES” should be returned, but I get the entire preinput= too…
Or more simply:
:put [/terminal/ask preinput="> "]
> something
> something
The value return in this case should be just “something”, not “> something”.
It looks like the issue is more that the “preinput” name is unclear, it should have been something like “default”.
In the example you suggest that the preinput is a “prompt” on the same line, but in fact it is the initial content of the input buffer, that you can backspace away and then change.
So it seems natural that it is returned.
The behaviour has not changed since I wrote this post, as far as I can tell. Didn’t realise you can actually erase the preinput text, though. (maybe that was changed)
http://forum.mikrotik.com/t/v7-12beta-testing-is-released/168851/1
value-name is what most people will want to use. prompt seems wholly redundant, and I was gonna say so is preinput, but in light of being able to erase it, I guess it might be useful.
Yeah, value-name should have been named “prompt”, and pre-input should have been named “default”.
What is now “prompt” is redundant because a parameter without name is also considered a prompt (probably for backward compatibility?) and because a linefeed is issued after it (so you could just use a :put command instead).
Well, to me, it actually sound logical. If there were a parameter named default I’d expect it to mean “return this if the input buffer is empty”, whereas preinput sounds more like “pre-fill the input buffer with this string, please”.
@amm0 do you remember my implementation of this. I added a help/info line that was displayed underneath and the next input field was shifted down and displayed directly under that help/info.
So if you want to use pre-input as help/info then better ask for that extra line being displayed.
[highlight]value[/highlight]
test value test
value
value
This is a test
Courier-This is a test
-This is a test
Veranda-This is a test
Tahoma-This is a test
Georgia-This is a test
Thanks to Andriys, I learned that I can use different fonts (BBCode) in post. Not all looks good.
Well “value-name” does what I want: keep question on same line. I swear this was changed someplace…
But “value-name” is very poor choice for the functionality. I ignored it since “value-name=” is normally what the “default attribute” is. e.g.
/ip/address/print
:put [/ip/address/get 0 address]
111.211.111.61/29
:put [/ip/address/get 0 value-name=address]
111.211.111.61/29
So…
/terminal/ask “my question”
. should be same as
/terminal/ask value-name=“my question”
At least, to be consistent with undocumented language reference. e.g. value-name= is normally same “unnamed” default attribute most place (e.g. in ~1300 other cmds).
when can we expect OpenVPN to be fixed permanently?
anyone else have an issue with s-rj01 SFPs and auto flow control being on causing no link to be established after a brief iface down period? (on an rb5009)
Also have S-RJ01 and RB5009, it’s even my WAN link so I would know pretty soon if something goes wrong there.
How do you define brief itf down periods ? How does that happen?
I have it hooked to a laptop I use for work so at night it goes to sleep and when I come back the next day the connection will not establish without disabling interface and enabling it or other intrusive of stuff like that.
Hmm … I don’t really power off my ISP modem so maybe there is something odd there when you really shut down that connection.
(that’s what I use SFP for right now since I use ether1 as 2.5G trunk to AX3 and most of the other ports are also occupied).
Does S-RJ01 support full auto negotiation mode? If it doesn’t, then it’s expected to see problems. Most NICs, while in sleep mode, auto negotiate slower speeds (10Mbps half-duplex is pretty common mode) and if the other end (S-RJ01) doesn’t do its job properly, then the link goes AWOL.
!) ethernet - changed “advertise” and “speed” arguments, and removed “half-duplex” setting under “/interface ethernet” menu;
!) sfp - convert configuration to support new link modes for SFP and QSFP type of interfaces;
1- what are the implications of this removal in scenarios where we have to match a device with fixed speed on the other side?
(plenty of home automation stuff i know of is hard-set to 10/half or 100/half)
Also, eventually i limit the advertised rates to avoid the interface trying to speak 1000/full and failing, on problematic cable runs
2- will this change the naming scheme for existing interface types/products?
HI,
We have removed the setting “half-duplex=yes | no”, because it got replaced with new “speed” arguments. For example:
/interface ethernet set ether1 speed=10M-baseT-half auto-negotiation=no
Speed settings were changed to represent all the link-modes, since the previous speed setting was too ambiguous.
These new link-modes are now identical for “speed” and “advertise”. The difference is whether auto-negotiation is enabled or not. Speed is used with disabled auto-negotiation and accepts only one link-mode. Advertise is used with enabled auto-negotiation and accepts multiple link-modes.
Thanks for the feedback!
What’s new in 7.12beta9 (2023-Sep-25 15:19):
!) ethernet - changed “advertise” and “speed” arguments, and removed “half-duplex” setting under “/interface ethernet” menu;
!) health - removed “temperature” health entry from boards, where it was the same as “sfp-temperature”;
!) sfp - convert configuration to support new link modes for SFP and QSFP type of interfaces;
*) bfd - improved system stability;
*) bgp - fixed “input.filter-chain” argument selection in VPN configuration;
*) bgp - improved logging;
*) bluetooth - added basic support for connecting to BLE peripheral devices;
*) console - export required properties with default values;
*) console - improved system stability;
*) console - restrict permissions to “read,write,reboot,ftp,romon,test” for scripts executed by DHCP, Hotspot, PPP and Traffic-Monitor services;
*) l3hw - fixed IPv6 route suppression;
*) led - fixed “interface-status” configuration for virtual interfaces;
*) lora - added LNS protocol support;
*) lte - changed R11e-LTE ARP behavior to NoArp;
*) lte - fixed sub-interface auto-removal in multiple APN setups;
*) lte - show correct data class when connected to 5G SA network;
*) mqtt - added on-message feature for subscribed topics;
*) mqtt - added parallel-scripts-limit parameter to set maximum allowed number of scripts executed at the same time;
*) mqtt - added wildcard topic subscription support;
*) netinstall - added option to discard branding package;
*) netinstall - display package filename in GUI Descption column if package description is not specified;
*) netinstall-cli - added option to discard branding package;
*) netinstall-cli - allow “.rsc” script filenames;
*) poe-out - driver optimization for AF/AT controlled boards;
*) poe-out - fixed rare CRS328 poe-out menu and poe-out port config loss after reboot;
*) route - added “single-process” configuration setting, enabled by default on devices with 64MB or less RAM memory (CLI only);
*) route - added “suppress-hw-offload” setting for IPv6 routes;
*) route - reverse community “delete” and “filter” command behavior;
*) routerboard - added “reset-button” support for RB800, RB1100 and RB1100AHx2 devices;
*) sfp - fixed 25Gbps link with FEC91 (introduced in v7.12beta7);
*) snmp - changed “mtxrGaugeValue” type to integer;
*) switch - fixed packet forwarding between Ethernet ports for CRS354 switches (introduced in v7.12beta7);
*) webfig - fixed timezone for interface “Last Link Down/Up Time”;
*) wifiwave2 - correctly add interface to specified “datapath.interface-list”;
*) wifiwave2 - fixed re-connection failures for 802.11ax interfaces in station mode;
*) wifiwave2 - limit L2MTU to 1560 until a fix is available for a bug causing interfaces to fail transmitting larger frames than that;
*) wifiwave2 - log more information regarding authentication failures;
*) winbox - added “Host Key Type” setting under “IP/SSH” menu;
*) winbox - added “Key Owner” setting under “System/User/SSH Keys” and “System/User/SSH Private Keys” menus;
*) winbox - added “Remote Min Tx” parameter under “Routing/BFD/Session” menu;
*) winbox - added “Startup Delay” setting under “Tools/Netwatch” menu;
*) winbox - added “Use BFD” setting under “Routing/RIP/Interface-Template” menu;
*) winbox - added MQTT subscription menu;
*) winbox - allow to specify server as DNS name under “Tools/Email” menu;
*) winbox - rename “DSCP” setting to “DSCP (+ECN)” under “Tools/Traffic-Generator/Packet-Templates” menu;
*) winbox - rename “Name” setting to “List” under “IP,IPv6/Firewall/Address-List” menu;
*) winbox - rename “Password” button to “Change Now” under “System/Password” menu;
*) wireguard - added “auto” parameter for “private-key” and “presharde-key” parameters;
*) wireguard - request public or private key to be specified in order to create peer;
*) x86 - igb updated driver to 5.14.16 version;
*) x86 - igbvf updated driver from in-tree Linux kernel;
*) x86 - updated latest available pci.ids;