Quick follow-up question - with this inside the 10-report-down script:
IFUP=$(ifstatus ${CFG} | jsonfilter -e '@.up')
logger -t "modemmanager" "interface ${CFG} (network device
${INTERFACE}) ${STATE}"
proto_init_update $INTERFACE 0 proto_send_update
$CFG [ "${IFUP}" = "true" ] && ifup ${CFG}
Arjen Smit writes:
> This question actually does extend to IPv6, here also via the available
> control protocol (QMI/AT/etc) the connection is initiated. It is the modem
> firmware that runs a SLAAC client process to receive a /64 prefix. Then
> the data interface on the host is able retrieve
> > If you could have it debugged a bit more, e.g. with gdb in order to
> > get a backtrace, that would be great. Not sure how easy that is in
> > your target device though.
> >
>
> I tried briefly, but the problem is that gdb slows everything down, and
> this messes with all the connection
Hey,
>
> I have a further question about all of this.
>
> My script works in that I see disconnect reported at 11:18:08 and then
> wan back up 11:18:13, but that is a fairly slow reconnection. My modem
> RG502Q-EA in Zyxel NR7101 supports automatic reconnect with something
> along the lines of
