Davidc502- wrt1200ac wrt1900acx wrt3200acm wrt32x builds

Had an issue with Adblock not working for me after the last update on my WRT3200ACM. Was able to resolve and wanted to share in case anyone else experienced the same. Ads were coming through so it appeared disabled. Suspend and refresh buttons in Luci were grayed out and not working along with missing field entries as per below:

Note that trying to restart processes or trying to reinstall the packages from Luci did not work. Turns out the configuration files needed updating. To fix it, opkg remove luci-app-adblock and then opkg remove adblock after logging in via SSH in the terminal. Then install using the --force-maintainer option as per:

Keep in mind you should reboot, enable Adblock, and then enable your blocklist sources (including some new ones) afterward. Hope this helps others who experienced the same.

3 Likes

I keep having issues with wifi, maybe someone has some advice. I am using 31 aug release on wrt32x.

[209131.610689] ieee80211 phy0: staid 1 deleted
[209193.278164] ieee80211 phy0: staid 3 deleted
[209197.930106] ieee80211 phy0: staid 3 deleted
[209529.638475] ieee80211 phy0: staid 1 deleted
[209761.597476] ieee80211 phy0: staid 3 deleted
[209767.635696] ieee80211 phy0: staid 3 deleted
[209936.369259] ieee80211 phy0: staid 1 deleted
[210366.050342] ieee80211 phy0: staid 1 deleted
[210405.515871] ieee80211 phy0: staid 3 deleted
[210410.602744] ieee80211 phy0: staid 3 deleted
[211427.833154] ieee80211 phy0: staid 3 deleted
[211433.869417] ieee80211 phy0: staid 3 deleted
[212321.569360] ieee80211 phy0: staid 1 deleted
[212970.241880] ieee80211 phy0: staid 1 deleted
[213011.266109] device wlan1 left promiscuous mode
[213011.270748] br-lan: port 2(wlan1) entered disabled state
[213011.305470] ieee80211 phy1: change: 0x40
[213011.385106] ieee80211 phy1: change: 0x100
[213011.436221] device wlan0 left promiscuous mode
[213011.440843] br-lan: port 3(wlan0) entered disabled state
[213011.575353] ieee80211 phy0: staid 1 deleted
[213011.595471] ieee80211 phy0: staid 3 deleted
[213011.615458] ieee80211 phy0: staid 2 deleted
[213011.635325] ieee80211 phy0: change: 0x40
[213011.739250] ieee80211 phy0: change: 0x100
[213013.363806] ieee80211 phy1: change: 0xffffffff
[213013.456119] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
[213013.464080] br-lan: port 2(wlan1) entered blocking state
[213013.469611] br-lan: port 2(wlan1) entered disabled state
[213013.475294] device wlan1 entered promiscuous mode
[213013.480204] br-lan: port 2(wlan1) entered blocking state
[213013.485645] br-lan: port 2(wlan1) entered forwarding state
[213013.492231] br-lan: port 2(wlan1) entered disabled state
[213013.655919] ieee80211 phy0: change: 0xffffffff
[213013.769252] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[213013.776373] br-lan: port 3(wlan0) entered blocking state
[213013.781865] br-lan: port 3(wlan0) entered disabled state
[213013.787468] device wlan0 entered promiscuous mode
[213013.792484] br-lan: port 3(wlan0) entered blocking state
[213013.797931] br-lan: port 3(wlan0) entered forwarding state
[213014.527436] br-lan: port 3(wlan0) entered disabled state
##INPUTDSCP
iptables -t mangle -A PREROUTING -p udp --in-interface wan --destination 192.168.1.2 -m multiport ! --source-ports 53,5353 -j DSCP --set-dscp 40
iptables -t mangle -A PREROUTING -p tcp --in-interface wan --destination 192.168.1.2 -m multiport ! --source-ports 53,5353 -j DSCP --set-dscp 0

Will this code work with david or would you provide me with the proper iptables rule for inbound dscp marking?

@warchief

Hello,

I've not actually worked with dscp marking. Did you try the rule? Just looking at it I was not sure if the interface was wan or eth0

I am using standard openwrt on a linksys 3200acm. From what I understand openwrt does not allow inbound dscp marking. I am now looking into 3rd party devolopments to fix this and customize the rules more. I was inputting this rule into openwrt>network>firewall>custom rules but it does not read in wireshark this is meant to be on the wan.

Did you see this thread? This may not apply to your case though.

I found the most firmware options with the Netgear R7800 (Nighthawk X4S R7800-100NAS): Voxel, Kong, Hnyman and DD-WRT. It's running on Qualcomm Atheros hardware (unlike the X6 R8000 disaster that is Broadcom, which davidc502 mentioned). If you can find one used for 100 USD or less, go for it. For the record I have WRT3200ACM and R7800.

Are you running Kong Openwrt on the R7800?

Hi to all!

I need your help :slight_smile:
Can someone point me to the right direction on how to do an update?

What are the steps someone needs to perform in order to update this build?
Every time I try to update this build I click update and keep settings but after the process completes
I always find my self in a situation that my settings were restored but also some of the default packages are still there... ex: dnscrypt proxy 2 is missing and is reverted back to 1. SQM the same...
if I remember correctly also most of my packages are not there and I have to reinstall them...

Is there anyway I can click update and forget? without having to redo almost everything?

Thanks a lot for your time!

@kuriSu-kUN

Keep settings is just that.. settings or configurations not packages, so some could be lost when upgrading.

If you are going through the manual process for dnscrypt-proxy 2 then yes, it will always revert to version 1 after an upgrade. The reason being the default package is version 1. At some point, my plan is to include version 2 as default, but I need to do some testing first before making that change.

The best thing to do is to document the packages you know are not a part of the standard build, and write them down. Then write a small script to restore them after an upgrade (Lots of shell wizards here to help). From there, make that directory a part of the "Keep Settings" routine.. Meaning you can select the /root directory, for example, as part of your save settings, and your script will be in the /root directory after every upgrade. So, after an upgrade just ssh to the directory, run the script, and all the packages will be restored.

1 Like

dnscrypt-proxy Version 1 Poll

Who here is still using Version 1?

Anybody?

dnscrypt-proxy 2 ftw

2 Likes

I am. The last time I used v2 and updated the firmware, my router was caught in some sort of loop when dns services started and I couldn't access the router, or anything else. I had to do a hard reset at that point.

I'm leaving v1 on, because that is what comes with the firmware, and I can upgrade the firmware without having to worry about such problems.

1 Like

When you get a chance, try the v2 version again and see if it is still happening. Really, I don't want to see anyone left behind.

@Jruuu
Was the power led flashing?

dnscrypt-proxy 2 ftw. It's running great.

/me too...

dnscrypt v2 here

Also dnscrypt-proxy v2.

dnscrypt-proxy v2