This seems to solve my problem. Many thanks, Ben
On Sat, Aug 9, 2008 at 6:53 PM, Don Dailey <[EMAIL PROTECTED]> wrote: > On Sat, 2008-08-09 at 17:43 +0100, Matthew Woodcraft wrote: > > Don Dailey wrote: > > > I am looking at this page: > > > > > > http://cryp.to/publications/masquerading-idle-connections/ > > > > > > and wondering if it's relevant. It seems to describe the problem > > > pretty well, talks about a 15 minute timeout which would do it and the > > > timeout is built into the linux kernel but can be changed. > > > > > > I'm really very weak on networking so I'm not sure what I'm actually > > > reading or whether this fix needs to be applied on the server end or > the > > > client end. Any ideas is this is relevant? > > > > That page is talking about long-obsolete software, but yes, it seems very > > likely that this is the basic issue. > > > > Most home 'internet routers' and many firewalls do network address > > translation, and will fail to maintain a connection after some amount of > idle > > time. > > > > Trying to reconfigure the firewalls to have a longer timeout is probably > a > > waste of effort. I think arranging for either the CGOS server or the > client to > > send some boring message every few minutes will be the most practical > > solution. > > CGOS has an info message that can be sent to the clients. It is > designed to send messages which can be basically ignored, or to support > future monitoring features, perhaps announcing match-ups of the current > round, etc, or broadcasting messages that the system will be going > down. A future graphical client might perhaps display whatever > messages are sent in a message box or something. > > I used to broadcast an estimate of the time remaining until the next > round. I took it out, now I am putting it back in to see what happens. > It will serve as a type of keepalive signal perhaps. The estimate > isn't very accurate because it's based on the assumption that everyone > left will use all their time remaining which rarely happens. > > If there is some kind of inactivity timeout, hopefully it will not > require the client to also send messages. > > - Don > > > > > > > > > > > > -M- > > _______________________________________________ > > computer-go mailing list > > computer-go@computer-go.org > > http://www.computer-go.org/mailman/listinfo/computer-go/ > > _______________________________________________ > computer-go mailing list > computer-go@computer-go.org > http://www.computer-go.org/mailman/listinfo/computer-go/ >
_______________________________________________ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
