I was under the same impression after reading Remote access to Raspberry PI 3 in LAN.
That makes perfect sense.
Absolutely. We’d like to be able to debug things locally and run a few commands on the host OS to understand why the device drops the cellular connection. Mostly when we add a new device to the fleet by hanging it up a postlamp, where it is not easily reachable later on.
Our Ublox L210 modem is recognized as an ethernet device so we copy the following file to system-connections
whenever we flash a new device:
[connection]
id=public-cellular
type=ethernet
interface-name=usb0
This being said, I am willing to test your approach with type=gsm
and autoconnect=true
. From what I understand, network management was vastly improved in ResinOS 2.x and the file above was created with Resin 1.x in mind.
Great minds think alike. We already have a pending Jira ticket for this
I will certainly have a look at this too.
Thanks a lot @chrischabot. While the initial issue is not entirely solved yet, I learned a great deal reading your answer.