Davidc502- wrt1200ac wrt1900acx wrt3200acm wrt32x builds

solidus1983 · September 1, 2019, 5:30pm

Whats your uhttp settings. You can find this out by using Winscp and logging into the route using the SCP protocol.

Its located in /etc/config/ under the file uhttpd

as a comprarison

config uhttpd 'main'
	list listen_http '0.0.0.0:80'
	list listen_http '[::]:80'
	list listen_https '0.0.0.0:443'
	list listen_https '[::]:443'
	option home '/www'
	option rfc1918_filter '1'
	option cgi_prefix '/cgi-bin'
	option lua_prefix '/luci'
	option lua_handler '/usr/lib/lua/luci/sgi/uhttpd.lua'
	option script_timeout '60'
	option network_timeout '30'
	option ubus_prefix '/ubus'
	option redirect_https '1'
	option cert '/etc/uhttpd.crt'
	option key '/etc/uhttpd.key'
	option realm 'WRT32X'
	option max_requests '5'
	option http_keepalive '0'
	option tcp_keepalive '1'
	option max_connections '80'

If its still stuck use ssh to restart uhttpd with ./etc/init.d/uhttpd restart

Currently working on a newer version

macosta1 · September 1, 2019, 7:01pm

Thanks @solidus1983, this was my original file which was similar to yours,

config uhttpd 'main'
        list listen_http '0.0.0.0:80'
        list listen_http '[::]:80'
        list listen_https '0.0.0.0:443'
        list listen_https '[::]:443'
        option redirect_https '1'
        option home '/www'
        option rfc1918_filter '1'
        option max_requests '1'
        option max_connections '100'
        option cert '/etc/uhttpd.crt'
        option key '/etc/uhttpd.key'
        option cgi_prefix '/cgi-bin'
        list lua_prefix '/cgi-bin/luci=/usr/lib/lua/luci/sgi/uhttpd.lua'
        option script_timeout '60'
        option network_timeout '30'
        option http_keepalive '20'
        option tcp_keepalive '1'
        option ubus_prefix '/ubus'

config cert 'defaults'
        option days '730'
        option bits '2048'
        option country 'ZZ'
        option state 'Somewhere'
        option location 'Unknown'
        option commonname 'OpenWrt'
type or paste code here

I've changed the file adding your values and modified the following line.

list lua_prefix '/cgi-bin/luci=/usr/lib/lua/luci/sgi/uhttpd.lua'

restarted uhttpd service and working great now with no visible issues and muuuuuch quicker that even used to be before the update(s).

Thanks for the help.

solidus1983 · September 1, 2019, 8:03pm

No problem thats what a community is for after all.

combathero · September 2, 2019, 9:37pm

Hi guys, I have WRT1900ACv1 with the latest r10899 build and router-on-stick setup. I tried iperf between vlans but getting frequent soft reboots after few mins of iperf testing. Issue was non-existent on stable openwrt r7808. Any ideas what the cause of reboots?

davidc502 · September 2, 2019, 10:20pm

Been an on and off issue with the v1 for at least a year and a half. My recommendation would be to stay on r7808.

Best Regards,

slim0287 · September 3, 2019, 1:19am

All, I have a question which is slightly off-topic but you all have been very helpful to me in the past so I figured I'd ask.

I recently upgraded from cable to fiber and got a big increase in speed, much lower ping and jitter. Great stuff. However, I needed to switch from an Arris Surfboard SB6183 cable modem to an Arris BGW210-700 Gateway. That wasn't a big deal, I sorted out how to do a passthrough to my Linksys WRT1900ACS which is running OpenWrt, davidc502's latest build. I'm using 1g full duplex on the Gateway through the port the Linksys router is connected to. Everything appears to run great, and a lot faster. Of course, I also shut off the wireless on the Gateway.

However, when I travel I run a Wireguard server on my router that I connect to, and I open a port on the router to do so. My question is this: Now that I have this Arris BGW210 Gateway, will simply opening the port on my router work? Or do I need to also open a port on the Gateway?

Thanks

davidc502 · September 3, 2019, 1:53am

@slim0287

Correct, with ip passthrough, the outside interface of the router should have the public IP, so it "should" be matter of just opening what port you want.

scott68 · September 3, 2019, 1:58am

Here is a decent tutorial which may help:
https://www.reddit.com/r/Ubiquiti/comments/b1x5l6/how_to_properly_configure_the_arris_bgw210_for/

slim0287 · September 3, 2019, 3:47am

@scott68 @davidc502 Thanks, fellows. It appears I did this properly, and I appreciate the confirmation.

komodo_1 · September 3, 2019, 9:40pm

Considering fwknop to open the port?

trohn_javolta · September 4, 2019, 12:46pm

Sry to get back to this. The issue clearly isn't at torguard's end since on my pc I get full download speed at all time so it's sth. different on the router.
I don't know why openvpn or openssl now only uses 50% of cpu, maybe anyone here has an idea?

I'm sure I can get my usual 80 mbps download speed, the question is how can I get openvpn client to use all cpu power again...

I didn't test a new config on a fresh, untouched build yet. I will flash newest build to the 2nd partition.
Is there a certain tutorial on how to exactly configure openvpn client that you recommend?
I wan to make sure I do everything according to "playbook" to rule out a deprecated way of configuring everything.

treefiddy · September 4, 2019, 1:20pm

After issues with DFS / 5ghz i switched to a Ubiquiti nanoHD. I still love my 1900ACS and the WRT32X as main routers and i will stick with them. Openwrt and your builds are still the best

Nauttor · September 4, 2019, 1:51pm

Sadly, that was exactly my path, I bought too nanoHD and give up on the 1900ACs wifi. It's sad that the manufacturer "abandoned" it. Now the 1900acs is just my router, and it works flawlessly for that.

Any news about the bug that make the web to load slowly?
@macosta1 I applied your values to the uhhtpd.conf and it appears to be snappier now, we'll see. Thanks

treefiddy · September 5, 2019, 2:21pm

someone said that the web load issues are chrome related. Firefox is much faster and it looks like it does not have the issue at all.

BigRon · September 5, 2019, 11:34pm

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.

smokers · September 7, 2019, 7:04am

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

warchief · September 7, 2019, 9:14pm

##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?

davidc502 · September 8, 2019, 12:52am

@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

warchief · September 8, 2019, 12:57am

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.

davidc502 · September 8, 2019, 1:57am

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