Installed r36104-2018.June.10 on my WRT1900ACS_v1 as flash upgrade without issues, seems to be running fine so far - will report any issues found (kept all settings from r36079 which I had running about 8.5 days without issues).
Kernel Version: Linux 4.9.107 #155 SMP PREEMPT Sat Jun 9 12:51:41 CEST 2018 armv7
DD-WRT config reference for my WRT1900ACS_v1: wired devices ~75, wireless ~20 clients using 5GHz-80Mhz-AC-Only & 2.4GHz-20Mhz-NG-Mixed with 2 additional APs in house (D-Link DAP-1650 - same SSID/Config, non-overlapping channels), IPv6 on, DHCP reservations for all known devices, local Raspberry Pi NTP, access rules (internet block security cameras), port forwards, no QOS, running OpenVPN server, firewall rules (OpenVPN & Guest), Guest 2.4GHz Wi-Fi segmented network/DHCP
_________________
Router: Linksys WRT1900ACS_v1
Firmware: DD-WRT v3.0-r36104 std 06/10/18
Cable Modem: Motorola MB7420
ISP: Comcast (250 Mbps down | 10 Mbps up)
I Installed r36104 on my Linksys WRT1900 ACS V2 with a flash upgrade and have no issues thus far. I was running r36079 for a week and a half and kept my settings from that build.
WiFi speeds measured at ~ 500 Mbs using iperf3 between a wired desktop and a wireless laptop. Network connection is >100 Mbs download and >10 Mbs upload through OOKLA Speedtest app and also with a wireless Xbox. OpenVPN client is connected and working.
DD-WRT for my WRT1900ACS V2: ~30 wireless devices, ~5 wired devices. Mixture of 5GHz and 2.4GHz. Running OpenVPN client. Running dedicated PiHole DNS server on a Raspberry Pi, Guest 2.4 GHz wifi network.
If I have any troubles, I’ll make a post. _________________ FIRMWARE: 6-20-2018 - r36168
MODEM: ARRIS SURFBoard SB6183
ROUTER: Linksys WRT1900ACS V2
ISP: TWC Spectrum 100 Mbps Download | 10 Mbps Upload
SERVICES: IVPN OpenVPN Client
Just installed on my wrt1900acs v1.
Everything works: vpn server and client with PBR, entware, transmission, samba (from both esata ssd and usb3), access restriction, SNMP with local cacti server, ntp etc..
wifi driver seems updated from the driver binary of the latest linksys firmware, see https://github.com/kaloz/mwlwifi/issues/299 and bolt text below. old mwlwifi fw is 0x0702091a. I do not have the necessary hardware to test this properly, but would be nice to know if is any better.
still got this on my 1200v2. Speedchecker for Wifi still not working.
Jun 11 21:24:00 1200 user.info : Maybe dhcpfwd had died, we need to re-exec it
Jun 11 21:26:00 1200 user.info : Maybe dhcpfwd had died, we need to re-exec it
Jun 11 21:28:01 1200 user.info : Maybe dhcpfwd had died, we need to re-exec it
Jun 11 21:30:00 1200 user.info : Maybe dhcpfwd had died, we need to re-exec it
Jun 11 21:32:00 1200 user.info : Maybe dhcpfwd had died, we need to re-exec it
Jun 11 21:34:00 1200 user.info : Maybe dhcpfwd had died, we need to re-exec it
Jun 11 21:36:00 1200 user.info : Maybe dhcpfwd had died, we need to re-exec it
Jun 11 21:38:00 1200 user.info : Maybe dhcpfwd had died, we need to re-exec it
Jun 11 21:40:00 1200 user.info : Maybe dhcpfwd had died, we need to re-exec it
Jun 11 21:42:00 1200 user.info : Maybe dhcpfwd had died, we need to re-exec it
Jun 11 21:44:00 1200 user.info : Maybe dhcpfwd had died, we need to re-exec it
Jun 11 21:46:00 1200 user.info : Maybe dhcpfwd had died, we need to re-exec it
Jun 11 21:48:00 1200 user.info : Maybe dhcpfwd had died, we need to re-exec it
Jun 11 21:50:00 1200 user.info : Maybe dhcpfwd had died, we need to re-exec it
Jun 11 21:52:00 1200 user.info : Maybe dhcpfwd had died, we need to re-exec it
Jun 11 21:54:00 1200 user.info : Maybe dhcpfwd had died, we need to re-exec it
Jun 11 21:56:00 1200 user.info : Maybe dhcpfwd had died, we need to re-exec it
Jun 11 21:58:00 1200 user.info : Maybe dhcpfwd had died, we need to re-exec it
Jun 11 22:00:00 1200 user.info : Maybe dhcpfwd had died, we need to re-exec it
Working as a Client Bridge (routed) with a WRT3200ACM with 35681.
Posted: Tue Jun 12, 2018 10:53 Post subject: Multicast filtering option does not work properly
I have a Linksys WRT1900ACS V2 router and yesterday I upgraded it to r36104. Today I realized that my router still receives multicast packets from my ISP network even if I turned on the Multicast filtering option in the security tab. The multicast packets are sending to 224.0.0.1 address into my local network.
Here is the log :
-----------------------
IN=eth0 OUT= MAC=<MAC ADDRESS OF MY ISP ROUTER> SRC=<LAN IP ADDRESS OF MY ISP ROUTER> DST=224.0.0.1 LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=4108 PROTO=2
Maybe this mistake was exist in the previous dd-wrt releases also.
Joined: 07 Apr 2018 Posts: 66 Location: Calgary, AB Canada
Posted: Wed Jun 13, 2018 13:46 Post subject:
im running this build on my WRT32x and it seems no matter what I try I cannot split my VPN (OpenVPN/ExpressVPN). Whenever I try and use policy based routing it prevents WAN access for whatever static ip's specified in the PBR window (example 192.168.0.100/32)
I have tried many other ways to split the vpn and direct through firewall scripts with iptables in administration/commands etc.. nothing works.
im running this build on my WRT32x and it seems no matter what I try I cannot split my VPN (OpenVPN/ExpressVPN). Whenever I try and use policy based routing it prevents WAN access for whatever static ip's specified in the PBR window (example 192.168.0.100/32)
I have tried many other ways to split the vpn and direct through firewall scripts with iptables in administration/commands etc.. nothing works.
Is SFE disabled or enabled? There was some discussion here among other places, iirc, where PBR would not work with SFE enabled..
EDIT: Ah, I see you already found this out in your "ExpressVPN & DD-WRT (Please Assist)" thread. Good to hear that fixed it for you.
Last edited by AmesJainchill on Wed Jun 13, 2018 18:22; edited 1 time in total
Joined: 07 Apr 2018 Posts: 66 Location: Calgary, AB Canada
Posted: Wed Jun 13, 2018 18:20 Post subject:
The issue is now solved thanks to spurious help earlier. He told me about the SPE issue and now PBR seems to work.
Only a couple other things to figure out now and my network will be 100% solid.
First is what to enter in PBR Field to cover the 192.168.0.100-192.168.0.149 ip range. Or must I enter all 50 ip addresses individually with a /32 on the end of each one. (192.168.0.100-149 reflects my DHCP range setup in DD-WRT). I perfer to have all devices save 3 which I have assigned static IPs (192.168.0.205-207) behind the vpn.
One other thing, is how to assign custom DNS servers to the aforementioned 3 static ip addresses from the router as the devices themselves do not have the ability to use custom DNS.
