Re: [LEDE-DEV] Open and secure firmware for Quectel 4G modems [Was: Re: Quectel EC20 QMI autoconnect issues [Was: Re: [LEDE-DEV, 3/3, v3] uqmi: Prevent 'POLICY MISMATCH' error.]]

Harald Welte writes: > On Sun, Jan 08, 2017 at 11:10:20PM +0100, Bjørn Mork wrote: >> Note that there is nothing Quectel here. This is a standard Qualcomm >> platform. The output above comes from the Sierra Wireless EM7455 >> originally delivered as part of my Lenovo X1

Re: [LEDE-DEV] Open and secure firmware for Quectel 4G modems [Was: Re: Quectel EC20 QMI autoconnect issues [Was: Re: [LEDE-DEV, 3/3, v3] uqmi: Prevent 'POLICY MISMATCH' error.]]

Hi Bjorn, On Sun, Jan 08, 2017 at 11:10:20PM +0100, Bjørn Mork wrote: > Note that there is nothing Quectel here. This is a standard Qualcomm > platform. The output above comes from the Sierra Wireless EM7455 > originally delivered as part of my Lenovo X1 Carbon, running bog > standard firmare.

Re: [LEDE-DEV] Open and secure firmware for Quectel 4G modems [Was: Re: Quectel EC20 QMI autoconnect issues [Was: Re: [LEDE-DEV, 3/3, v3] uqmi: Prevent 'POLICY MISMATCH' error.]]

Hi Petr, On Sun, Jan 08, 2017 at 08:26:23PM +0100, Petr Štetiar wrote: > Indeed, it's very interesting and very scary. This modems are quite powerful > devices, usually equiped with very good, but limited uplink connection, still > making it ideal candidate for DDoS botnet for example, like any

Re: [LEDE-DEV] Open and secure firmware for Quectel 4G modems [Was: Re: Quectel EC20 QMI autoconnect issues [Was: Re: [LEDE-DEV, 3/3, v3] uqmi: Prevent 'POLICY MISMATCH' error.]]

Petr Štetiar writes: > Bjørn Mork [2017-01-08 23:10:20]: > >> The output above comes from the Sierra Wireless EM7455 originally delivered >> as part of my Lenovo X1 Carbon, running bog standard firmare. > > Oops. How did you get into the shell of your modem? Is it a

Re: [LEDE-DEV] Open and secure firmware for Quectel 4G modems [Was: Re: Quectel EC20 QMI autoconnect issues [Was: Re: [LEDE-DEV, 3/3, v3] uqmi: Prevent 'POLICY MISMATCH' error.]]

> Adding laforge and zecke to the Cc loop. > > Matti Laakso [2017-01-08 14:39:34]: > > Hi, > > > I'm almost done with checking the connection state using a > > proto_run_command with a simple script running uqmi --get-data-status > > periodically. If the check fails, the

Re: [LEDE-DEV] Open and secure firmware for Quectel 4G modems [Was: Re: Quectel EC20 QMI autoconnect issues [Was: Re: [LEDE-DEV, 3/3, v3] uqmi: Prevent 'POLICY MISMATCH' error.]]

Bjørn Mork [2017-01-08 23:10:20]: > The output above comes from the Sierra Wireless EM7455 originally delivered > as part of my Lenovo X1 Carbon, running bog standard firmare. Oops. How did you get into the shell of your modem? Is it a root shell also? Seems like some serial

Re: [LEDE-DEV] Open and secure firmware for Quectel 4G modems [Was: Re: Quectel EC20 QMI autoconnect issues [Was: Re: [LEDE-DEV, 3/3, v3] uqmi: Prevent 'POLICY MISMATCH' error.]]

Petr Štetiar writes: > Adding laforge and zecke to the Cc loop. > > Matti Laakso [2017-01-08 14:39:34]: > > Hi, > >> I'm almost done with checking the connection state using a proto_run_command >> with a simple script running uqmi --get-data-status

[LEDE-DEV] Open and secure firmware for Quectel 4G modems [Was: Re: Quectel EC20 QMI autoconnect issues [Was: Re: [LEDE-DEV, 3/3, v3] uqmi: Prevent 'POLICY MISMATCH' error.]]

Adding laforge and zecke to the Cc loop. Matti Laakso [2017-01-08 14:39:34]: Hi, > I'm almost done with checking the connection state using a proto_run_command > with a simple script running uqmi --get-data-status periodically. If the > check fails, the script dies and