Any chance for WR3000P support? Looks like a nice upgrade to WR3000H - 512MB RAM, USB port, PoE ...
Sounds reasonable. Most of the work should already be done as it's extremly close to the WR3000H. But ... It's up to someone owning the device to do the work. And the PoE part is new.
1 Like
https://github.com/openwrt/openwrt/pull/19636 - tested with 24.10.2, all the basic functionality works (except WAN LED), PoE is untested as I don't have any PoE enabled switch or injector
3 Likes
Do you plan to address GitHub review comments by aiamadeus? I'd love to have this device supported officially instead of having to build the image myselfâŚ
Also this thread discusses adding support for TR3000 and what caught my eye there was the fact there were issues with WAN port initially, but were fixed along the way (too cumbersome to try to locate the fix for me right now). Come to think of it now, WAN vs. WAN LED may not be all that similar - sorry, I'm browsing on the phone only, so it's not the easiest to get the bigger picture/connect the dots right awayâŚ
1 Like
Iâm planning to buy one to use as access point. How did you install the firmware? Using the TFTP method?
I did not yet. Have requested intermediate firmware w/o signature check from Cudy, received it via email and my next planned step is to apply it to the device on top of Cudy's factory-shipped firmware. The final step after that should be to apply OpenWrt sysupgrade image on top of intermediate firmware and from that point on, the device should run pure OpenWrt firmware (which does not exist unless you build one yourself, hence my question to @haed).
1 Like
@miles - apologies, I was busy recently, and frankly hate these AI generated comments. Should be able to address these this weekend so the PR can be merged.
No issues with WAN port apart from the fact that the led is not blinking - running rock stable connected via 2.5G for the last couple of weeks.
No need to apologize, I am not making any demands, just curious if you gave up on that PR - glad to hear that's not the case. And yes, the comments did not look like there were any functional issues, so I get the sentiment. Fingers crossed with the PR :â -â ) And thank you!
Hi all,
i just ordered the p version as well. Was anyone able to test the POE funcitionality?
Hi all, is there any update on POE testing?
Let's assume that if the answer would be yes, someone would have leave a message here.
Only news about this device is its incoming support in 24.10.
Can anyone confirm USB port functionality? I finally got to install openwrt build on this device (tried both 24.10-snapshot and snapshot) and USB does not work for me. I am plugging in Huawei E3372 stick for LTE internet and see that the stick works for a couple of seconds - its LED starts to flash, but suddenly stops shortly thereafter. I found message âusb_vbus: disablingâ in both 24.10-snapshot and snapshot which I guess indicates USB port being shut down at that point for some reason. It doesn't show any signs of life afterwards - unplugging/re-plugging does nothing and nothing shows up in log either - only reboot âhelpsâ, but with the same outcome.
The stick is guaranteed to work - this is an attempt to move it from older mt7621 device running 23.05 series to a filogic one - so I am assuming either a faulty Cudy unit or something's off in dts (my wild guess). As a next step, I will probably try to reflash stock firmware to see if I can rule out HW issue, but would rather hope it's not my unit.
see issue 21231
2 Likes
Awesome, thank you very much! After adding kmod-usb-xhci-mtk, everything works as expected. I checked the GitHub issue one more time to see if it moved anywhere PR-wise and now see this will be handled automatically going forward (although by using kmod-usb3 instead of kmod-usb-xhci-mtk).
You need to add kmod-usb3, and the issue will be fixed in next releases
Also read this. This talks about kmod-usb3, not kmod-usb-xhci-mtk. Should the later by installed be default too?
kmod-usb3 has a dependency on kmod-usb-xhci-mtk, so the one that's actually needed (that's the kmod-usb-xhci-mtk) will be included even if only kmod-usb3 is selected. What puzzles me a bit is a need for kmod-usb3 when the device only has USB 2.0 port according to the manufacturer specs. Not that additional ~10kB needed for kmod-usb3 would matter, but it is a bit confusing and sounds like an overkill to me.
I have verified that kmod-usb-xhci-mtk is enough to be added - my current image does not contain kmod-usb3, yet the LTE stick (finally) runs without any issues (which was not the case without kmod-usb-xhci-mtk).
Edit: decided to overcome my own laziness and spell out kmod names instead of short references used originally (I'm posting from the mobile).
1 Like
Every filogic device has USB3 controller with one USB2 and one USB2/USB3 port. Independently of attached regulators and outside ports.
2 Likes
Sounds logical.
I remember asking the same question. USB3 has USB2 pins. The vendor choose to sold only an USB2 port with these pins, surely for the lower cost.
3 Likes
apparently there is a bloody battle out-there for the penny
the only alternative I was able to find with a USB3 port is the Cudy TR3000 in a similar price range but it has DDR3 and only 2 small antennas compered to Cudy WR3000P v1 with DDR4 with 4 larger antennas
I wonder how easy would be to solder a USB3 port on the Cudy WR3000P v1
Edit: I ended-up getting the Cudy WR3000P v1 & my next purchase will probably be a Cudy TR3000
looking for a USB 3.x OpenWrt wifi router is not an easy task. the only alternative to the Cudy TR3000 that I was able to find was this WD-R3003N-G2 product
Edit II: I am suspecting stability issues for the USB 3.x as there are plenty of such issues on the x86 world. an unstable or problematic USB 3.x is simply useless. I am looking forward on hearing USB 3.x experiences with OpenWrt on the Cudy TR3000
1 Like