102

Good!

  1. Download Cudy's custom 19.07 build .
  2. Find the firmware update section in the Cudy' firmware, flash Cudy's custom openwrt build.
  3. Go to the Flash Firmware section and flash your sysupgrade file. Be sure to uncheck "Keep settings and retain the current configuration".
  4. At the end you'll have your openwrt installed..
103

@lrussell887 thanks a lot for your work.

@gbellifemine I still have no clue why your files are not working... As I said, using the ones from @123serge123 has worked for me...

104

Probably we are using different environments.
Just a check.
Can you verify if the other dts files use "gpio0"? I would like to understand what's different.
Go in directory "openwrt/target/linux/ramips/dts" and launch the command "grep -lri gpio0 mt7621*.dts".
I have no mt7621*.dts file containing the string "gpio0".

105

Without having read through all of the previous 100 postings: What is the current status of your development for the WR1300?

I can see there are experimental (but working) images available for downloading, right?
Will anybody submit patches or a PR?

3 Likes
106

You definitely use master branch. Just compare SoC mt7621 gpio controller description in openwrt-19.07 branch and master branch. As you can see there exist gpio0-gpio2 marks in 19.07 and only gpio mark in master.

107

I see, thanks a lot.

There is some technical reason for such differences?

108

I don't understand what you mean in "technical reason".
Such differences result from changes in gpio-controller driver source code.

109

Hi there,

Thanks for the instructions!
I been following up every step and everything seems fine expect I cannot activate the 5GHz network.
Radio1 is showing as "not active" and I cannot find how to activate it. I've tried restarting the radio1 device and also the router itself but it's the same....
I'm totally new with OpenWRT about this so probably I'm missing something important here.

Does anyone know how I can activate the 5GHz wifi network?

Many thanks!

5ghz-not-active
5ghz-not-active1253×373 67.5 KB

EDITED:
This logs could be usefull:

Sun Sep 20 11:33:07 2020 kern.info kernel: [  154.452382] IPv6: ADDRCONF(NETDEV_UP): tmp.radio1: link is not ready
Sun Sep 20 11:33:12 2020 kern.info kernel: [  159.452654] IPv6: ADDRCONF(NETDEV_UP): tmp.radio1: link is not ready
Sun Sep 20 11:33:17 2020 kern.info kernel: [  164.472334] IPv6: ADDRCONF(NETDEV_UP): tmp.radio1: link is not ready
Sun Sep 20 11:33:22 2020 kern.info kernel: [  169.512290] IPv6: ADDRCONF(NETDEV_UP): tmp.radio1: link is not ready
Sun Sep 20 11:33:27 2020 kern.info kernel: [  174.482501] IPv6: ADDRCONF(NETDEV_UP): tmp.radio1: link is not ready
Sun Sep 20 11:33:32 2020 kern.info kernel: [  179.482256] IPv6: ADDRCONF(NETDEV_UP): tmp.radio1: link is not ready
Sun Sep 20 11:33:37 2020 kern.info kernel: [  184.492330] IPv6: ADDRCONF(NETDEV_UP): tmp.radio1: link is not ready
Sun Sep 20 11:33:42 2020 kern.info kernel: [  189.502270] IPv6: ADDRCONF(NETDEV_UP): tmp.radio1: link is not ready
Sun Sep 20 11:35:43 2020 daemon.err hostapd: Configuration file: /var/run/hostapd-phy1.conf
Sun Sep 20 11:35:43 2020 kern.info kernel: [  311.331893] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
Sun Sep 20 11:35:43 2020 kern.info kernel: [  311.341233] br-wan6: port 1(wlan1) entered blocking state
Sun Sep 20 11:35:43 2020 kern.info kernel: [  311.346622] br-wan6: port 1(wlan1) entered disabled state
Sun Sep 20 11:35:43 2020 kern.info kernel: [  311.352517] device wlan1 entered promiscuous mode
Sun Sep 20 11:35:43 2020 daemon.notice hostapd: Channel 136 (primary) not allowed for AP mode, flags: 0xe00717b NO-IR RADAR
Sun Sep 20 11:35:43 2020 daemon.warn hostapd: wlan1: IEEE 802.11 Configured channel (136) not found from the channel list of current mode (2) IEEE 802.11a
Sun Sep 20 11:35:43 2020 daemon.warn hostapd: wlan1: IEEE 802.11 Hardware does not support configured channel
Sun Sep 20 11:35:43 2020 daemon.err hostapd: Could not select hw_mode and channel. (-3)
Sun Sep 20 11:35:43 2020 daemon.notice hostapd: wlan1: interface state UNINITIALIZED->DISABLED
Sun Sep 20 11:35:43 2020 daemon.notice hostapd: wlan1: AP-DISABLED
Sun Sep 20 11:35:43 2020 daemon.err hostapd: wlan1: Unable to setup interface.
Sun Sep 20 11:35:43 2020 daemon.notice hostapd: wlan1: interface state DISABLED->DISABLED
Sun Sep 20 11:35:43 2020 daemon.notice hostapd: wlan1: AP-DISABLED
Sun Sep 20 11:35:43 2020 daemon.notice hostapd: wlan1: CTRL-EVENT-TERMINATING
Sun Sep 20 11:35:43 2020 daemon.err hostapd: hostapd_free_hapd_data: Interface wlan1 wasn't started
Sun Sep 20 11:35:43 2020 daemon.notice hostapd: nl80211: deinit ifname=wlan1 disabled_11b_rates=0
Sun Sep 20 11:35:44 2020 kern.info kernel: [  311.429017] device wlan1 left promiscuous mode
Sun Sep 20 11:35:44 2020 kern.info kernel: [  311.433636] br-wan6: port 1(wlan1) entered disabled state
Sun Sep 20 11:35:44 2020 daemon.notice netifd: radio1 (3571): cat: can't open '/var/run/wifi-phy1.pid': No such file or directory
Sun Sep 20 11:35:44 2020 daemon.notice netifd: radio1 (3571): WARNING (wireless_add_process): executable path /usr/sbin/wpad does not match process  path (/proc/exe)
Sun Sep 20 11:35:44 2020 daemon.notice netifd: radio1 (3571): Command failed: Invalid argument
Sun Sep 20 11:35:44 2020 daemon.notice netifd: radio1 (3571): Device setup failed: HOSTAPD_START_FAILED
Sun Sep 20 11:40:56 2020 daemon.info hostapd: wlan0: STA 50:ec:50:14:f6:8f WPA: group key handshake completed (RSN)
Sun Sep 20 11:40:56 2020 daemon.info hostapd: wlan0: STA 20:f4:78:20:48:b2 WPA: group key handshake completed (RSN)
Sun Sep 20 11:50:56 2020 daemon.info hostapd: wlan0: STA 50:ec:50:14:f6:8f WPA: group key handshake completed (RSN)
Sun Sep 20 11:50:56 2020 daemon.info hostapd: wlan0: STA 20:f4:78:20:48:b2 WPA: group key handshake completed (RSN)
Sun Sep 20 12:00:56 2020 daemon.info hostapd: wlan0: STA 50:ec:50:14:f6:8f WPA: group key handshake completed (RSN)
Sun Sep 20 12:00:56 2020 daemon.info hostapd: wlan0: STA 20:f4:78:20:48:b2 WPA: group key handshake completed (RSN)
Sun Sep 20 12:10:56 2020 daemon.info hostapd: wlan0: STA 50:ec:50:14:f6:8f WPA: group key handshake completed (RSN)
Sun Sep 20 12:10:56 2020 daemon.info hostapd: wlan0: STA 20:f4:78:20:48:b2 WPA: group key handshake completed (RSN)
Sun Sep 20 12:20:56 2020 daemon.info hostapd: wlan0: STA 50:ec:50:14:f6:8f WPA: group key handshake completed (RSN)
Sun Sep 20 12:20:56 2020 daemon.info hostapd: wlan0: STA 20:f4:78:20:48:b2 WPA: group key handshake completed (RSN)
Sun Sep 20 12:25:14 2020 kern.info kernel: [ 3282.217876] mtk_soc_eth 1e100000.ethernet eth0: port 4 link down
Sun Sep 20 12:25:17 2020 kern.info kernel: [ 3285.168274] mtk_soc_eth 1e100000.ethernet eth0: port 4 link up
Sun Sep 20 12:27:18 2020 kern.info kernel: [ 3406.368072] mtk_soc_eth 1e100000.ethernet eth0: port 4 link down
Sun Sep 20 12:27:21 2020 kern.info kernel: [ 3409.310791] mtk_soc_eth 1e100000.ethernet eth0: port 4 link up
Sun Sep 20 12:30:56 2020 daemon.info hostapd: wlan0: STA 50:ec:50:14:f6:8f WPA: group key handshake completed (RSN)
Sun Sep 20 12:30:56 2020 daemon.info hostapd: wlan0: STA 20:f4:78:20:48:b2 WPA: group key handshake completed (RSN)
Sun Sep 20 12:31:17 2020 kern.info kernel: [ 3644.736994] mtk_soc_eth 1e100000.ethernet eth0: port 4 link down
Sun Sep 20 12:31:57 2020 kern.info kernel: [ 3685.080055] mtk_soc_eth 1e100000.ethernet eth0: port 4 link up
Sun Sep 20 12:32:08 2020 kern.info kernel: [ 3695.598913] mtk_soc_eth 1e100000.ethernet eth0: port 4 link down
Sun Sep 20 12:32:11 2020 kern.info kernel: [ 3698.556635] mtk_soc_eth 1e100000.ethernet eth0: port 4 link up
Sun Sep 20 12:32:46 2020 kern.info kernel: [ 3734.146715] mtk_soc_eth 1e100000.ethernet eth0: port 4 link down
Sun Sep 20 12:32:49 2020 kern.info kernel: [ 3737.057296] mtk_soc_eth 1e100000.ethernet eth0: port 4 link up
Sun Sep 20 12:32:53 2020 kern.info kernel: [ 3740.642006] mtk_soc_eth 1e100000.ethernet eth0: port 4 link down
Sun Sep 20 12:32:56 2020 kern.info kernel: [ 3743.585288] mtk_soc_eth 1e100000.ethernet eth0: port 4 link up
Sun Sep 20 12:32:57 2020 daemon.warn dnsmasq[2395]: possible DNS-rebind attack detected: web.whatsapp.com
Sun Sep 20 12:39:55 2020 daemon.err uhttpd[1179]: luci: accepted login on / for root from 192.168.1.121
Sun Sep 20 12:40:56 2020 daemon.info hostapd: wlan0: STA 50:ec:50:14:f6:8f WPA: group key handshake completed (RSN)
Sun Sep 20 12:40:56 2020 daemon.info hostapd: wlan0: STA 20:f4:78:20:48:b2 WPA: group key handshake completed (RSN)
110

In your logs:

Change channel or country code in radio1 settings. Current channel 136 in current country don't support AP mode.

111

That did the trick :yum:
Many thanks!

112

Is there any detail instructions？i wanna have a try.

113

See the following pages:
https://openwrt.org/faq/how_do_i_send_prs_pull_requests
https://openwrt.org/faq/how_do_i_send_patches

1 Like
114

In the States, the price has dropped on this Cudy Model.

https://www.amazon.com/Cudy-1200Mbps-Customized-pre-Installed-WR1300/dp/B085RLFRH3?ref_=ast_sto_dp

Cudy has a new model in the ready, the AC2100, and the web page also promises OpenWrt support:

http://www.cudy.com/productinfo/105182.html

In the past, when Cudy introduced a new model, it was briefly discounted.

115

Thank you for the build, this is what made me buy this router!

I am running trying to enable swap on a USB stick, but it is not working:

root@OpenWrt:~# swapon /dev/sda1
block: failed to swapon /dev/sda1 (-1)

Is swap enabled in the kernel?

116

OK, after a reboot the command is not failing and swap is working, go figure ...

117

In the US price is now $29.90 and you can get 5% off(covers taxes for some of us) using code CUDYUS2005 on Amazon. Nice little router for experimenting.

1 Like
118

After a few days running OpenWrt on the router (latest build by lrussell887), I noticed that the wifi connection is not as good as with the original firmware:

  • Signal strength seems lower at similar distance
  • I get frequent disconnections even close to the router (at least for 5ghz band)
  • One of my phone cannot see the AP anymore in 2.4ghz

I tried to switch to different channels to see if that would make a difference, but the result is the same.
Also, I live in a house and there are no other wifi networks around.

Am I the only one having those issues? Any idea on how to investigate further? I really love the software...

1 Like
119

I have a few routers running the firmware and haven't noticed any issues. Did you set the appropriate Country Code under the Advanced Settings of both the 2.4 GHz and 5 GHz radios? They determine the maximum transmit power and allowed channels for the networks. Without it set, it may default to a lower dBm and it's possible 2.4 GHz picked a channel outside of the channels allowed in your country, which would create connectivity issues.

120

It's reassuring that you dont have the issues.
The country code is set and the max transmission power is set to 20dbm for 2.4ghz and 21 for 5ghz (max allowed in the UI).
I forced the 2.4ghz channel to be 9, it is authorized in my country, changing it doesnt seem to improve the situation.
For 5ghz I tried to set the channel, but the setting resets itself to auto after some time, not sure why.

121

Channel 9 on 2.4 GHz is an overlapping channel. Are there any other routers in range broadcasting between channels 6 and 11? Typically the best practice for 2.4 GHz is to set the channel to 1, 6, or 11, since they're non-overlapping, and leave the width at 20 MHz unless you're sure no other APs are around. Do a scan and see which one of those channels has the fewest APs.

As for the channel resetting itself on 5 GHz, it's possible you're selecting a DFS channel. If the router detects what it thinks may be a radar, it's forced to stop broadcasting and to choose a different channel. Different channels in the 5 GHz range also have different power limits. In the United States, for example, you'd preferably choose channel 36 or 149 if you're broadcasting an 80MHz station to avoid DFS unless otherwise necessary due to congestion.

This article might be of some help.