Like on 1 out of 100 devices its useful and on 99 useless? Useless codestuff imho...It's not useless, it can be used as Capsman to manage devices using new wifi driver.
Thanks!To my understanding:
1- yes.
2- correct, consequence from having (wave2) wifi in base package now.
3- yes. See also 2.
oh god no!! I am still recovering from nat-ein, which gave me severe depression and life-crisis...*) firewall - added "nat-pmp" support;
7.12 not working with CCR2004-1G-12S+2XS and RJ45 SFP-GB-GE-T , very sad thing, you fix one thing and break another.
/tool traffic-generator quick stream=UDP1,UDP2,UDP3 pps=1
:delay 1s
/quit
/tool traffic-generator quick stream=UDP1,UDP2,UDP3 pps=1
:delay 1s
/tool traffic-generator stop
Is this sill the case? I did a lot PIM-routing stuff around 2018/2019 with ROSv6 and it worked really good.PIM is non-functional on RouterOS v7.
Thats a simple DNAT-rule.everything that comes from 10.10.10.10 and goes to 192.168.35.10 translate it to 192.168.1.10
Even after reading this a few times, I dont know what this means?*) bridge - prevent bridging the VLAN interface created on the same bridge;
I remember that topic, this was a very specific use-case.Ask that in the topic about "Full-Cone NAT"... those people seem to have a use for it.
We get things like a disk manager, instead of some long awaited fixes in the basic functionality of a router.
because I find such rules unnecessary cosmetics
Without the SNAT-rules, the whole concept wont work (assuming the DNS-Server is in the same (V)LAN as the DNS-Client)!![...]there should be no need for your extra sourcenat rules!
where can I find macsec settings in winbox?
PPTP and public-IP - enough information, simply dont do this!!we have a pptp server that has public ip address...
/tool netwatch edit [/tool netwatch find comment~"DNS1"] up-script=""
Any suggestions?expected end of command (line 1 column 70)
Did you a downgrade beyond the factory-firmware?Updated soft- and firmware on these models without any issues:
CCR2004-1G-12S+2XS
ROS 6.49What version is your routerboot(firmware) at?