https://www.ejabberd.im/node/5119 en https://www.ejabberd.im/node/5119#comment-58194 <div class="quote-msg"> <div class="quote-author"><em>badlop</em> wrote:</div> <p>If ejabberd is using that configuration, then ejabberd should try to connect to localhost:389, and you should be able to sniff the traffic like this:</p> <p>If that doesn't happen, then it means ejabberd isn't using those options. Maybe you are editing an ejabberd.cfg that ejabberd doesn't read? maybe you hav another {auth_method, internal} that overwrites the ldap one, ...</p></div> <p>i was sniffing traffic and didnt see anything coming from the ejabberd-instance. i saw the traffic of my other ldap client just fine.<br /> im not using {auth_method, internal} either as you can see in the relevant part of the config i posted.<br /> and ejabberd is using the config file because when i change auth back to internal in it it works just fine.<br /> thanks anyway.</p> Wed, 04 Jan 2012 21:27:41 +0000 senz comment 58194 at https://www.ejabberd.im https://www.ejabberd.im/node/5119#comment-58190 <p>If ejabberd is using that configuration, then ejabberd should try to connect to localhost:389, and you should be able to sniff the traffic like this:</p> <pre> $ sudo tcpflow -i lo -ec tcp port 389 tcpflow[17846]: listening on lo 127.000.000.001.36666-127.000.000.001.00389: 00...c+..dc=poke .. ...............cn..robin0...cn ..cn1...robin01.00389-127.000.000.001.36666: 01...d,..cn=robin,ou=users,dc=poke0.0 127.000.000.001.00389-127.000.000.001.36666: 0....e. ...... 127.000.000.001.37946-127.000.000.001.00389: 0)...`$.....cn=robin,ou=users,dc=poke..aaaf 127.000.000.001.00389-127.000.000.001.37946: 0....a. ...... </pre><p> If that doesn't happen, then it means ejabberd isn't using those options. Maybe you are editing an ejabberd.cfg that ejabberd doesn't read? maybe you hav another {auth_method, internal} that overwrites the ldap one, ...</p> Wed, 04 Jan 2012 16:23:00 +0000 mfoss comment 58190 at https://www.ejabberd.im