11 KiB
AT Telnet Daemon and Simple Admin combo installer/uninstaller
This will install a Combination of https://github.com/natecarlson/quectel-rgmii-at-command-client/tree/main/at_telnet_daemon and; https://github.com/rbflurry/quectel-rgmii-simpleadmin
ONLY FOR THE QUECTEL RM520N-GL
WORK IN PROGRESS NOT READY TO INSTALL
Installation Automated
Script will do everything but setup Nate's at_telnet_daemon
adb shell wget -P /tmp https://raw.githubusercontent.com/iamromulan/quectel-rgmii-simpleadmin-at-telnet-daemon/main/install_on_modem.sh
adb shell chmod +x /tmp/install_on_modem.sh
adb shell sh /tmp/install_on_modem.sh
Uninstallation Automated
Script will ask to remove Simpleadmin then ask to remove AT Telnet Daemon
adb shell wget -P /tmp https://raw.githubusercontent.com/iamromulan/quectel-rgmii-simpleadmin-at-telnet-daemon/main/uninstall_on_modem.sh
adb shell chmod +x /tmp/install_on_modem.sh
adb shell sh /tmp/install_on_modem.sh
2 Original README.md files
AT Telnet Daemon for Quectel Modem
This will provide a telnet interface to the AT command port of Quectel modems that are connected via a RGMII Ethernet interface (aka a "RJ45 to M.2" or "Ethernet to M.2" adapter board). It is an alternative to the ETH AT command interface that Quectel provides, which is a bit flaky and requires a custom client.
The downside is this does require ADB. But that documentation is covered on my main page: https://github.com/natecarlson/quectel-rgmii-configuration-notes
If you're interested in supporting more work on things like this:
Features
- Supports multiple clients connected via telnet at the same time. They will all see the same data. Commands entered by the clients are send in the order they are received; there shouldn't be any problems with commands getting garbled by multiple inputs. (The intent of this is to allow other scripts to connect via TCP and inject commands into the modem.. for example, a connection stats monitoring script.)
- Relatively lightweight; uses the Unix port of Micropython, which is remarkably small. Having Micropython available on the modem also opens up many other opportunities; however, be aware that it isn't at parity with CPython, and that it needs different modules (ie, you can't just use pip.)
Known issues
- This currently only works with RM520 modems! My build environment targeted the library versions of the RM520; the other modems have an older environment. I'll rebuild on an older base version soonish.
- If your telnet client sends each character individually (instead of waiting for you to press enter), this won't work properly. I'll get a patch in for it soonish. I've confirmed that with default settings putty, netcat, and NetKit telnet all work fine. (I'll always recommend using a client that waits to send until you hit enter, though, as it makes it possible to fix type-o's before sending to the modem!)
This currently listens on port 5000 on all interfaces. If you're not behind CGNAT, this is a big risk!It now listens on both IPv4 and IPv6, but sets up a firewall rule to prevent external access. If your public input interface is something under than rmnet+, it will not work, however.- It's also currently unauthenticated.
- The connection is not encrypted.
- The socat binary is from a different source. I will add a public build for it at some point, which will alleviate risk. For now, I haven't seen anything suspicious about it.
- The method I use to interact with the smd11 interface is kind of a kludge right now. Micropython doesn't have direct os.open support, and I haven't been able to figure out a way to interact directly with /dev/smd11 from python without that, due to missing ioctls/etc. So, I've set up a socat instance that listens on /dev/ttyIN and /dev/ttyOUT. I then use a pair of cat's - one reading from smd11 and writing to ttyIN, and one reading from ttyIN and writing to smd11. It's all automated by the systemd scripts, including proper restarts/etc, but it's still a bit of a kludge. I'm open to suggestions on how to improve this.
- I haven't tested this with modems other than the RM520 as of yet.
- I'm not super happy with the micropython build I'm shipping right now - but it does work! I plan on modifying it to clean up the sys.path to make it easier to install additional extensions/etc.
Requirements
- RM520 modem. It will not work on RM50x yet (see above.)
- ADB access to the modem
Installation
- Clone this repository to a host connected via USB to the modem
- In a shell, navigate to the at_telnet_daemon directory.
- Run the following commands from your host:
adb push micropython /usrdata/micropython
adb push at-telnet /usrdata/at-telnet
adb shell chmod +x /usrdata/micropython/micropython /usrdata/at-telnet/modem-multiclient.py /usrdata/at-telnet/socat-armel-static /usrdata/at-telnet/picocom
adb shell mount -o remount,rw /
adb shell cp /usrdata/at-telnet/systemd_units/*.service /lib/systemd/system
adb shell systemctl daemon-reload
adb shell ln -s /lib/systemd/system/at-telnet-daemon.service /lib/systemd/system/multi-user.target.wants/
adb shell ln -s /lib/systemd/system/socat-smd11.service /lib/systemd/system/multi-user.target.wants/
adb shell ln -s /lib/systemd/system/socat-smd11-to-ttyIN.service /lib/systemd/system/multi-user.target.wants/
adb shell ln -s /lib/systemd/system/socat-smd11-from-ttyIN.service /lib/systemd/system/multi-user.target.wants/
adb shell mount -o remount,ro /
adb shell systemctl start socat-smd11
adb shell sleep 2s
adb shell systemctl start socat-smd11-to-ttyIN
adb shell systemctl start socat-smd11-from-ttyIN
adb shell systemctl start at-telnet-daemon
Now, it should be ready for you to connect on port 5000.
Troubleshooting
I can type commands in, but I don't see any output
I haven't perfected the systemd units yet. If it doesn't work, sometimes it might help to stop everything and start it again, one by one..
adb shell systemctl stop at-telnet-daemon socat-smd11 socat-smd11-to-ttyIN socat-smd11-from-ttyIN
adb shell systemctl start socat-smd11
adb shell sleep 2s
adb shell systemctl start socat-smd11-to-ttyIN
adb shell systemctl start socat-smd11-from-ttyIN
adb shell systemctl start at-telnet-daemon
If it still doesn't work, log in and try picocom:
adb shell
systemctl stop at-telnet-daemon
/usrdata/at-telnet/picocom /dev/ttyOUT
..and see if you can issue AT commands. (Ctrl-A, Ctrl-X to exit picocom - hold down Ctrl the whole time.)
If it works there, try manually launching the daemon from your adb shell: /usrdata/at-telnet/modem-multiclient.py. The first thing it does is issues an ATE0 command, so if the bridge isn't working, you will get:
bash-3.2# ./modem-multiclient.py
[2023-07-08 16:21:33: INFO/606ms] AT Server listening on TCP port 5000
[2023-07-08 16:21:33: WARNING/638ms] Did not get expected OK when running ATE0. Result: b''
If it's still not working, let me know!
Simple Web Admin Interface for Quectel Modem using RJ45 Boards
Simple Admin / Monitoring web UI for Quectel modems that are connected via a RGMII Ethernet interface (aka a "RJ45 to M.2" or "Ethernet to M.2" adapter board). Such as Generic RJ45 Board or the MCUZone board
This heavily relies on the work of Nate building on top of at_telnet_daemon which is required prerequisite install before this will work.
Warning
Working in ADB is complex and running additional items not from the factory can be dangerous. Please run this with caution and be warned this comes "AS IS" without warranty and I will not be responsible for anything that happens in result of using this project.
Tested Quectel Modems
Currently Only the RM520 has been tested and determined working, I will be doing additional tests the For the RM502.
If you are able to test on other modems and get it working, feel free to PR.
Requirements
- ADB access to your modem
- Installing Nate's at_telnet_daemon
Installation Automated
Script will do everything but setup Nate's at_telnet_daemon
adb shell wget -P /tmp https://raw.githubusercontent.com/iamromulan/quectel-rgmii-simpleadmin-at-telnet-daemon/main/install_on_modem.sh
adb shell chmod +x /tmp/install_on_modem.sh
adb shell sh /tmp/install_on_modem.sh
Installation DIY
adb push quectel-rgmii-simpleadmin /usrdata/simpleadmin
adb shell chmod +x /usrdata/simpleadmin/scripts/* /usrdata/simpleadmin/www/cgi-bin/* /usrdata/simpleadmin/ttl/ttl-override
adb shell mount -o remount,rw /
adb shell cp /usrdata/simpleadmin/systemd/* /lib/systemd/system
adb shell systemctl daemon-reload
adb shell ln -s /lib/systemd/system/simpleadmin_httpd.service /lib/systemd/system/multi-user.target.wants/
adb shell ln -s /lib/systemd/system/simpleadmin_generate_status.service /lib/systemd/system/multi-user.target.wants/
adb shell ln -s /lib/systemd/system/ttl-override.service /lib/systemd/system/multi-user.target.wants/
adb shell mount -o remount,ro /
adb shell systemctl start simpleadmin_generate_status
adb shell systemctl start simpleadmin_httpd
adb shell systemctl start ttl-override
Access Simple Admin
This will launch on port 8080 by default, you are welcome to change that if you do not desire to use the QCMAP_CLI in the simpleadmin_generate_status.service file.
Launch your browser to http://192.168.225.1:8080
The backend and frontend will automatically update every 30 seconds. Will implement ways to change the update time in the future but will need some additional users testing to see if this is stable enough.
Access Notice!
This is not password protected at the moment, please be careful if you are not CGNAT and have a public IP as this will be available to the public
Note About TTL Mod
If you are currently using Nate's TTL-Override, please remove that systemd service
adb shell /etc/initscripts/ttl-override stop
adb shell mount -o remount,rw /
adb shell rm -v /etc/initscripts/ttl-override /lib/systemd/system/ttl-override.service /lib/systemd/system/multi-user.target.wants/ttl-override.service
adb shell mount -o remount,ro /
adb shell systemctl daemon-reload
Acknowledgements
This heavily uses the AT Command Parsing Scripts (Basically a copy with minor tweaks) of Dairyman's Rooter Source https://github.com/ofmodemsandmen/ROOterSource2203