[FS#3499] [netifd] no way to monitor the real state of a connection via protocol handlers
openwrt-bugs at lists.openwrt.org
Sat Feb 5 12:47:25 PST 2022
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#3499 - [netifd] no way to monitor the real state of a connection via protocol handlers
User who did this - Aleksander Morgado (aleksander0m)
I haven't seen your reply until now; sorry!
We recently discussed about how to best handle this in the MM mailing list, and a solution like the one you suggest, using `proto_init_update $ifname 0; proto_send_update`, makes sense.
The way forward I'm suggesting is to allow ModemManager to run "post-event" dispatcher scripts; e.g. we could allow the user to have custom scripts that are run by the MM daemon when a given connection is connected or disconnected. Then, the openwrt packaging could provide a script to call on network-triggered disconnections, which would do the `proto_init_update $ifname 0; proto_send_update` call to notify netifd that the connection is really down.
What do you think of this? It would not require a separate daemon to monitor the connection, it would all be managed by MM and the openwrt-installed dispatcher script.
More information can be found at the following URL:
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
More information about the openwrt-bugs