V7.24beta [development] is released!

Announcements
21

was hoping to see some DoH improvements especially related to this error:DoH server response not OK: 0:

22

Beta Should not be on [development]!
Beta (and RC when it arrives that level) should be on [testing]
Alpha (or "ab" as MikroTik calls it) is the one that should be on [development].

image
image823×117 4.9 KB

23 
l3hw - added HW offloaded support for VLAN interfaces created directly on Ethernet for CRS8xx series switches

Does this apply to QinQ as well, or only single tagged?

24

this exactly, just succesfully netinstalled from one mikrotik device to another,

25

The /app YAML syntax for "secrets" (or "secret") is a bit unclear. Perhaps it's intentional to allow both singular secret: and plural secrets:, and allow both a string and array as the secret/s... but IMO it be better is there was ONE correct way to define these things.

e.g. note the various ways "secrets" are defined:

name: librenms
services:
  db:
    image: docker.io/mariadb:10
    secrets:
      - librenms__database_password
  redis:
    image: docker.io/valkey/valkey:8
    secrets:
      librenms__valkey_password

name: roundcube
services:
  roundcubedb:
    image: docker.io/library/postgres:17
    secrets:
      - roundcube__database_password

  roundcubemail:
    image: docker.io/roundcube/roundcubemail:latest-fpm-alpine
    ....
    secret:
      - roundcube__database_password

Further, its bit unclear if the appname__secretname requires the app name: prefix, or if there "global" to all apps, or if it's that is just your own convention in built-in apps.

26
  • l3hw - added HW offloaded support for VLAN interfaces created directly on Ethernet for CRS8xx series switches;

This is exciting! Does this also mean that the underlying ethernet interface no longer has to be added to a bridge to get l3hw routing?

27

This imho fixes the "post quantum key attack" warning you see when connecting via ssh.

28

Maybe in a future version an added switch like :wink: :

/export no-bloody-apps-data

could be added ...

29

Great idea! And it's already implemented! I totally forgot about this feature added in 7.23:

image
image414×133 3.44 KB

So

/export path=!app

does the job. And the bogus directories are also not created on the file system. This is fine as a workaround for me.

30

Enabling netinstall package makes winbox3 to exit right after connecting to the router.

31

how to permanently disable DHCP?

image
image1087×735 102 KB

32

The issue with "/apps" export and extra files will be addressed in the upcoming releases.

33

I would also appreciate it when user-manager data would be part of the user-manager database and its backup, not in /export.

34

Only single tagged.

35

Yes, you can route VLANs by creating VLAN interfaces directly on ether interfaces, on CRS8xx.

36

Content deleted by author.

37

@EdPa Any chance we can get an option with netinstall to keep user certificate store?

Thanks!

38

For me, given how netinstall works and/or is supposed to work, it doesn't make sense... next steps are ask app? ask container? Ask to not "format" the device?......

There are clear and precise methods with which to export all custom certificates in bulk and reimport them later, always in bulk...

39

I know that a system export and import has the certificates store. An option to just backup the certificate store would be great add on for me. I tried using a script but it's not always full proof when a few have a private keys.

Thanks

40 
:local certpass "myprivatepass"

/certificate
:foreach cert in=[find] do={
 :local certname [get $cert name]
 export-certificate $cert file-name="auto_$certname" type=pkcs12 export-passphrase=$certpass
}