Re: works from SSH tunnel but not from remote
Am Donnerstag, 19. Juli 2012, 19:56:23 schrieb Julius Schwartzenberg: This looks quite old fashioned to me ;) LOL nice! I would expect ::1 and :: instead there. Maybe your client is indeed trying to use IPv6? My ISP is still unable to provide IPv6 :( But no, it is the gSASL bug.
ejabberd migration
Hi, I have migrated one (hura! :) ) user from ejabberd to jabberd2 with mysql backend. I have written a small PHP script which parses some information out of an ejabberd dump (ejabberdctl dump foo). It is not complete. The most ugly point is that this script does not recover the user passwords. But it's a start. It prints some INSERT statements. Please have a look at the XXX's before using. cheers Danielattachment: migrate.php
Re: works from SSH tunnel but not from remote
Hi again, I tried at home from my router with mcabber. Everything worked fine. Then I tried from my working machine (which is behind the router) and... guess... it worked, too ;) Erm, Kopete? What are you doing? thanks for your attention Daniel Am Montag, 16. Juli 2012, 23:51:25 schrieb magic-jabbe...@damage.devloop.de: If I create a tunnel on port 5222 (ssh -L 5222:localhost:5222 devloop.de) and if I set my jabber client to connect to localhost:5222 everything is working fine. Login works, presence message are comming in. This is the log: -- Jul 16 23:26:32 devloop jabberd/c2s[4445]: [8] [127.0.0.1, port=49636] connect Jul 16 23:26:32 devloop jabberd/c2s[4445]: [8] legacy authentication succeeded: host=devloop.de, username=damage, resource=Kopete Jul 16 23:26:32 devloop jabberd/c2s[4445]: [8] requesting session: jid=dam...@devloop.de/Kopete Jul 16 23:26:32 devloop jabberd/sm[4422]: session started: jid=dam...@devloop.de/Kopete -- But if I try to use the normal remote way and try to connect directly to devloop.de:5222 my client is hanging during login. And the log is just: -- Jul 16 23:27:28 devloop jabberd/c2s[4445]: [8] [91.37.187.80, port=33738] connect --
Re: works from SSH tunnel but not from remote
Sorry, once again it's me. I noticed that kopete is working if I explicitly set the connection server (in my case devloop.de). Setting the connection server results on major XML changes. Please note that 'verison=1.0' in the first stream tag of the XML. I don't know much about the XMPP protocol. May someone is able to give me a tip about what is going wrong? Is that a jabberd2 or a kopete problem? thanks Daniel --- without connection server set (not working) --- ?xml version=1.0? stream:stream xmlns:stream=http://etherx.jabber.org/streams; version=1.0 xmlns=jabber:client to=devloop.de ?xml version='1.0'?stream:stream xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client' from='devloop.de' version='1.0' id='13ipsmggju6kqcb82rqdmqfny42xtfuujdjbz0sj' stream:features mechanisms xmlns=urn:ietf:params:xml:ns:xmpp-sasl mechanismPLAIN/mechanism mechanismDIGEST-MD5/mechanism /mechanisms auth xmlns=http://jabber.org/features/iq-auth/ register xmlns=http://jabber.org/features/iq-register/ /stream:features auth xmlns=urn:ietf:params:xml:ns:xmpp-sasl mechanism=DIGEST-MD5/ challenge xmlns=urn:ietf:params:xml:ns:xmpp- saslcmVhbG09ImRldmxvb3AuZGUiLCBub25jZT0icEFWL3hRZUg5KzUvNEVVX2t0b3dhZz09IiwgcW9wPSJhdXRoIiwgY2hhcnNldD11dGYtOCwgYWxnb3JpdGhtPW1kNS1zZXNz/challenge response xmlns=urn:ietf:params:xml:ns:xmpp- sasldXNlcm5hbWU9ImRhbWFnZSIscmVhbG09ImRldmxvb3AuZGUiLG5vbmNlPSWwQVYveFFlSDkrNS80RVVLa3Rvd2FnPT0iLGNub25jZT0ieEFweU1Hb2ZZRlROR0xKUnRhTHlIekQ0NlJYOHZzeDg4T2JobmF4WTMzRT0iLG5jPTAwMDAwMDAxLGRpZ2VzdC11cmk9InhtcHAvZGV2bG9vcC5kZSIscW9wPWF1dGgscmVzcG9uc2U9OWU0NjY0MjQ3MDEzMzYzNDI2Mjg2NGRiNDFlYzAxOWYsY2hhcnNldD11dGYtOA==/response success xmlns=urn:ietf:params:xml:ns:xmpp-sasl/ ?xml version=1.0? stream:stream xmlns:stream=http://etherx.jabber.org/streams; version=1.0 xmlns=jabber:client to=devloop.de --- --- with connection server set (working) --- ?xml version=1.0? stream:stream xmlns:stream=http://etherx.jabber.org/streams; xmlns=jabber:client to=devloop.de ?xml version='1.0'?stream:stream xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client' from='devloop.de' id='x64pfgs4l4jlb4m6h2lj9t22cfgq9xw641wjhpn2' iq type=get to=devloop.de id=auth_1 query xmlns=jabber:iq:auth usernamedamage/username /query /iq iq type=result id=auth_1 query xmlns=jabber:iq:auth usernamedamage/username resource/ password/ digest/ /query /iq iq type=set to=devloop.de id=auth_2 query xmlns=jabber:iq:auth usernamedamage/username digest[Filtered]/digest resourceKopete/resource /query /iq [rosters etc.] --- Am Dienstag, 17. Juli 2012, 22:34:36 schrieb magic-jabbe...@damage.devloop.de: Hi again, I tried at home from my router with mcabber. Everything worked fine. Then I tried from my working machine (which is behind the router) and... guess... it worked, too ;) Erm, Kopete? What are you doing? thanks for your attention Daniel Am Montag, 16. Juli 2012, 23:51:25 schrieb magic-jabbe...@damage.devloop.de: If I create a tunnel on port 5222 (ssh -L 5222:localhost:5222 devloop.de) and if I set my jabber client to connect to localhost:5222 everything is working fine. Login works, presence message are comming in. This is the log: -- Jul 16 23:26:32 devloop jabberd/c2s[4445]: [8] [127.0.0.1, port=49636] connect Jul 16 23:26:32 devloop jabberd/c2s[4445]: [8] legacy authentication succeeded: host=devloop.de, username=damage, resource=Kopete Jul 16 23:26:32 devloop jabberd/c2s[4445]: [8] requesting session: jid=dam...@devloop.de/Kopete Jul 16 23:26:32 devloop jabberd/sm[4422]: session started: jid=dam...@devloop.de/Kopete -- But if I try to use the normal remote way and try to connect directly to devloop.de:5222 my client is hanging during login. And the log is just: -- Jul 16 23:27:28 devloop jabberd/c2s[4445]: [8] [91.37.187.80, port=33738] connect --
works from SSH tunnel but not from remote
Hi, I am going crazy with that: If I create a tunnel on port 5222 (ssh -L 5222:localhost:5222 devloop.de) and if I set my jabber client to connect to localhost:5222 everything is working fine. Login works, presence message are comming in. This is the log: -- Jul 16 23:26:32 devloop jabberd/c2s[4445]: [8] [127.0.0.1, port=49636] connect Jul 16 23:26:32 devloop jabberd/c2s[4445]: [8] legacy authentication succeeded: host=devloop.de, username=damage, resource=Kopete Jul 16 23:26:32 devloop jabberd/c2s[4445]: [8] requesting session: jid=dam...@devloop.de/Kopete Jul 16 23:26:32 devloop jabberd/sm[4422]: session started: jid=dam...@devloop.de/Kopete -- But if I try to use the normal remote way and try to connect directly to devloop.de:5222 my client is hanging during login. And the log is just: -- Jul 16 23:27:28 devloop jabberd/c2s[4445]: [8] [91.37.187.80, port=33738] connect -- I don't think it is a firewall problem as packets are received by c2s daemon. Just one thing I determined: -- devloop ~ # ping devloop.de PING devloop.de (127.0.0.1) 56(84) bytes of data. 64 bytes from devloop.de (127.0.0.1): icmp_req=1 ttl=64 time=0.019 ms -- My server resolves itself as 127.0.0.1 through /etc/hosts file. But I don't think it's a problem because I already tried without that. Any ideas what's going on there? I can provide XMLs if needed but I really hope it's a kind of 'RTFM problem'... Some infos about my installation: - version 2.2.4 - mysql storage backend - sm and router are bound to 127.0.0.1 - c2s and s2s are bound to 0.0.0.0 - sm has auto-create user enabled thanks in advance Daniel PS: My client is able to connect to another jabber server.
MySQL Script
Hi, I decided to switch to jabberd2. Erlang and lua are not my favorite languages ;) I think C is the best on Linux machines. However, I have seen the MySQL script provided by jabberd2 which you can use to create the database used by jabberd2. I noticed alle the TEXT and TINYTEXT fields in it. Also there are no table references set (which is not possible because of the TEXT fields). Is there a reason for that? Can I just change the field types? regards Daniel
