| Author |
Message |
|
| Guest |
 Posted: Wed Jul 26, 2006 1:55 am |
 |
|
|
Guest
|
Here is the problem as far as I understand it. I am aware that jabber is heavily DNS dependant, and that every jabber server has to have exactly one, unique hostname, and it will flatly refuse people who call it by another hostname than the one it considers the true one. For instance I recently became disillusioned with DNS hosting company A, where my host was synx.A, and I decided to try DNS hosting company B, where my host is synx.B. Currently people connect to my jabber server at synx.A, so if I change the internal, unique hostname my jabber server knows into synx.B, all the people connecting via synx.A will suddenly be unconditionally refused, even though I have not discontinued the use of the name synx.A. The DNS translates properly, but then the jabber server refuses them.
My question is this: how can I tweak ejabberd so that it accepts people who call it synx.A and people who call it synx.B? Are my initial assumptions wrong, and it doesn't care whether people connect via synx.A or synx.B, or even @ the raw IP address? If I cannot accept connections both as synx.A and synx.B, do I just have to warn all my users, wait months for all of them (some VERY rare) to connect at least once and receive the broadcast warning, and then switch hoping that they'll manually change their own account information? The latter doesn't seem like a nice situation, and I'd appreciate knowing how to make the hostname an array instead of a scalar, or something to the like, so that the server doesn't refuse synx.A after switching to synx.B.
I only have one computer, so I can't point synx.A to a "spare" jabber server. It's just my little local server that some of my friends use to communicate.
--
Pandora "Starling/Tasci/Antinomy/Figment/???" synx
jabber: http://synx.dyndns.org/jabber.png
_______________________________________________
ejabberd mailing list
ejabberd@jabber.ru
http://lists.jabber.ru/mailman/listinfo/ejabberd
Post recived from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Thu Jul 27, 2006 4:44 am |
|
|
|
Guest
|
On Tue, 25 Jul 2006 18:54:55 -0700
Synx <ejabberd@synx.dyndns.org> wrote:
> Are my initial assumptions wrong, and it doesn't care whether people connect via synx.A or synx.B, or even @ the raw IP address?
My initial assumptions aren't wrong, but I did a little digging and here's what I found:
the host verification checker uses list:memberof to verify the hosts, which means that even though you can't connect as anything besides a proper host, you can set multiple 'proper' hosts. In my case it might look like:
{hosts, ["synx.A","synx.B","localhost"]}.
That would allow my server to act as synx.A, synx.B and localhost. Unfortunately... I don't know which of these hosts it uses for server to server communication. I guess it uses whatever host is the same as the user initiating communication that becomes s2s? Can't tell.
Perhaps more unfortunately, accounts can only have one host. That is, if I make synx13@synx.A, and then add 237 of my dearest friends to the roster, then try to switch to synx13@synx.B, I have to manually, one by one contact each of my friends, and then tell them to use the new account, just as if I switched to someothersynx@synx.A. I see this as a weakness in the XMPP protocol itself though, having no authorized automatic way to transfer rosters between accounts, and I guess ejabberd can't fix what the jabber developers themselves don't see as a solvable problem.
If I break down and hack together some rotten perl script to force erlang and mnesia to cough up and mangle their internal database, facilitating transfer of rosters, I'll be sure to post it as a follow-up to this message.
--
Pandora "Starling/Tasci/Antinomy/Figment/???" synx
jabber: http://synx.us.to/jabber.png
_______________________________________________
ejabberd mailing list
ejabberd@jabber.ru
http://lists.jabber.ru/mailman/listinfo/ejabberd
Post recived from mailinglist |
|
|
| Back to top |
|
| Guest |
| Posted: Thu Jul 27, 2006 2:52 pm |
|
|
|
Guest
|
Hello,
I think you are mixing two different problems:
- Identity of the users: The user are identified by their Jabber ID:
UserID@Jabberdomain. For a user to be the same, it's userId and
Jabberdomain must be the same.
- Getting the ip address of the Jabber server via the DNS.
You can use in your client whatever IP address you want or server
name. The JID you use to connect has to remain constant however.
=> Most clients offer and option to set up the name or IP or the
actual server to connect to.
I hope this helps,
--
Micka |
|
|
| Back to top |
|
|
|
All times are GMT
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum
|
|
|
Digg It
Del.icio.us
Reddit
Facebook
Stumble Upon
Technorati
