which version of icqv7t are you running? also please try running it (icq) with the defaults that seems to work pretty well
Lars Petersen wrote:
>> 20021028T13:19:04: [warn] (io_select): 127.0.0.1(21) is being
>> connection rate limited
>
>What are you doing with the jabberd on port 21? Port 21 is ftp ...
Port 21 is the source port - not the destination port...
I think that I have identified the problem, but I have no idea as to how I am supposed to fix it. The problem is the icq
transport! I start it with this command line:
/usr/local/jabber/icqv7t/icqv7ext -n icqv7ext -s password -h 127.0.0.1 -p 1235 -m sms.example.com &
And if I exchange 127.0.0.1 with my real IP the rate limit errors change too! So that must mean that it is the icq
transport process that is generating all the connections... My question is now how can I fix it? Or just keep the rate limit
errors from appearing - i.e. tell jabber not to calc karma from localhost etc...
Also almost every time I send an ICQ message it looks like so:
20021028T13:45:21: [alert] (icq.example.com): Packet received: <message type='chat' to='[EMAIL PROTECTED]' from='lars
@example.com/Psi'>
<body>hiya</body></message>
20021028T13:45:21: [alert] (ICQv7-t): Session's found
20021028T13:45:21: [alert] (ICQv7-t): retransmitting packet: <message type='chat' to='123@icqv7ext' from='[EMAIL PROTECTED]/Psi'><body>hiya</body></message>
I am guessing that the retransmitting is because the main jabber process is receiving the packet and passing it on to the
icqv7ext process... Am I right?
The only critical thing that I have right now is the strange rate limits from 127.0.0.1 on various ports...
I will **really** appreciate any insights you might have! :)
Regards,
Lars Petersen
_______________________________________________
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev
_______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
