works ok on RB951G with 6.2
Same here on RB2011UAS-RM.
6.2 BUG REPORT
plateforme RB951G
Reset counters on ethernet interface does not works
winbox and cli
Jarda “I alerady did (nr. 2013080466000205 - about loosing graphs). Today I received advice to netinstall v6.2. I am not sure that it will help, but I will try to.”
This is interesting. MT support told me there is no need to use netinstall. They also told me because I used it (RoS 6.2 with netinstall 5.25) I lost 2 routers. Ticket no. 2013081366000304. So i guess there is different answer for every MT admin about the same thing. Depends which answer suits Mikrotik best? Am I wrong?
Hi mikrotik
When will be the next release?
Thanks
I hope the new version gets tested better before it is called “stable”
If you need a beta tester, you can send me the file/link, as we run quite some scripts and routing on our networks here. I will know soon enough if it works or not, or what might have gone wrong within the scope we use.
Tx
+1 for stability. 6.2 was kind of a mess.
Sent from my SCH-I545 using Tapatalk 2
I mentioned this before on 6.1 – and I put in a bug request – is that mantis installation still being used or is the forum the way to go?
Anyway the bug is here http://bugs.mikrotik-routeros.com/view.php?id=50
in 6.0RC9 and below tool fetch lets you specify a ip value in the address and a host name in the host parameter. It would call out the address with the host header you specified in host.
With 6.2 it requires the address parameter but completely ignores it if the host is present and instead does a dns lookup on the host name and then routes to it. Being able to specify the address independently from the host name is really handy for scripting monitoring or failover on webservers that have virtual hosts and multiple ips per domain name. it is also very userful for monitoring/failover of proxies.
Tools → Torch shows only traffic on the selected interface. in Ethernet stats you see also traffic of subinterfaces (VLANs), which is not shown in Torch
Will 6.3 include any fixes for the St reliability issues with wireless links we have seen with every version 6.x? I am getting pretty p*ed off with having to reboot APs just because they randomly decide that they cannot be bothered to pass traffic anymore (even though they are still registered with the client).
Why not try testing your software properly for a change before releasing it???
I didn’t realize that the interfaces also showed VLAN traffic. Is this always the case or is it a bug in 6.2? Is there a way to get it to show only traffic not “claimed” by a vlan?
-Eric
Feature Request for 6.3 >
adding the possibility to execute script with parameters
/system script run script1 $1 $2 $3 $4
thanks
Armand
+1 
and to have a firewall filter/mangle:
action=run-script
script-str=MyScript $src-address $out-interface…
That would be ridiculous! 
I’ve got the same problem
+1
IP route is not working with sfp interface.
be more precise. plateforme, Ros version, etc…
On CCR-1036 with 6.2, It is working for me.
regards
armandfumal thank you for responce. I have CCR1036 with 6.2 and 3.09 firmware. At this moment im using ether6 as a main uplink port. But when i change from ether6 to sfp1 my gateway is unreachable which is x.x.172.77. Im using Mikrotik S-31DLC20D sfp.
My config:
/ip route> print
DST-ADDRESS PREF-SRC GATEWAY DISTANCE
0 A S 0.0.0.0/0 x.x.172.78 ether6 1
1 ADC 10.0.1.0/24 10.0.1.1 VLAN - 101 0
2 ADC x.x.172.76/30 x.x.172.78 ether6 0
3 ADC x.x.232.0/24 x.x.232.1 VLAN - 100 0
4 ADC 172.16.1.0/24 172.16.1.1 VLAN - 102 0
5 ADC 172.16.2.0/24 172.16.2.1 ether1 0
6 ADC 192.168.2.0/24 192.168.2.1 VLAN - 2 0
ip address print
Flags: X - disabled, I - invalid, D - dynamic
ADDRESS NETWORK INTERFACE
0 172.16.2.1/24 172.16.2.0 ether1
1 192.168.2.1/24 192.168.2.0 VLAN - 2
2 x.x.232.1/24 x.x.232.0 VLAN - 100
3 10.0.1.1/24 10.0.1.0 VLAN - 101
4 172.16.1.1/24 172.16.1.0 VLAN - 102
5 x.x.172.78/30 x.x.172.76 ether6
ip firewall nat print
Flags: X - disabled, I - invalid, D - dynamic
0 chain=srcnat action=src-nat to-addresses=x.x.232.254
src-address=192.168.2.0/24 out-interface=ether6
1 chain=srcnat action=src-nat to-addresses=x.x.232.254
src-address=172.16.2.0/24 out-interface=ether6
2 chain=srcnat action=src-nat to-addresses=x.x.232.254
src-address=172.16.1.0/24 out-interface=ether6
3 chain=srcnat action=src-nat to-addresses=x.x.232.254
src-address=10.0.1.0/24 out-interface=ether6
If you want to move your uplink to your sfp interface, you should also change all the relevant config like NAT.
Change the ether6 to sfp interface.