Joined: 08 May 2018 Posts: 14126 Location: Texas, USA
Posted: Fri Jun 05, 2020 13:50 Post subject:
moisesmcardona wrote:
Router/Version: Linksys EA6500 v1
File: dd-wrt-43334-ea6500.trx
Reset?: N
Status: Bootloop
Fails to boot. Same behavior of 43324. Went back to 43320.
No reset, no serial or syslog files to help troubleshoot. This one and your 43324 reports are useless. You should try backing up your configuration for 43320 if you have to revert to it, reset completely, flash, do your configuration in steps until you figure out what boot loops it. Otherwise, just saying it boot loops is not very helpful. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Posted: Fri Jun 05, 2020 15:55 Post subject: E1200v2
Router/Version: E1200v2
File/Kernel: dd-wrt.v24-43334_NEWD-2_K3.x_mega-nv64k.bin
Previous/Reset: 43290 nv64k build no reset
Mode/Status: Working for now
Issues/Errors: Initial flash the router did not boot right away. The WebUI was unresponsive and ssh and telnet did not accept any connections. It did allow Wifi connections but no internet access. I have not power cycled the router but let it sit all night and in
the morning it showed the WebUI and allowed internet access. I have attached the syslog dumps I can get from the router after the flash. Current uptime is approximately 12 hours.
Joined: 26 Mar 2013 Posts: 1855 Location: Hung Hom, Hong Kong
Posted: Fri Jun 05, 2020 17:15 Post subject:
iFrog wrote:
I can't answer for Samba, as I don't use router level Samba. However, my smart lights have been acting funny (especially with the Google Assistant).
I rolled back to build 43217 and was surprised that the Samba also rebooted when I tried to access it after some idle period of not using Samba. It gave me an false impression that I was hit by a Samba "virus" from build 43320.... well.. sort of.
I think it's a very very bad idea to embed Samba into the kernel! Samba should stay in user-space...
And I am wondering how much junk had been added to the Linux kernel core ....
_________________ Router: Asus RT-N18U (rev. A1)
Drink, Blink, Stretch! Live long and prosper! May the Force and farces be with you!
I can't answer for Samba, as I don't use router level Samba. However, my smart lights have been acting funny (especially with the Google Assistant).
I rolled back to build 43217 and was surprised that the Samba also rebooted when I tried to access it after some idle period of not using Samba. It gave me an false impression that I was hit by a Samba "virus" from build 43320.... well.. sort of.
I think it's a very very bad idea to embed Samba into the kernel! Samba should stay in user-space...
And I am wondering how much junk had been added to the Linux kernel core ....
I seem to have sorted out my smart home issues, and they didn't appear to be related to DD-WRT. I tried the router NAS features about a year or so back, and I just find it a bad idea overall to depend on these limited devices for something a dedicated NAS, or even desktop computer are better suited for. With that said, It is a quick solution, and when I tried it, it worked ok. I would personally just rather head a dedicated NAS, or desktop for a full operating system. Maybe I'm misunderstanding that DD-WRT is a full linux environment, but for some things compared to a desktop / server install, it feels limited, if nothing more, by the CPU, and not having internal storage, if nothing else.
Posted: Fri Jun 05, 2020 18:42 Post subject: Re: Netgear Nighthawk R7000
mwchang wrote:
twindragon6 wrote:
Is Beamforming working in this build? There have been a lot of changes on the SVN lately! I kinda don't wanna flash anything that isn't at least semi stable.
Out of curiosity:
How do you test beam-forming?
How do you prove that a beam has been formed?
Using EM radiation meters? :)
Posted: Sat Jun 06, 2020 10:17 Post subject: Netgear R7000 - VAP failure
Router: R7000
Firmware: 06/04/2020 -r43334
Previous: stock Netgear
Mode: Gateway/AP
Errors/Issues: VAP fail
Uptime: About 15 minutes
Reset: no
fresh install on a new stock Netgear R7000.
nvram erase && reboot
All configuration set from dd-wrt GUI
guest Network (configured on br1, dhcp, nat, iptables) working on lan
guest VAP working on br0
guest VAP NOT working when associated to br1 (Wifi client don't connect)
Posted: Sat Jun 06, 2020 11:28 Post subject: UPDATE: Workaround for Netgear R7000 - VAP failure
eolo wrote:
Router: R7000
Firmware: 06/04/2020 -r43334
Previous: stock Netgear
Mode: Gateway/AP
Errors/Issues: VAP fail
Uptime: About 15 minutes
Reset: no
fresh install on a new stock Netgear R7000.
nvram erase && reboot
All configuration set from dd-wrt GUI
guest Network (configured on br1, dhcp, nat, iptables) working on lan
guest VAP working on br0
guest VAP NOT working when associated to br1 (Wifi client don't connect)
The workaround of the first post " Workaround startup command:
sleep 10;stopservice nas;stopservice wlconf;startservice wlconf;startservice nas" doesn't work for me .
Found this working workaround : "Startup command:
sleep 10;stopservice nas;wlconf eth1 down;wlconf eth1 up;wlconf eth2 down;wlconf eth2 up;startservice nas"
Posted: Sat Jun 06, 2020 13:04 Post subject: Re: UPDATE: Workaround for Netgear R7000 - VAP failure
eolo wrote:
eolo wrote:
Router: R7000
Firmware: 06/04/2020 -r43334
Previous: stock Netgear
Mode: Gateway/AP
Errors/Issues: VAP fail
Uptime: About 15 minutes
Reset: no
fresh install on a new stock Netgear R7000.
nvram erase && reboot
All configuration set from dd-wrt GUI
guest Network (configured on br1, dhcp, nat, iptables) working on lan
guest VAP working on br0
guest VAP NOT working when associated to br1 (Wifi client don't connect)
The workaround of the first post " Workaround startup command:
sleep 10;stopservice nas;stopservice wlconf;startservice wlconf;startservice nas" doesn't work for me .
Found this working workaround : "Startup command:
sleep 10;stopservice nas;wlconf eth1 down;wlconf eth1 up;wlconf eth2 down;wlconf eth2 up;startservice nas"
I wanted to get some Clarification on this issue since I also have an R7000: Do VAPs apply to guest networks, or are they more involved with that? While it wasn't on this particular build, I was able to create a guest network, but then after talking to people more experienced in what I was doing, found I didn't need to bother with guest networks. With this said, If I did want to do a single guest network would the VAPs issue described here affect me?
Upgrade from Kongac 30910M, with reset
All configuration set from dd-wrt GUI
guest Network (configured on br1, dhcp, nat, iptables) working on lan
guest VAP working on br0
guest VAP NOT working when associated at br1 (client don't connect)
Same issue as R7000, solved with same workaround: "Startup command:
sleep 10;stopservice nas;wlconf eth1 down;wlconf eth1 up;wlconf eth2 down;wlconf eth2 up;startservice nas"
Posted: Sat Jun 06, 2020 16:43 Post subject: Re: UPDATE: Workaround for Netgear R7000 - VAP failure
iFrog wrote:
eolo wrote:
eolo wrote:
Router: R7000
Firmware: 06/04/2020 -r43334
Previous: stock Netgear
Mode: Gateway/AP
Errors/Issues: VAP fail
Uptime: About 15 minutes
Reset: no
fresh install on a new stock Netgear R7000.
nvram erase && reboot
All configuration set from dd-wrt GUI
guest Network (configured on br1, dhcp, nat, iptables) working on lan
guest VAP working on br0
guest VAP NOT working when associated to br1 (Wifi client don't connect)
The workaround of the first post " Workaround startup command:
sleep 10;stopservice nas;stopservice wlconf;startservice wlconf;startservice nas" doesn't work for me .
Found this working workaround : "Startup command:
sleep 10;stopservice nas;wlconf eth1 down;wlconf eth1 up;wlconf eth2 down;wlconf eth2 up;startservice nas"
I wanted to get some Clarification on this issue since I also have an R7000: Do VAPs apply to guest networks, or are they more involved with that? While it wasn't on this particular build, I was able to create a guest network, but then after talking to people more experienced in what I was doing, found I didn't need to bother with guest networks. With this said, If I did want to do a single guest network would the VAPs issue described here affect me?
Thanks
Hi iFrog,
you need VAP only if you want to have more than 1 SSID on a wireless interface.
If you use your WiFi router/AP only with 1 SSID there is no need of VAP. For example, if you dedicate a router for Wifi guest access, you don't need to use VAP.
The need of a separate SSID (and consequently VAP) is for not sharing the WPA2 password with guest, and for isolating guest from your home network.
My home setup is an AP with 3 SSID:
1) WiFi for me and my family, bridged on the home LAN
2) WiFi for guest, no access to home network, only internet access
3) WiFi for IoT, no access to home network, only internet access
Posted: Sat Jun 06, 2020 16:49 Post subject: Re: UPDATE: Workaround for Netgear R7000 - VAP failure
eolo wrote:
iFrog wrote:
eolo wrote:
eolo wrote:
Router: R7000
Firmware: 06/04/2020 -r43334
Previous: stock Netgear
Mode: Gateway/AP
Errors/Issues: VAP fail
Uptime: About 15 minutes
Reset: no
fresh install on a new stock Netgear R7000.
nvram erase && reboot
All configuration set from dd-wrt GUI
guest Network (configured on br1, dhcp, nat, iptables) working on lan
guest VAP working on br0
guest VAP NOT working when associated to br1 (Wifi client don't connect)
The workaround of the first post " Workaround startup command:
sleep 10;stopservice nas;stopservice wlconf;startservice wlconf;startservice nas" doesn't work for me .
Found this working workaround : "Startup command:
sleep 10;stopservice nas;wlconf eth1 down;wlconf eth1 up;wlconf eth2 down;wlconf eth2 up;startservice nas"
I wanted to get some Clarification on this issue since I also have an R7000: Do VAPs apply to guest networks, or are they more involved with that? While it wasn't on this particular build, I was able to create a guest network, but then after talking to people more experienced in what I was doing, found I didn't need to bother with guest networks. With this said, If I did want to do a single guest network would the VAPs issue described here affect me?
Thanks
Hi iFrog,
you need VAP only if you want to have more than 1 SSID on a wireless interface.
If you use your WiFi router/AP only with 1 SSID there is no need of VAP. For example, if you dedicate a router for Wifi guest access, you don't need to use VAP.
The need of a separate SSID (and consequently VAP) is for not sharing the WPA2 password with guest, and for isolating guest from your home network.
My home setup is an AP with 3 SSID:
1) WiFi for me and my family, bridged on the home LAN
2) WiFi for guest, no access to home network, only internet access
3) WiFi for IoT, no access to home network, only internet access
So I need 2 VAP.
Regards.
Thanks, I understand what you're saying. So If I want to setup a guest network, on the same router ,as the physical SSIDs then I would be using VAPs. If I were to connect separate access point with it's own login separate from the router's built in wireless I would not be using VAPs, and if I just want the physical interfaces on the main router, then I wouldn't be using VAps either. I'm just making sure I'm understanding what I read here. As the term VAps and other things aren't really mentioned with proprietary firmware. I see it mostly with open firmwares.
I think it's a very very bad idea to embed Samba into the kernel! Samba should stay in user-space...
Ever since in-kernel samba has been implemented, I lost smb access from my mobile devices and have been experiencing bugs trying to access the file system (incomplete file listing, router crashes/reboots, etc). I had to migrate my media server setup over to a linux system (from windows server) to get crap to work. It's been frustrating to say the least but things appear to be more stable on my new linux server. However, I still lost smb access from my android devices (used for ebook/calibre server)