Before an upgrade: Remember to make backup/export files before an upgrade and save them on another storage device; Make sure the device will not lose power during upgrade process; Device has enough free storage space for all RouterOS packages to be downloaded. What's new in 7.23.1 (2026-Jun-02 12…

Rewrite Radius-Request username with Circuit-ID DHCP-Option82 or PPPoE+ Option82(or PPPoE+) sub-options Are we talking about DHCP sub options with Mikrotik Device ? I have done this with my RB750GL long time ago, with my old IPTV. [image] DHCP Option help General …

[image] patrikg: Are we talking about DHCP sub options with Mikrotik Device ? Yes, we are talking about DHCP Sub-Options... But no in the scope you are mentioning. In the message of this topic you replied I mentioned using the information that comes on Option82, parse/cut/append the string,…

Every piece of information exchanged between the DHCP-Client and DHCP-Server is done via HEX-Encoded "options", indeed But this is "internal behaviour" and should, ideally, never leak into userspace. RouterOS already deals with this for a number of DHCP Options All of those are either: availab…

[image] jbl42: Which actually uses an ASCII string after the binary header. Yes, and it's the "opaque" part that the RFC talks about. Only the 0x01 0x08 part (the sub-option type and the 8-byte length) has a specified format in the RFC. The part that follows is vendor specific and is only sp…

[image] CGGXANNX: You can use the thousands of helper tools/pages and convert the substring you want to search into hex and input that content in the search field? Winbox should be the tool for this, in my view. You shouldn’t have to use some external tool just to make the raw byte value rea…

[image] CGGXANNX: This is clearly not the case. No one modifies the content of the fields in the packets by hex-encoding them. The original bytes stay the same as added by the first relay agent that added the option 82. The later relay agents only completely remove/replace the option (if they do…

[image] fischerdouglas: APPEND their info to the already existent Circuit-ID info on Option-82. And that behavior goes against the RFC recommendations. You can read this section 2.1.1 RFC 3046 - DHCP Relay Agent Information Option 2.1.1 Reforwarded DHCP requests A DHCP relay agent may recei…

[image] CGGXANNX: Yes, and it's the "opaque" part that the RFC talks about. Only the 0x01 0x08 part (the sub-option type and the 8-byte length) has a specified format in the RFC I never argued in a different direction. The point is circuit-id does not have to be ASCII, but is is allowed to c…

BUG in firmware or Upgrade script issue for older AC devices with wifi-qcom-ac package? My 4 CAP devices (cAP AC and wAP AC, all with IPQ4019 chip and wifi-qcom-ac package) dropped their wifi networks on update to 7.23.1. Wifi interfaces where there but would not go active showing as disabled in in…

I also have one cap ac under capsman control. None of the described issue happened to me. Any upgrade since I can remember, including 7.23.1, went flawlessly. But I usually upgrade as soon as a new stable/testing version is available. So I can't speak for what happens on larger gaps when e.g. upgrad…

7.23.1 [stable] is released!

Announcements

EdPa July 6, 2026, 10:20am 187

Version 7.23.2 has been released: