>This is the output from when you logged in using a client
>jabbberd/c2s. See if you can find some from the router:
>jabberd/router.
After setting up a router log in router.xml, I see the following when I
start and stop PyAIMt
Tue Dec 6 18:39:15 2005 [notice] [127.0.0.1, port=36236] connect
Tue Dec 6 18:39:52 2005 [notice] [127.0.0.1, port=36236] disconnect
Tue Dec 6 18:39:57 2005 [notice] [127.0.0.1, port=36237] connect
Tue Dec 6 18:46:48 2005 [notice] [127.0.0.1, port=36237] disconnect
Tue Dec 6 18:48:06 2005 [notice] [127.0.0.1, port=36247] connect
>> I'm a little confused about the aim gateway being resolved. But that
>>could just be my ignorance.
>That was because you logged in, it's trying to look for the aim
>gateway on your server, that's all good.
Should my client be able to talk to the aim gateway directly? Should it be
resolving using the gateway using DNS to the public IP of the server?
>See if you can get a tcpdump of traffic on port 5347 on the localhost
>interface as you start the transport.
Using tcpdump I do see traffic for port 5347 on the lo interface.
Thank you all for the help in figuring this out. I figure once I get the
first transport working the rest of the Py transports should be pretty easy.
