Such a major blocking issue, it is a shameIncredible that the forgotten space in the message "route,bgp,error HoldTimer expiredpeername" (between expired and peername) still hasn't been fixed...
Such a major blocking issue, it is a shameIncredible that the forgotten space in the message "route,bgp,error HoldTimer expiredpeername" (between expired and peername) still hasn't been fixed...
Amen to that!Shocking story there, Shoka.
Got your tin-foil hat ready for when IPv4 will be deprecated?
So true, unfortunately
Having worked with project mgmt for many years and bitching with devs about versioning for equal amount of years I can only say that the more devs, the more opinions on what the standards are.
Sad.
Nice workChanges since last rc (rc7) Find using compare duplicate cells in Excel.
That's something i'm missing everytime we go out of test/beta/rc to a stable version!Yeah, because it is relative to 7.1. They should have made a changelog relative to 7.2rc7 as well.Tjeez ... that's a LOONG changelog indeed ...
I’m also seeing a memory leak.There seems to be a memory leak somewhere in v7.2rc7:
weekly.gif
monthly.gif
That's right"Partitioning on RB5009 not working" on any 7.0.5+ / 7.1.5- / 7.2rc5- version, regardless terminal, webfig or any (compatible) winbox 32/64 version used
I'm a very positive person, so i'm sure it will helpUnfortunatelly, provoking answer from MikroTik by posting here doesn't work very often.
Latest winboxStill missing other details, like winbox version, if is used webfig, the terminal, etc.
Using latest test version ( 7.2rc5 )You do not provide any useful information, for example RouterOS version...
Using a RB5009 i reach over 700Mbit over wireguard.It appears my Wireguard setup is much slower on the RB5009 than on the RB4011, achieving only 150 Mbps to the same endpoint. Has anyone else experienced this issue?
RB5009 is rock solid here.uh, it's all over facebook and reddit how these lock up and reboot. Basically a clean config with nothing but static routes configured. Plain as it gets.
Reading is a real art.......Is there going to be webfig or WinBox support for ZeroTier instead of just cli?
Did not see any announcement......I'm pretty sure I have seen a 7.2rc2 yesterday in the testing "train" and was about to install in on our lab setup... but no seeing it anymore !? Was it pulled ?
Thanks, great news!Thank you very much for the report. We found out the issue, that some VLAN packets are not processed correctly. We are working on the fix for the issue.
Any suggestions for a device model?
Would be nice to have around 1Gbit speeds.
Every time i think Mikrotik can't fuck there release proces up any more they prove me wrong.To avoid accidental move to v7 from v6, a new channel was added. Use UPGRADE channel for this major upgrade, only if you are sure you are ready for it.
Yep, still a problem on the RB5009No, RB5009 fails. CCR2004 works.Doest this testing version fix the DHCP-PD over PPPoE VLAN interface?
same issue hereI am using PPPoE to get connected to Internet. Still I cannot get IPv6 address from my ISP through IPv6 DHCP Client. It works on v6 though.
Works for me! What is the problem you are encountering? Please show relevant config.
RB5009 IGMP Proxy not working
Now indeed it does, seems to be a temporary hickupPDF works for me............
This makes me very happy, can't wait for the igmp-proxy to be there.....
PIM is already available in rc1. IGMP Proxy will be available in rc2.
Same here, without igmp-proxy i cannot use this versionNo going to GA with no igmp proxy? that's a show stopper for me
How soon is soon?please just wait a little bit, we are preparing for release of the next beta soon
Seriously Normis, please stop this nonsense.What is "release" in your opinion? There is v7 on the download page. Apparently it was released somehow.
works nowCan you try now? it must be working
No issues with IGMP Snooping here using RB4011 and a couple of HAP AC2 devicesIGMP Snooping not work correct with this release.
4x rb2011, 1x CRS106 and 1x HeX
After some minutes the MDB-table is empthy and the multicast flood to all ports :(
Try different settings, not help.
Don't expect rc in for long time, they first need to include all functionality and have that tested for some time.Lets hope to see 7.1 b3 or porbably 7.1 rc tomorrow xD
Is this high on the todo list?There is no multicast package, it is now part of system package, however IGMP-Proxy is not available in ROSv7 at the moment.
Reinis is not a developer
viewtopic.php?f=19&t=93106&start=550#p748615Maybe I am looking with my nose.. but is there a changelog available?
Good point!4.14 has longer EOL than 4.19
There is no v7This is already done in v7Please add IEEE 802.1AE AKA MACSEC to Router & SwitchOS.
There is as you can see at the top of this page:
BETA Testing and Feature Suggestions for the next RouterOS release (ROS v7)
There is no v7This is already done in v7Please add IEEE 802.1AE AKA MACSEC to Router & SwitchOS.
Why not, holds the same informational value: nothingIn that case, please do not say V7 but instead say: Some version we might release in the (probably distant) future
Really?
In that case, please do not say V7 but instead say: Some version we might release in the (probably distant) futureIt doesn't even mean v7 exists.
Exactly my point. The beta with iPhone fixes is not public yet. Please wait a little bit. it's being released today
Will the new driver appear in version 6.X or do we need to wait for the legendary version 7?You are right, that MikroTik made wireless driver doesn't have Wave2 support, so new chipset benefits are not there. We are working on a new driver.
Strange, all works fine here after upgrading to rc64Same problem here, I updated from rc51 to rc64 and now the mikrotik does not seems to forward ipv6 packets anymore.I updated to rc64, but it seems I can not communicate with ipv6. There was no problem with at least rc56.
Then why when upgrading from version 6.42rc20 to version 6.42rc27 the router again ceased to give signs of life?No, only if older version was 6.42rc17 - 6.42rc24
No, only if older version was 6.42rc17 - 6.42rc24
6.42rc24 ....................................... 6.42rc27 how long will this last?
So not gonna happen at all since v6 seems to be te last version for this century given the speed of development.Not gonna happen before v7 due to kernel limitations.
For folks having trouble with IPsec in latest RCs, change your peer generate policy from port-strict to port-override. Support says they are working on a fix for this, but that was enough to get it working for me.