[EMAIL PROTECTED] said:
} The problem happens when you double-click on the Quake2 entry in the
} left-hand window to "update the servers". The first or second time,
} you will get a good list of servers and decently low ping times. If
} you do this a few more times, all of the sudden, all the ping times
} goto 9999 and from the Linux server's logs, you see:
} Jan 13 00:07:09 trinity2 kernel: ip_masq_new(proto=UDP): no free
} ports.
} The only solution I found to this problem is to reboot. I cannot
} unload the ip_masq_quake module since it is "in use"
I know zilch about quake....
However I guess its making a UDP connection to each server in turn, and
that there are a number of servers - guesstimate of the order of a
thousand plus.
Thats going to open up masq tunnels which with UDP remain until they time
out.
A workround is probably to set the UDP timeout down to something small - a
few seconds ought to be OK I guess for quake, also for DNS.... what other
UDP are people putting through their masq?? The quake module would
possibly be able to diddle with the timeouts as another near solution.
[or if a signoff was sent as part of the protocol it could close the
tunnel down]
Nigel.
--
[ [EMAIL PROTECTED] - Systems Software Engineer ]
[ Tel : +44 113 207 6112 Fax : +44 113 234 6065 ]
[ Real life is but a pale imitation of a Dilbert strip ]
[ We're recruiting http://www.theplanet.net/profile/recruit.htm ]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
For daily digest info, email [EMAIL PROTECTED]
