Davidc502- wrt1200ac wrt1900acx wrt3200acm wrt32x builds


#1519

Soory for the delay, thank cybrnook for confirming this. No issue here, everything work ok with tcpdump-mini


#1520

Hmm... Looks like it's not a DNS issue. Server reply to 503 error instead of next chunk.

Anyway, you can play with "Advanced settings" in "Network - DHCP and DNS" - it have 2 parameters - "Max. concurrent queries" and "Size of DNS query cache". First is about flood, second about caching more. But if increased values didn't change the picture - use other IPTV provider (or even use TorrentTV).


#1521

Thanks david for your fast help. My WRT1200Ac is unbelievable stable now. Take a look at my current uptime (maybe i really need to update to fix some security issues :slight_smile: )

//Edit:
Just did the upgrade and it worked perfectly. First i uploaded the dnscryptv2 script to /root, set the folder to the backup and after the upgrade i executed the script (make sure the script is executable)


#1522

You can now easily upgrade the libelf package manually.
SSH to router, then type:

wget -O /tmp/libelf1_0.175-3_arm_cortex-a9_vfpv3.ipk https://downloads.openwrt.org/snapshots/packages/arm_cortex-a9_vfpv3/base/libelf1 _0.175-3_arm_cortex-a9_vfpv3.ipk

opkg install /tmp/libelf1_0.175-3_arm_cortex-a9_vfpv3.ipk

After that, SQM is working again.

BTW: cake is also not showing in luci for me though installed but seems to be working when using 'layer_cake.qos':

root@OpenWrt:/tmp/run/sqm# opkg list-installed | grep sched
kmod-sched - 4.14.95-1
kmod-sched-cake - 4.14.95+2019-01-08-331ac70c-1
kmod-sched-connmark - 4.14.95-1
kmod-sched-core - 4.14.95-1
root@OpenWrt:/tmp/run/sqm# tc -d qdisc
qdisc noqueue 0: dev lo root refcnt 2
qdisc mq 0: dev eth1 root
qdisc fq_codel 0: dev eth1 parent :8 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc fq_codel 0: dev eth1 parent :7 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc fq_codel 0: dev eth1 parent :6 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc fq_codel 0: dev eth1 parent :5 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc fq_codel 0: dev eth1 parent :4 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc fq_codel 0: dev eth1 parent :3 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc fq_codel 0: dev eth1 parent :2 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc fq_codel 0: dev eth1 parent :1 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc mq 0: dev eth0 root
qdisc fq_codel 0: dev eth0 parent :8 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc fq_codel 0: dev eth0 parent :7 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc fq_codel 0: dev eth0 parent :6 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc fq_codel 0: dev eth0 parent :5 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc fq_codel 0: dev eth0 parent :4 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc fq_codel 0: dev eth0 parent :3 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc fq_codel 0: dev eth0 parent :2 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc fq_codel 0: dev eth0 parent :1 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc fq_codel 0: dev ifb0 root refcnt 2 limit 10240p flows 1024 quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc noqueue 0: dev br-lan root refcnt 2
qdisc fq_codel 0: dev tun0 root refcnt 2 limit 10240p flows 1024 quantum 1500 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
qdisc cake 8025: dev pppoe-wan root refcnt 2 bandwidth 30Mbit diffserv3 triple-isolate nonat nowash no-ack-filter split-gso rtt 100.0ms raw overhead 0
qdisc ingress ffff: dev pppoe-wan parent ffff:fff1 ----------------
qdisc cake 8026: dev ifb4pppoe-wan root refcnt 2 bandwidth 97Mbit besteffort triple-isolate nonat wash no-ack-filter split-gso rtt 100.0ms raw overhead 0

#1523

Hello David,
I just got a WRT32X and put your latest release (r9133) and i have major issues with getting some Sonoff swicthes to connect to wifi. Although so far with my WRT1900ACS i had no issue at all with the same settings. I tried also to go to a previous version (r9028) and i have the same problem.
With the stock Linksys Firmware these devices connect as they should.

The problems i think lies in the fact that the dhcp is not offering ip for them, while i see them as connected devices.
Here's something from the system log:

This is from a device connected and getting IP as it should:

Sat Feb 2 15:08:56 2019 daemon.notice hostapd: wlan1-1: AP-STA-CONNECTED 78:0f:77:47:ff:d1
Sat Feb 2 15:08:56 2019 daemon.info hostapd: wlan1-1: STA 78:0f:77:47:ff:d1 WPA: pairwise key handshake completed (RSN)
Sat Feb 2 15:08:58 2019 daemon.info dnsmasq-dhcp[6139]: DHCPDISCOVER(br-lan) 78:0f:77:47:ff:d1
Sat Feb 2 15:08:58 2019 daemon.info dnsmasq-dhcp[6139]: DHCPOFFER(br-lan) 192.168.1.189 78:0f:77:47:ff:d1
Sat Feb 2 15:08:58 2019 daemon.info dnsmasq-dhcp[6139]: DHCPREQUEST(br-lan) 192.168.1.189 78:0f:77:47:ff:d1
Sat Feb 2 15:08:58 2019 daemon.info dnsmasq-dhcp[6139]: DHCPACK(br-lan) 192.168.1.189 78:0f:77:47:ff:d1 RMMINI-47-ff-d1

And this is where the problem is with some Sonoff devices:

Sat Feb 2 15:09:03 2019 daemon.info hostapd: wlan1-1: STA 5c:cf:7f:f9:a6:cf IEEE 802.11: associated (aid 4)
Sat Feb 2 15:09:03 2019 daemon.notice hostapd: wlan1-1: AP-STA-CONNECTED 5c:cf:7f:f9:a6:cf
Sat Feb 2 15:09:03 2019 daemon.info hostapd: wlan1-1: STA 5c:cf:7f:f9:a6:cf WPA: pairwise key handshake completed (RSN)
Sat Feb 2 15:09:03 2019 daemon.info hostapd: wlan1-1: STA 5c:cf:7f:95:8d:c2 IEEE 802.11: associated (aid 5)
Sat Feb 2 15:09:03 2019 daemon.notice hostapd: wlan1-1: AP-STA-CONNECTED 5c:cf:7f:95:8d:c2
Sat Feb 2 15:09:03 2019 daemon.info hostapd: wlan1-1: STA 5c:cf:7f:95:8d:c2 WPA: pairwise key handshake completed (RSN)
Sat Feb 2 15:09:04 2019 daemon.info hostapd: wlan1-1: STA 5c:cf:7f:3b:72:9f IEEE 802.11: associated (aid 6)
Sat Feb 2 15:09:04 2019 daemon.notice hostapd: wlan1-1: AP-STA-CONNECTED 5c:cf:7f:3b:72:9f
Sat Feb 2 15:09:04 2019 daemon.info hostapd: wlan1-1: STA 5c:cf:7f:3b:72:9f WPA: pairwise key handshake completed (RSN)
Sat Feb 2 15:09:04 2019 daemon.info hostapd: wlan1-1: STA 80:7d:3a:32:c4:47 IEEE 802.11: associated (aid 7)
Sat Feb 2 15:09:04 2019 daemon.notice hostapd: wlan1-1: AP-STA-CONNECTED 80:7d:3a:32:c4:47

I also tried to delete all my config and start fresh, same results.
Any clues what might be the issue?


#1524

Hi @Pasxalisk, I had a very similar issue with "dumb" IoT devices on my LAN when I first started using OpenWrt on a WRT32X. I got it working by enabling "Allow legacy 802.11b rates" for the interface/SSID they were connecting to. YMMV, but this may help...

legacy_rates


#1525

@WiteWulf Thank you for your response.
Just tried it. No luck.
This is what i keep getting:

Screenshot_1

And this is how it should be (WRT1900ACS)
Screenshot_2


#1526

Hello,
It's been a while since I last used David's builds and I know we install the lede-mvebu-cortexa9-linksys-wrt3200acm-squashfs-factory.img first and then copy the de-mvebu-cortexa9-linksys-wrt3200acm-squashfs-sysupgrade.bin to the tmp folder with putty and then I have forgotten everything from that point.

I have been seeking some step by step instructions on install and basic config. Are there any such instructions available somewhere; without having to read the "war and peace" documentation on the WRT website?


#1527

@Morrile37
You don't need to do that.
You flash .img from the stock firmware directly and you are set.
The -sysupgrade.bin firmwares are for flashing a new firmware via Luci web interface.


#1528

Dunno then, sorry ¯_(ツ)_/¯


#1529

https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=318427

Edit: https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=318516


#1530

Hello Pasxalisk,

Many thanks for the reminder.

Morrile37


#1531

Thanks @xquewx

After installing the new libelf package, libintl-full8 was auto-removed!
I had to do:

opkg update
opkg install libintl-full8

Afterwards SQM was working fine again.


#1532

Turn OFF ALL LEDs on a WRT Router using Davidc502's Image.

I am using Davidc502's latest build r9133 for both WRT1900AC & WRT3200ACM routers.

I have searched for a way to turn-off ALL indication LEDs on both these routers but only with limited success.

The issue is that the LEDs for these 2 WRT routers dim over time with use. i.e. the most used (activated) LEDs Power, Internet and 2.4GHz LEDs are almost not readable while the less activated 5GHz, eSATa and USBs are as bright as when the WRT was new. This seems to be a well known issue with the WRT line of routers.

I will focus on the WRT3200ACM as that is the one I want to turn-off the LEDs the most in order to save the LEDs for future use if needed. The LED indications are not needed now since the router is in a location that is not normally accessed.

BTW the LINKSYS Stock Firmware has a GUI switch setting for turning OFF ALL LEDs. i.e. ON/OFF Switch on the GUI screen

I have used the LUCI SYSTEM-LED CONFIGURATION page to try and set all LEDs off but with about 50% success. I manage to get the following LEDs set to OFF and they stay OFF: Power, Internet, eSATA, USB1, USB2 & WPS.

The 2.4GHz and 5GHz do get set to OFF but the setting does not survive a Reboot. They revert to their normal function on a Reboot.

The 4 LAN LEDs: I could not figure out how to turn them OFF at all. There are no options in the GUI LUCI SYSTEM-LED CONFIGURATION page to set them.

The WRT3200ACM /etc/config/system config file that controls the LEDs and that I have had 50% success is below:

config led
	option name 'Power'
	option default '0'
	option sysfs 'rango:white:power'
	option trigger 'none'

config led 'led_wan'
	option name 'WAN'
	option sysfs 'pca963x:rango:amber:wan'
	option default '0'
	option trigger 'none'

config led
	option name '2.4 GHz'
	option sysfs 'rango:white:wlan_2g'
	option trigger 'none'
	option default '0'

config led
	option name '5 GHz'
	option sysfs 'rango:white:wlan_5g'
	option trigger 'none'
	option default '0'

config led
	option default '0'
	option name 'eSATA'
	option sysfs 'rango:white:sata'
	option trigger 'none'

config led 'led_usb2_ss'
	option name 'USB 2 SS'
	option sysfs 'pca963x:rango:white:usb3_2'
	option default '0'
	option trigger 'none'

config led 'led_usb1'
	option name 'USB 1'
	option sysfs 'pca963x:rango:white:usb2'
	option default '0'
	option trigger 'none'

config led 'led_usb2'
	option name 'USB 2'
	option sysfs 'pca963x:rango:white:usb3_1'
	option default '0'
	option trigger 'none'

config led
	option default '0'
	option name 'WPS'
	option sysfs 'pca963x:rango:white:wps'
	option trigger 'none'

The main questions I have are:

Has anyone here managed to set ALL LEDs to OFF via software configuration or Command Line commands in DavidC502's image on the WRT3200ACM?

If so, how?

If so, how to set it up to survive a Reboot?


#1533

I tried and couldn't figure it out. Some of the LEDs are controlled directly by drivers that aren't exposed to LUCI, I believe. Simple solution: black insulation tape across the front panel.


#1534

Thanks for the reply but the light is not the issue, I just want to save the LEDs for future use. Tape does not solve that issue.


#1535

In the past I have had same issues. After a lot of time of test and error I figured out that sonoff devices wifi chips (flashed with tasmota firmware) needs a clean wifi environment. So be shure to select fixed channels configuration to work in (those less used in your area) and the most important, if you have more than one wifi ap/router sharing the same ssid be shure to use different channels for each of them.


#1536

I saw that 18.06.2 just dropped recently. Are there any major changes from that build that would be making it's way into the next Davidc502 release, or have those all been incorporated into the snapshots?

Maybe a better question is- what sort of major changes/features/fixes/etc have the Davidc502 builds had over time, and what is the best way to track them and compare feature/fix parity with official builds?

Thanks!


#1537

Hi. I've got the WRT1900ACSV2 and flashed the router with the latest Davidc502 openWRT firmware from stock (01-25-19). When setting up wireless, I could set 5Ghz TX Power to 30dbm however I could only set the 2.4Ghz TX power to 20dbm (using 00 - World option). DDwrt firmware allowed me to set it to 30dbm on the 2.4Ghz range. Is it possible to set 2.4Ghz to 30dbm on openWRT?

Second question: Under the SQM, I could not find the option 'cake' under Queueing Discipline though 'Piece of Cake' option can be found in Queue Setup script. How can I get the cake option?

Thanks for your help! My first time using OpenWRT coming from DDwrt.


#1538

The power controls are meaningless for both 2,4 and 5ghz as power is completely controled by the router. I consider them dummy controls as they do nothing.

Im afraid I have not worked with cake. Hopefully someone with experience will respond.