Joined: 13 Jun 2006 Posts: 1608 Location: SE Michigan USA
Posted: Sun Aug 20, 2017 20:28 Post subject:
elvisimprsntr wrote:
myersw wrote:
I am running davidc502 LEDE. His has latest wireless drivers and kernel. Runs well for me and is more up to date. He provides a 4.4 kernel for the wrt1900ac v1 again with latest drivers.
I am guessing you are aware of his builds, but if not here is link.
https://davidc502sis.dynamic-dns.net/
This site also has a link to his Openwrt support thread.
The problem with the LEDE builds from https://davidc502sis.dynamic-dns.net/
is the root certificate is not trusted and macOS High Sierra Safari will not allow you to accept the untrusted cert.
You can get around this issue easily. Just SSH or Telnet in to router. Go to /etc/config. Edit the file uhttpd and edit two lines. Place a comment mark in front of them.
Example from my modified file
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'
The # are the 2 commented lines. Some folks claim you can just change the line
option redirect_https '1'
to a 0 instead of 1. I was not successful with that. After the changes reboot the router and you should be able to login.
With the above change Chrome does not complain.
I am running davidc502 LEDE. His has latest wireless drivers and kernel. Runs well for me and is more up to date. He provides a 4.4 kernel for the wrt1900ac v1 again with latest drivers.
I am guessing you are aware of his builds, but if not here is link.
https://davidc502sis.dynamic-dns.net/
This site also has a link to his Openwrt support thread.
The problem with the LEDE builds from https://davidc502sis.dynamic-dns.net/
is the root certificate is not trusted and macOS High Sierra Safari will not allow you to accept the untrusted cert.
You can get around this issue easily. Just SSH or Telnet in to router. Go to /etc/config. Edit the file uhttpd and edit two lines. Place a comment mark in front of them.
Example from my modified file
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'
The # are the 2 commented lines. Some folks claim you can just change the line
option redirect_https '1'
to a 0 instead of 1. I was not successful with that. After the changes reboot the router and you should be able to login.
With the above change Chrome does not complain.
PS I hate nanny browsers that know better then me.
Hi,
Made the cutover to LEDE using David's builds on a WRT1900ACv1, WRT1200ACv2 & WRT1900ACSv2. Been 100% solid on all devices and better wifi throughput.
Never Say Never Again. LOL. It was a full nightmare for last two years with WRT Linksys series even with stock, DDWRT and LEDE (btw most hated UI and system for me). Instead of enjoying Internet I constantly forced to load something and try to improve it.
But now I am on Netgear r7800 with really great working DDWRT Kong based at 250mbs Internet. Its miles ahead of Marvel. Love it and highly recommend to try
I was on LEDE for a week but last 2 days using DNSCrypt my laptop stopped resolving DNS randomly for a few seconds causing Chrome to crash.It crashed every hour or so.
Flashed back to DD WRT and no crashes past 24 hours.
Not tried davids new build though.
Never Say Never Again. LOL. It was a full nightmare for last two years with WRT Linksys series even with stock, DDWRT and LEDE (btw most hated UI and system for me). Instead of enjoying Internet I constantly forced to load something and try to improve it.
But now I am on Netgear r7800 with really great working DDWRT Kong based at 250mbs Internet. Its miles ahead of Marvel. Love it and highly recommend to try
Hi,
Excellent point. Never say never. This is a great group of people trying to make a great product. I enjoyed using DD-WRT and at some point, I may use it again.
Until then, best regards!
Joined: 13 Jun 2006 Posts: 1608 Location: SE Michigan USA
Posted: Mon Aug 21, 2017 21:44 Post subject:
jefftk99 wrote:
vit5421 wrote:
Never Say Never Again. LOL. It was a full nightmare for last two years with WRT Linksys series even with stock, DDWRT and LEDE (btw most hated UI and system for me). Instead of enjoying Internet I constantly forced to load something and try to improve it.
But now I am on Netgear r7800 with really great working DDWRT Kong based at 250mbs Internet. Its miles ahead of Marvel. Love it and highly recommend to try
Hi,
Excellent point. Never say never. This is a great group of people trying to make a great product. I enjoyed using DD-WRT and at some point, I may use it again.
Until then, best regards!
Very true.
There have been times for me when DD-WRT seemed better then LEDE on my wrt3200 and there have been times when I felt LEDE was better.
Right now I am on the LEDE is better side, BUT I know that could change with the next dd-wrt release. Why I try each one as the dev releases a new build _________________ Unifi Security Gateway:Unifi Firmware Netgear r7800:Voxel Firmware Modem:Netgear CM500V voice and Data. ISP:Comcast tutorial for flashing "WRT" series: http://www.dd-wrt.com/phpBB2/viewtopic.php?t=287813 DD-WRT Installation, Upgrade & Basic Setup–Cliff Notes: http://www.dd-wrt.com/phpBB2/viewtopic.php?t=311117 Kong DD-WRT Config Tutorial: http://www.instructables.com/id/Install-and-Configure-a-DD-WRT-Kong-Router/ I tried to be normal once. Worst 2 minutes ever.
Never Say Never Again. LOL. It was a full nightmare for last two years with WRT Linksys series even with stock, DDWRT and LEDE (btw most hated UI and system for me). Instead of enjoying Internet I constantly forced to load something and try to improve it.
But now I am on Netgear r7800 with really great working DDWRT Kong based at 250mbs Internet. Its miles ahead of Marvel. Love it and highly recommend to try
Hi,
Excellent point. Never say never. This is a great group of people trying to make a great product. I enjoyed using DD-WRT and at some point, I may use it again.
Until then, best regards!
Very true.
There have been times for me when DD-WRT seemed better then LEDE on my wrt3200 and there have been times when I felt LEDE was better.
Right now I am on the LEDE is better side, BUT I know that could change with the next dd-wrt release. Why I try each one as the dev releases a new build
While LEDE does not have a lot of features DD-WRT has out of the box, I do not use or need them. In March, moved to a separate appliance from http://protectli.com running open source enterprise class firewall software from http://www.pfsense.org to allow me to easily add a Netgear LB1120 LTE Modem for dual WAN failover. I tried a number of off-the-shelf dual WAN failover routers (Cisco, Linksys), none of which offered the features I needed to restrict which LAN IP had access to the LTE failover WAN. Higher end enterprise class firewalls which may have offered those features were not cost effective for my needs. I could not be more pleased with pfSense, Protectli, and Netgear LTE modems.
WAN1: Crapcast -> Soon to be ATT Fiber
WAN2: ATT IoT LTE 1GB/yr for $25
AP1: WRT1900ACSv1:AP mode, wired to FW1, firewall and DHCP disabled
AP2: WRT1900ACv1: xfinitywifi WWAN Client Bridge guest access, firewall, NAT, DHCP
AP3: WRT3200ACM: AP mode, wired to AP1, firewall and DHCP disabled, testing before placing into service
EASY WAY TO FLASH LEDE
The easiest way I found to flash LEDE is to download the LEDE factory image, then use the TTL Serial Console to flash via TFTP. Just remember to perform a factory reset after flashing LEDE to wipe out any config remnants from previous firmware. This eliminates the need to flash back to Linksys factory firmware just to re-flash LEDE, and you can flash over both partitions at the same time. Instructions: http://www.dd-wrt.com/phpBB2/viewtopic.php?p=1054186#1054186
The added bonus is LEDE drops into a Linux prompt over the TTL Serial Console so you can change the IP address to access the LuCI interface while still wired to you existing network. Example: ifconfig br-lan 192.168.69.200 netmask 255.255.255.0. The TTL Serial Console will also echo console log output so you can monitor what LEDE is doing.
If you need a Linksys WRT Series TTL Console Port Adapter, I still have a few left out of the 100 I had made in China for everyone. http://www.ebay.com/itm/132070173439 Demand does not seem to be that high, so I am not sure if I will have more made.
SUMMARY
DD-WRT seems to be getting bloated as it tries to do everything, for all routers in existence, and mostly by one or two developers (BS and Kong). And since Kong has stopped supporting the WRT Series, the quality of the DD-WRT builds for them seems to be on the decline. LEDE seems focused on doing a very limited number of things very well, but allows one to add additional packages to suit your specific needs.
After 10+ faithful years of running DD-WRT on my various routers over the years, I just might never switch back to DD-WRT. This may very well be my last post on DD-WRT, but I am sure you will be able to find me on the LEDE or OpenWRT forums.
Cheers!
Elvis
@elvisimprsntr
I will not agree with your statements coz all problems are related to WRT`s units not to DDWRT. I did try LEDE and dont like it at all and will newer use it.
Many people are saying now that WRT`s are rock solid and working good on DDWRT or LEDE but its never been like that for my two years with 1200, 1900ac and acs and 3200 even with 2017 latest builds. Its half baked product btw same as LEDE in my opinion.
Two months ago I get rid of all my WRT units and get two Netgear r7800 with Kong build. (I am not using VPN and NAS functions).
Looks like Kong is working very hard now with r7800 and its really amazing how Qualcomm-Atheros can be miles ahead of Marvel. I am finally very happy internet user now.
Its just my opinion only
I've have a different experience with openwrt/LEDE, I've tried it and I prefer dd-wrt!
I use almost all the bells and whistles that are included within the dd-wrt package so for me, the LEDE would prove to be far more time consuming to achieve the same experience.
Joined: 27 Apr 2016 Posts: 112 Location: Down down .... under
Posted: Wed Aug 23, 2017 10:21 Post subject:
Uptime now 19 days, 40 min
I see a new build has just been released. Will hold-off on an upgrade as v3.0-r33006 is pretty stable. _________________ Linksys WRT1900ACv2 - My new go to build: DD-WRT v3.0-r44048 std (08/02/20) - STABLE
My WRT1900ACv2 has now been serving me for more than 5years Most reliable router I have ever owned!
Posted: Wed Aug 23, 2017 16:26 Post subject: using dd-wrt tutorial for update
fwiw, using the tutorial commands to determine what partition is active (linksys/dd-wrt), then setting and rebooting seemed to work; however, after the reboot, it always booted back to dd-wrt. these commands were entered via the dd-wrt command shell ui. my suspicion is that the "set" command failed cause the partition was correct and it did reboot. using the same commands via ssh got her done.
hopefully, the 5ghz band will have a bit more oomph now. 33006 was fairly stable but relatively slow at 5ghz speeds vs 2.4.
post reboot, i found it interesting that all my previous dd-wrt settings were maintained. not sure if that's good or bad just yet. _________________ asus rt-ac86u stock: 3.0.0.4.384_45149
wrt3200acm: r34578 {sunset}
"why nibble when u can take a byte."
Anyone else having WiFi disconnects randomly with the v3.0-r33006 release on WRT1900ac? WiFi says disconnected for a minute or so and no ssids are visble then they eventually come back. I just got the WRT1900AC on clearance and this is the first DD-WRT build in have tried. I tried LEDE first but hated the UI so back to DD-WRT for me (used on other routers).
Any idea what causes these disconnects? Is it a hardware issue and would be present in Linksys official firmware, the WiFi driver that DD-WRT uses or something else entirely?
