Resetting Bearer on OpenWRT

[Amol Lad]

Hi Enrico,

Can you please share what you did to address this?

I think this is very much desired enhancement especially when the signal is not that great and there and frequent disconnections/reconnections occurring.

Thanks
Amol


The information in this email communication (inclusive of attachments) is confidential to 4RF Limited and the intended recipient(s). If you are not the intended recipient(s), please note that any use, disclosure, distribution or copying of this information or any part thereof is strictly prohibited and that the author accepts no liability for the consequences of any action taken on the basis of the information provided. If you have received this email in error, please notify the sender immediately by return email and then delete all instances of this email from your system. 4RF Limited will not accept responsibility for any consequences associated with the use of this email (including, but not limited to, damages sustained as a result of any viruses and/or any action or lack of action taken in reliance on it).-----Original Message-----
From: ModemManager-devel <modemmanager-devel-bounces at lists.freedesktop.org> On Behalf Of Enrico Mioso
Sent: Sunday, 8 September 2019 12:55 PM
To: Aleksander Morgado <aleksander at aleksander.es>
Cc: ModemManager (development) <modemmanager-devel at lists.freedesktop.org>; James Hilliard <james.hilliard1 at gmail.com>
Subject: Re: Resetting Bearer on OpenWRT

Hi!
On Sun, 8 Sep 2019, Aleksander Morgado wrote:
> Absolutely no idea, because I don't know how netifd expects that to be
> reported or how it does connection monitoring. Any info on how that
> works would be appreciated.

I admit I didn't follow the entire discussion from the beginning, so sorry for the noise in case what I am telling is useless.
From my unerstanding, anyone please correct me if I am wrong, lots of relevant code is in OpenWRt's netifd-proto.sh.
From my understanding, netifd expects to be informed by protocol handlers about when things change, especially because in this case the network interface wouldn't change it's state apparently.
So, as righly pointed out by you, MM may directly emit ubus events simulating what a protocol handler does, or it may invoke a shell script carrying out that task, keeping the state consistent.
This is what I did in AGH - I am not saying it's the best solution, but that's the route I choose.


Enrico
_______________________________________________
ModemManager-devel mailing list
ModemManager-devel at lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel