![]() So, I unplug/replug again, and now everything is working, but not really dependable for an enterprise class product. So, just to play around some more because I really didn't do anything besides unplug it, then plug back in I decide to reboot it just to make sure it comes back up.DAMN THE WORLD SUCKS AGAIN! Now, the thing has a public IP, but no luck getting to the Internet. And, crazy enough I do an ifconfig and now the interface has a public address on it, so I ping 8.8.8.8 and it works.HOORAY ALL IS GOOD IN THE WORLD! Or at least I thought. So, just to see what happens I unplugged the modem/plugged back in. I have rebooted the server several times so far, but it has never had any effect. ![]() Originally, when I posted this the new interface was getting a private IP in 192.168.1.x/24 (.2 in this case), which is the private network that it uses when setting it up to communicate with the modem if you need to. Actually, to better describe it, it is working under specific circumstances. I have it working now, or better yet it has decided to work and I didn't do anything but dumb luck trial and error troubleshooting. Ok, so I have an update.kind of strange behavior. Note: If you are powering your USB modem from a Raspberry Pi, it is a good idea to enable the full 1.2A current throughput for the USB ports, you can see how to do this here With some of the modems listed in the ModemManager Supported Devices list you may find they struggle to connect, this is most likely due to usbmodeswitch not knowing how.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |