Good idea. Write us the result...We should email the executives of the company starting with Mr. Tully.
Normis:We have not advertised v7 as a version. The first post in this forum thread is by a user.
All unfixed Problems with ROS, where we get the answer, „will be fixed in ROS7“ show us how Mikrotik cares about there costumers, we decided last year to not buy Mikrotik Wireless anymore because of ARM NV2 Issue, what looks like it fixed now. (first issues told to support on Xmas 2017. viewtopic.php?f=7&t=128916&p=633371&hil ... v2#p633371 -to now, so it is about 13 month for this fix) and in all this time nothing as information so I think it is not possible to do serious Business with Mikrotik.Sry Mikrotik - your public relations behaviour is a total desaster when it comes to this topic.
This is a user forum. So I don‘t expect u guys to do the right thing nor do I expect that u even know the truth. We all know that here and there especially software projects might end in a desaster. In combination with the announcement years ago there is a dramatic chance, that ur development is lost in space, i.e. will never been finished.
This would be a desaster for the community but it will hit others even more if their business is based on your products.
Answering ‚it will be ready when its ready‘ is not an option anymore after years of ‚coming soon‘ answers. But this is again something I would expect to be dealt with by you board. So there must be anything more serious than ‚alpha status‘, ‚coming soon‘, ‚not ready yet‘. If you are lost in space and don‘t believe you gonna make it shortly - plz tell us. This will be the better option and will let u determine the right action to be taken.
Nothing has changed from that time. Please suggest what answer you wanted to hear.Normis:We have not advertised v7 as a version. The first post in this forum thread is by a user.
Your post from 08Jan 2015 - v7 is currently in internal testing, and will be released as beta when it's stable enough
Your post from 06 Feb 2015 - We will release a beta, when it will exist. Currently v7 is in alpha stage, many functions are not completed and non functional. Beta needs at least all functions to be somewhat operational.
This topic about V7 was created itself?
And now you say V7 is not a version? Are you kidding?
I understand you can not say anything, but do not make fun of us at all
We are not able to do Business decisions with a maybe or "in near future"
Nothing has changed from that time. Please suggest what answer you wanted to hear.
The feature I'm personally interested in is udp support for openvpn which was requested in 2008. It's not even a new feature just an extension of existing one. It was never stated that it is not feasible or possible.It is not never. I suggested to stop worrying about it and use v6.
About the features, which features do you need? Remember that MikroTik does not implement features by demand. It might not be feasible or possible to make something. Everything has to be evaluated individually.
As a WISP - I'm primarily interested in wireless so I'm interested about spectral scan on AC. And wave2 support?Nothing has changed from that time. Please suggest what answer you wanted to hear.
As many other people, I also expect that when v7 comes out, my router will be able to do anything I've ever dreamed of and more, and make me a coffee on top of that (without any additional hardware required, that's how great will v7 be).... when you now release a v7 that is just a 6.44 with new kernel there will be a large uproar.
The point is that many new features have been postponed for many many years "until v7" even when they do not require a new kernel at all!As many other people, I also expect that when v7 comes out, my router will be able to do anything I've ever dreamed of and more, and make me a coffee on top of that (without any additional hardware required, that's how great will v7 be).... when you now release a v7 that is just a 6.44 with new kernel there will be a large uproar.
Mikrotik writes its own drivers, and maintains its own kernel patches to the Tile CPUs. It is open to discussion if this is a good decision, but I don't know enough (both of the internals of Mikrotik business and of driver development) to have an informed opinion.There is obviously a huge stumbling block as to why a kernel upgrade has not happened, either in a 6.x version or the unicorn v7.
Let’s not forget that Mikrotik is mostly made up of open source software, maybe one or more elements can’t be upgraded to a more recent kernel?
My guess is that it’s fast path / fast track… They both rely on the route cache, which isn’t available in more recent kernels.
some cases promise fix on v7 are not fix yet on v6 thought.Very good response pe1chl, you are getting it.
Anyway, I am just trying to keep expectations mild. Most development is done on v6, as you can see from all the new features, fixes and huge changelogs.
But for now it's RouterOS 9 ("Nein" in German)maybe skip straight to RouterOS X (10)
Don't worry you'll have RouterOS 7 soon enough.. (when pigs will fly)But for now it's RouterOS 9 ("Nein" in German)maybe skip straight to RouterOS X (10)
This is the first question from this thread in 2015.Hi,
When RouterOS v7 beta1 is gonna to be released?
someone may not liveAges are not ending by 2020.
The cycle of RoS?May not... But others will be borned.
/31 supportIt is not never. I suggested to stop worrying about it and use v6.
About the features, which features do you need? Remember that MikroTik does not implement features by demand. It might not be feasible or possible to make something. Everything has to be evaluated individually.
About features, due to adaptation of IPv6, IPv6 route marking should be implemented ASAP. Also recursive routing should be supported for easy implementation of BGP on IPv6.It is not never. I suggested to stop worrying about it and use v6.
About the features, which features do you need? Remember that MikroTik does not implement features by demand. It might not be feasible or possible to make something. Everything has to be evaluated individually.
my estimation is 1 - 2 yearsGuys, what are you arguing about? Everyone of us knows the v7 release date. Really. Just a mathematics. We are at 6.44 now. Each release requires 3-4 months. So.... 700 - 644 = 56 release cycles. 56 * 4 / 12 = 18,(6) years. So, the year 2037 will be year of 7.00 release!
P.S. Don't thank
You forgot "make me a coffee" button.RouterOS v7 MUST include stable x86-64 architecture for PC. New and old ethernet drivers compatibility, and/or the ability to install custom drivers from linux repositories.
You're right, but lot of people concerns (including me) about the x86-x64 PC support through the forums. So we need a real "official" industrial coffee machine for all.You forgot "make me a coffee" button.
Don't worry. I'm sure it will be fixed with RouterOS v7never ever solved...
This is my expectation as well.I think there's a high risk that some architectures/platforms will be stuck on ROS v6 for flash-size and toolchain reasons. v7 will probably be ARM and x86_64 only, and will probably lack some features thats simply not portable (I guess MPLS- and tunnel stuff).
No worries, mate, just ship all your latest MT products to me I will take them off your hands and will pay shipping LOL. In Nova Scotia, we help you part with those things that are stressing you out. Its the least we can do. Things are so chill here.Wow this is the biggest blunder in the history of the internet.
Such a shame since RouterOS is great except for this problem with IPv6 in general.
This should be open sourced before they go under. Really it's pretty much to late.
I say open source RouterOS 7+ now or die. Release it for the community to make it work. At least they will be able to try and do something.
As long as they get what they need working, other parts can be addressed over time, and not by waiting over 10 years <SHOCKING>.
This is so bad I think you are really left with corruption as the only explanation, (trying hard not to be paranoid) that and incompetency that is not being addressed.
Incompetency can be resolved. Retardation of an entire corporation is mind boggling. No one is at the wheel.
Or get some financing to hire as many experts (all on here waiting for a decade) to add what seems like a simple enough thing.
Can I install https://dd-wrt.com/ DD-WRT on this RB4011 paper weight? Will a refund on my new RB4011 send the right message or should I hope my loses will help support a company that has passed the point of no return, and think maybe it will be usable in a few years,
If we get some kind of source we can replace or another company can maybe take charge. Can this be given to apache.org or something?
How can we as a community get Mikrotik to allow us to take the wheel and get shyt done!? Can we start a class action lawsuit? I'll sign it, I have losses due to negligence. We need to decentralize people. For the Grid with Arduinos or similar (I'm for WiFi GPUs in light-bulbs?).
A boycott? A petition? anything. Something to through a stone at maybe?
Okay so what's my alternative Cisco? Does their GUI need Java so lame or lamer are my two choices. Bummer. "It's mi way or the Huawei." [ No there out too. ]
I know this sounds like a rant but it feels like I'm drowning. So desperate to find real solutions. Best one I can think of would be to open source RouterOS.
Is this link below anything, a download archive of binaries or what? Is there a Git Repo for RouterOS. Who can explain why that is not possible? If not, I think I'm done, because 5 years ago was the time to act on this idea. It's really too late for even that. Just stop fixing ROSv6 it's dead without IPv6. Divert all resources to release even a borken alpha as soon as possible.
https://github.com/robimarko/routeros-GPL
I've burned uncountable hour$ smeared over a number of months tracking down this horrible truth about RouterOS' grievous incompetency. It makes me & us look bad and has jeopardised many other companies with similar pointless losses too. [ It's no longer worth my time to pursue this route. ]
Okay so it's too bad it does not even make coffee but it probably has enough juice for that.
If Mikrotik sold to Google, Google would conclude to do the right thing and shut it down in about 9 days (a current statistical fact about google these days see Google+ etc.).
Can I get on a mailing list for when ROS7 is available just so in another 10 years I can have a good laugh?
Okay now I go get a couple of boxes of paper towels for my tears I'm drowning in.
My final thought to share is that we could have a mass burial. This idea will create a release deadline so on Bury Your Mikrotik Day say April 1st 2020 (joke is on us), we all just say a final goodbye together to a tragic death of a good friend, cut down in it's prime by what is best defined a stupid senseless crime against humanity.
Perhaps MT is counting down ... so next beta from the one shown in video (probably not current any more as @Normis hinted) was beta98 ... and so forth. So v7 will be released to public when count-down reaches beta1From the video:
7.00beta99 so long past beta1 as the title asks for
I have seen v6.99, when MT is working on the fix/debugging of some crash fixed on our routersPerhaps MT is counting down ... so next beta from the one shown in video (probably not current any more as @Normis hinted) was beta98 ... and so forth. So v7 will be released to public when count-down reaches beta1From the video:
7.00beta99 so long past beta1 as the title asks for
viewtopic.php?p=725088#p725088 — isn't that about authenticity?
I can't imagine what Mikrotik stock would be like if they were public. The stock would be more volatile than TSLA based on public statements.dude, honestly i'm not here for the lulz. we work with business customers and we expect clear statements from MT so that we can plan our next hardware purchases.
I think the plan is very clear if you're dealing with Enterprise customers. The "It's ready when it's ready" statement says it allviewtopic.php?p=725088#p725088 — isn't that about authenticity?
dude, honestly i'm not here for the lulz. we work with business customers and we expect clear statements from MT so that we can plan our next hardware purchases.
Unfortunately some of us are in such a scenario where we must decide to work on a custom firmware solution for Routerboard devices or spend the money replacing all Mikrotik hardware.I don't mind replacing everything tomorrow for something else that fulfill my needs.
I fully agree. "It's ready when it's ready" is what a hobbyist writes. Or a beginner.The "It's ready when it's ready" statement says it all
Just like Google, btw.This "It's ready when it's ready" approach is something that shouldn't be part of your PR if you are an enterprise company. If so, then your management is seriously lacking.
Agree, yet Google is not selling any enterprise HW products and no customers are planning any new infra deployments based on their hw etc...Just like Google, btw.
HW products by Mikrotik are mostly fine. It's mostly software which makes us sometimes unhappy. ROS7 is, after all, software which will, hopefully, run on our existing HW. All in all, this is not that far from what we expect from google ... only that for google's services you most of times pay with personal data and for Mikrotik's services you pay with hard cash and electricity ... and receive back some heat (you can't say that about google's services).Agree, yet Google is not selling any enterprise HW products and no customers are planning any new infra deployments based on their hw etc...Just like Google, btw.
I was talking about Google Cloud Services. You pay for it in cash alsoonly that for google's services you most of times pay with personal data and for Mikrotik's services you pay with hard cash and electricity ...
Well that sounds better (but still no heat in exchange I guess). Unlike majority of inhabitants of Earth I value my own personal data and choose to pay with cash ... it's much easier to decide if something is worth the price or not ...I was talking about Google Cloud Services. You pay for it in cash alsoonly that for google's services you most of times pay with personal data and for Mikrotik's services you pay with hard cash and electricity ...
Omg, just ordered rb4011 and I thought something is seriously wrong.Such a shame since RouterOS is great except for this problem with IPv6 in general.
No. It's just a signal of no signal. Typical around these corners...A lot of days without New firmware... Is It a Ros 7 signal?
not yetA lot of days without New firmware... Is It a Ros 7 signal?
What an awesome slogan for Mikrotik!It's getting closer every day!
Don't use that example, we all hope that it will not be vaporware like Windows Phone..."Trust in Mikrotik! What you're waiting for is getting closer every day!" TM
Microsoft tried patenting that for Windows Phone/Mobile, but Mikrotik got there first
Windows Phone was not vaporware, it was real ... shit. And that's why it disappeared real soon ...we all hope that it will not be vaporware like Windows Phone...
Well, it really showed that Microsoft thrives only on existing installed base.Windows Phone was not vaporware, it was real ... shit. And that's why it disappeared real soon ...
Indeed we don't want to see the same thing happen to RouterOS.Well, it really showed that Microsoft thrives only on existing installed base.Windows Phone was not vaporware, it was real ... shit. And that's why it disappeared real soon ...
In a "new market", it really stands no chance against the competition.
However, what I meant is that the platform has almost (and also completely) disappeared many times, with the proponents clinging onto a promised new version time after time.
And every time it failed to deliver. We would not want that same thing happen to RouterOS...
I just want to let everyone know, that v7 is progressing pretty good this year, and most core functionality is usable. Some more difficult parts need to be done and we can release a public beta.
Thanks for the feedback @normis! It sure adds a bit more of clarity, although there's no rough timelines.I just want to let everyone know, that v7 is progressing pretty good this year, and most core functionality is usable. Some more difficult parts need to be done and we can release a public beta.
@normis: so in another words, the easier parts are done and now we are just couple of decades from release?Some more difficult parts need to be done and we can release a public beta.
When it's released.This is the day we were looking for. If there are any memorable dates in the Mikrotikls history, don't forget to add this day to it.
Now the question is: When we will be able to install the first public version?
I was at a MUM recently and they said we could expect "stable" RouterOS 7 release before the end of the year.p.s. Now, before everyone get's super hyped and expects a release next month...Personally, and by experience in the software engineering industry, I don't expect any betas before EOCY 2019 or Q1 2020.
Already answered here!I was at a MUM recently and they said we could expect "stable" RouterOS 7 release before the end of the year.p.s. Now, before everyone get's super hyped and expects a release next month...Personally, and by experience in the software engineering industry, I don't expect any betas before EOCY 2019 or Q1 2020.
However, I should add that it was not mentioned WHICH year that was!
The problem is that this only mentions beta versions.Already answered here!I was at a MUM recently and they said we could expect "stable" RouterOS 7 release before the end of the year.
However, I should add that it was not mentioned WHICH year that was!
Thanks for sharing that! Like I estimated. EOCY or Q1 2020.Already answered here!I was at a MUM recently and they said we could expect "stable" RouterOS 7 release before the end of the year.p.s. Now, before everyone get's super hyped and expects a release next month...Personally, and by experience in the software engineering industry, I don't expect any betas before EOCY 2019 or Q1 2020.
However, I should add that it was not mentioned WHICH year that was!
That is not true. Work on v6 development still continues while v7 is being developed.The problem is that this only mentions beta versions.
I do require more IPv6 functionality (like policy routing, hopefully also NAT66) somewhat urgently for a production environment, not really the place to run early beta versions.
Best would be when that appeared in v6 but as I understood, no more work is being done on IPv6 in RouterOS v6.
But not on IPv6 within v6, as far as I understood. IPv6 is (as a whole) apparently a lower priority than IPv4 within RouterOS.That is not true. Work on v6 development still continues while v7 is being developed.The problem is that this only mentions beta versions.
I do require more IPv6 functionality (like policy routing, hopefully also NAT66) somewhat urgently for a production environment, not really the place to run early beta versions.
Best would be when that appeared in v6 but as I understood, no more work is being done on IPv6 in RouterOS v6.
NothingAny news about ROS v7 in hungary MUM?
Can you give some information on what kernel it will be using 4.x or 5.x?I just want to let everyone know, that v7 is progressing pretty good this year, and most core functionality is usable. Some more difficult parts need to be done and we can release a public beta.
4.xxCan you give some information on what kernel it will be using 4.x or 5.x?I just want to let everyone know, that v7 is progressing pretty good this year, and most core functionality is usable. Some more difficult parts need to be done and we can release a public beta.
I recently visited a MUM and there was no mention in the opening announcement, but the people at the MikroTik desk said "it will certainly be released before the end of the year".Today we have a New mum. I Hope any news about Ros v7 or any improvement in router
=================================================================================================================I recently visited a MUM and there was no mention in the opening announcement, but the people at the MikroTik desk said "it will certainly be released before the end of the year".Today we have a New mum. I Hope any news about Ros v7 or any improvement in router
They did not mention WHICH year.
All I can say is that development of v7 has picked up in the last few months, more than ever. While I can't promise anything stable, it is pretty safe to say, that some kind of public test release (like beta for specific platforms) could be expected this year. The chances of that happening are now higher than ever before, when similar promises were made.
That is not true. Work on v6 development still continues while v7 is being developed.I do require more IPv6 functionality (like policy routing, hopefully also NAT66) somewhat urgently for a production environment, not really the place to run early beta versions.
Best would be when that appeared in v6 but as I understood, no more work is being done on IPv6 in RouterOS v6.
I more need netmap66 - in IPv6 is more actuallyAre you implying that RFC6296 NAT66 and IPv6 policy routing is coming soon, then? It would be great to see it on some kind of product development roadmap!
It's fake, even one of the Mikrotik support personnel joked about the video. Someone was using a custom program to jest with us all.It isnt a fake. It is real but we don't have beta...
from 2.6.29
=)old kernel....
It was fixed in 5.1.11 and even that kernel can be considered old now. The current version is 5.1.15 right now.If you are talking about SACK panic, then all Linux version starting from 2.6.29 are affected.
It's even not this month! Way too old!!!!111oneoneRight ... 5.1.11 released 17 Jun 2019 ...
when it's 1072 with ROS 7 becomes useless. why do we need beta for some devices in the end of this year.... may be. Now mainline kernel 5.2 . The kernel in nonexistent ROS 7 is outdated yet now.time to ask when it comes router os 8 with 5.x.x kernel?When? please an update - we are in so much pain with the existing 1072's and really don't want to replace them all if we don't need to!
Or at least open up a version of CHR for ISO install with Intel drivers...
LOLOL! I'm not sure man kind will be around for a Router OS version 8when it's 1072 with ROS 7 becomes useless. why do we need beta for some devices in the end of this year.... may be. Now mainline kernel 5.2 . The kernel in nonexistent ROS 7 is outdated yet now.time to ask when it comes router os 8 with 5.x.x kernel?When? please an update - we are in so much pain with the existing 1072's and really don't want to replace them all if we don't need to!
Or at least open up a version of CHR for ISO install with Intel drivers...
It is not version 8 it is Buterfly version XLOLOL! I'm not sure man kind will be around for a Router OS version 8when it's 1072 with ROS 7 becomes useless. why do we need beta for some devices in the end of this year.... may be. Now mainline kernel 5.2 . The kernel in nonexistent ROS 7 is outdated yet now.time to ask when it comes router os 8 with 5.x.x kernel?When? please an update - we are in so much pain with the existing 1072's and really don't want to replace them all if we don't need to!
Or at least open up a version of CHR for ISO install with Intel drivers...
Please remember to add Duke Nukem ForeverRouterOS v7 is almost there, just need to add some components...
photo_2019-07-17_11-51-35.jpg
Can it run on rb411 or need a more powerful 4 core processor?RouterOS v7 is almost there, just need to add some components..
Will not run, you need one core per pixel.
CCR1072 seems to be weakWill not run, you need one core per pixel.
But will it run Crysis?RouterOS v7 is almost there, just need to add some components...
photo_2019-07-17_11-51-35.jpg
ROS v7 is IPv6-Ready. Then it will become IPv6-Steady, and finally IPv6-Go!Will ROS v7 sport a IPv6-Ready logo from the beginning?
We won't use ROS v7, ROS v7 will use us ...Another one time... When chupaca... When can we use ROS v7?
Mikrotik is unfortunately now the Netware of networking products. Your decision to switch to Mikrotik was a mistake, they'll seriously lagging behind in standards, features and are still running an old linux kernel.I have migrated my network to mikrotik from ubiquity and im not so sure about this desicion.
Unfortunately you are right.. It was a mistake, There are many people here in spain removing mikrotik devices and switching to ubiquiti, it is sad because i like mikrotik but I fell as they dont worry about they clients...Mikrotik is unfortunately now the Netware of networking products. Your decision to switch to Mikrotik was a mistake, they'll seriously lagging behind in standards, features and are still running an old linux kernel.I have migrated my network to mikrotik from ubiquity and im not so sure about this desicion.
Yes we Are, the Home-Brew Drivers they do, Are 50-70% behind real Performance in PTP and PtmP, new Features, not Seen , real issue with every new chipset (arm Nv2 issue for more than 12 Month), 4011 Turms of 5ghz, don’t work with more than 80 mhz, mu-Mimo (we possible See This when competiors have 802.11ax on market)Are we there yet?
-Yes we Are, the Home-Brew Drivers they do, Are 50-70% behind real Performance in PTP and PtmP, new Features, not Seen , real issue with every new chipset (arm Nv2 issue for more than 12 Month), 4011 Turms of 5ghz, don’t work with more than 80 mhz, mu-Mimo (we possible See This when competiors have 802.11ax on market)Are we there yet?
This Mikrotik Wireless, a dead-end
-Most of the features are implemented, but MU-MIMO is WIPWhat is the current status of wave 2 features in Mikrotik wireless drivers?
-which featues are missing now? we already released the driver update in last betas.
160MHz works, like Reinis said, only MU-MIMO is not implemented as the only remaining Wave2 feature.
Version 6.46beta16 has been released.
*) wireless - improved 802.11ac stability for all ARM devices with wireless;
*) wireless - improved U-APSD (WMM Power Save) support for 802.11e;
Oh but competitors (in the same price segment) have their problems as well... Fast roaming not working right, multicast filtering an all-or-nothing selection only, unusable "optimization" features that lock out a percentage of devices due to incompatibility, etc.Yes we Are, the Home-Brew Drivers they do, Are 50-70% behind real Performance in PTP and PtmP, new Features, not Seen , real issue with every new chipset (arm Nv2 issue for more than 12 Month), 4011 Turms of 5ghz, don’t work with more than 80 mhz, mu-Mimo (we possible See This when competiors have 802.11ax on market)Are we there yet?
This Mikrotik Wireless, a dead-end
shure, but other vendors have a way in the right direction, there HQ and LQ Products everything for the right PlaceOh but competitors (in the same price segment) have their problems as well... Fast roaming not working right, multicast filtering an all-or-nothing selection only, unusable "optimization" features that lock out a percentage of devices due to incompatibility, etc.Yes we Are, the Home-Brew Drivers they do, Are 50-70% behind real Performance in PTP and PtmP, new Features, not Seen , real issue with every new chipset (arm Nv2 issue for more than 12 Month), 4011 Turms of 5ghz, don’t work with more than 80 mhz, mu-Mimo (we possible See This when competiors have 802.11ax on market)Are we there yet?
This Mikrotik Wireless, a dead-end
There is so much missing.....
Wave 1 Missings:
- Output Power Managment
- Spectral Scan
- Channel sizes
Wave 2 Missings:
- no wave 2 features available
What’s about 802.11k, 802.11r and 802.11v, we need that in the EU for every Wireless Network in
Government Places / Meeting Rooms etc
ROFL Keyko, you made my day.Koala PicI just want to let everyone know, that v7 is progressing pretty good this year, and most core functionality is usable. Some more difficult parts need to be done and we can release a public beta.
Thanks, I needed a laugh. If you shilled any harder I would've fell on to the floor laughing.I find Mikrotik has grown a lot over these past 5 years and while many of you question their management decisions, I still think they've been doing well for themselves. Though I agree with @nz_monkey with his "hero car" post that RouterOS is what it's all built on and taking into account that the CCR is, well, at the core of their and our business can't be neglected.
Maybe you are going backwards
Hey, I'm all for smiles and grins but after looking up shill in the dictionary I can honestly say that that wasn't the intention of my post. Yes, I posted in a "take it or leave it" sorta way but not for their sake; for ours. Mikrotik routers sit at the core of our network but we are not in the ISP businness and we're still on 100% IPv4 so we don't have a major grief like you guys do with BGP, etc. We'd be looking elsewhere if it ever came to that, instead of buying CCRs and then whining in a forum. As we did with our wireless gear and switches (none are Mikrotik).Thanks, I needed a laugh. If you shilled any harder I would've fell on to the floor laughing.
Yes, only for ARM architecture and only for hap ac^2 and WAPGR LTE/4G/LTE-US testing, to get v7 ready for upcoming 5G products, according to Sergejs. support for remaining boards will gradually come outI don't speak Russian but I take it that the beta is now available? mt.lv/v7 ?
Thank you for the info. Well played MikroTik. There I was a few posts up saying it'll be v8 that gets released!Yes, only for ARM architecture and only for hap ac^2 and WAPGR LTE/4G/LTE-US testing, to get v7 ready for upcoming 5G products, according to Sergejs. support for remaining boards will gradually come outI don't speak Russian but I take it that the beta is now available? mt.lv/v7 ?
it has v6.45.5 feature set and main change is new Linux Kernel atm, feature will gradually come out in time. First they need help with stability testing on those boards
Hmmm, I just installed it on my cAP AC and it works as expected as cAP.Yes, only for ARM architecture and only for hap ac^2 and WAPGR LTE/4G/LTE-US testing, to get v7 ready for upcoming 5G products, according to Sergejs. support for remaining boards will gradually come outI don't speak Russian but I take it that the beta is now available? mt.lv/v7 ?
it has v6.45.5 feature set and main change is new Linux Kernel atm, feature will gradually come out in time. First they need help with stability testing on those boards
No current ETA can be given but won't be years...Any info about V7 on Tile? (CCR)
No current ETA can be given but won't be years...
Ros v7 is release!
Yup. Got 1 kernel panic so definitely would run this in lab onlyanyone installed it on a 4011 yet?
and you flashed it back to 6.x?Yup. Got 1 kernel panic so definitely would run this in lab onlyanyone installed it on a 4011 yet?
I tried this on a cAPAC which is connecting to a CCR as the manager, but get this on the capacHmmm, I just installed it on my cAP AC and it works as expected as cAP.Yes, only for ARM architecture and only for hap ac^2 and WAPGR LTE/4G/LTE-US testing, to get v7 ready for upcoming 5G products, according to Sergejs. support for remaining boards will gradually come outI don't speak Russian but I take it that the beta is now available? mt.lv/v7 ?
it has v6.45.5 feature set and main change is new Linux Kernel atm, feature will gradually come out in time. First they need help with stability testing on those boards
caps,info CAP connect to ccr1 (::ffff:10.0.0.254:5246) failed: ssl: fatal alert received (6)
caps,info CAP failed to join ccr1 (::ffff:10.0.0.254:5246)
caps,debug ::ffff:10.0.0.4:40338 failed to connect, handshake failed: error 140890e9 (6)
Yes it runs about 30s so upload and Downgrade works....and you flashed it back to 6.x?Yup. Got 1 kernel panic so definitely would run this in lab onlyanyone installed it on a 4011 yet?
decades?No current ETA can be given but won't be years...Any info about V7 on Tile? (CCR)
Okay, that's an announcement! You can just leave it like that...If you are an ISP, please forget about v7 for one more year. It will be in beta for a long time still
You can share the source (url) of the changelog?IMG_20190910_001102_513.jpg
There is no changelog, because this is the first and only release
Changelog:
v6.xx changed to reflect correct version v7.xx
It's already fixed with this script:Since 2013 MikroTik promises to fix bugs with v7 (recursive ipv6 nexthops etc)
Recursive nexthops in v7 works without any scripts.
Woahhhhhhhhhhhh!!!!Recursive nexthops in v7 works without any scripts.
I prefer such a "dated" GUI any time over the "modern" low-contrast borderless black-background layout that others use.Yea the GUI is getting a bit dated, but you have to think of it this way. Mikrotik is such a big tool, rewriting to match something the "U" company has done is no small task.
THIS. I hate the "modern" flat UIs. They are awful, and quite hard to use.I prefer such a "dated" GUI any time over the "modern" low-contrast borderless black-background layout that others use.
Even when selecting the white background I prefer to have borders between stuff and not those large white surfaces with grey or blue text floating in it.