Quote:
Originally Posted by MrCode
I will say that I have tried other types of encryption before, most notably WEP, and that seems to allow me to connect, but then the other computer that needs to connect wirelessly (a Windows laptop) can't seem to manage a stable connection. I don't think disabling encryption is an option either, simply because we'd like to keep the router secure (not my decision).
|
Understood. I was suggesting it simply as a diagnostic tool to make sure everything other than encryption was working. Then I realized that changing that setting would likely involve a reboot of the router. Given that a reboot seems to solve your problems anyway, it would not be much use as a diagnostic. :-/
BTW, I don't know if you are already aware of this, but WEP has been known to be broken for a long time. Just recently somebody announced they can crack WPA in under a minute. (I don't know if the talk where this was to be demonstrated has happened yet or not.) So for "consumer grade" solutions, if you want your wireless to be secure, you need to use WPA2.
Quote:
..Just as a short note, does anyone have any good suggestions for Linux-based disk image backup software? Preferrably freeware, if possible. Doesn't necessarily have to be FLOSS. I've determined that my WD hard disk (the one with Ubuntu on it) is failing, and I can't seem to get rsync to work on /. I'll open a separate thread on this issue if need be.
|
I've used
partimage. A number of different live CDs contain it, including
SystemRescueCd. It's main drawback is that if you want to send the data over a network, you must run
partimaged on the remote computer. That too can be found on live CDs. (Knoppix used t o have both -- probably still does.) Unless you really need it, I would suggest you not use the compression since that is likely to slow things down. Something you
dont need if the disk is failing.
If you just want to make a bit-for-bit copy of the disk (or a partition) and don't want to do anything fancy,
dd will do the job. Since you are likely to be hitting bad blocks,
dd_rescue might be more appropriate. It has a front end called
dd_rhelp which is supposed to help more. (Disclaimer: I have not used
dd_rhelp and have minimal experience with
dd_rescue.) The output of
dd (and I would guess the others) can be piped into
ssh for easy transportation across a network. With a little more work but less overhead you can also do it with
netcat running on each end.
Make sure you have everything lined up before you start so you don't excercise the disk unnecessarily. And
definitely make sure you do any prior downloading and research from another machine!
BTW, just see what happened, I started up rsync to copy from / with the -a option. . As soon as I saw it was copying (verified on the other end) I stopped it. You probably want to exclude /proc and /sys. But you also don't want to waste time with a failing disk trying to get something to work. It is also possible it was having trouble due to bad sectors.
Good luck.
(If you need more info, you probably should start a new thread.)