Re: [Vserver] jabber in a guest

On Sat, 14 Oct 2006 23:12:02 -0400
Chuck <chuck@sbbsnet.net> wrote:

> do i need any special b or c capabilities to run jabber 2 in a guest?

i'm running jabberd 1.4.3 in a guest with standard capabilities and no
problems.

i run all my transports in the same guest, all through 127.0.0.1 with no
problems. for temporary testing purposes i have used transports in a
different guest connecting to the jabberd, by way of network ip address (ie
192.168.0.1), with no problem.

my jabberd is configured to accept s2s connections (ie talk.google.com) and
that works.

> i keep getting logs like this for its various elements:
>
> Oct 14 23:02:12 jabber jabberd/s2s[27854]: attempting connection to
> router at 127.0.0.2, port=5347
> Oct 14 23:02:12 jabber jabberd/s2s[27854]: [4] [router] write error:
> Connection refused (111)
> Oct 14 23:02:12 jabber jabberd/s2s[27854]: connection to router closed
>
>
> or is it I just have to figure out configurations better? i tried the
> same configs on the host and that ran.

if something doesn't work, i would say the problem is either in your use of
127.0.0.2 (which is network-wise no different than 127.0.0.1, an
internal-machine-routable-only ip address, but i still don't understand
vserver's handling of 127.0.0.0/8 as my usage of 127.0.0.1 has always
worked the way i needed) or your iptables configuration.

> the host of course protects the guests using iptables, and the 5222 port
> is passed but none of the other internal ones such as 5347. do i have to
> include them too? i am trying to move it off a host into a guest. i
> tried mapping everything to the guest primary ip as well, but that didnt
> do anything different.

have iptables log all rejections/denials and then you'll quickly learn if
the problem is your firewall rules. i don't use iptables on my vserver
host (probably should, but haven't been able to justify it), but if you've
accepted 127.0.0.0/255.0.0.0, then accepting individual ports for
jabber transports isn't necessary.

> im using amd64 with the following:
>
> 2.6.18-vs2.0.2-gentoo-r8
> util-vserver-0.30.211

i'm also using amd64 but on ubuntu's 2.6.15 with debian testing's
backported util-vserver 0.30.210, but i don't think any of that matters in
this context.

corey

-- 
undefined@pobox.com
_______________________________________________
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver