New 1.0.4.6 based custom firmware

[kfurge]

...
export PATH=/opt/bin:${PATH} export LD_LIBRARY_PATH=/opt/lib:${LD_LIBRARY_PATH}
...
mount -o bind /shares/${pool}/opt /optcat /proc/mounts > /opt/etc/fstab

If these two lines are indeed concatinated as shown, things won't work very well. Break them apart at the appropriate spots. The mount must work to get a functional /opt.

Also, you're multiply exporting PATH and LD_LIBRARY_PATH in both scripts. No harm, I think, but you only need to do it once.

Otherwise, things looked OK.

- K.C.

[Gregoire.Favre]

Hello,

thank to the new firmware I have flashed my router and now I have :

telnet 192.168.1.1
Trying 192.168.1.1...
Connected to 192.168.1.1.
Escape character is '^]'.
(none) login: admin
Password:
Login incorrect

I have tried to change the password/login in the web interface but all attempts fails.

Any idea ?

[IMM22]

Hello,

thank to the new firmware I have flashed my router and now I have :

telnet 192.168.1.1
Trying 192.168.1.1...
Connected to 192.168.1.1.
Escape character is '^]'.
(none) login: admin
Password:
Login incorrect

I have tried to change the password/login in the web interface but all attempts fails.

Any idea ?

The login is: root

[Gregoire.Favre]

Great : it works now !!!

Thank you very much (that could be written somewhere...)

[IMM22]

If these two lines are indeed concatinated as shown, things won't work very well. Break them apart at the appropriate spots. The mount must work to get a functional /opt.

Also, you're multiply exporting PATH and LD_LIBRARY_PATH in both scripts. No harm, I think, but you only need to do it once.

Otherwise, things looked OK.

- K.C.

ummhh. the line are break apart, that's correct. But I don't manage to put it to work ? Do you have some kind of script allredy made for that, thanks.

All other stuff, well ***** (5 stars)

[kfurge]

ummhh. the line are break apart, that's correct. But I don't manage to put it to work ? Do you have some kind of script allredy made for that, thanks.

All other stuff, well ***** (5 stars)

The .profile and last rc.local script I posted on the web page are exact copies of what's currently running on my router. Try using the .profile as-is along with the second rc.local script. If that runs OK, then proceed to modify as necessary.

If that doesn't work, please post your /etc/passwd file (with passwords removed, of course) and the output from the "set" and "mount" commands from a login shell.

- K.C.

[kfurge]

Thank you very much (that could be written somewhere...)

It was... In the installing section step 3.1...

However, it's a fine point and easily missed. My incredibly bland web page certainly doesn't help it stand out. ;-)

- K.C.

[LeperKing]

Point 3.2 part 3
mount -o bind /shares/MYVOLUME1/opt /opt (didn't work)
mount -o bind /shares/MYVOLUME1/opt/ opt/ (did work)

I don't think there is any difference....

LK

P.S. Sorry KC I'm probably splitting hairs

[sollie]

Question: do i loose my hd content, when i do and firmware upgrade.

Sollie.

[kfurge]

Question: do i loose my hd content, when i do and firmware upgrade.

Sollie.

Not from anything I did.

However, during my experimentation, I found out the asus firmware rewrites the content of /shares/MYVOLUME1/MYSHARE1/web every time the router starts up.

- K.C.

[kfurge]

Point 3.2 part 3
mount -o bind /shares/MYVOLUME1/opt /opt (didn't work)
mount -o bind /shares/MYVOLUME1/opt/ opt/ (did work)

I don't think there is any difference....

I tried it both ways on my Ubuntu linux system just now and they both worked. I assume it would be the same for the router.

I'd not recommend the second way without at least a "cd /" before the mount command since the mount point is relative.

Is it possible that /shares/MYVOLUME1/opt existed at boot-up and /opt was automatically mounted by the rc.local script before you manually attempted to run the command?

- K.C.

[PsycoMantis]

Step 3.2

Is it meant to be shares/MYVOLUME1/MYSHARE1/opt ?

Thanks,
LK.

But then there is also a "bug" in the rc.local....

The entry

"mount -o bind /shares/${pool}/opt /opt"

which is

mount -o bind /shares/MYVOLUME/opt /opt

should then also be changed to:

mount -o bind /shares/${pool}/${share}/opt /opt

or not ?

- PM

[kfurge]

But then there is also a "bug" in the rc.local....

The entry

"mount -o bind /shares/${pool}/opt /opt"

which is

mount -o bind /shares/MYVOLUME/opt /opt

should then also be changed to:

mount -o bind /shares/${pool}/${share}/opt /opt

or not ?

- PM

The rc.local file as posted is correct.

I had mistakely put /shares/MYSHARE1 instead of /shares/MYVOLUME1 at the location referred to by the message.

Since I've updated the web page, the post, and subequent reply, no longer have the correct context.

Putting opt within reach of the file sharing utilities at /shares/MYVOLUME1/MYSHARE1 could be very convenient, but also potentially insecure. I chose /shares/MYVOLUME1 because none of the canned Asus utilities can reach it.

- K.C.

[hmantsao]

Could someone have the same problem which can't kill httpd as me ?

The process of my route don't have thttpd process but those have two httpd process, and this process start by themself after i use "killall" command. It seem this process provide kernel level. Do i right? and how can i stop it?

===after i use killall the screen as below==
587 admin 304 S /opt/sbin/dropbear
907 admin 1388 S httpd 80 y
1033 herman 2776 S < /usr/local/samba/sbin/smbd
========cut. =================

[kfurge]

The process of my route don't have thttpd process but those have two httpd process, and this process start by themself after i use "killall" command. It seem this process provide kernel level. Do i right? and how can i stop it?

As you noted, there are two http servers running on the router. The first one, httpd, is the one that serves up the routers web configuration pages on port 80. I see no reason why you would want to kill this one.

The second one, thttpd, is used to serve up your custom web content on port 8080. Incoming requests to port 80 on the WAN interface are redirected to the internal port 8080. You can easily kill and restart thttpd as demonstrated in this script:

http://home.comcast.net/~kfurge/rc.local_3

The "watchdog" process is very likely what's restarting the web servers after you kill them because it regularly pings them to see if they're still alive. I recommend a "killall -9" of the watchdog process. My router got substantially more stable after killing watchdog.

After reviewing the watchdog the source code provided in the 1.0.4.2 release it's easy to understand why... That watchdog code is not good at all.

- K.C.