That is fixed text. I want to see the topics that are visible when logging in memory. These differ per message.Prefix already exist...
That could be, but I wonder how much money they save in the end when it turns out the devices are difficult/impossible to update and they have to send an engineer...I think most of these Mikrotik SMIPS devices are bought by WISPs so they have cheapest possible AP for lowest tier service plans...
No, this is wrong! See reply #216.If, as you say, you have default route, then there is no need to add static routes to nowhere, you can use address lists
It looks like it. That sure is not good! Similar to you, I always add routes like that and they should not simply drop the packets.Have "unreachable" routes disappeared in beta5 (or even before)?
/ip firewall mangle add action=change-mss chain=forward new-mss=clamp-to-pmtu passthrough=yes \ protocol=tcp tcp-flags=syn
9V should be OK though. It is specified for 8-30V. We often run them on 12V instead of 24.Device is shiped standard with a 24V power adapter. Go figure.
I think the problem was in beta4 as well, when I upgraded to beta4 I also had problems but I do not exactly remember what. I started from scratch then as well.Is it a problem with beta4 or beta5?Unfortunately looks like CHR upgrade from beta4 to beta5 may break the image.
Then maybe MikroTik should put that in their .ova files and/or make the disk images that size?There has been a discussion before that images should be 128 MB at least.
I had this issue long time ago with a CHR.
See reply #7 above.Hello everyone, where are the promised BGP filters?
This is the only thing that stops me from moving to v7.
I only have a copy of the machine as it was before I attempted the upgrade. I can send it when no others have a copy of the failed one.Can any one of you send us a RAW disk image from damaged CHR?
There also is a non-DoH resolver memory leak, I have upgraded my test system to check if it has now been fixed. (takes a while)I do not see any information about DoH memory leak fix.Version 6.49beta22 has been released.
So it's still not fixed?
When you want that kind of throughput, MikroTik wireless is not the best choice for you (except maybe the 60 GHz products).I often do stuff that requires a gigabit internet connection, and getting even close to that with wireless would be great.
That is the COPY button that is already there.I'd love to see "duplicate" command for firewall rules, to create similar rule. Especially useful if want to try something by copying old rule and then temporary disable old one. And when create several similar rules.
Did you know that /export verbose works when /export doesn't? For me that was a great discovery!I wish MT acknowledged the problem so that not everybody (and their dog) reports it as some great discovery.
You are right! /export verbose works correctly, only when verbose is omitted it is slow and generates crashdumps.Follow up:
I noticed that verbose exports are considerably faster. Can someone else confirm that?