I flashed a K24_std_nokiad build to my TM with an SD mod (my TM is my favorite router!).
I posted in the BS 17967 build thread that I was having a problem with the sd card. That has been resolved thanks to a tip by Dark_Shadow. Now optware, mypage, & bwmon are working.
I have nothing negative to report except for one minor mostly cosmetic issue.. (even vwiz is working!)
The small issue I am seeing is that in the admin, management tab, the total/free size of the sd card, the free shows just a "-" (no quotes).
Not a big deal... but we are trying to make the build(s) "perfect" right?
My RT-N16 with a usb drive is next. That will get a K26_std_usb_nas build.
Great work Dev's.. I really like the nvram status feature.. That beez a winna
EDIT: There was some discussion about SSH not working in the BS build thread as well as in TRAC. SSH worked right away on this build. It may be that I didn't give it long enough to build the key after enabling ssh when I flashed BS's build yesterday. Comments in TRAC stated the SSH worked in BS's build.
Barry,
Interesting, I still get a connection refused trying an SSH connection using the latest WinSCP stable. Guess I'm going to have to do some mucking around. yea, I read the comments in the other thread about this issue...."dd-wrt.v24-17990_NEWD-2_K2.6_mini.bin"
Side note, why does your sig now have a mod deleted comment ? bad boy ? _________________ 1 WRT160N v3 - remote AP WPA2 Personal Aes dd-wrt-mini-trailed CPU OC400,
2 wrt54G v3(BCM4712 chip rev 1, corerev=7)- AP WPA2 Personal Aes dd-wrt-mini-generic CPU OC228,
1 wrt54gs v6 - remote AP WPA2 Personal Aes dd-wrt-micro CPU OC228 ,
3 WAP54g v3 - repeater, client Bridge, repeater bridge dd-wrt-micro CPU OC225,
1 NetGear WNR2000 v3 AP Atheros AR7241 ver 1 rev 1.1 (0x0101) Trailed build CPU OC360
DD-WRT usually the most current BS builds and less frequently lately EKO builds(because of new BS rules that eliminated EKO builds I used).
Joined: 26 Jan 2008 Posts: 13049 Location: Behind The Reset Button
Posted: Fri Dec 09, 2011 18:04 Post subject:
gene wrote:
Barry,
Interesting, I still get a connection refused trying an SSH connection using the latest WinSCP stable. Guess I'm going to have to do some mucking around. yea, I read the comments in the other thread about this issue...."dd-wrt.v24-17990_NEWD-2_K2.6_mini.bin"
Side note, why does your sig now have a mod deleted comment ? bad boy ?
BS's 17967.. I could not connect using ssh. Reading trac, there was some discussion and a few worksforme, workshere, invalid, etc..
After enabling ssh on the router, I couldn't connect but I may not have waited long enough for the keys to build. So I used the fix posted in the 17967 build thread and that worked.. I was having problem getting optware and mypage to run so I flashed back to 17201. Last night, I flashed eko's 17990, enabled ssh, gave it a couple of minutes and I could ssh right in using winscp.
In regards to my sig.. I haven't been bad.. Or at least not any worse than usual. I saw that sig in another forum and I liked it.. It made me laugh.. _________________ [Moderator Deleted]
Me and dc are still experiencing problems here and would love if someone wants to help troubleshoot the ssh problem.
I've verified after many many tests that problems could be of two tipes, always in regard to rsa key (dss is processed ok):
1. You don't reset nvram before upgrading. Old sshd_rsa_host_key is there in nvram. New dropbear binary doesn't like this "old" format and exits. That's why me, dc, and you barryware as you said, got connection refused.
2. When you reset nvram when upgrading to this or 17990 build you end up with dropbear running well because it generates new keys. But dd-wrt isn't able to write the sshd_rsa_host_key variable that ends up to be blank. This is because here with an e4200 and at dc's place with an e3000, noone else tried, the command:
dropbearconvert dropbear openssh /tmp/root/.ssh/ssh_host_rsa_key /tmp/root/.ssh/rsa
thinks that is a dss key and exits with segmentation fault.
So, in fact, the rsa key is generated again and used by dropbear's server binary. But it is always NOT saved into nvram, so it's not restored at reboot and another one is generated making you unable, from your client, to understand if you're connecting to your server, or not.
Barry,
Interesting, I still get a connection refused trying an SSH connection using the latest WinSCP stable. Guess I'm going to have to do some mucking around. yea, I read the comments in the other thread about this issue...."dd-wrt.v24-17990_NEWD-2_K2.6_mini.bin"
Side note, why does your sig now have a mod deleted comment ? bad boy ?
BS's 17967.. I could not connect using ssh. Reading trac, there was some discussion and a few worksforme, workshere, invalid, etc..
After enabling ssh on the router, I couldn't connect but I may not have waited long enough for the keys to build. So I used the fix posted in the 17967 build thread and that worked.. I was having problem getting optware and mypage to run so I flashed back to 17201. Last night, I flashed eko's 17990, enabled ssh, gave it a couple of minutes and I could ssh right in using winscp.
In regards to my sig.. I haven't been bad.. Or at least not any worse than usual. I saw that sig in another forum and I liked it.. It made me laugh..
OMG, now I feel foolish, today I had NOT enabled SSH to test, the previous build I did have it enabled, SSH does indeed work with this build now for me. However WiViz does not work.
UPDATE: opps, maybe spoke too soon, on cold boot, a new rsa key is being generated for each boot. since I know what I'm connecting to, its not a problem, but it needs fixin as clients should not have to update the key every time the router boots. _________________ 1 WRT160N v3 - remote AP WPA2 Personal Aes dd-wrt-mini-trailed CPU OC400,
2 wrt54G v3(BCM4712 chip rev 1, corerev=7)- AP WPA2 Personal Aes dd-wrt-mini-generic CPU OC228,
1 wrt54gs v6 - remote AP WPA2 Personal Aes dd-wrt-micro CPU OC228 ,
3 WAP54g v3 - repeater, client Bridge, repeater bridge dd-wrt-micro CPU OC225,
1 NetGear WNR2000 v3 AP Atheros AR7241 ver 1 rev 1.1 (0x0101) Trailed build CPU OC360
DD-WRT usually the most current BS builds and less frequently lately EKO builds(because of new BS rules that eliminated EKO builds I used).
Were changes made to iptables some how? I have my gateway/router setup with guest wifi on wl0.1 using "Seperate LAN and WLAN wiki" and cannot get acess to the Internet. My guests are handed an IP, DNS, gateway from DHCP but cannot reach the Internet.
Any ideas? Is this a bug or just a change to NAT or something? I've never had a problem with this setup/guide/wiki always works 100% until the last few 17xxx builds.
Thanks in advance!
-mrengles
EDIT: Should have mentioned running this all on a Cisco-Linksys E4200 v1
Joined: 24 Feb 2009 Posts: 2026 Location: Sol System > Earth > USA > Arkansas
Posted: Sat Dec 10, 2011 7:15 Post subject:
I took the "second" plunge and went on to update to this firmware (17990). It appears to work a bit better than the last one (in regards to rebooting and all of that), but then it could have been the way I updated previously. I will report if anything changes, but otherwise seems to be a fairly stable build. _________________ E3000 22200M KongVPN K26
WRT600n v1.1 refirb mega 18767 BS K24 NEWD2 [not used]
WRT54G v2 16214 BS K24 [access point]
Try Dropbox for syncing files - get 2.5gb online for free by signing up.
Read! Peacock thread
*PLEASE* upgrade PAST v24SP1 or no support.
Joined: 09 Aug 2009 Posts: 86 Location: The Beach...
Posted: Sat Dec 10, 2011 7:44 Post subject:
Updated my WNDR3300 Client Bridge to dd-wrt.v24-17990_NEWD_std-nokaid_nohotspot_nostor and Port 1 is still broken as with 17967. Haven't checked the WAN to Switch blocking access yet. May do the AP later. Have to get ready for the new Internet installer in the AM.