no, it doesn't.
The device will come with a default OEM Stock Firmware complete with LuCI GUI installed.
... isn't referring to the openwrt image you DLed from "here".
you forgot to add a couple of extra !:s.
Stock I tried to point to 192.168.1.1 and it dodn't work - thus queries about a fw build including luci..
!!!!!!
apples and bananas ?
what stock may or may not include, we can't control.
does it matter ? most people will reflash it, the 1st thing they do, when they get it.
one could however add a warning about LuCI not always getting shipped with the OEM image.
you're barking up the wrong tree.
I also ordered two OpenWRT One chickens and recently received them.
It took me a while to figure out why the configuration is not being written and it always restores after a reboot :). But switching the lever on the back of the router helped it.
But I'm not that experienced to do everything through the console so I searched for Luci. The seller and all sources claim that the device will come with Luci pre-installed, but it is not.
When I installed Luci manually, I encountered incompatibility with the current firmware. I still installed and Luci some of the Luci chips don't work properly.
Is there a guide (step by step) somewhere on how to install Luci correctly into OpenWRT One? Thanks
Both units I have OOB had LuCI installed on first power up. TBH I only found out inadvertently when I selected the Firmware OEM Stock URL link from the wiki that pointed me at the firmware-selector page and noticed LuCI is installed by default on all firmware-selector builds. All I had to do was point my browser to 192.168.1.1.
LuCI won’t present on OOB power up until you point your browser at it.
In normal production environment the NAND/NOR selector should always be set to NAND.
As noted above if you point to the firmware-selector url you get a current snapshot image with LuCI installed. I am not sure of the current status of the firmware-selector and the latest package manager that uses APK instead of OPKG.
Check out the How-To.pdf Here
I was not lucky enough to find Luci with my OpenWRT One. But maybe I just searched wrong.
OpenWRT One is supposed to have only a Snapshot and it supposedly does not include the Luci environment https://firmware-selector.openwrt.org/?version=SNAPSHOT&target=mediatek%2Ffilogic&id=openwrt_one
If you go to your link above and select Customize installed packages and/or first boot script to expand the base packages you will find that LuCI is indeed built in to the firmware-selector by default. It is only when you download an image from downloads.openwrt.org that LuCI isn’t included.
2 Likes
Was going nowhere trying to get things up and running, but then I figured out how to connect to the serial console...FANTASTIC, no more guessing what in the world is going on. The main problem I am running into is whether I use a requested build or something from downloads.openwrt.org, there is no luci and there isn’t even opkg.
I have never been able to update via “upgrade the firmware”, now that I have console access, I see:
## Checking hash(es) for FIT Image at 46000000 ...
Hash(es) for Image 0 (kernel-1): crc32+ sha1+
Hash(es) for Image 1 (fdt-1): crc32+ sha1+
Hash(es) for Image 2 (rootfs-1): crc32+ sha1+
Remove UBI volume fit (id 4)
Remove UBI volume rootfs_data (id 5)
Creating dynamic volume fit of size 11141387
11141387 bytes written to volume fit
## Error: "led_loop_done" not defined
If I try to load via “full recovery”, it works, and I see version for a requested build with luci:
OpenWrt SNAPSHOT, r28124-efc0c4666b
If I try to load via “full recovery”, it works, and I see version for a downloads.openwrt.org snapshot build with luci:
starting USB...
Bus xhci@11200000: xhci-mtk xhci@11200000: hcd: 0x0000000011200000, ippc: 0x0000000011203e00
xhci-mtk xhci@11200000: ports disabled mask: u3p-0x1, u2p-0x0
xhci-mtk xhci@11200000: u2p:1, u3p:1
Register 200010f NbrPorts 2
Starting the controller
USB XHCI 1.10
scanning bus xhci@11200000 for devices... 2 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
234341 bytes read in 14 ms (16 MiB/s)
SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
Erasing 0x00000000 ... 0x000fffff (8 eraseblock(s))
Writing 262144 byte(s) (128 page(s)) at offset 0x00000000
Writing 262144 byte(s) (128 page(s)) at offset 0x00040000
Writing 262144 byte(s) (128 page(s)) at offset 0x00080000
22282240 bytes read in 947 ms (22.4 MiB/s)
Erasing 0x00000000 ... 0x07efffff (1016 eraseblock(s))
Writing 22282240 byte(s) (10880 page(s)) at offset 0x00000000
done
OpenWrt SNAPSHOT, r28124-efc0c4666b
Unfortunately same snapshot, but again opkg is not found.
I then ran sysupgrade -n with the itb file (in NAND mode) and I lost the serial output, but it did say sysupgrade successful at the end. I then tried a different sysupgrade version and it worked, but went into a boot loop, so I installed another one and it worked (I can see the different version in the MOTD), and did not loop, so I can update via NOR and sysupgrade.
However, no matter what image I install, opkg never seems to be present!
Any advice for troubleshooting would be greatly appreciated!
I do not see owut or apt or apk either, maybe there is some breakage with the package manager changes?
If that is the case, it would be nice to have a "known good" OpenWrt One image somewhere, rather than just the daily snapshot.
I ran a custom build with apk and owut appended to the installed packages and now I can see those as well as log in to luci. Perhaps all of my previous images were fine (except maybe some didn't really have luci) and just not having opkg was throwing me for a loop.
opkg no longer exists in OpenWrt. See major change notice
you can always switch to the 24.10 snapshots, they still use opkg - https://downloads.openwrt.org/releases/24.10-SNAPSHOT/targets/mediatek/filogic/, they're however inaccessible through firmware-selector, so you can't customize them.
1 Like
Tried latest 24.10-SNAPSHOT firmwares (r28029-3ecfc24c51)
Did a NAND flash via sysupgrade.itb
Still got: ## Error: "led_loop_done" not defined
Did a NOR flash
Got: Error, no UBI device selected!
Tried latest snapshot firmwares (r28146-52b6c92479)
Did a NOR flash
Got: Error, no UBI device selected!
Tried older 24.10-SNAPSHOT firmwares (r28027-2d465fbf57), since I still had this downloaded from the other day
Did a NOR flash
Working, opkg is present and luci is included!
Someone with an OpenWrt One, could you please let me know of the reported noise level you see (e.g. on the luci network/wireless page)?
In BananaPi-R4 device we see quite noisy levels (around -80 dBm), perhaps because the pluggable wifi-module on the bpi-r4 does not have any shielding around the wifi-chips. It looks like the OpenWrt One also does not have any shielding - but you still might have better values because of the large heatsink on the chips, so I'm curious what the noise levels are.
Was anyone successful in powering the router via PoE yet? My switch (Cisco CBS250-16P-2G) supports 802.3 AT but the status, the LAN port is connected to, only shows "searching". PoE is successfully delivered to other ports (two raspberry pi) and there is a good 100 something W power left.
Trick question, is a PoE module physically present (soldered in)?
(the vertical daughter PCB, on the bottom of the image, between the ethernet transformers/ just above/ between the two rj45 ports)
Yes, that's there. Checked it initially already but just to be sure I checked it again.
I checked the schematic and description but couldn't find anything that would enable/disable PoE
Looking at the picture: The little battery is only for the RTC and has no influence on PoE, right?
Nothing to do. Unplug the regular power and add your Poe connector and give it a few seconds to config/boot.
To test it, I just added a patch cable from a multi port poe switch I have for my AP and a couple of poe cameras to verify it powers the OpenWrt One.
Correct.