Code Forums - View Single Post

ender · 01-16-2005, 05:13 PM

It may be just me, but I don't think the router is the issue here. 'Timeouts,' or at least the ones you are describing have nothing to do with the router. To the router, you are connected, and it will keep you connected for as long as it can. The remote server may have a timeout for idle activity, which would be the issue. That can't be fixed by a router setting. Unless I'm just totally off base here, which may be the case. Anyway, the way to fix this is to get a good MUD client that supports 'pinging' .. well.. something like that anyway, just to keep the connection going, sending a packet every once in a while. Even just sending the 'look' command every 5 minutes would do the trick.

Again, just tell me if I'm completely nuts. Yes, my spelling is horrible.

01-16-2005, 05:13 PM	#11 (permalink)
ender Code Monkey Join Date: Mar 2003 Location: Evansville, IN Posts: 75	It may be just me, but I don't think the router is the issue here. 'Timeouts,' or at least the ones you are describing have nothing to do with the router. To the router, you are connected, and it will keep you connected for as long as it can. The remote server may have a timeout for idle activity, which would be the issue. That can't be fixed by a router setting. Unless I'm just totally off base here, which may be the case. Anyway, the way to fix this is to get a good MUD client that supports 'pinging' .. well.. something like that anyway, just to keep the connection going, sending a packet every once in a while. Even just sending the 'look' command every 5 minutes would do the trick. Again, just tell me if I'm completely nuts. Yes, my spelling is horrible. __________________ while(1) fork();