+1Switches mikrotik without igms snooping and DHCP snooping is cheap toys ! Why these toys you produce?
+1Switches mikrotik without igms snooping and DHCP snooping is cheap toys ! Why these toys you produce?
Why are you testing different using versions of ROS? Just check if "V6.28rc20 -> Server V6.28rc20" is OK.
I'll solve this, but when someone like me relays on management over sstp link and begins upgrade on false end .....Yes, I agree that this is BAD, unfortunately this is not the first time . But I know what answer will give you the Support team. Upgrade both ends and then make a test.
/interface ethernet switch ingress-port-policer add burst=100k port=ether24-slave-local rate=60M
This happens to me with 6.24, 6.25 and 6.27 also (not tested on other versions).CRS125 ingress-port-policer is not working in v6.28rc20. Cannot do more than 1-5Mbps when set.
iperf does 1-5Mbps. Not 60M, 1-5M.Code: Select all/interface ethernet switch ingress-port-policer add burst=100k port=ether24-slave-local rate=60M
If I delete ingress-port-policer, goes back to normal and iperf does 900Mbps.
Who said anything about upgrading actual in-production SSTP servers? Pull a router out of stock and configure it as a temporary/test SSTP server. If you have no spare RouterBoards sitting around, fire up a copy of x86 RouterOS on a spare PC, or heck, even as a VM inside of VMware or something. There are TONS of options open to you that wouldn't require you to install a beta version of the OS on production routers!How can I upgrade geographicali dispersed routers at once ? If there will be no other solution I'll be forced to do that, but breaking compatiblity betwen versions is very BAD.Why are you testing different using versions of ROS? Just check if "V6.28rc20 -> Server V6.28rc20" is OK.
Got this back from support:Fixing the fetch ssl bug would be fantastic since it makes /tool fetch unusable for me:
http://forum.mikrotik.com/viewtopic.php?f=1&t=95576
Hopefully we will see this in the RC? Normis, can you confirm?Re: [Ticket#2015040666000483] Bug with /tool fetch and https.
Hello,
Its due to bug in ssl library. Next release will have the fix.
Regards,
Maris B.
I do not know how burst is working.Shouldn't that burst value be higher? The moment it goes in burst mode, it will send at 100k, than back to 60M, again burst mode at 100k and so on. Maybe burst = 100M?
This is fixed in version 6.28rc20. Thanks a lot MikroTik!Sending e-mail is still broken for me. The issue is described here:
System Error sending email timeout occurred
Any chance to get that fixed?
It would definitely be helpful to have some kind of release timeline. I certainly don't want the releases rushed or buggy, but it's very beneficial to know roughly when the new code will come out for testing and maintenance window planning.I agree. I would rather time spent and get a quality release, instead of rushing and releasing garbage.
That said, I would like some more communication as to how the fixes are proceeding.
IE - We now have SSTP fixed, working on BGP this week, and we want to make sure OSPF is good before we release this one.
(Just an example)
+1It would definitely be helpful to have some kind of release timeline. I certainly don't want the releases rushed or buggy, but it's very beneficial to know roughly when the new code will come out for testing and maintenance window planning.I agree. I would rather time spent and get a quality release, instead of rushing and releasing garbage.
That said, I would like some more communication as to how the fixes are proceeding.
IE - We now have SSTP fixed, working on BGP this week, and we want to make sure OSPF is good before we release this one.
(Just an example)
Well said Nathan. I have similar thoughts on tons of complaints here. Use stable versions that work for you, test the hell out of newer versions of ROS on some backup or spare router...simple as that.Who said anything about upgrading actual in-production SSTP servers? Pull a router out of stock and configure it as a temporary/test SSTP server. If you have no spare RouterBoards sitting around, fire up a copy of x86 RouterOS on a spare PC, or heck, even as a VM inside of VMware or something. There are TONS of options open to you that wouldn't require you to install a beta version of the OS on production routers!
-- Nathan
+1Well said Nathan. I have similar thoughts on tons of complaints here. Use stable versions that work for you, test the hell out of newer versions of ROS on some backup or spare router...simple as that.Who said anything about upgrading actual in-production SSTP servers? Pull a router out of stock and configure it as a temporary/test SSTP server. If you have no spare RouterBoards sitting around, fire up a copy of x86 RouterOS on a spare PC, or heck, even as a VM inside of VMware or something. There are TONS of options open to you that wouldn't require you to install a beta version of the OS on production routers!
-- Nathan
Could you please tell us what center frequencies you were using on both ends? Could you provide support output files to support@mikrotik.com?So I have two devices that I just upgraded to 6.28 because of superior ethernet performance... One is an RB911G-HPnD the other is a RB912UAG-HPnD. They are about 1.4 miles apart with signals in the low 50/high 40's. I noticed that they were see a 20 mhz channel negotiation with channel set to 20/40 eC Figured there was interference so I tried Ce. Still couldn't get better than 144mb negotiation... On a whim, I changed one side to eC and left the other at Ce... Now running at 300/400mb/s and a 40mhz channel. What is up with that?
Could you please tell us what center frequencies you were using on both ends? Could you provide support output files to support@mikrotik.com?So I have two devices that I just upgraded to 6.28 because of superior ethernet performance... One is an RB911G-HPnD the other is a RB912UAG-HPnD. They are about 1.4 miles apart with signals in the low 50/high 40's. I noticed that they were see a 20 mhz channel negotiation with channel set to 20/40 eC Figured there was interference so I tried Ce. Still couldn't get better than 144mb negotiation... On a whim, I changed one side to eC and left the other at Ce... Now running at 300/400mb/s and a 40mhz channel. What is up with that?
We just tried the same command and it didn't crash the board. From what RouterOS version you made the upgrade?Updated a rb2011.
[admin@rb2011-despa] /interface> set 5 l2mtu=1600 mtu=1540
action timed out - try again, if error continues contact MikroTik support and send a supout file (13)
[admin@rb2011-despa] /interface>
[admin@rb2011-despa] /interface>
[admin@rb2011-despa] /interface>
[admin@rb2011-despa] /interface>
[admin@rb2011-despa] /interface> print
(And after the print it seems to be hanging).
I had to change the MTU manually because it lost the original MTU after the update.
And the router has crashed. I can no longer access it.
Latest version grabbed 5 minutes ago.