Re: works from SSH tunnel but not from remote
i want to unsubscribe. On Tue, Jul 17, 2012 at 6:48 PM, wrote: > Hey guys, > good news: I will go to bed, now. So no further mails for _today_ ;) > > http://www.mail-archive.com/jabberd2@lists.xiaoka.com/msg01710.html > > I guess this is my problem, isn't it? And kopete is falling back to > none-sasl > authentication if you manually provide a connection server, right? > > cheers > Daniel > > Am Dienstag, 17. Juli 2012, 23:12:35 schrieb > magic-jabbe...@damage.devloop.de: > > 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) > > --- > > > > > > http://etherx.jabber.org/streams"; > version="1.0" > > xmlns="jabber:client" to="devloop.de"> > > > > > xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client' > > from='devloop.de' version='1.0' > > id='13ipsmggju6kqcb82rqdmqfny42xtfuujdjbz0sj'> > > > > > > > > PLAIN > > DIGEST-MD5 > > > > http://jabber.org/features/iq-auth"/> > > http://jabber.org/features/iq-register"/> > > > > > > > > > > cmVhbG09ImRldmxvb3AuZGUiLCBub25jZT0icEFWL3hRZUg5KzUvNEVVX2t0b3dhZz09Ii > > > wgcW9wPSJhdXRoIiwgY2hhcnNldD11dGYtOCwgYWxnb3JpdGhtPW1kNS1zZXNz > > > > dXNlcm5hbWU9ImRhbWFnZSIscmVhbG09ImRldmxvb3AuZGUiLG5vbmNlPSWwQVYveFFlSD > > > krNS80RVVLa3Rvd2FnPT0iLGNub25jZT0ieEFweU1Hb2ZZRlROR0xKUnRhTHlIekQ0NlJYOHZzeD > > > g4T2JobmF4WTMzRT0iLG5jPTAwMDAwMDAxLGRpZ2VzdC11cmk9InhtcHAvZGV2bG9vcC5kZSIscW > > > 9wPWF1dGgscmVzcG9uc2U9OWU0NjY0MjQ3MDEzMzYzNDI2Mjg2NGRiNDFlYzAxOWYsY2hhcnNldD > > 11dGYtOA== > > > > > > > > > > > > http://etherx.jabber.org/streams"; > version="1.0" > > xmlns="jabber:client" to="devloop.de"> > > --- > > > > --- > > with connection server set (working) > > --- > > > > > > http://etherx.jabber.org/streams"; > > xmlns="jabber:client" to="devloop.de"> > > > > > xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client' > > from='devloop.de' id='x64pfgs4l4jlb4m6h2lj9t22cfgq9xw641wjhpn2'> > > > > > > > > damage > > > > > > > > > > > > damage > > > > > > > > > > > > > > > > > > damage > > [Filtered] > > Kopete > > > > > > > > [rosters etc.] > > --- > > >
Re: works from SSH tunnel but not from remote
Hey guys, good news: I will go to bed, now. So no further mails for _today_ ;) http://www.mail-archive.com/jabberd2@lists.xiaoka.com/msg01710.html I guess this is my problem, isn't it? And kopete is falling back to none-sasl authentication if you manually provide a connection server, right? cheers Daniel Am Dienstag, 17. Juli 2012, 23:12:35 schrieb magic-jabbe...@damage.devloop.de: > 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) > --- > > > http://etherx.jabber.org/streams"; version="1.0" > xmlns="jabber:client" to="devloop.de"> > > xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client' > from='devloop.de' version='1.0' > id='13ipsmggju6kqcb82rqdmqfny42xtfuujdjbz0sj'> > > > > PLAIN > DIGEST-MD5 > > http://jabber.org/features/iq-auth"/> > http://jabber.org/features/iq-register"/> > > > > > cmVhbG09ImRldmxvb3AuZGUiLCBub25jZT0icEFWL3hRZUg5KzUvNEVVX2t0b3dhZz09Ii > wgcW9wPSJhdXRoIiwgY2hhcnNldD11dGYtOCwgYWxnb3JpdGhtPW1kNS1zZXNz > > dXNlcm5hbWU9ImRhbWFnZSIscmVhbG09ImRldmxvb3AuZGUiLG5vbmNlPSWwQVYveFFlSD > krNS80RVVLa3Rvd2FnPT0iLGNub25jZT0ieEFweU1Hb2ZZRlROR0xKUnRhTHlIekQ0NlJYOHZzeD > g4T2JobmF4WTMzRT0iLG5jPTAwMDAwMDAxLGRpZ2VzdC11cmk9InhtcHAvZGV2bG9vcC5kZSIscW > 9wPWF1dGgscmVzcG9uc2U9OWU0NjY0MjQ3MDEzMzYzNDI2Mjg2NGRiNDFlYzAxOWYsY2hhcnNldD > 11dGYtOA== > > > > > > http://etherx.jabber.org/streams"; version="1.0" > xmlns="jabber:client" to="devloop.de"> > --- > > --- > with connection server set (working) > --- > > > http://etherx.jabber.org/streams"; > xmlns="jabber:client" to="devloop.de"> > > xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client' > from='devloop.de' id='x64pfgs4l4jlb4m6h2lj9t22cfgq9xw641wjhpn2'> > > > > damage > > > > > > damage > > > > > > > > > damage > [Filtered] > Kopete > > > > [rosters etc.] > ---
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) --- http://etherx.jabber.org/streams"; version="1.0" xmlns="jabber:client" to="devloop.de"> PLAIN DIGEST-MD5 http://jabber.org/features/iq-auth"/> http://jabber.org/features/iq-register"/> cmVhbG09ImRldmxvb3AuZGUiLCBub25jZT0icEFWL3hRZUg5KzUvNEVVX2t0b3dhZz09IiwgcW9wPSJhdXRoIiwgY2hhcnNldD11dGYtOCwgYWxnb3JpdGhtPW1kNS1zZXNz dXNlcm5hbWU9ImRhbWFnZSIscmVhbG09ImRldmxvb3AuZGUiLG5vbmNlPSWwQVYveFFlSDkrNS80RVVLa3Rvd2FnPT0iLGNub25jZT0ieEFweU1Hb2ZZRlROR0xKUnRhTHlIekQ0NlJYOHZzeDg4T2JobmF4WTMzRT0iLG5jPTAwMDAwMDAxLGRpZ2VzdC11cmk9InhtcHAvZGV2bG9vcC5kZSIscW9wPWF1dGgscmVzcG9uc2U9OWU0NjY0MjQ3MDEzMzYzNDI2Mjg2NGRiNDFlYzAxOWYsY2hhcnNldD11dGYtOA== http://etherx.jabber.org/streams"; version="1.0" xmlns="jabber:client" to="devloop.de"> --- --- with connection server set (working) --- http://etherx.jabber.org/streams"; xmlns="jabber:client" to="devloop.de"> damage damage damage [Filtered] Kopete [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 > > --
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 > --
