/* HINT: Search archives @ http://www.indyramp.com/masq/ before posting! */
geoffrey lee <[EMAIL PROTECTED]> wrote:
>
> ICQ connects fine, but after 30 seconds or so, if you need to contact
> the ICQ server (say, update info..) there is no netwrok activity and
> then it just says that you aren't connected
My theory is that the ICQ servers expect to see all of your packets for
one "session" on the same UDP port. Now, the port you're sending on is
certainly fixed, at your client, but the masq server forgets about the
connection if it's idle for 160 seconds (your UDP timeout), and then
when you send your next command packet, a new port number is chosen by
the masq server, and the ICQ server does not like it.
I suggest you raise the UDP timeout higher. I have mine set to 300
(five minutes) and it works well. I typically don't see the timer ever
drop below about three minutes, so I would think your value of 160
should be enough. But you might try raising it a little at a time,
until you find a satisfactory value.
> my icq firewall timeout is 30 seconds (default on icq99b)
I am really beginning to suspect that ICQ's use of keep-alives is not
affected by that timeout value. It seems to be used more to close off
old TCP connections instead, but I could be wrong.
The above is my opinion, based on observations, and should not be taken
as any basis of fact. :)
--
[EMAIL PROTECTED] (Fuzzy Fox) || "Good judgment comes from experience.
sometimes known as David DeSimone || Experience comes from bad judgment."
http://www.dallas.net/~fox/ || -- Life Lessons
_______________________________________________
Masq maillist - [EMAIL PROTECTED]
Admin requests can be handled at http://www.indyramp.com/masq-list/ -- THIS INCLUDES
UNSUBSCRIBING!
or email to [EMAIL PROTECTED]
PLEASE read the HOWTO and search the archives before posting.
You can start your search at http://www.indyramp.com/masq/
Please keep general linux/unix/pc/internet questions off the list.
