What advantages does DoT have over DoH? If you had to pick one, is that the one you prefer? Why?
hecatae - Congratulations, that was fast 
Znevna - We will re-check this issue with repartitioning.
Sob - We will check what we can do about NAT netmap functionality in ROS.
memelchenkov - Works for us. Can you provide supout file from this device to support@mikrotik.com which would be generated right after you have tried to make a backup?
anav - The particular case which we did manage to reproduce and fix was that router could freeze, go to unusually high CPU usage, or reboot when wireguard interface was being added/removed.
return container support
Any idea when we might see better logging for the routing components of v7 ?
There is only one big difference. DoH uses https port, so can’t block by port. DoT uses a known port, so operators like it, since they can block it.
SUP-84114 just filed. Thanks!
I noticed it used the configuration i had used to try ( in a previous version in the past ) but didn’t work.
It seems it keeps the configuration you created in the past and uses that on upgrading.
In my case it created 4 partitions as i tried to create before.
Yeah I thought so too.
Scary a little, isn’t it?
soon! just some minor things left.
disabling default bgp template and enabling it result to invalid flag, workaround remove the default template and create again from scratch!
p.s i don’t have issues with container support in MT, but first prioritized the core routing features of v7 specially BGP and MPLS support and general stability over all of the ROS v7, there were a lot of people buying high end CCR with V7 only OS as an ISP core router and suffering set back in deploying it in production from mild to extreme case, we have a few people and colleague deploying MT in internet exchange only to be embarrassed and bring other gear in a next few weeks and throw a towel as a result.
@ MT Please take this criticism carefully we really loved your product you are getting there but please add more resource on your BGP/MPLS programmer and Q&A department
Please if you do have roadmap please published it, people don’t necessarily influence the direction of ROS v7 we just want to gauge on where we at and what were are going to do also in the future, we just want a respect for what we deserved
Yay! I’ll take your word for it so maybe already next week? 
Joking apart, it’s good to know that work is in progress, thank you!
Another release without full VRF functionality (as attested by posts from buset1974 and loloski above).
I’m perplexed that we’re up to a dot-four release, but there still appear to be chunks of L3 VPN functionality missing. These are not bugs; they are things that haven’t even been implemented. Specifically, output filters don’t work and it’s not possible to use the mangle to look up routes in a VRF.
Can MikroTik provide some indication of when this might be addressed?
In RB5009 - cannot disable and/or remove DHCP client with “D” flag (not enough permissions). DHCP client is appearing automatically after plug in USB Huawei LTE modem (3372h).
On 7.3 stable release I can remove dhcp client without any permissions issues.
It seems that the terminal icon in the web login page is missing… (hap ac3, accessing from iPadOS 15.5/safari)
*) webfig - updated WebFig HTML files with the new MikroTik logo and removed Telnet option from index page;
Maybe the user-manager could use some makeovers too?
Would MT care enough to implement the reseller functionality in the user manager?
*) mpls - fixed VPLS functionality when PW peer is an immediate neighbor;
I hoped this would fix the VPLS crash I have been experiencing - alas, it has not. One ping goes through and then one core of my device goes to 100% and it locks up and eventually reboots on its own.
NAT with IPSEC with Use IP Firewall enabled still not working correctly. Connections are freezes. Fortunately, Bridge Filter Marks now works!! So IP Firewall for some (incl. my) cases may be replaced with Bridge Filter. I’m done with IP Firewall but who cares about it, beware.
So … any more details around this? Is this an interim fix or rather permanent? And how does it affect performance?
I can say it has “fixed” the port flapping issue I’ve had since 7.x was released on my CRS328. I’ve been running 7.4beta2 since June 7, and haven’t had a single port flap since. I’d been having port flapping every 5 minutes to a few hours (once I disabled anything that wrote to NAND) prior to this release, on all versions of 7.x. It seemed to be related to NAND operations, in my case, but that may have just been one of the triggers.
My switch isn’t doing anything taxing so I can’t speak to performance implications, and I do have the same question(s). It seems like a kludge type of fix vs. root cause, but I am extremely happy to have a stable network again after 6+ months of trying to get traction on my support ticket until it was taken seriously.
CRS328-24P-4S+ is advertised as having one CPU core, and it had one in v6.
Product code CRS328-24P-4S+RM
Architecture ARM 32bit
CPU 98DX3236
CPU core count 1
It got one extra core enabled for some reason in v7, which probably was not supposed to happen. Don’t sweat about it.