And again, it looks like the wifi is the one that crashes (reboots) the e900. Crashes did not cease with PPTP server and client turned off (though DDNS or QoS still on).
I am happy to see anyone fixing this, though now I suspect that people are enjoying their well-deserved vacations. Too bad the VPN won't work for me when I need it!
Posted: Thu Jul 24, 2014 2:00 Post subject: wpa_supplicant fails to start
I am testing a R7000 in client bridge, with firmware DD-WRT v24-sp2 (07/23/14) kongac - build 24710M.
It looks like wpa_supplicant doesn't work at all. Althoug I configured everything int the webui, the process does not appear to be running on the device. So, I manually created the files, and executing it with "-d" or "-dd" for debugging returns nothing. No error message, but no process started either. It looks like it exits as fast as it is started.
So, no WPA-Enterprise in client bridge mode for the R7000.
Router Model
Netgear WNDR3400(Version 1)
Firmware Version
DD-WRT v24-sp2 (06/23/14) mega - build 24461
Kernel Version
Linux 3.10.44 #2683 Mon Jun 23 13:03:57 CEST 2014 mips
Everything I've tested so far works. WAN was a little buggy at first, changed the MAC address and it started working.
Known Issues:
-----------------------------------------------------------------------------------------------------------------------
(1) WDS with encryption is currently only possible if 5G radio is disabled. This is no bug
but a curent limitation of the wds auth daemon.
Not sure if the reply was intended to me but... I am not trying to use/configure a WDS; just a regular client-bridge. The radio connect to the AP as a client, and the interface is bridged to the switch in order to provide LAN connectivity to ethernet devices. In this mode, the radio is not accepting client connections at all. So, this is no WDS here.
Posted: Sat Aug 02, 2014 3:31 Post subject: Linksys e3000 & e1500
Linksys e1500 & e3000 r24461 - Mega builds (trailed as either e1500 or e3000) seem to work great. Although, when switching from 20Mhz to Wide HT40 channel list has no selectable channels, just auto. Must switch extension channel from lower to upper or vice-versa and hit save before channel list returns to normal. WDS verified working (Disable CTS, beacon to 75. Investigating performance...). Bug in the GUI when setting channel and width to Auto GUI reports the TX
power as Auto. Changing TX power fixes this seemingly cosmetic issue. Setting both the client and host to auto-channel and auto-channel width works for WDS, although possibly counter-intuitive... QoS uplink and downlink seem to need to be set twice their normal value to achieve desired results with RTP FQ_CODEL.
Flashing
I broke my teeth trying to flash these units. Investigating for bad network cable or Windows 7. Bad flash recovery done using http management mode and from SliTaz, but it seemed that flashing mega builds always failed in management mode. Had to flash mini (r21676) trailed builds. 30/30/30 reset a must to get proper operation before flashing mega (r24461) sucessfully through the GUI. e3000 recovered with a TFTP flash from Windows 7, but not with e1500. SliTaz, no problem either way... Perhaps Windows 7 sucks.
Last edited by DanielIkard on Mon Aug 04, 2014 4:53; edited 8 times in total
Sorry to cause inconveniences but i just jumped in the thread after long and havent read much. I am requsting for help as I just flashed
dd-wrt.v24-24461_NEWD-2_K3.x_mega-e3000.bin
..n my E3000 and seems like this build is faulty and I cant recover the router.
The LAN segment is broken and cant access the router from my local computer. The Wifi 5 Ghz radio is also broken so the only way of accessing the router is via the 2.5 Ghz radio.
Any idea as to how to recover the router?..
Thanks
These people are much more intelligent than I... So here goes!
1.) Check your network settings. Static IP to 192.168.1.1 with an IP of 192.168.1.128. Full 30/30/30 reset then check again. Make sure to unplug the network cables when you do the reset.
2.) Start a ping to 192.168.1.1. If it comes back ttl=100 then it is waiting for a flash. If it's ttl=64 then the ddwrt os has started. Boot your router and notice it's behavior. If it goes ttl=100 a few times and then ttl=64 it's booting. If it does 100 a few times and then goes nothing it's not booting. If it goes ttl=100 and stays that way then it's in "management mode". Management mode is a failsafe for bad flash on certain linksys routers. To get it into management mode tap the reset button a few times as it starts up. Go to 192.168.1.1 on your browser to access the management mode GUI.
3.) Once in management mode load r21676. This one:
Reboot and then full reset and marinate (unplug for a minute). If still no check with a different patch cable. If still no try with a thumb drive linux. I like SliTaz. Still no? Try a different PC or TFTP. I sucessfully recovered once with tftp and Windows 7 on an unrelated bad flash.
Once r21676 is loaded full reset again and load r24461 through the GUI and full reset again. The full resets are key, so don't cut corners! r24461 works great on my e3000 but like I said before I broke my teeth trying to flash it correctly! Good to know it wasn't just me. Were you using Windows? Did you have other devices connected? Careful pressing the reset button not to do it too hard. Don't want to bust it unless you have a security driver. Also always only use trailed builds at the moment and refer to my above post about some GUI oddities. For r24461 use:
Ups.. I dont know whre my reply form an hour ago went..
In any case..THANK YOU very much for your help. Unfortunately it doesnt work . Here is the story:
The LAN segment of the buid seems to be compleatley broken, That is, if I connect a cable to the fully resetted router (wiht a fixed IP), the response to a PING is unreachable.. strange becasue it would have to be "no esponse".. right?.
The wired thing is that the router is recognized by the build as a wrt54g/gs/gl (built on June 23, 13:03 cest).
I hve had quite a number of dd-wrt routers but I havent flashed for a while so I dont know if wireless flashing has been implemented in recent build. If that isnt the case, unless you can think of another option, then I thnk I lost the router.
