Koozali.org: home of the SME Server

Idle timeout for disconnect and an error message

Steve Hiner

Idle timeout for disconnect and an error message
« on: September 15, 1999, 12:30:06 PM »
I was wondering where I change the timeout for disconnecting from my dial-up connection.  When I access a web page the server dials out as expected but it hangs up the connection after 30 seconds or so.  I usually don't even have time to move on to another page before it disconnects me (I am currently writting this in my browser off-line because it disconnect right after loading this page).  I don't see that timeout listed in the manager settings - I assume it is in a script or a .conf file somewhere but I don't know where.

Also, every once in a while after the server connects to my ISP I will get the following error on the console:
tcp_v4_rebuild_header(): not valid sock addrs: saddr=00000000 rcv_saddr=00000000

Any ideas?

By the way, I have solved my earlier problems - they were a combination of pilot error and Microsoft networking being finiky.

Steve Hiner

Kim Morrison

RE: Idle timeout for disconnect and an error messa
« Reply #1 on: September 15, 1999, 06:13:24 PM »
Dear Steve

Yes, we're working to improve the timeout rules in the diald configuration and we'll also be providing more user control over those rules in the next version of our software.  

The error message is something we've seen too. We haven't studied in depth yet but preliminary tests show that it seems to be harmless.  We're quite certain that the error message is unrelated to the diald timeout issue.

Regards,

Kim

Steve Hiner

RE: Idle timeout for disconnect and an error messa
« Reply #2 on: September 15, 1999, 09:06:08 PM »
Kim,

I didn't mean to imply that the two issues were related.  I guess I should have posted two different messages (that would have been more "thread safe" at least).

I too had notice that the tcp error was harmless, I just wanted you to know about it.

Steve

Roger Wrethman

RE: Idle timeout for disconnect and an error messa
« Reply #3 on: September 19, 1999, 10:15:02 PM »
I saw this message when I tried to launch fetchmail at the command prompt, but it only showed this once, seems to me like fetchmail tried to start before the link was up.