New 1.0.4.6 based custom firmware

Quote:

---

Originally Posted by Chris Thompson

My one remaining problem is when, using putty to log on via dropbear to the root I do not know the default password.

---

The default password for root is empty. That's why you can telnet in as root without any difficulty. I'm pretty sure dropbear will not allow root logins at all. I'm even more sure it won't allow a root login if the account does not have a password.

You'll need to add a user account, use that to log in, then use 'su' to switch to root when needed. This is the best way anyway.

How you add the account depends on your router's configuration. In particular whether your in AP or Gateway mode and whether or not you've enabled UBA mode (user based authentication). Please post your configuration.

Quote:

---

Originally Posted by Chris Thompson

...where do I put the authorized_keys file obtained from puttygen? And will it work, what are the files in opt/etc/dropbear/dropbear_dss_host_key and dropbear_rsa_host_key?

---

The ipkg installation should have configured everything you need. The first connection from a client will exchange the keys and confirm your trust level. Once trust has been established, the client machine will confirm the keys every time you log in behind the scenes. If the keys change, your client will tell you so.

- K.C.

Quote:

---

Originally Posted by gratitude182

@Stefan

i think this one helped for me:

http://www.wl500g.info/showthread.ph...highlight=ubsa

grat182

---

While I was testing my mt-daapd configuration, I removed the user that was authenticated for MYSHARE1. Then I re-entered the same user to restore my previous configuration. I had rebooted the asus many times before with the reset-buttton (very fast), so I did again. But this time it did not reach the Ready-state anymore, but showed just the same mad behaviour that others have experienced.
Only resetting to factory defaults helped.
But applying UBSA mode got the system mad again and again.
So, finally I was saved by this lovely forum: I removed __pdc\passwd

It's definitely a BUG from Asus that causes this idiot behaviour. :eek: Remember never to delete a user and reentering it. I did not test a different username.

Marc

Quote:

---

Originally Posted by kfurge

FWIW, I've actually stopped spinning down my HDD. I didn't like how long it takes to spin up. I didn't like the mechanical wear and tear either.

After reviewing the datasheet for the Toshiba HDD in the router I discovered it supports an APM mode where it spins in a low power state at about 40% of the full rotational speed. This mode dissipates only slightly more power than a full spin-down. However, the drive spins up in about half the time with much less tortional stress. For those interested, after installing the hdparm ipkg, put these lines in your rc.local:

# Do the necessary steps so the internal HDD will enter low power
# idle after 5 minutes and low RPM idle after 1 hour
mount -o remount,noatime,nodiratime /shares/${pool}
/opt/sbin/hdparm -B 164 ${internal_hdd}
/opt/sbin/hdparm -B 114 ${internal_hdd}
smartctl -dT ${internal_hdd}

The timing equations and details for the two calls to hdparm can be found in the datasheet.

- K.C.

---

Hi KC,

I would like to do the same like you did but my harddisk model is HDT722516DLAT80 (HITACHI Deskstar T7K250). I've checked the datasheet from Hitachi and it says the following which I do not know how I should set the parameters for hdparm:

10.14 Advanced Power Management feature set (APM)
This feature allows the host to select an advanced power management level. The advanced power management level
is a scale from the lowest power consumption setting of 01h to the maximum performance level of FEh. Device
performance may increase with increasing advanced power management levels. Device power consumption may
increase with increasing advanced power management levels. The advanced power management levels contain
discrete bands described in the section of SET FEATURES command in detail. This feature set uses the following
functions:
• A SET FEATURES subcommand to enable Advanced Power Management
• A SET FEATURES subcommand to disable Advanced Power Management
Advanced Power Management is independent of the Standby timer setting. If both Advanced Power Management
and the Standby timer are set, the device will go to the Standby state when the timer times out or the device's
Advanced Power Management algorithm indicates that the Standby state should be entered.
The IDENTIFY DEVICE response word 83, bit 3 indicates that Advanced Power Management feature is supported
if set. Word 86, bit 3 indicates that Advanced Power Management is enabled if set. Word 91, bits 7-0 contains the
current Advanced Power Management level if it is enabled.

I read from your reply to dophine who is using the same Hitachi HD at http://wl500g.info/showthread.php?t=...light=spindown -- do you mean i can use the same settings like you did?

/opt/sbin/hdparm -B 164 ${internal_hdd}
/opt/sbin/hdparm -B 114 ${internal_hdd}

Could you kindly advise? I'm using "hdparm -S 180 ${internal_hdd}" now which spinsdown the harddisk, not the best option from the advice you had given.

Btw, i noticed that S.M.A.R.T. is not enabled when i look at the admin page for the harddisk details. It doesn't look right to me, am i missing something?

Many thanks for your help!

cheers,
Patrick

Quote:

---

Originally Posted by patrickquek

Could you kindly advise?

---

Sure. From section 12.39.3 of d7k250p_spv1.8.pdf it looks like the timing equations for your HDD are the same as mine. Therefore, the values should work OK for you too. That section contains everything you need to adjust the timing to meet your needs.

I've been running with the 5min/1hr timing for a few months now and it works pretty well for me.

Quote:

---

Originally Posted by patrickquek

Btw, i noticed that S.M.A.R.T. is not enabled when i look at the admin page for the harddisk details. It doesn't look right to me, am i missing something?

---

Unfortunately, SMART has to be disabled to allow the drive to enter low power modes. This is because the httpd process (yes, the same one that serves up the web configuration interface) regularly polls the SMART status from the HDD. With my drive, this kept it from entering any of the low power modes.

- K.C.

Quote:

---

Originally Posted by kfurge

The default password for root is empty. That's why you can telnet in as root without any difficulty. I'm pretty sure dropbear will not allow root logins at all. I'm even more sure it won't allow a root login if the account does not have a password.

You'll need to add a user account, use that to log in, then use 'su' to switch to root when needed. This is the best way anyway.

How you add the account depends on your router's configuration. In particular whether your in AP or Gateway mode and whether or not you've enabled UBA mode (user based authentication). Please post your configuration.



The ipkg installation should have configured everything you need. The first connection from a client will exchange the keys and confirm your trust level. Once trust has been established, the client machine will confirm the keys every time you log in behind the scenes. If the keys change, your client will tell you so.

- K.C.

---

OK, now what I need ssh access for is to replace Telnet when I dissable it from rs.local. I can now see how I can log in to root with no password. However, I am sure I must be doing something wrong as I can not log into any of my user accounts via telnet either. Only the root. I have three user accounts created by the web interface. The wl700ge is set up as a Gateway and I am using USBA. If I was able to access any of my user accounts by telnet I may be able to sort the rest out, but right now I am lost for an answer.

Chris.

Quote:

---

Originally Posted by Chris Thompson

The wl700ge is set up as a Gateway and I am using USBA. If I was able to access any of my user accounts by telnet I may be able to sort the rest out, but right now I am lost for an answer.

Chris.

---

Everything you've said so far seems OK. Can you post the output of 'cat /etc/passwd' to make sure all of the links are OK. XXXX out the password field if necessary.

It should look something like:

root:XXXXX:0:42000:root:/:/bin/sh
kfurge:XXXXX:1001:42000:kfurge:/opt/home/kfurge:/opt/bin/bash

Also, make sure all shells you want to use are listed in /etc/shells. Finally, to help troubleshooting further, please post the last few lines of 'logread' immediately after an invalid login.

- K.C.

Kfurge, i think you did a great job. I still use you mod above openwrt. So my question: Why dont you change more things in the firmware? I dont think asus will do. So we can make a better firmware. I will help.

Sollie.

Quote:

---

Originally Posted by sollie

So my question: Why dont you change more things in the firmware?

---

This thread sums up my thoughts on this topic:

http://wl500g.info/showthread.php?t=8590

So far, there's nothing I've wanted to do that couldn't be done with the existing firmware. In fact, the only thing that currently can't be changed on a running system at boot time via rc.local is the kernel itself.

What I think is missing is the transfer of this know-how so everyone benefits from the collection of tricks that makes all of this magic possible. I think a wiki can help with this communication and keep the information within up-to-date.

- K.C.

Quote:

---

Originally Posted by kfurge

Everything you've said so far seems OK. Can you post the output of 'cat /etc/passwd' to make sure all of the links are OK. XXXX out the password field if necessary.

It should look something like:

root:XXXXX:0:42000:root:/:/bin/sh
kfurge:XXXXX:1001:42000:kfurge:/opt/home/kfurge:/opt/bin/bash

Also, make sure all shells you want to use are listed in /etc/shells. Finally, to help troubleshooting further, please post the last few lines of 'logread' immediately after an invalid login.

- K.C.

---

The passwd file is as follows:

root::0:42000:root:/:/bin/sh
nora:XXXXX:35001:42000:nora:/opt/home/nora:/bin/false
thompsoncm:XXXXX:35002:42000:thompsoncm:/dev/null:/bin/false
test:XXXXX:35000:42000:test:/dev/null:/bin/false

I was unable to find anything in /etc/shells, that does not mean that there is nothing there ;-)

The puty log is as bellow:

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2007.03.17 23:58:03 =~=~=~=~=~=~=~=~=~=~=~=
(none) login: nora

Password:
warning: cannot change to home directory

The last line might hold the clue! But where should the home directory be and how should it be pointed to?

Quote:

---

Originally Posted by Chris Thompson

The passwd file is as follows:

root::0:42000:root:/:/bin/sh
nora:XXXXX:35001:42000:nora:/opt/home/nora:/bin/false
thompsoncm:XXXXX:35002:42000:thompsoncm:/dev/null:/bin/false
test:XXXXX:35000:42000:test:/dev/null:/bin/false

I was unable to find anything in /etc/shells, that does not mean that there is nothing there ;-)

---

OK, three problems:

1) Your home directories, with the exception of nora, all point to /dev/null. Make them all point somewhere real, and make sure they're all owned by the appropriate user.

2) Your shells. All accounts have a shell of /bin/false. This is what is normally put in when you absolutely want to deny a login to an account. Put a valid shell here such as /opt/bin/bash.

3) If you don't have a valid /etc/shells or the shells listed within /etc/shells do not include the shells listed in the password files, then you will also be denied a login. You must fix this too. One of the modifications to the custom firmware was a symlink from /etc/shells to /tmp/shells. Symlink from /opt/etc/shells to /tmp/shells within rc.local. Now make sure /opt/bin/bash is listed in /etc/shells.

- K.C.

Quote:

---

Originally Posted by kfurge

Sure. From section 12.39.3 of d7k250p_spv1.8.pdf it looks like the timing equations for your HDD are the same as mine. Therefore, the values should work OK for you too. That section contains everything you need to adjust the timing to meet your needs.

I've been running with the 5min/1hr timing for a few months now and it works pretty well for me.

Unfortunately, SMART has to be disabled to allow the drive to enter low power modes. This is because the httpd process (yes, the same one that serves up the web configuration interface) regularly polls the SMART status from the HDD. With my drive, this kept it from entering any of the low power modes.

- K.C.

---

Hi KC,

Thanks for the prompt response and advice, appreciate it!

I'm running into another unexpected problem with my 700ge's wireless connection (arrgghh).

I can connect wirelessly fine if i do not setup any encryption. The connection is stable as well.

Once i setup WEP, the performance is erratic. Often i cannot even associate (though i can see the SSID with full signal strength when i View Wireless Network from XP). When i attempt to "Connect", it waits at "Waiting for network" for very long or "Detecting network type"... and nothing happens after that. For the times when I am able to connect, i run continuous ping to see how stable the connection is -- it gets disconnected after about 3 minutes, then back on again.. very erratic.

I've reflashed back to the original ASUS 1.0.4.6 rom to try it out with the same results. I've performed resets many times (by holding down reset > 5s)
with no improvements.

Also, I'm also not able to complete EZSetup successfully. It was always stop at the 3rd box, and it says there's a problem with the EZSetup connection. Tried with box LAN and wireless connection. I figured it wasn't a big deal to use EZSetup since i can set it up manually but with the above problem i described, it worries me :-(

I've used 2 laptops and my PDA to verify. Looks like a hardware problem?

Thanks for any advice in advance.

cheers,
Patrick
Thanks.

@patrick

my settings are:
Authentication Method: wpa-psk
WPA Encryption: TKIP
WEP Encryption: 128bits

and everything works fine. maybe this works also for you.

grat182

Quote:

---

Originally Posted by gratitude182

@patrick

my settings are:
Authentication Method: wpa-psk
WPA Encryption: TKIP
WEP Encryption: 128bits

and everything works fine. maybe this works also for you.

grat182

---

Hi grat182,

Thanks for helping. I tried that and it worked for a while, after that the same problem like I described happen. Really weird huh.

Tried all the permutations (64 bit, AEP/TKIP etc) but no good. I guess if the simplest WEP encryption didn't work than something aint' right :-(

Any thing else I could have missed?

cheers,
Patrick

Quote:

---

Originally Posted by patrickquek

I've used 2 laptops and my PDA to verify. Looks like a hardware problem?

---

Yes, I'd suspect you've got a dud. I'm sure there's HW acceleration for encryption/decryption in the SoC device. This block is probably flakey.

- K.C.

Quote:

---

Originally Posted by kfurge

OK, three problems:

1) Your home directories, with the exception of nora, all point to /dev/null. Make them all point somewhere real, and make sure they're all owned by the appropriate user.

2) Your shells. All accounts have a shell of /bin/false. This is what is normally put in when you absolutely want to deny a login to an account. Put a valid shell here such as /opt/bin/bash.

3) If you don't have a valid /etc/shells or the shells listed within /etc/shells do not include the shells listed in the password files, then you will also be denied a login. You must fix this too. One of the modifications to the custom firmware was a symlink from /etc/shells to /tmp/shells. Symlink from /opt/etc/shells to /tmp/shells within rc.local. Now make sure /opt/bin/bash is listed in /etc/shells.

- K.C.

---

Thank you very much. I have done as you said and now it works.
I did not realise that some of the steps, i.e. file modifications had to be done manually.
I carried out the following steps:

1&2/ The passwd file was edited to give all users a path to their home directory;
(nora:XXXXX:35003:42000:nora:/opt/home/nora:/opt/bin/bash).
The relevant directories were created, (mkdir -p /opt/home/nora) and given ownership by the respective user (chown nora /opt/home/nora)

3/ The path opt/bin/bash was added to shells (echo "opt/bin/bash">> /etc/shells). The symlink was already in rc.local.

There is no way I would of fixed those three snags myself, thank you again.

What I did manage to do was to get putty working with SSH and dropbear.
Was really quite easy compared to the above.

Use Puttygen to create the public and private keys.
Copy the private one to the PC hard drive.
Create a hidden directory SSH in the user folder (mkdir /opt/home/nora/.ssh)
Copy & Past the public key, all of it with no additions, from Puttygen into a new file authorized_keys into this directory (echo ((right click past)) > /opt/home/nora/.ssh/authorized_keys)
And that is it just configure Putty to use the private key you saved on the PC hard drive. At the login prompt enter your user name and it should connect.

I hope this may be of some help to any others with problems connected with SSH on dropbear.

Chris.