The official Mikrotik router thread

I hope this information helps someone in the future - I spent a bit of time stuck on this.

I'm running DHCPv6 relay on a MikroTik and needed devices to use their DHCPv6-assigned addresses instead of SLAAC addressing.

To prevent the Mikrotik from advertising the prefix information while still sending Router Advertisements (so devices can get a default gateway), you need to disable the autonomous flag (A-Flag) under /ipv6/nd/prefix

Example:
/ipv6 nd prefix default
set autonomous=no

Alternatively, use advertise=no and add prefix in /ipv6/nd/prefix manually with whatever parameters you need.
 
5/22 13:57
RouterOS 7.19 [stable]

What's new in 7.19 (2025-May-22 10:53):

*) arm64 - fixed possible transmit queue timeout on CCR2216, CCR2116, RDS2216;
*) arp - added warning, when "Published" ARP entry used on an interface with "reply-only" ARP mode enabled;
*) bgp - added input.filter-community;
*) bgp - fixed excessive CPU usage;
*) bgp - fixed input.accept-community;
*) bgp - fixed memory leak on receiving notify and closing session;
*) bgp - improved performance on BGP input;
*) bonding - added setting for LACP active/passive modes;
*) bridge - added new STP monitoring fields for bridge and ports (Tx/Rx BPDU, Tx/Rx TC, forward/discard transitions, last topology change, message-age, max-age, remaining-hops, bridge-id);
*) bridge - fixed bridge port hang when using invalid port IDs;
*) bridge - fixed dhcp-snooping in QinQ setups;
*) bridge - fixed issue when local MACs were removed unnecessarily;
*) bridge - fixed minor memory leak on link down;
*) bridge - fixed multicast packet flow on hardware offloaded bridge which acts as "multicast-router";
*) bridge - improved default bridge and port layout on console and GUI;
*) bridge - improved stability in case of configuration error (introduced in v7.15);
*) bridge - moved "TCHANGE" logs from bridge,stp to bridge,stp,debug;
*) bridge - offload VXLAN only if another HW offloaded port exists in the bridge;
*) bridge - properly flush bridge hosts when bonding is used as bridge port and loses hw-offloading status;
*) bridge - rename "ports" to "interface" under MDB table for configuration consistency with other menus;
*) bridge - renamed STP monitor fields (port-number to port-id, designated-port-number to designated-port-id, designated-bridge to designated-bridge-id);
*) bridge - show designated-* monitor field for all port roles;
*) bridge - show warning instead of causing error when using multicast MAC as admin-mac (introduced in v7.17);
*) bth - properly specify "in-interfac...
 
DStvNothingOn said:
5/22 13:57
RouterOS 7.19 [stable]

What's new in 7.19 (2025-May-22 10:53):

*) arm64 - fixed possible transmit queue timeout on CCR2216, CCR2116, RDS2216;
*) arp - added warning, when "Published" ARP entry used on an interface with "reply-only" ARP mode enabled;
*) bgp - added input.filter-community;
*) bgp - fixed excessive CPU usage;
*) bgp - fixed input.accept-community;
*) bgp - fixed memory leak on receiving notify and closing session;
*) bgp - improved performance on BGP input;
*) bonding - added setting for LACP active/passive modes;
*) bridge - added new STP monitoring fields for bridge and ports (Tx/Rx BPDU, Tx/Rx TC, forward/discard transitions, last topology change, message-age, max-age, remaining-hops, bridge-id);
*) bridge - fixed bridge port hang when using invalid port IDs;
*) bridge - fixed dhcp-snooping in QinQ setups;
*) bridge - fixed issue when local MACs were removed unnecessarily;
*) bridge - fixed minor memory leak on link down;
*) bridge - fixed multicast packet flow on hardware offloaded bridge which acts as "multicast-router";
*) bridge - improved default bridge and port layout on console and GUI;
*) bridge - improved stability in case of configuration error (introduced in v7.15);
*) bridge - moved "TCHANGE" logs from bridge,stp to bridge,stp,debug;
*) bridge - offload VXLAN only if another HW offloaded port exists in the bridge;
*) bridge - properly flush bridge hosts when bonding is used as bridge port and loses hw-offloading status;
*) bridge - rename "ports" to "interface" under MDB table for configuration consistency with other menus;
*) bridge - renamed STP monitor fields (port-number to port-id, designated-port-number to designated-port-id, designated-bridge to designated-bridge-id);
*) bridge - show designated-* monitor field for all port roles;
*) bridge - show warning instead of causing error when using multicast MAC as admin-mac (introduced in v7.17);
*) bth - properly specify "in-interfac...
Click to expand...
7.19 is now the latest update you can get on any of the channels.
The dev channel is running 7.19rc3 which is older than 7.19.

RouterOS v7 has a very different dev cycle to v6. The v6 days were wild in comparison.
 
RouterOS 7.19.1 [stable]
May 26th 2025, 07:51
What's new in 7.19.1 (2025-May-23 17:27):

*) certificate – fixed support for certificates imported or added in RouterOS v7.4 or earlier (introduced in v7.19);
*) console - improved stability when a running script is removed;
*) container - stability improvements;
*) disk - fixed RAID component size to match the value in the superblock;
*) disk - improved handling of RAID spare disks;
*) disk - improved stability when using RAID;
*) ethernet - fixed flow-control for RB5009;
*) iot - fixed incorrectly shown LoRa payload RSSI values;
*) poe-out - fixed PoE-out reset when inserting specific SFP modules on RB5009;
*) poe-out - upgraded firmware for 802.3at PSE controlled boards (the update will cause brief power interruption to PoE-out interfaces);
*) routing-filter - use zero as default as-path length (allows matching empty as path);
*) sfp - correctly classify 100Mbps modules as "100M-baseFX";
 
Anyone experiencing any stability issues on 7.19.1?

I've now had the router lock up twice this weekend where I needed to do a power-off restart to get it back up again. Earlier today it hung as well but recovered (was unresponsive to pings for 1-2mins) so I don't know what to make of this. Nothing in the logs and everything else with the router seems to be working as it should.

Mikrotik hEX S.
 
What's new in 7.19.2 (2025-Jun-20 10:55):



*) bfd - fixed socket leak;

*) bgp - fixed withdraw when input.accept-nlri is non-existent;

*) btest - properly close unsuccessful TCP test sockets;

*) console - added prompt to /disk/format command;

*) disk - do not allow to start Btrfs replace command when a Btrfs replace process is already running;

*) disk - improve disk file system detection;

*) hotspot - allow only "http:" and "https:" schemas in dst field;

*) iot - added LoRa interface recovery mechanism;

*) iot - LoRa stability improvement;

*) iot - LR8G/9G firmware update;

*) ip-service - fixed "print count-only interval" when dynamic entries are added (introduced in v7.19);

*) ip-service - fixed setting services by name (introduced in v7.19);

*) ipsec - fixed responder on key exchange compute failure (introduced in v7.19);

*) ipv6 - do not show IPv6 FastPath as active when connection tracking or IPsec is used;

*) l2tp-ether - fixed interface creation/removal process;

*) lte - added support for R11e-LTE6 v039 firmware release;

*) lte - do not dial further if modem detects eSIM without profiles;

*) lte - fixed eSIM management function for mmips and mipsbe architecture CPUs;

*) lte - fixed eSIM provisioning for servers that do not send content-length in the HTTP response;

*) route - fixed destination ordering for SNMP;

*) route - fixed SNMP probing of IPv6 routes;

*) route - make routing table print faster with hw-offload, gateway and blackhole queries;

*) switch - fixed ACL rules when ports are not specified (fixes dynamic rules for RoMON);

*) switch - fixed advertise and speed settings for ether1 on RB5009 (introduced in v7.19.1);

*) webfig - improved screen reader support for WiFi fields in Quickset;

*) webfig - make combobox accessible to screen readers;

*) webfig - more space to branding logo;

*) wifi-qcom - fixed beacon loss issues and improved stability for IPQ-6018;

*) wifi-qcom - improved regulatory compliance;

*) winbox - fixed "Last Topology Change" for bridge port monitor;
 
7.19.3 dropped:


*) bridge - allow IPv6 FastPath when dhcp-snooping is enabled;
*) iot - LoRa LNS stability improvement;
*) lte - AT modems, fixed typos in commands sent to modem when APN with authentication is used (AT+CGAUTH; AT$QCPDPP);
*) lte - R11e-LTE and R11e-LTE6, fixed possible crash on device unexpected removal or during RouterOS shutdown;
*) mpls - improved stability when handling VPLS packets;
*) radius - fixed RADIUS client section becoming unresponsive when RadSec is configured, but server is not responding;
*) radius - fixed wrong RadSec port number in logs;
*) radius - properly verify certificate when RadSec is used;
*) sfp - added sfp-power-class and sfp-max-power monitor values for QSFP;
*) supout - added IPv6 NAT section;
*) switch - fixed ACL rules with "redirect-to-cpu" (introduced in v7.19.2);
*) switch - fixed bonding issues after switch reset (introduced in v7.18);
*) switch - fixed port blocking with spanning tree on EN7523 switch (introduced in v7.19);
*) swos - changed firmware file location (URL) for software update checks;
*) system - reduced RouterOS ARM package size;
*) winbox - show/hide corresponding fields when switching RADIUS client mode between RadSec and UDP;
 
PhireSide said:
7.19.3 dropped:


*) bridge - allow IPv6 FastPath when dhcp-snooping is enabled;
*) iot - LoRa LNS stability improvement;
*) lte - AT modems, fixed typos in commands sent to modem when APN with authentication is used (AT+CGAUTH; AT$QCPDPP);
*) lte - R11e-LTE and R11e-LTE6, fixed possible crash on device unexpected removal or during RouterOS shutdown;
*) mpls - improved stability when handling VPLS packets;
*) radius - fixed RADIUS client section becoming unresponsive when RadSec is configured, but server is not responding;
*) radius - fixed wrong RadSec port number in logs;
*) radius - properly verify certificate when RadSec is used;
*) sfp - added sfp-power-class and sfp-max-power monitor values for QSFP;
*) supout - added IPv6 NAT section;
*) switch - fixed ACL rules with "redirect-to-cpu" (introduced in v7.19.2);
*) switch - fixed bonding issues after switch reset (introduced in v7.18);
*) switch - fixed port blocking with spanning tree on EN7523 switch (introduced in v7.19);
*) swos - changed firmware file location (URL) for software update checks;
*) system - reduced RouterOS ARM package size;
*) winbox - show/hide corresponding fields when switching RADIUS client mode between RadSec and UDP;
Click to expand...
Updated 2 devices and all good.
 
Updated to 7.19.4 last night and since then, I see these errors in my log:

1754502709571.png

Repeating every 30 seconds. Thing is, PoE is disabled as that port goes to the Ubiquiti PoE injector that then leads to my Unifi AP AC LR. I tried it on Auto On as well, but there seems to be no change.

I wonder if this has anything to do with my constant AP rebooting that I have every few weeks?
 
PhireSide said:
Updated to 7.19.4 last night and since then, I see these errors in my log:

View attachment 1839405

Repeating every 30 seconds. Thing is, PoE is disabled as that port goes to the Ubiquiti PoE injector that then leads to my Unifi AP AC LR. I tried it on Auto On as well, but there seems to be no change.

I wonder if this has anything to do with my constant AP rebooting that I have every few weeks?
Click to expand...
So interesting it bypasses the dumb injector and the router sees the request. Unfortunate it generates an error for something it should not acknowledge as you have PoE off, but still interesting

Its new so maybe they will refine it and you wont see the errors - log - output PoE-Out LLDP negotiation to poe,info topic;

My guess is the reboots are coincidental, but no idea. Out of interest what are you supplying PoE from that router. Is the "we dont have any more power" correct? Can scotty not give the captain anything more :)
 
Well, from my calcs the HeX S should be able to give 12 watts total (500mA * 24v), which is more than the Unifi AP AC LR is asking according to the LLDP message above.

According to the AP spec sheet, the max power draw of the AP ought to be 6.5w, which is within that power budget, so I am not sure why the PoE injector is asking for more than that, as the LAN port on the injector is coupled to ether5 which is the PoE out port on the Hex S.

In any case, maybe the reboots are related, or maybe not. What I did for now, is turn off Neighbour discovery in IP -> Neighbor. Oddly enough, keeping it enabled but disabling "LLDP PoE Power" made no difference. What did make a difference is turning Discovery off altogether.

The correct thing to do would be to move the cable to another ethernet port on the HeX S which has no PoE out at all, and see if I get any funny messages logged then. That sounds like a job for another day though.
 
PhireSide said:
According to the AP spec sheet, the max power draw of the AP ought to be 6.5w, which is within that power budget, so I am not sure why the PoE injector is asking for more than that, as the LAN port on the injector is coupled to ether5 which is the PoE out port on the Hex S.
Click to expand...
The AP through the injector is demanding its full 802.3af limit of 15.4W My suspicion is you would see the same error message on a non PoE port.

Wonder if that handshake keeps happening on all passive injectors. Do you know if thats a 24V or 48V injector? If its 24V that could maybe explain the continued request
 
yogidabear said:
The AP through the injector is demanding its full 802.3af limit of 15.4W My suspicion is you would see the same error message on a non PoE port.

Wonder if that handshake keeps happening on all passive injectors. Do you know if thats a 24V or 48V injector? If its 24V that could maybe explain the continued request
Click to expand...
I switched it to ether3 on my router (my spare port) and reconfigured the right VLAN tags, then reenabled Neighbor discovery and so far it hasn't returned. So it seems like something to do with ether5 (the only PoE out port) that is causing the messages in the log even when PoE is set to disabled.

It's very strange, maybe like you said a bug that needs to be squashed as it only started appearing with 7.19.4.

It's the injector that I got with the AP; if memory serves it is a 24v 0.5A passive injector (POE-24-12W-G)
 
PhireSide said:
I switched it to ether3 on my router (my spare port) and reconfigured the right VLAN tags, then reenabled Neighbor discovery and so far it hasn't returned. So it seems like something to do with ether5 (the only PoE out port) that is causing the messages in the log even when PoE is set to disabled.

It's very strange, maybe like you said a bug that needs to be squashed as it only started appearing with 7.19.4.

It's the injector that I got with the AP; if memory serves it is a 24v 0.5A passive injector (POE-24-12W-G)
Click to expand...
Yes it was introduced in this version, not the bug the functionality :) yes they were supplied with 24V injectors so that could be the issue. The poe negotiation is never completed as 48V is never supplied. Thanks for reporting all this as I think its interesting.
 
yogidabear said:
Yes it was introduced in this version, not the bug the functionality :) yes they were supplied with 24V injectors so that could be the issue. The poe negotiation is never completed as 48V is never supplied. Thanks for reporting all this as I think its interesting.
Click to expand...
It would have helped had I read the release notes properly...


*) log - output PoE-Out LLDP negotiation to poe,info topic;

🤦‍♂️

At least moving the cable from ether5 to ether3 has cleared up the errors...small win, I suppose.
 
Hi all,
anyone use Tailscale on their MikroTik?
Scenario: Son is remote from home, but want to use DSTV stream. I was thinking to set up a VPN on the Mikrotik, so he can connect to it, to do the "phone home proximity" check all the streaming services use these days. Will something like this work?
 
LandyMan said:
Hi all,
anyone use Tailscale on their MikroTik?
Scenario: Son is remote from home, but want to use DSTV stream. I was thinking to set up a VPN on the Mikrotik, so he can connect to it, to do the "phone home proximity" check all the streaming services use these days. Will something like this work?
Click to expand...
I use Tailscale but it runs on a machine within my LAN, not on the Tik itself.

What router do you have?
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X