Working with OpenWRT | Here, a number of work results from the OpenWRT world are presented. |
Scripts:
- The script /etc/hotplug.d/tty/10-persistent_ttys creates persistent USB tty device links under /dev/serial/by-port . Never again need to mess with reordered tty devices after plugging USB serial adapters or after reboot...
Modules:
- Some CAN modules are missing from the official builds (yet), so please find here a makefile package/kernel/linux/modules/can.mk (and config.ar71xx to build your own, use as .config in build root) and some pre-built 19.07.1 ar71xx modules for the candlelight FW-based CAN/USB adapters (gs_usb.ko) and the virtual CAN tunnel vxcan. Patch for the endianess bug in gs_usb is here.
NB: these need to be installed used opkg --force-depend install ./abc.ipk because of the different kernel build IDs. Will try to fix this later...
Prepared images, mangled or custom-built:
- This is my OpenWRT 18.06.1 image to flash straight onto a TL-WPA8630 V1, which usually does not work with sysupgrade or factory images:
openwrt-18.06.1-ar71xx-generic-tl-wpa8630-v1-sqfs-initial.bin
Please note you can upgrade using regular sysupgrade images once flashed.
- This is my OpenWRT 18.06.1 image to flash straight onto a TL-WPA8630P V1, which usually does not work with sysupgrade or factory images:
openwrt-18.06.1-ar71xx-generic-tl-wpa8630p-v1-sqfs-initial.bin
Hacking and preparing patches:
- This is my OpenWRT 18.06.2+ snapshot (heavily based upon work from here) for i.onik Cloub Hub, aka LogiLink UA0175, firmware-wise the same as LogiLink WL0156 (possibly WL0157) and WiFi-S1 Storage Sharer:
openwrt-18.06-snapshot-r7704-9ee8c8daf4-ramips-rt305x-ionik-cloud-hub-squashfs-sysupgrade.bin
Installation from USB (eg) with normal image:Please note: for opkg, this goes to a private repository (free to use), to keep kmod versions aligned with this build.
# (connect to LogiLink SSID) telnet 10.10.10.254 # (use root/91657853) cd /media/Disk1 # (continue with mtd_write)
or installation from USB with serial console attached, from recover image (get there by pressing reset during boot):
cd /media/sda1 mtd_write write openwrt-18.06-snapshot-r7704-9ee8c8daf4-ramips-rt305x-ionik-cloud-hub-squashfs-sysupgrade.bin mtd5
Attention: this firmware fails to create an encrypted AP. Once you try, your box will be bricked unless you soldered a console connection!
- This is my OpenWRT 18.06.2+ snapshot for D-Link COVR-2500 devices (sold in bundles as COVR-P2502).
openwrt-18.06-snapshot-r7704-9ee8c8daf4-ar71xx-generic-covr-p2500-squashfs-factory.bin
openwrt-18.06-snapshot-r7704-9ee8c8daf4-ar71xx-generic-covr-p2500-squashfs-factory101.bin
Installation can be done from the oem firmware upgrade menu. The factory image is used for fw1.0.0 and possibly also fw1.0.1b2 (not checked); when running fw1.0.1b8, you need the (encrypted and signed) factory101 image! After flashing, let the device settle for a minute, then power-cycle. There is no network connectivity, as the oem firmware is based on an old OpenWRT and overwrites the fresh default configuration. The solution is to reboot into the failsave recovery mode (pressing the reset button shortly after boot for a moment), ssh to 192.168.1.1 and erase the overlay fs containing the original configuration of the device.umount /overlay; jffs2reset && reboot now
To use the build-in PLC adapter, you need to download covr-p2500-plc.tar.gz, extract to eg /tmp and run the two scripts in there (see README).
cd /tmp wget http://www.netadair.de/openwrt/public_scripts/covr-p2500-plc.tar.gz tar xvzf covr-p2500-plc.tar.gz cd covr-p2500-plc ./get_firmware.sh ./install.sh
then check /etc/config/plc and enable the plc, and /etc/init.d/plchost restart .
TODO: Find out how to get access to the build-in USB hub ports.
- This is my OpenWRT 18.06.2+ snapshot for TP-Link TL-WPA8630(P) V2 devices.
openwrt-18.06-snapshot-r7781-f63a1caf22-ar71xx-generic-tl-wpa8630-v2-squashfs-factory.bin
openwrt-18.06-snapshot-r7781-f63a1caf22-ar71xx-generic-tl-wpa8630-v2-squashfs-sysupgrade.bin
Installation can be done from the oem firmware upgrade menu, however the image binary needs to be renamed to an oem file name (pattern) like wpa8630pv2_eu-up-ver3-0-0-P1-20190618-rel47112.bin (maybe it just a check for file name length, though, didn't bother checking...) . It may be advisable to flash to the latest oem fw available first before going to OpenWRT, to get the latest firmware & pib file for the PLC adapter as well.
Older:
- This is my LEDE 17.01.4 image to flash straight onto a TL-WPA8630, which usually does not work with sysupgrade or factory images:
lede-17.01.4-ar71xx-generic-tl-wpa8630-squashfs-initial.bin
- This is my LEDE 17.01.4 image to flash straight onto a TL-WPA8630P V1, which usually does not work with sysupgrade or factory images:
lede-17.01.4-ar71xx-generic-tl-wpa8630pv1-squashfs-initial.bin