other:hardware:mudi
Differences
This shows you the differences between two versions of the page.
| — | other:hardware:mudi [2023/02/22 06:49] (current) – created - external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Mudi Cellular Router ====== | ||
| + | I have a real need for some kind of Internet communication independent of someone else's connection. I work remotely at times. I'm also a technician and occasionally clients need me because their Internet service is down. | ||
| + | |||
| + | I have several choices. I can use my T-Mobile Cell phone (which has a hot-spot capability), | ||
| + | |||
| + | Mine was getting old, so I decided it was time to replace it. I wanted to find something that better met my needs. After a lot of searching, I found the Mudi; a portable 4G/LTE router from a company I never heard of named [[https:// | ||
| + | |||
| + | https:// | ||
| + | |||
| + | It is actually a router, with [[https:// | ||
| + | |||
| + | It also has the ability to do wired networking. That is a major thing I wanted. //And// it comes with the necessary hardware already (a USB-C dongle with a network connection and a power passthrough, | ||
| + | |||
| + | I got mine today, went to the T-Mobile store and got a SIM, plugged it in and booted up, connecting from my Chromebook using the simple instructions on the card included. Went through the very simple configuration screen and, boom, it is working. I'm not a big fan of " | ||
| + | |||
| + | Out of curiosity, I ssh'd to the routers IP. ssh root@router.ip, | ||
| + | |||
| + | At my company, we build routers and sell them to clients, so of course, my office has one. Mine has an extra port for Internet access which was planned for a fail over in case my primary Internet Service Provider went down (which happens). One of the reasons I wanted the LAN connection was to be able to plug this in when that happened again. | ||
| + | |||
| + | I plugged the Mudi into my SmartAppliances router and, with a few simple configuration changes, my Mudi is now my backup Internet connection. I tested it by setting the Mudi as the backup WAN device, then unplugging the primary device. The router realized it was down and automatically swapped to the cellular router. | ||
| + | |||
| + | There was a lot of thought put into this, or maybe it is a function of OpenWrt; I don't know. But, the device will act as a router, an Access Point and a Range Extender. The wired network connection can be b4e your LAN or used as the WAN source, but with your device(s) protected by the firewall. | ||
| + | |||
| + | The DHCP server allows you to use static IP Binding (aka Sticky IP). The firewall lets you set up port forwards, open up ports on the router, or even set up a DMZ. Oh, and you can tether the device to your cell phone, so the data flows through there instead of devices actual data plan. | ||
| + | |||
| + | You can even plug in a microSD filled with files and access them directly from devices plugged into the router. It appears to only support SMBv1 and SMBv2, so I had problems connecting from my Chromebook, since it appears to only support SMBv3 (native, I got it working with an app from the AppStore). The block device (USB/ | ||
| + | |||
| + | Oh, and good documentation: | ||
| + | |||
| + | Had a small problem. When I tested it the first time, I found that [[https:// | ||
| + | |||
| + | Bad news; this appears to only work flawlessly with T-Mobile in the US. There are several comments at [[https:// | ||
| + | |||
| + | I'm very pleased with this purchase, and wish more people would monetize Open Source (and give some of the money back to the developers). | ||
other/hardware/mudi.1676450125.txt.gz · Last modified: (external edit)
