No, this has always been the case - really annoying. The bridge uses the mac-address of one of the slaved interfaces. Use Admin Mac on bridges.
Frankly, the feature list is a bit disappointing after such a long wait and after seeing some of the feature matrices on the help site.
Which features are missing in your opinion?
avahi / mdns-reflection; I have to do this on a raspberry pi now. It’s a necessary feature, if you separate your iot stuff from production networks.
To be clear: I mean the list of new/updated features in the “What’s new in 7.1beta3”.
I hoped for BGP GUI. What I got was BGP that no longer works (even in commandline, see report above).
I am hoping for new features in IPv6, including NPT. (I think policy routing is already getting better)
LHGGR


DHCP leases as DNS entries without scripts.
+1 Would be nice to have a checkbox on a lease / pool
LHGGR
My routes didn’t upgrade too it’s stuck on “calculate download size”
تم الإرسال من Redmi Note 8 Pro باستخدام Tapatalk
LHGGR
You cannot update that way. You have to download it yourself, upload to the router, and reboot.
Hello, i try to install on X86.
[admin@mikrotik] /system package> print
Flags: X - disabledNAME VERSION SCHEDULED
0 ipv6 6.42.12
1 security 6.42.12
2 dhcp 6.42.12
3 mpls 6.42.12
4 routing 6.42.12
5 advanced-tools 6.42.12
6 ppp 6.42.12
7 system 6.42.12[admin@mikrotik] /system package> update download
channel: development
current-version: 6.42.12
latest-version: 7.1beta3
status: ERROR: missing ipv6-7.1beta3.npk
Is IPv6 not implemented yet?
thanks,
glueck
AGAIN: you cannot update it that way.
Download the package from the website, upload it to your router, and reboot.
And at least make sure you have a backup of your system that you can restore outside of RouterOS (like a disk image), as it is probably going to fail.
Certainly when you try to update from such an ancient version!
Why don’t you update that to 6.47 first???
AGAIN: you cannot update it that way.
Download the package from the website, upload it to your router, and reboot.
And at least make sure you have a backup of your system that you can restore outside of RouterOS (like a disk image), as it is probably going to fail.
Certainly when you try to update from such an ancient version!
Why don’t you update that to 6.47 first???
Yes, sorry. I do it that way and it worked!
thanks,
glueck
I changed both my simple queue and my queue-tree back to sfq and my router has remained stable for 14 hours. I SOO wanted CAKE to be ready for primetime usage on my home router but as I stated above it was causing reboots every 30-45 mins or so. Heres hoping they get the kinks ironed out in the next release.
please remember that this is an unstable beta, and things can and will break. Please report your findings to support or here. The version is not ready for commercial use on important systems
Reporting that on multiple CCR2004 with zero configuration that the system is barely responsive.
catched the same problem on my ccr2004 with 7beta3. 7beta2 worked more stable
ok, NOW hap ac3 makes perfect sense, it was custom made for new wireless package. and works on my device like a charm, i need to double check it but the feel is that mobile devices have easier time to communicated to AP when i’m on the far side of the house. Normal home GW features work like a charm, will play with new queueing shortly.
Only issue so far is that one of the old laptops refuses to connect to new wireless driver, and nothing in the logs. will have to dig into what chipset is there, some kind of Intel that is all i can say so far.
Which features are missing in your opinion?
Macvlan feature missing
Just a quick update/feedback on wifiwave2 on an Audience
As mentioned, the default scripts do not work, even with a factory reset. So I had to connect via MAC, setup a bridge, add wifi 1/2/3 and ethernet to it, assign dhcp client so I can give it an IP.
On my Surface Pro 5, I would get with the old drivers 150-230 on a fast.com speedtest (I have a 1GB download connection but the Surface is only 2x2). With wifiwave2, it seems to be 190-250 more consistently, as well I see an anecdotal boost in range as well, except in one dead spot in my house but nothing works there as it is over the garage.
I tried running the command to kick off weak signal’ed devices but it crashed the router when I tried and had to be factory reset.
Seems like a good first step…and since my Audience isn’t my primary router ( I have a Hap AC for that) I don’t care that the default script didn’t work.
Which features are missing in your opinion?
Unicast VxLAN tunnels would be of great use.
A better explanation of route filters.
Zerotier