>> >> 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?
>the client won't connect directly to the gateway, no.
>The connection will be: client -> c2s -> router -> pyaimt.
After a few more tests, here is what I found by running jabber in debug
router.c:246 dropping unknown or invalid packet for s2s component proper
I'm also still curious about the DNS lookup for the transport jid when a
client attempts to register with the service.
If I use a jid to a fqdn that is defined in DNS to the public IP of the box
the resolution works great. If I use a jid that is a fqdn that is not
defined in DNS the lookup fails.
When I start PyAIMt I'm assuming I should see the transport authenticate
with the router right???
