I'm having some probles connecting to my machine at home in that if both sides are idle for some short time, the connection was lost. I have done some research and have found: - It does this with every protocol. I opened up telnet to work and the same things happens. In fact, if I use Windows Netscape at work to get my mail via IMAP, if I don't do anything for a while, then try to add/del/move mail, it says server disconnected or something like that. If I try again it usually works. Obviously my web server is unaffected, as http is a connectionless protocol. I am assuming mail connections are happening fast enough that nothing is lost. - The timeout happens at about one minute. So if I am reading my mail and my phone rings, I need to shell out of pine and run "top" so I'll get enough IO so it doesn't time out. - It would be nice to verify the problem is definitely on my end by trying to access it from somewhere else, but this won't be practical for a few days. This sure smells like an ipchains problem. I looked into the timeouts I heard about for ipchains, but those are only for masquerading. But I'm not masquerading ssh, I'm connected to my linux server via it's public name/address connected straight to the cablemodem through eth0 via. Is it still masquerading then? Background: Red Hat 6.1 2.2.12-20 running ipchains, server has two ethernet cards with one going to a cablemodem and another going to a hub with threee or so other computers on it. Thanks in advance, -- ------------------------------------------------------------------- DDDD David Kramer [EMAIL PROTECTED] DK KD http://kramer.ne.mediaone.net DKK D DK KD HYDROGEN: A colorless, odorless gas which, DDDD given enough time, turns into people. - To unsubscribe from this list: send the line "unsubscribe linux-net" in the body of a message to [EMAIL PROTECTED]
