API. Listening interfaces and bridges doesn't report deletions

RouterOS Scripting
1

Hello.

As subject says, using the commands:

/interface/listen ?dynamic=true?#|
/interface/bridge/listen ?#|

never receive a reply when I delete any dynamic interface (actually, PPPoE clients) or delete bridges.
But, I receive replies when new dynamic interfaces are created or new bridges are created or modified.

It’s just an example; I can receive pppoe clients disconnections in /ppp/active/ path. But, what about bridge?

On the other side, users (by /user/listen command), addresses (/ip/address/listen) and prots (/interface/bridge/port/listen) reports everything just fine.

Must I listen bridge in other path?

2

Try to use

/interface/print
=follow=
?dynamic=true
?#|

instead.

Print with “follow” behaves pretty much the same as “listen”, as “print” is supposedly the only command that can accept queries.

3

Thank you for your interest.

I did some tests and found this “tips”.

  • There are bridge, vlans, etc .dead replies while listening to /interface/. Deeper than this path (like /interface/bridge or /interface/vlan) don’t reply.
  • There is not .dead replies from dynamic interfaces while listening to /interface/ Must listen on their specific path (/ppp/active, for example)
  • Using listen or print =follow= behaves identical regarding .dead replies.
  • Queries with listen, actually works!! Is it a new non-notified API feature? (Because in documentation especifically says what you said: queries only works with print/getall command)
  • “OR” and “AND” Query calculation where there is only one query word, doesn’t works. It makes sence, because it’s intended for 2 values.

Not sure if I’m correct or wrong.

4

Yeah, I’ve also noticed that “/listen” is effectively an alias for “/print” with “follow-only” argument.

The .dead replies not being consistent across menus is probably a RouterOS bug.