[clug-talk] COsmoPOD-like Recommendations?
sgrover at open2space.com
Thu Jun 22 16:05:41 PDT 2006
> On Thursday 22 June 2006 11:47, Gustin Johnson wrote:
>> You can also port foward several ports from your firewall your home linu
>> box (eg botg22 & 9922 fowarded to your linux box. sshd should be able to
>> listen on more than one port at the same time.
> That's an option I should look at for web. My Citadel installation is on port
> 2000. If I could forward a jonwatson.ca/url to port 2000, that would solve
> half my problem.
> SSH is a problem because our firewall at work pretty much only has 21 and 80
> open...I guess I could put it on 21 but then I lose my FTP.
I don't know the details of how/why you are using FTP, but SSH has a
nice feature called SFTP (built in to ssh). Most of today's ftp clients
that I know of can also access SFTP. This would do two things for you
- it removes the conflict on port 21 (ftp or ssh), and removes a service
from the box, meaning it has less work to do, so should run a little
better. In addition, it ups you security some.
If that's not an option, then you *could* do some creative IP
forwarding. Something along the lines of "if traffic arrives on port 21
from your work's IP address, then forward that to port 22 for ssh
access, otherwise assume it is plain ol' ftp".
As for leaving your laptop on during the day, well you need SOME box on
during the day anyways, and I'd rather leave a laptop running than a
desktop just for the power consumption...
As for Kmail crashing on you all the time, that's an application
specific issue and should be thought of independently of your
connectivity issues. But, I recently did run into a problem that caused
Kmail to crash on start for me. The problem was that I had used another
IMAP client and removed some emails from the IMAP folder Kmail was last
viewing. So when Kmail would start, it would try to load that folder,
and it just so happened that the last viewed email had been removed,
causing kmail to crash. I got around this by being very very quick with
the mouse and selecting another folder before kmail tried to process the
current one (I got lucky). Your problems sound somewhat similar... I'm
not sure if this is simply a configuration problem, or if it's a bug
that should be reported...
More information about the clug-talk