L009, latest stable RouterOS.
DHCP Server/Leases: many of the (actively dedicated) addresses has an invalid “bridge port”.
Now I realized some of them also has “sfp1” as bridge port, but I don’t have “sfp1” (I disabled it).
Is this a known issue?
Without your config, there will be no chance to help.
Will post it later.
In the meantime can anyone answer to this please:
In the winbox gui, there is “bridge port" field in leased DHCP address list. But in /ip/dhcp-server/leases/print detail there is no info about “bridge port”.
Am I having an improper gui table config? == is “bridge port" field actually meaningless in dhcp leases?
If you look in the documentation, you'll see that there is no property, including read-only ones, for the bridge port. The same applies to the IP -> ARP table. The property does not exist, you won't see it if you use the REST API to fetch the tables either, but you see it listed in WinBox/WebFig.
From my observations, the bridge port information is pulled by WinBox/Webfig themselves, by combining with the data from the Bridge -> Hosts table (/interface bridge host). On my RB5009, probably due to the way the data is extracted from the switch chip, this Bridge Hosts table is very slow. It takes seconds for the table content to appear. The same delay happens with the Bridge Port column of the DHCP Leases table: while the other columns of the lease table is populated instantly, the Bridge Port column first shows "unknown" everywhere. Only after a few seconds delay do the "unknown" placeholders change into the real port values, it's the same in WebFig. My guess is that WinBox/WebFig fetches the bridge host data from the API and populate the Bridge Ports column afterwards by matching the MAC addresses between the two datasets. The Bridge Ports data is not included in the initial Leases table content.
The Bridge -> ARP table delays the display of the whole table though. However, the whole delay here appears to be because it's pulling the host name information from the other menus too. And there is no delay with the REST API (which provides no Bridge Port or Host Name data).
The Bridge -> Hosts delay does not exist on the other MikroTik models that I own. And on those devices, there is no delay with the Bridge Port column display on the DHCP Leases table..
So, if you see wrong values under the Bridge Port column, first check the Bridge -> Hosts table if the value there are also wrong.
Thank you! Indeed strange: after a power-cycle, all bridge ports (in dhcp table) are seems correct now.