to start a new thread …
[@cip-hotty] > /tool sniffer get running
value-name: Script Error: missing required values
input does not match any value of value-name
This worked in 2.9, and still shows as valid when you hit to complete ‘runn’… but it doesn’t take it.
Maybe it’s just the GET command isn’t working right.
Here is what I used to accomplish:
:if ([/tool sniffer get running] != true ) do={ }
Sam
and another CLI issue I ran into:
:if ([ :typeof $variable ] = ip ) do={
:log info ("Destination ip is " . $variable)
}
The above doesn’t log anything, however the same syntax all on one line does:
:if ([ :typeof $variable ] = ip ) do={ :log info ("Destination ip is " . $variable) }
Bug?
Sam
on RP112
i got 100% cpu usage alot
missing wireless interface on reboot
on x86
after a 3 min of using with hotspot the router stop responding
no ping nothing
taloot - please send a supout.rif file to support! always send this file to support when you see a problem.
Wrap won’t reboot
under dhcp server I think not all info is showing under lease (small who cares really)
I think 3.0 is taking more memory and therefore is having issues on these rb112s? Just a guess. I notice with < 5mb of ram available things start going haywire.
recommend to disable the unneeded packages to increase the free memory. Also suggest to use Winbox instead of console(terminal), as console takes more memory.
in MT 3.0beta5 queues is not working, and many times MT is making a disconnetion to winbox after some changes.
I logged in to winbox when under load, still had heaps of ram left (100mb) but pings when way high, then disconnect, then no more.
CPU was very low tho, doesn’t make big sence.
Hard reboot fixed.
Thanks
NTP client doesn’t works too.
I’m having continuous reboots, without suppout being generated.
CPU load is relatively low, under 20% with wireless + pppoe + some NAT activated.
Hope this helps.
Edit: RouterOs 3.0Beta5 running on RB112
NTP client via Unicast to default router and to remote router time sync = OK..
No reboots here.. Platform = HP DL140, SuperMicro 2X Xeon.
PS ALL 4 cores picked up.. (2X Hyper Threaders).. Yeh !!!
Craig
winbox bug:
create a nat rule in the dst-nat chain.
try to choose jump-target - shows firewall filter chains instead of nat chains…
CLI shows the correct items.
[@cip-hotty] /ip firewall nat> set 3 jump-target=
JumpTarget ::= bot-dstnat | bot-srcnat | dstnat | srcnat
whereas on the winbox dropdown for that same item I see:
input, output, forward, etc.
Sam
another winbox bug:
ip firewall address-lists shows multiple duplicate items in the dropdown list (filter dropdown on the top right)
I show over 250 for the same list name. . .
Sam
Sam…
They just dont want you to miss it… 
