SDundee,
I think BS took some junk out
https://svn.dd-wrt.com/changeset/41118
but all in all he has cleaned up a lot also
you just have to dig thru https://svn.dd-wrt.com//timeline to see mostly what's what
then, on the other hand, BS may NOT always put exactly what he changes in there.
AND you been asking about JFFS2
r41135 dmesg still shows a bit of
I only use it for slightly altered unbound.conf (add ovpn server network to unbound.conf)
https://forum.dd-wrt.com/phpBB2/viewtopic.php?p=1165673#1165673
and that is only needed because I like to use the router's local DNS when connected to its ovpn server
local DNS while connected to its ovpn server works fine if not running unbound --- but it also is good while running unbound since I made the changes to unbound.conf
---
r41135 now has unbound ver 1.9.3
yea, I checked it by disabling JFFS2 and let unbound use its own .conf but it still don't work the way I like it to
Now don't misunderstand me, you still can't install over any Linksys firmware newer than FW_EA8500_1.1.4.168206
unless you use serial cable to get around Linksys silly firmware lock. ---
If you have a 'made for North America' EA8500 you can use the GUI to install DD-WRT using the
r41174 'factory-to-ddwrt.img' over these guys or older Linksys FW:
FW_EA8500_1.1.3.166845_prod.img
FW_EA8500_1.1.4.168206_prod.img
You CANNOT GUI install DD-WRT over these guys or any newer Linksys firmware:
FW_EA8500_1.1.4.169978_prod.img
FW_EA8500_1.1.4.173728_prod.gpg.img
Posted: Tue Oct 01, 2019 15:18 Post subject: latest firmware
Hello! I have 2 questions for you, folks!
1. It's safe to install latest firmware from oficial beta ftp?
2. In latest firmware top light is non functioning, it's normal?
Posted: Tue Oct 01, 2019 16:05 Post subject: Re: latest firmware
keefeere wrote:
Hello! I have 2 questions for you, folks!
1. It's safe to install latest firmware from oficial beta ftp?
2. In latest firmware top light is non functioning, it's normal?
1.
Linksys EA8500
DD-WRT v3.0-r41218 std (10/01/19)
Linux 4.9.194 #474 SMP Mon Sep 30 03:10:28 CEST 2019 armv7l
works well for me
2.
The top 'Linksys' light has never worked on any DD-WRT k4.9.x build.
It does work ok if you use an old k3.18.x build ----and this is noted in many places so you might search if you have further
Posted: Wed Oct 02, 2019 4:05 Post subject: Re: latest firmware
mrjcd wrote:
1.
Linksys EA8500
DD-WRT v3.0-r41218 std (10/01/19)
Linux 4.9.194 #474 SMP Mon Sep 30 03:10:28 CEST 2019 armv7l
works well for me
2.
The top 'Linksys' light has never worked on any DD-WRT k4.9.x build.
It does work ok if you use an old k3.18.x build ----and this is noted in many places so you might search if you have further
Posted: Thu Oct 03, 2019 21:18 Post subject: EA8500 and Home Automation
Over the past several years, I have aquired many IP based home automation products, from smart light bulbs, switches, thermostat, cameras and sensors. They are beginning to tie up a large portion of my regular WiFi connectivity. I would like to move them all onto a virtual WiFi on a different subnet using my EA8500, if possible.
Is anyone here doing this already? What would be the best method (and simplest) to make this happen? Since none of these devices support "N" that I am I am aware of, I would want to make the virtual wifi "G" or "B/G" only. some of these devices only support dhcp as well...so keep that in mind. I also need to make sure both subnets can still be routed to each other. Any ideas?
Joined: 21 Jan 2017 Posts: 1783 Location: Illinois Moderator
Posted: Fri Oct 04, 2019 14:22 Post subject: Re: EA8500 and Home Automation
lexridge wrote:
Over the past several years, I have aquired many IP based home automation products, from smart light bulbs, switches, thermostat, cameras and sensors. They are beginning to tie up a large portion of my regular WiFi connectivity. I would like to move them all onto a virtual WiFi on a different subnet using my EA8500, if possible.
Is anyone here doing this already? What would be the best method (and simplest) to make this happen? Since none of these devices support "N" that I am I am aware of, I would want to make the virtual wifi "G" or "B/G" only. some of these devices only support dhcp as well...so keep that in mind. I also need to make sure both subnets can still be routed to each other. Any ideas?
What you are describing is virtual access points under the wireless settings tab. What I don't know is if virtual AP's can truly have different network modes from the "real" chipset settings used. That you will have to play with. Also, I am not sure if you need a new vlan to get a new subnet...this is getting beyond my area of knowledge. _________________ FORUM RULES
Posted: Fri Oct 04, 2019 15:06 Post subject: Re: EA8500 and Home Automation
lexridge wrote:
I would like to move them all onto a virtual WiFi on a different subnet using my EA8500, if possible.
That is a very simple thing to do.
lexridge wrote:
I would want to make the virtual wifi "G" or "B/G" only.
Don't believe is possible with the EA8500. The VAP will follow whatever its main physical wireless interface is set at.
NG-Mixed is a good setting ...well if you need N also for you main
lexridge wrote:
I also need to make sure both subnets can still be routed to each other.
Well I don't see there is much point in putting them on a different subnet.
Now, you could put them on different subnet and resrict access to maybe just 1 or 2 devices on main subnet via some firewall/iptable rules.
Then again I don't see the point unless you just want these smart light bulbs, switches, thermostat, cameras and sensors restricted from your main network....on the other other hand I see NO point unless some of these devices have communication with their manufacturer or some other online source that you would NOT want to have access to your main net.
I don't have any such devices so can't really say much --- maybe someone else will know more.
Posted: Fri Oct 04, 2019 18:06 Post subject: Re: EA8500 and Home Automation
mrjcd wrote:
lexridge wrote:
I would like to move them all onto a virtual WiFi on a different subnet using my EA8500, if possible.
That is a very simple thing to do.
lexridge wrote:
I would want to make the virtual wifi "G" or "B/G" only.
Don't believe is possible with the EA8500. The VAP will follow whatever its main physical wireless interface is set at.
NG-Mixed is a good setting ...well if you need N also for you main
lexridge wrote:
I also need to make sure both subnets can still be routed to each other.
Well I don't see there is much point in putting them on a different subnet.
Now, you could put them on different subnet and resrict access to maybe just 1 or 2 devices on main subnet via some firewall/iptable rules.
Then again I don't see the point unless you just want these smart light bulbs, switches, thermostat, cameras and sensors restricted from your main network....on the other other hand I see NO point unless some of these devices have communication with their manufacturer or some other online source that you would NOT want to have access to your main net.
I don't have any such devices so can't really say much --- maybe someone else will know more.
I am actually starting to rethink this a bit. Presently I have around 40 physical devices and probably another 25 virtual ones (scripts combining hardware functions). All are being controlled via a Raspberry Pi (Mozilla IoT and HA-Bridge for Hue to X10 compatibility) and Alexa. I did discover the TPLink devices DO indeed call home but managed to block them via the Access Restrictions in the router. I think I will keep them all on the same Wifi for now. I will just hard code in their DCHPs in the upper range (192.168.0.150-250) hopefully never exceeding 100 devices. Thanks for your thoughts on this matter.
lexridge,
If one of the main reasons is to free up channel bandwidth then I would just throw in another router (a cheapy unit prolly work fine) setup as a WAP.
You can still have on separate subnets if you wanted and let the main EA8500 do all DHCP or have the WAP doing DHCP for separate subnets wired VLAN or wireless....can't say 'bout other units but I know the EA8500 setup as a WAP can also do VLANs & multiple VAPS on different subnets while its main wired interface (not talking 'bout its WAN) is still on your main net. Any ports or VAPs can be on main net plus whatever ports or VAPs can be on a different isolated/or not subnet
good luck to ya --- seems like you already have quite a handful
