/tool/flood-ping - failure: not allowed by device-mode

RouterOS General
1

Good morning everyone,

I’d like to let you know that I’m reporting an issue with the [/flood-ping] tool. I updated to version 7.18.2 and it stopped working.

Hardware:
routerboard: yes
model: CCR2004-1G-12S+2XS
revision: r3
serial-number: XX
firmware-type: al64
factory-firmware: 7.16.1
current-firmware: 7.18.2
upgrade-firmware: 7.18.2


System mode sample:
system/device-mode/print
mode: advanced
allowed-versions: 7.13+,6.49.8+
flagged: no
flagging-enabled: yes
scheduler: yes
socks: yes
fetch: yes
pptp: yes
l2tp: yes
bandwidth-test: yes
traffic-gen: no
sniffer: yes
ipsec: yes
romon: yes
proxy: yes
hotspot: yes
smb: yes
email: yes
zerotier: yes
container: no
install-any-version: no
partitions: no
routerboard: no
attempt-count: 0

Error:
/tool/flood-ping address=192.168.1.1 count=200
failure: not allowed by device-mode

Any recommendations for enabling this feature?

Regards.

2

The notorious device mode has been discussed much on this forum. Search around.

Also:
Device-mode

3

I hope your device is near you… device-mode is the worst mikrotik idea.

You have to enable the socks.

4

@dang21000
please do not write random useless things without any use or any solution.

what is off is on OP, for example… traffic-gen



But can I know or not why you never read the changelogs???

paste this on terminal and simply press reset button on 10 seconds.
/system device-mode
update activation-timeout=10s mode=advanced flagged=no flagging-enabled=yes bandwidth-test=yes container=no email=yes fetch=yes
hotspot=yes ipsec=yes l2tp=yes pptp=yes proxy=yes romon=yes scheduler=yes smb=yes sniffer=yes socks=yes traffic-gen=yes
zerotier=yes install-any-version=no partitions=yes routerboard=yes
for previous versions some items like install-any-version=no partitions=yes routerboard=yes must be removed, and mode=enterprise, etc. etc.

5

Answer for OP to use flood ping:

system/device-mode/update traffic-gen=yes