That is the problem, WPA2+WPA3 will not work with all clients. Especially old and IoT clients have trouble with that.
You can only use WPA2 and when you want WPA3 you need to put that on a different SSID.
Indeed it works, but how reliable is that? Is there a description somewhere?Code: Select all2600::
![]()
This is just WRONG!!!/interface/bonding/ set LAG2 arp=proxy-arp disabled=yes
Flash memory full?After upgrading old RB2011 to 7.19 beta7, can't upload anything any longer (e.g. can't upgrade to beta8). File list empty. Scripts that create backups fail.
What's up with that?
https://help.mikrotik.com/docs/can you share the documentation link, google was not enough for me to find itAs is stated in the documentation, the check for locally originated routes is "if ( bgp-network )"
what do you want to achieve?anyone have problem with bgp filtering for local as?
regexp ^$ or bgp-path-len < 1 did not works
Are you calling us from 2010? Or is it an April fools joke?in the future when IPv6 implementation start rising massively
/routing table
add disabled=no fib name=test
add disabled=no fib name=test
Please read the posting again. What works for 16MB devices should work for all, but it does not.They do kind of, on 16MB (and some other) devices upgrade packages are downloaded to RAM not disk...
+1@MT any chance on fixing BGP sessions refresh on winbox3 just like how ros v6 behave?
Ok, that hints that the bug is actually not in RouterOS but in the terminal emulator part of WinBox 4.Get some serious terminal emulator (not putty or winbox terminal). Then you won't see/have any issues.
Look on page 1 of this topic!I have upgraded a PPC 1100AHx2 router to 7.18.2 from 7.13 and the login page is messed up. Any ideas?
Correct, I edited it. I meant ax2.AC2 only has 128Mb RAM ??
It's AX2 we're talking about.
Yes, that certainly is the case. Netinstall and import an export made just before (not a restore of a backup).Thanks for the advice, It seems based on this that it would be recommended to netinstall when moving from v6 to v7.
:error can only exit with error. what would be useful is an exit that exits without error.It's not related to loops and there is an :error command already for that.
Please read previous replies to a release thread before adding another.After the update, openvpn is rebooting the rb on each external connection made.
Well in the Newsletter #123 topic it already begins... "we want ZFS, not BTRFS".Prophecy?
I use BGP routing, and I am sad it no longer works reliably (as it did in v6 and for some time in v7, I would say between 7.10 and 7.15).+1, I couldn't agree more. I use those features, and I am happy with the functionalities they provide...