Hmmm… I wonder which part of these instructions on the help page was not clear.
https://help.mikrotik.com/docs/display/ROS/Container
Container package needs to be installed
I agree with you (and I have proposed several times) that the package menu should have some sort of listing of available packages and a way to install them by command (both commandline and the GUI version) instead of having to fiddle with zip files and uploading.
It should be easy to do, as the required packages are available from the upgrade server. The device knows how to download them when you do an upgrade. So why not when initially adding them?
No idea.
I will apologize, you are correct.
https://help.mikrotik.com/docs/display/ROS/Packages
That page does NOT indicate HOW a package should be installed …
But that’s nothing new related to this release, is it ?
bug report:
ppp on-up and on-down scripts do not run when they have empty line after their (script)name in profile window.
please fix it. it was annoying.
volkirik, your issue is not related to 7.5beta.
E.g. on 6.48.6:
/system script add name=test policy=test source=":log info test"
/system scheduler add interval=10s name=test on-event="test\r\n" policy=test
Will not run, but
/system script add name=test policy=test source=":log info test"
/system scheduler add interval=10s name=test on-event="test" policy=test
Will.
The newline makes the difference between a script (name) and actual code. I think this is by design.
So if you reference to a script (name) in any code window (ppp/dhcp/scheduler/…), make sure you don’t append a newline.
this design must be fixed sir!
No, it must not. If you want a newline, use this:
/system/scheduler/add interval=10s name=test on-event="/system/script/run test\r\n" policy=test
Should work…
Hopefully there will soon be a new beta that fixes this:
What’s new in 7.4.1 (2022-Aug-04 14:48):
*) firewall - fixed “in-interface-list” matcher when VRF is used;
My VRF experiment stranded on this bug but I am running beta version…
So that fix…did NOT fix?
I think pe1chl wants to test this on 7.5betaX and not 7.4.x, and that the fix came out on 7.4.x before 7.5betaX.
That is right, it is a bit strange that a fix is released in the stable version before first trying it in a beta…
I tried to convert my manually setup config that uses 2 route tables, BGP and routing rules into a VRF config and it failed in the firewall config that entirely uses interface lists.
Of course I have 2 partitions so I reverted to my config prior to this change (which I copied). So when a 7.5beta with this fix is released I will try again.
same here.
indeed weird that its fixed in stable channel while not in testing.
What’s new in 7.5beta8 (2022-Aug-09 12:36):
*) bridge - fixed “new-priority” value validation for NAT rules;
*) certificate - fixed handling of empty AKID by SCEP client;
*) container - fixed free disk space checking;
*) dhcpv4-server - fixed removal of dynamic leases when server is removed;
*) health - fixed “temperature” and “power-consumption” readings on RB1100x4;
*) health - improved voltage reading on CRS112-8P-4S;
*) hostpot - fixed Walled Garden functionality for HTTPS sites;
*) hotspot - automatically reject all HTTPS requests passing through HotSpot server for unauthorized users;
*) hotspot - limit maximum allowed connections based on free RAM resources;
*) hotspot - removed “https-redirect” option;
*) ike2 - allow sending certificate chain as initiator;
*) leds - fixed wireless LED functionality on LHGG;
*) lte - disallow empty APN name only for default entry;
*) lte - fixed UDP performance on MMIPS devices;
*) ping - improved service stability;
*) rb5009 - fixed ether1 status reporting after system reboot;
*) routerboard - added “reset-button” script feature for TILE devices;
*) sfp - improved combo SFP ports initialization handling on CRS312-4C+8XG, CRS328-4C-20S-4S+;
*) ssh - added AES support for PEM decryption;
*) switch - removed limit for number of hardware-offloaded bonding interfaces;
*) swos - fixed SwOS upgrade procedure on CRS305-1G-4S+;
*) vrrp - added “sync-connection-tracking” compatibility with preemption-mode;
*) vrrp - fixed HW offloaded bridge MAC address learning when changing from VRRP master to backup;
*) vrrp - fixed high CPU usage when “sync-connection-tracking=yes” and the backup router goes offline;
*) vrrp - fixed initial connection tracking synchronization, a backup router now always receives all existing connections;
*) vrrp - improved connection tracking synchronization protocol (CTSYNC), the new protocol is incompatible with previous RouterOS versions with “sync-connection-tracking=yes”;
*) wifiwave2 - disable wireless interface after wireless configuration reset;
*) wifiwave2 - fixed group key update for client devices which connect via fast BSS transition;
*) wifiwave2 - fixed usage of Canada country setting on US locked devices;
*) wifiwave2 - improved default channel width selection for interfaces in station mode;
*) wireless - fixed interface initialization on x86 devices;
*) x86 - allow downgrading to RouterOS v6 only if it was previously installed;
is this
*) ping - improved service stability;
the fix about ticket 67221?? varius ping issue posted into the forum?
yes it should fix various reported ping issues
I hope we will see this fix in a stable release soon.
almost one year after the first report… Just to learn…
4 months just to fight about it is a real issue and not a configuration issue
3 months to fight about a x86 pltaaform issue… “x86 is dead use chr…” Chr had the same issue… then “it is a mellanox issue…:”
then just 5 months to fix it…
12 months where the first 7 seven could be saved…
regards
Ros
Any chance the broken Detect Internet feature is going to be fixed soon (report since 7.2)?
Thanks!
Yes, stop using it.
I was hoping the container fix was miraculously related to this:
container,info,debug 2022/08/10 13:53:18.589837 [fatal] Cannot create DNS data dir at /opt/adguardhome/work/data: mkdir /opt/adguardhome/work/data: permission denied
but apparently not 
Stop using containers.
Helpful, right?