On Thursday 14 March 2002 08:00 am, [EMAIL PROTECTED] wrote: > I complied the latest CVS-version on my SuSE-Linux computer (not behind a > firewall) and I noticed (as with older "licq 1.1.0 CVS-Snapshots" too), > that after an unpredictable time no messages - sent over server - won't > arrive any recipient anymore. That appears to everybody, no matter what > icq he has. If I disconnect and than connect to the icq-server again, all > messages will arrive fine for a while... but only for a while. That could > be 10 minutes or an hour. Then I have to disconnect and connect again. If > everybody had icq 2002 or licq 1.1.0 on his client, it would be no > problem, because these clients are able to handle "direct" connections > between firewalls. But to someone who has icq2001 behind a firewall for > example I MUST send indirect over the server (I know the reason is the new > protocol). And it is very nerving to ask peoples always, if he gets my > messages you know?.
I have not had any problems with sending messages through the server at all. Perhaps you can show a packet where it works, and then the next packet where it doesn't work? > Is there anybody with the same problem? - Is it a bug from licq? - Or must > I install ipv6 on my linux computer (i noticed, that licq generates ipv6 > packets)? Generally I think it's not a problem with licq.. rather with AOL > ;) The question is, what can I do against it? licq doesn't generate ipv6 packets at all. It only generates a packet with the aim protocol and lets the kernel put the headers on it. Jon _______________________________________________ Licq-main mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-main
