/ip dns static
add forward-to=192.168.89.2 match-subdomain=yes name=otherdomain.lan type=FWD
add forward-to=192.168.89.2 match-subdomain=yes name=89.168.192.in-addr.arpa type=FWD
add forward-to=2001:db8:200::1 match-subdomain=yes name=0.0.2.0.8.b.d.0.1.0.0.2.ip6.arpa type=FWD
This brings us one step closer to Zerotier on CHR. Is there any documentation on how to enable tun/tap devices for a container?*) container - added tun/tap support for containers;
Here's hoping we get a detailed reply, I'm not updating a single ARM device until this is clarified.Is possible to have more detail about «fixed Netinstall procedure for ARM devices», please?
Why would I want to know? To prevent any problems with previous stable versions, until stable 7.5.x is available.
Thanks and good work.
I guess we'll be blessed with CAPsMAN working with wifiwave2 driver in 7.8 or something. Roaming will then get into another dimension (right now it's 1D, it'll become 3D).The last question is where is HW on which I could run this roaming?
Only HAP AC3 and Audience?? That is very sad that MT is not possible to deploy this wifiwave to CAP HW....
Probably it means just that, that they fixed some problems reported in v7 regarding netinstall and arm devices.Is possible to have more detail about «fixed Netinstall procedure for ARM devices», please?
Why would I want to know? To prevent any problems with previous stable versions, until stable 7.5.x is available.
Thanks and good work.
Nor do we, that's why rextended is asking for clarity.I don't know what that means.
Is simple: if on THIS version the "Netinstall procedure for ARM devices" is fixed,*) netinstall - fixed Netinstall procedure for ARM devices;
Sorry, there is nothing in the v7.5 beta that improves eyesight or literacy ;-PPThere's nothing in the changelog about netinstall and "previous versions" so please explain, rextended.
-> viewtopic.php?t=172168*) firewall - added support for RTSP helper;
What is a "RTSP-Helper"? I know RTSP is some kind of Video-Straming Protocol. Why do I need a "helper" and for what reason?
jul/28 00:33:10 container,info,debug /docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration
jul/28 00:33:10 container,info,debug /docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/
jul/28 00:33:12 container,info,debug /docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh
jul/28 00:33:16 container,info,debug 10-listen-on-ipv6-by-default.sh: info: Getting the checksum of /etc/nginx/conf.d/default.conf
jul/28 00:33:22 container,info,debug 10-listen-on-ipv6-by-default.sh: info: Enabled listen on IPv6 in /etc/nginx/conf.d/default.conf
jul/28 00:33:22 container,info,debug /docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh
jul/28 00:33:29 container,info,debug /docker-entrypoint.sh: Launching /docker-entrypoint.d/30-tune-worker-processes.sh
jul/28 00:33:29 container,info,debug /docker-entrypoint.sh: Configuration complete; ready for start up
jul/28 00:33:31 container,info,debug nginx: [alert] could not open error log file: open() "/var/log/nginx/error.log" failed (13: Permission denied)
jul/28 00:33:31 container,info,debug 2022/07/27 16:33:31 [emerg] 1#1: open() "/var/log/nginx/error.log" failed (13: Permission denied)
I guess this is expected. Until 7.4beta5 it was possible to write into non-mounted directories (internal container directories as extracted from tar file), which should not be permitted. I guess you'll either need to mount /var/log, or modify the docker file to mount it as tmpfs. Maybe Mikrotik should allow us to write to those directories but just not save the changes, like docker doesGetting permission error using plain nginx image.
...
root-dir=disk1/nginx. /var/log/nginx is not mounted.
*) ovpn - fixed encryption key renewal process which caused periodic session disconnects;
Check/Update your ticket SUP-67221any official words from MT about icmp/ping issue?
in 7.4 netwatch was fixed, but ping tool doesn't.
regards
Ros
It's added in the documentation:802.11k support
How can configure that?
stop/start newly created and started container and mounts should appear. We will fully fix this in next releases.Containers: is it possible to create mounts that the container can write into? My current tests with this beta show that it's not possible (permission error). It's an important function for many containers.
+1BGP: sessions screen in winbox (3.37) shows an uptime of 497d 02:23:00 shortly after the reboot at installation, ticking DOWN instead of UP!
stop/start newly created and started container and mounts should appear. We will fully fix this in next releases.Containers: is it possible to create mounts that the container can write into? My current tests with this beta show that it's not possible (permission error). It's an important function for many containers.
no update since a month ago :(Check/Update your ticket SUP-67221any official words from MT about icmp/ping issue?
in 7.4 netwatch was fixed, but ping tool doesn't.
regards
Ros
I only find an on/off switch for the feature.It's added in the documentation:802.11k support
How can configure that?
https://help.mikrotik.com/docs/display/ROS/WifiWave2
The current 802.11k/r functionality is just a work in progress in preparation for future use in real applications.I only find an on/off switch for the feature.
Isn't 802.11k supposed to provide the client with a list of neighboring APs? Where does this list come from? I suppose the list should either be manually configurable (I think this is possible in OpenWRT), created by a centralized management solution (like capsman) or populated by the AP itself by scanning its neighborhood (might cause short outages while scanning other channels).
I'm showing my age, but the current Capsman is V2That would likely be part of a new CAPsMAN2 that manages them.
maybe one day rb760 igs SFP port will have (again) SFP status ?*) sfp - fixed "eeprom" reading on single SFP port ARM devices;
MT seems able to identify and fix the issue, producing a test release. I am not able to test it because I don't have spare parts.hi,
with ros 7.5beta4 all the sfp and DAC cables still don't work under ccr2116 & ccr2004. the link just flaps endless, whatever setting you make. reported to support since months now, but still no fix.
even original mikrotik DAC cable doesn't work anymore since ros 7.3. latest working version in terms of sfp support was 7.2.3.
those are the one we have tested in all combinations and are not working in the top of the line mikrotik hardware with the 'stable' ros7 versions:
- mikrotik DAC cable Q+BC0003-S+
- fs.com DAC cable Q-4SPC01
- fs.com DAC cable Q-4SPC03
- fs.com MTP PLFI SM Cable with fs.com sfp
+1Any Chance of Adding Advertisements in BGP Option. Really Useful to Check what is getting Advertised to peers.
Currently in ROSv7 its very difficult to find our the Advertisements compared to ROSv6.
Please Mikrotik Team Look in to it....
+1Any Chance of Adding Advertisements in BGP Option. Really Useful to Check what is getting Advertised to peers.
Currently in ROSv7 its very difficult to find our the Advertisements compared to ROSv6.
Please Mikrotik Team Look in to it....
+1Any Chance of Adding Advertisements in BGP Option. Really Useful to Check what is getting Advertised to peers.
Currently in ROSv7 its very difficult to find our the Advertisements compared to ROSv6.
Please Mikrotik Team Look in to it....
admin@rb-00] /system/package/update> /system/device-mode/print
mode: enterprise
container: yes
[admin@rb-00] /system/package/update> /console/ # no /container command !
clear-history inspect
[admin@rb-00] /system/package/update> /system/package/
update disable downgrade enable export find print uninstall unschedule
[admin@rb-00] /system/package/update> /system/package/print
Columns: NAME, VERSION
# NAME VERSION
0 routeros 7.5beta5
You are providing console output without any question.What am I doing wrong
Thanks you very much for reading my mind... ;-)You are providing console output without any question.What am I doing wrong
Assuming you want container function, you first need to install the container package.
MANY Thanks !!! glad we have people like you on this forum, because... doc writers have a lot to catch up at mikrotik !ech1965, get architecture via /system resource print, download Extra packages, upload container-*.npk via ftp, scp or winbox and reboot to trigger the installation.
Container package is compatible with arm arm64 and x86 architectures.
MANY Thanks !!! glad we have people like you on this forum, because... doc writers have a lot to catch up at mikrotik !
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.Documentation is not yet clear ;-)
* https://help.mikrotik.com/docs/display/ ... quirements page says "container package must be installed" but does not tell you how
* There is no /system/package/install command
* no package repository configured in routeros to list available packages
/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
/system script add name=test policy=test source=":log info test"
/system scheduler add interval=10s name=test on-event="test" policy=test
/system/scheduler/add interval=10s name=test on-event="/system/script/run test\r\n" policy=test
My VRF experiment stranded on this bug but I am running beta version...What's new in 7.4.1 (2022-Aug-04 14:48):
*) firewall - fixed "in-interface-list" matcher when VRF is used;