Olá D3v1L,
Por favor, me dê uma força..
Eu instalei o jabberd2 a algum tempo e não tinha controle (monitoramento) e então resolvi pesquisar. Achei seu artigo interessante, porém não consegui fazer funcionar (acredito que possa ser um módulo do Perl).
Olha só:
bandersnatch config.xml
#############################################
<config>
<server>
<connectiontype>tcpip</connectiontype>
<hostname>192.168.1.39</hostname> // se eu coloco o hostname como o ip ou nome do servidor que roda o jabber, ele resulta o erro 2 que listei lá embaixo... e se eu coloco o ip ou o nome do servidor que roda o mysql então ele apresenta o erro 1 que mostrei lá embaixo também
<port>5347</port>
<secret>bandersnatch</secret>
</server>
<component>
<name>bandersnatch</name>
</component>
<mysql>
<server>192.168.1.39</server>
<dbname>bandersnatch</dbname>
<username>bandersnatch</username>
<password>bandersnatch</password>
</mysql>
<debug>
<level>0</level>
<file>stdout</file>
</debug>
<site>
<local_server>interno</local_server>
<admin_jids>admin@interno</admin_jids>
<confidential_jids>theboss@interno</confidential_jids>
<ignore_jids>chatbot@interno</ignore_jids>
<ignore_jids>bandersnatch@interno</ignore_jids>
<ignore_jids>headlines.interno</ignore_jids>
<local_domains>interno</local_domains>
<local_server>interno</local_server>
<admin_jids>admin@interno</admin_jids>
<confidential_jids>theboss@interno</confidential_jids>
<ignore_jids>chatbot@interno</ignore_jids>
<privacy>1</privacy>
<aggressive_presence>0</aggressive_presence>
</site>
</config>
################################################## ##
jabberd2 router.xml
################################################## ##
<!-- Router configuration -->
<router>
<!-- ID of the router on the network (default: router) -->
<id>router</id>
<!-- The process ID file. comment this out if you don't need to know
to know the process ID from outside the process (eg for control
scripts) -->
<pidfile>/var/run/jabberd2/router.pid</pidfile>
<!-- Log configuration - type is "syslog", "file" or "stdout" -->
<log type='file'>
<!-- If logging to syslog, this is the log ident -->
<ident>jabberd/router</ident>
<!-- If logging to syslog, this is the log facility
(local0 - local7) [default: local3] -->
<facility>local3</facility>
<!-- If logging to file, this is the filename of the logfile -->
<file>/var/log/jabberd2/router.log</file>
</log>
<!-- Local network configuration -->
<local>
<!-- IP address to bind to (default: 0.0.0.0) -->
<ip>192.168.1.33</ip>
<!-- Port to bind to (default: 5347) -->
<port>5347</port>
<!-- File containing the user table. This is where the router gets
its component and secret information from for component
authentication.-->
<users>/etc/jabberd2/router-users.xml</users>
<!-- Shared secret used to identify legacy components (that is,
"jabber:component:accept" components that authenticate using
the "handshake" method). If this is commented out, support for
legacy components will be disabled. -->
<secret>secret</secret>
<!-- File containing a SSL certificate and private key for client
connections. If this is commented out, connecting components
will not be able to request a SSL-encrypted channel. -->
<!--
<pemfile>/etc/jabberd/server.pem</pemfile>
-->
</local>
<!-- Timed checks -->
<check>
<!-- Interval between checks.
Checks will be run every n seconds.
0 disables all checks. (default: 60) -->
<interval>60</interval>
<!-- Keepalives.
Connections that have not been used for longer than
this many seconds will have a single whitespace character sent
to them. This will force the TCP connection to be closed if
they have disconnected without us knowing about it.
0 disables keepalives. (default: 0) -->
<keepalive>0</keepalive>
</check>
<!-- input/output settings -->
<io>
<!-- Maximum number of file descriptors. Note that the number of
possible connections will be slightly less than this, because
the router itself can use up four on its own. If the supply of
file descriptors is exhausted, new incoming connections will be
denied (default: 1024) -->
<max_fds>1024</max_fds>
<!-- Rate limiting -->
<limits>
<!-- Maximum bytes per second - if more than X bytes are sent in Y
seconds, connection is throttled for Z seconds. The format
is:
<bytes seconds='Y' throttle='Z'>X</bytes>
Default Y is 1, default Z is 5. set X to 0 to disable. -->
<bytes>0</bytes>
<!-- Maximum connects per second - if more than X connects are
attempted from a single IP in Y seconds, that IP is throttled
for Z seconds. The format is:
<connects seconds='Y' throttle='Z'>X</connects>
Default Y is 5, default Z is 5. set X to 0 to disable. -->
<connects>0</connects>
</limits>
<!-- IP-based access controls. If a connection IP matches an allow
rule, the connection will be accepted. If a connecting IP
matches a deny rule, the connection will be refused. If the
connecting IP does not match any rules, or it matches both an
allow and a deny rule, the contents of the <order/> option
determines what happens. -->
<access>
<!-- Rule check order (default: allow,deny)
allow,deny - Check allow rules, then check deny rules.
Allow by default.
deny,allow - Check deny rules, then check allow rules.
Deny by default. -->
<order>allow,deny</order>
<!-- Allow a network. If the mask isn't specified, it defaults to
255.255.255.255 (ie allow onle the specified IP) -->
<!--
<allow ip='127.0.0.0' mask='255.0.0.0'/>
-->
<!-- Allow a single host -->
<!--
<allow ip='12.34.56.78'/>
-->
<!-- Deny a network or a host -->
<!--
<deny ip='192.168.1.33' mask='255.0.0.0'/>
<deny ip='87.65.43.21'/>
-->
</access>
</io>
<!-- Name aliases.
Packets destined for the domain specified in the "name" attribute
will be routed to the component that has currently bound the name
in the "target" attribute (assuming it is online).
This is usually only required for some kinds of legacy
components (particularly jabberd 1.4 "uplink" components) -->
<aliases>
<!-- Example for a MUC component running from a jabberd 1.4 uplink -->
<!--
<alias name='conference.domain.com' target='muclinker'/>
-->
</aliases>
<!-- Access control information -->
<aci>
<!-- The usernames listed here will get access to all restricted
functions, regardless of restrictions further down -->
<acl type='all'>
<user>jabberd</user>
</acl>
<!-- These users can bind names other than their username -->
<!--
<acl type='bind'>
</acl>
-->
<!-- These users can bind a name as a default route -->
<!--
<acl type='default-route'>
<user>s2s</user>
</acl>
-->
<!-- These users can elect to receive all packets that pass through the router -->
<acl type='log'>
<user>bandersnatch</user>
</acl>
</aci>
</router>
##################################################
jabberd2 router-users.xml
##################################################
<!-- This is the list of known router users, and their authentication
secrets. Access control is done via the settings in router.xml -->
<users>
<user>
<name>jabberd</name>
<secret>secret</secret>
</user>
<user>
<name>bandersnatch</name>
<secret>bandersnatch</secret>
</user>
</users>
##################################################
Erro 1: Usando como 192.168.1.39
################################################## ##
interno:/var/www/bandersnatch# perl bandersnatch2.pl
Connect Error: connect: 111 -> Connection refused
Connected to MySQL database (bandersnatch@192.168.1.39) ...
interno:/var/www/bandersnatch#
################################################## ##
Erro 2: Usando como interno ou 192.168.1.33
################################################## ##
interno:/var/www/bandersnatch# perl bandersnatch2.pl
SASL Negotiation Failed at /usr/local/share/perl/5.8.4/POE/Component/Jabber/Client/J2.pm line 374.
Connected to MySQL database (bandersnatch@192.168.1.39) ...Failed to authenticate
We got disconneted
interno:/var/www/bandersnatch#
################################################## ##
O que pode ser isso cara? É mesmo o módulo do Perl (POE)? Não sei o que pode ser.
Abraços
Fala ae mano.. até que em fim!! rs....
vou dar uma lida ai.. mais de prima já foi para os favoritos..
Abraços...