temp reconnect your client to the main LAN, and DL the real openwrt sysupgrade image if you haven't already.
if you did, use scp from a command prompt (or DL winscp) to transfer it to the AP's /tmp folder, from ssh run sysupgrade -n /tmp/openwrt-24.10.0-mediatek-filogic-cudy_ap3000outdoor-v1-squashfs-sysupgrade.bin.
OK it's in. Now I know: the radios are disabled by default, and it thinks it's KING OF THE WORLD and wants to be 192.168.1.1 even if we already have one of those in the house. These are both different from Cudy's stock firmware. Now I'll spend the rest of the week reading about OpenWrt configuration and trying to make this thing work (and if roaming really works, I'll buy about a hundred more Cudy APs and toss my Asus stuff). I'll still finish the DOS TFTP server I was writing so I won't have to fiddle with Windows NIC/firewall settings every @#% time I trip up, because I'll bet I'm not done tripping up. This is fantastic. Thank you!!!
to temp make life easier:
edit /etc/config/network, change the lan paragraph to:
config interface 'lan'
option device 'br-lan'
option proto 'dhcp'
save and reboot.
hook it up to your main router.
keep in mind your AP will get a new IP after this, you'll need to check your main router to find out what it is.
Beautiful. WiFi is up, the thingy's sitting at 192.168.1.168 for now (same as the Cudy firmware was using), and I unclicked "Authoritative" on the DHCP server settings which I hope means it will politely defer to the Asus for that (until I replace the Asus with something OpenWrtable). Thanks yet again!
wiki page for AP is at https://openwrt.org/docs/guide-user/network/wifi/wifiextenders/bridgedap, keep in mind it'll tell you to use a static IP.
altering the DHCP was a smart thing.
The intermediate build is exactly like an initial flash of an unmodified OpenWrt release. Upon installation to a device with only one Ethernet port, that port will be in the LAN network with an IP of 192.168.1.1 and a DHCP server. The wifi will be disabled.
This is what I get for being inexperienced. It makes sense that it would be a totally vanilla OpenWrt of some vintage, except signed by Cudy so the stock firmware will allow it. So I should expect the same behavior on all my future OpenWrt adventures (I ordered a WR3000 to replace the other Asus RT-AX3000). I'll try to be less surprised next time!
In all fairness, the OpenWrt commit message should have mentioned this information. I just got this outdoor AP as well and will be installing OpenWrt onto it when I get the time. My LAN is 10.0.0.x, we'll see how that works out. But I'm suspecting @mk24 is correct and Cudy hasn't done anything special to that image, which would make the AP just act like a router...
To be continued.
It's standard Openwrt config, then it would have to be in all commits, since it applies to all devices.
https://openwrt.org/docs/guide-quick-start/start might contain some useful stuff
We're not talking about the OpenWrt images, this is about the transitional image Cudy provides. They could set its IP to anything else in the same subnet. Zyxel does it, Ubiquiti as well.
Flashed OpenWrt proper today, the transitional image indeed just does 192.168.1.1, it does not request an IP like the Cudy firmware seems to do by default. Too bad, would have been neat.
The whole point is to allow third party firmware, but also be sure that no one moves off of signed official firmware by accident or deception. Cudy is doing a really good job here.
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.