However, I’ve no idea how your device is meant to be used once it’s connected a an USBNET device. And now you’ve just posted, and you’ve got a problem.
You’re connected to your beaglebone via USB too which may cause problems. You’re only allowed to use one instance of a gadget driver, total. So you can not use USB serial, or USB networkign to the beaglebone in order for your device to work. You’re going power via barrel jack, connect to the beaglebone over the ethernet port. OR if you want to still power via USB, you’re going to have to figure out how to disable the USB gadget drivers for the beaglebone, while still having it available for your external device. I did notice you had TTYACM0 enabled so that’ll definitely have to go away.
@Robert, my brain is mostly fried today . . . is there a way for him to use g_multi, so he can have his TTYACM0, but disable the boards USB ethernet so his device can use the cdc driver ?
But now how do I test I am connected out that way instead of over the ethernet cable lol?
At the end of the day I want these devices to talk out the cell module to cloud servers and be able to acess them in the field via ssh. I have statically provisioned SIM cards so I can get to them.
usb1 is probably your external device. But you can find out via dmesg by issuing . .
$ dmesg | grep usb1
And using deductive reasoning. But also, once you get your cdc device working, I do not know how it’s meant to be used. Robert Suggested pppd which suggests to me it’s meant to be used a some sort of modem ?
They do not have firmware yet that supports pppd. I use ppp for other modems that do support it and that works this guys is just different (until firmware is baked).
Got the device to give me a connection to the outside world on the new kernel (4.1.21-bone-rt-r20, running Debian 8)
Had to add
auto usb0
iface usb0 inet dhcp
I now have a connection out. This modem in effect now is acting like a router. I have LAN address and not a WAN so I can’t ssh back to device from outside world. Working on that now.