Joined: 13 Jun 2006 Posts: 1608 Location: SE Michigan USA
Posted: Tue Aug 15, 2017 18:40 Post subject:
vit5421 wrote:
The last free version is InSSIDer 40020. Attached and just replace extension to msi. You can google it as well for this version.
I assume this is a .exe file when I looked at it. When I changed the extension I got a message about not running on the version of windows I have, which is windows 10 pro.
Dear Bill,
If you will change the extension to msi as my instruction it will work just fine. I like and trust InSSIDer but may be Acrylic will be good too
Joined: 13 Jun 2006 Posts: 1608 Location: SE Michigan USA
Posted: Tue Aug 15, 2017 19:41 Post subject:
vit5421 wrote:
Dear Bill,
If you will change the extension to msi as my instruction it will work just fine. I like and trust InSSIDer but may be Acrylic will be good too
Posted: Fri Aug 18, 2017 20:14 Post subject: 2.4GHz radio
The only issue I have had with this build is my 2.4GHz radio drops out ever so often. I will see it disappear on my phone then come back up shortly after. But haven't had any random reboots.
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
UPDATE
After nearly a week of testing LEDE on ACM, I have pressed it into service. The ACM is now my primary router. I run LEDE (Kernel 4.4) on ALL three routers.
AP1: WRT3200ACM: AP mode, wired to FW1, firewall and DHCP disabled
AP2: WRT1900ACSv1: AP mode, wired to AP1, firewall and DHCP disabled, backup
AP3: WRT1900ACv1: xfinitywifi WWAN Client Bridge guest access, firewall, NAT, DHCP
AP1: WRT3200ACM: AP mode, wired to FW1, firewall and DHCP disabled
AP2: WRT1900ACSv1: AP mode, wired to AP1, firewall and DHCP disabled, backup
AP3: WRT1900ACv1: xfinitywifi WWAN Client Bridge guest access, firewall, NAT, DHCP
Just curious, but are you doing your own builds? If not, where are you finding LEDE builds for devices other than the WRT1900ACv1 that are based on the 4.4 kernel (which I know DavidC does over on the LEDE forums due to the crashing issue with >4.4 kernels)?
AP1: WRT3200ACM: AP mode, wired to FW1, firewall and DHCP disabled
AP2: WRT1900ACSv1: AP mode, wired to AP1, firewall and DHCP disabled, backup
AP3: WRT1900ACv1: xfinitywifi WWAN Client Bridge guest access, firewall, NAT, DHCP
Just curious, but are you doing your own builds? If not, where are you finding LEDE builds for devices other than the WRT1900ACv1 that are based on the 4.4 kernel (which I know DavidC does over on the LEDE forums due to the crashing issue with >4.4 kernels)?
Joined: 13 Jun 2006 Posts: 1608 Location: SE Michigan USA
Posted: Sat Aug 19, 2017 15:13 Post subject:
elvisimprsntr wrote:
zabolots wrote:
elvisimprsntr wrote:
I run LEDE (Kernel 4.4) on ALL three routers.
AP1: WRT3200ACM: AP mode, wired to FW1, firewall and DHCP disabled
AP2: WRT1900ACSv1: AP mode, wired to AP1, firewall and DHCP disabled, backup
AP3: WRT1900ACv1: xfinitywifi WWAN Client Bridge guest access, firewall, NAT, DHCP
Just curious, but are you doing your own builds? If not, where are you finding LEDE builds for devices other than the WRT1900ACv1 that are based on the 4.4 kernel (which I know DavidC does over on the LEDE forums due to the crashing issue with >4.4 kernels)?
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.