New 1.0.4.6 based custom firmware

[kfurge]

Postscipt: I worked it out. All I needed to do was be patient. I entered "ssh 192.168.1.1" and pressed return, then I just waited. After a few minutes, eventually I got a prompt.

You shouldn't have to be too patient. My connect times are within a second or two unless the HDD's have to spin up. It's been my experience that long connect times are generally the result of an incorrect DNS configuration. You might want to double check your DNS settings.

- K.C.

[hal2k1]

In particular, "sudo bash" will get you a full root shell.

- K.C.

I tried "sudo bash" and also "sudo -s".

Both said "<user> is not in the sudoers file". Then it told me off.

[hal2k1]

You shouldn't have to be too patient. My connect times are within a second or two unless the HDD's have to spin up. It's been my experience that long connect times are generally the result of an incorrect DNS configuration. You might want to double check your DNS settings.

- K.C.

DNS settings of what? My client machine, or the router itself?

[hal2k1]

It's been my experience that long connect times are generally the result of an incorrect DNS configuration. You might want to double check your DNS settings.

- K.C.

Confusion reigns on this. My DNS values could well be awry.

If I type "ssh 192.168.1.1", why is a DNS lookup involved anyway?

PS: I found this page:
http://www.nslu2-linux.org/wiki/HowT...orRemoteAccess

and I see the following comment:

If you've problem logging into your slug with dropbear, 
i.e. if you wait the login prompt for ages, it may be a problem 
related to the random number generator. Try this quick and dirty trick:

cd /dev
mv random random.orig
cp urandom random

Does anyone think this will help? After I start the ssh command, it takes about 20 seconds for the prompt from the WL700ge to appear for the password.

[kfurge]

I tried "sudo bash" and also "sudo -s".

Both said "<user> is not in the sudoers file". Then it told me off.

You need to edit /opt/etc/sudoers as root to tell sudo what you can and cannot run. The easiest way is to simply add a new entry with your username that's otherwise exactly the same as root's like this:

# User privilege specification
root ALL=(ALL) ALL
you ALL=(ALL) ALL

- K.C.

[kfurge]

Does anyone think this will help? After I start the ssh command, it takes about 20 seconds for the prompt from the WL700ge to appear for the password.

No. We can't do this. Details are on my web page (search for devfs).

The only time dropbear cranks on the random number generator is when it needs to initially generate keys during the first connection with an unknown host. After that, the keys are simply confirmed.

Regarding DNS, servers generally do a reverse DNS lookup to put a sane name into the system log.

- K.C.

[kfurge]

DNS settings of what? My client machine, or the router itself?

The router.

- K.C.

[jeromv]

Hello Kfurge

First thanks a lot for all your contribution with your custom firmware.

I want to instal it but i faced two problems...

• On the one hand i'm not good enough in computer sience to do all the instructions step by step.

• On the other hand i'm french and i don't understand all the instructions.

I think we are a lot in the same case.
So to make all your work and contribution within the reach of everyone, can you (or another member that installed it) make an english tutorial with screenshots of every step ?
I offer to traduce it in french and german... and after we can post it here and in the WL-700g Tutorials section.

Hope someone will be interested....

Regards

Jerome

[hal2k1]

You shouldn't have to be too patient. My connect times are within a second or two unless the HDD's have to spin up. It's been my experience that long connect times are generally the result of an incorrect DNS configuration. You might want to double check your DNS settings.

- K.C.

OK, I fixed that. It was the DNS settings. All sweet now.

You need to edit /opt/etc/sudoers as root to tell sudo what you can and cannot run. The easiest way is to simply add a new entry with your username that's otherwise exactly the same as root's like this:

# User privilege specification
root ALL=(ALL) ALL
you ALL=(ALL) ALL

- K.C.

Fixed that too. Everything working, so I disabled the telnet in rc.local.

I tried the enhanced-ctorrent, in conjunction with screen. Worked like a charm ... I downloaded all of the 3.6 GB of the OpenSuSe 10.2 DVD iso file. No 2GB limit in sight, and no stopping mid-torrent. Also sweet.

So the only thing left now, really, is that I'd like to run rtorrent instead!

[IMM22]

OK, I fixed that. It was the DNS settings. All sweet now.




Fixed that too. Everything working, so I disabled the telnet in rc.local.

I tried the enhanced-ctorrent, in conjunction with screen. Worked like a charm ... I downloaded all of the 3.6 GB of the OpenSuSe 10.2 DVD iso file. No 2GB limit in sight, and no stopping mid-torrent. Also sweet.

So the only thing left now, really, is that I'd like to run rtorrent instead!

That's fine !!

But what is the propose of the screen?


It is possible to link enhanced-ctorrentwith the ASUS web interface, and maybe add some other configurations avaible in enhanced-ctorrent

Thanks

[MoD]

That's fine !!

It is possible to link enhanced-ctorrentwith the ASUS web interface, and maybe add some other configurations avaible in enhanced-ctorrent

Thanks

source code of webhooks is not included. you'll have to create your own

[n00ben]

source code of webhooks is not included. you'll have to create your own

is it possible to use the package 'ctcs'?

Description: CTorrent Control Server (CTCS) is an interface for monitoring and managing Enhanced CTorrent clients

sounds good but it is dependent on 'perl' and perl is apparently not an available package.

/regards
Henrik

[gratitude182]

@hal2k1

could you tell me, how do get c-torrent to work? i would like to try this....

thanks

gratitude182

[d3viant]

hmm, this firmware is working fairly well for me - the one thing I am trying to get working now is the nameserver on the router. ipkg provides the bind package for this purpose, but the install fails with

Installing bind (9.3.2-1) to root...
Downloading http://ipkg.nslu2-linux.org/feeds/op...2-1_mipsel.ipk
Configuring bind
/bin/ash: error while loading shared libraries: /bin/ash: symbol vprintf, version GLIBC_2.0 not defined in file libc.so.6 with link time reference
postinst script returned status 127
ERROR: bind.postinst returned 127

Is there any chance that this can be fixed? It looks like some undefined library issue, which I would have though would be handled via the ipkg dependency checker... but obviously not!

[kfurge]

So the only thing left now, really, is that I'd like to run rtorrent instead!

I compiled rtorrent (on the router actually!) and it seems to work OK. If someone is willing to work with me to test out the dependent libraries, I think I could fairly easily turn it into a hand-built ipkg. I believe all of the required libs are already built and ready.

I'm not a big torrent guy, but the combination of screen+rtorrent seems like it would be very good.

- K.C.