Plug in modems seem to remain tricky to control on Linux (used to use AT commands, some probably still do - I've done so with 3G sticks in the past; it was not straightforward...).
On large Linux distro's NetManager app now seems to dominate in attempt to work for all connection types. I suspect their are graphical frontends for this available from the major distro repos.
NetworkManager, uses ModemManager for modems like LTE ones:
https://www.freedesktop.org/wiki/Softwa ... edDevices/
Pointer to main page re: NetworkManager includes url links at foot of the target-gnome-NetworkManager page for different major distros such as Arch and Debian:
https://www.freedesktop.org/wiki/NetworkManager/
Maybe someone who writes Puppy internet connection frontends has all this worked out, so can hopefully help. I have a suspicion, but I may be wrong, that Puppy doesn't cater for this connect scenario well. If they don't, and can't, then I'd say Puppy should move to using NN/MM as well - though a bigger download than Puppy maybe wants, but NN/MM seems to be no where near as plugNplay as MSwindows in this regard.
I don't have a plugin modem of sort described, but if I did, I would certainly go with the upstream NetManager/ModemManager methodology (with MM's mmcli utility to get modem status and control it). Not using systemd may make things difficult nowadays documentation-wise...
The following has some instructions for when systemd used and when systemd not used:
"Gathering debug logs when using systemd"
"Generic steps to gather debug logs, when not using systemd"
details here:
https://www.freedesktop.org/wiki/Softwa ... Debugging/
Even Arch Linux wiki is less than wonderful on this topic. To make matters more complicated, there is tons of old out-of-date now useless information out on the web...
I hope what I am writing is relevant to the original post; I know nothing much about this topic so wouldn't be too surprised if miles of base.