Wireless router...?

Originally Posted by The_Griffin

And that router looks good, but I'm rather wary of Linksys routers since my current piece of crap is a Linksys WRV54G, and it's been nothing but a pain since I got it. At first it wouldn't even interact with the modem, and then once it did the thing started dropping the network.

If you're running p2p software such as bittorent on your current router, then maybe you're just generating too many connections. Some routers have a pretty conservative limit on these things. You can fix that using a telnet script.

I had no end of troubles with my router until I figured that trick out.

Jam it back in, in the dark.

192.168.0.1 23
WAIT "login:"
SEND "root\m"
WAIT "Password:"
SEND "admin\m"
WAIT "#"
SEND "cd /proc/sys/net/ipv4/netfilter\m"
WAIT "#"
SEND "echo 2048 > ip_conntrack_max\m"
WAIT "#"
SEND "echo 50 > ip_conntrack_generic_timeout\m"
WAIT "#"
SEND "echo 5 > ip_conntrack_tcp_timeout_close\m"
WAIT "#"
SEND "echo 120 > ip_conntrack_tcp_timeout_close_wait\m"
WAIT "#"
SEND "echo 1200 > ip_conntrack_tcp_timeout_established\m"
WAIT "#"
SEND "echo 120 > ip_conntrack_tcp_timeout_fin_wait\m"
WAIT "#"
SEND "echo 60 > ip_conntrack_tcp_timeout_time_wait\m"
WAIT "#"
SEND "echo 10 > ip_conntrack_udp_timeout\m"
WAIT "#"
SEND "cd /\m"
WAIT "#"
SEND "exit\m"

That script worked for me. Naturally you will need to put in your own router's IP, as well as the proper login details, but since I've run that script... it hasn't dropped the connection again. Mind you, this router is a POS. Just much less so with some tweaking.

There's nowhere I can't reach.