From owner-freebsd-questions@FreeBSD.ORG Wed Mar 11 13:59:56 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AD82937C for ; Wed, 11 Mar 2015 13:59:56 +0000 (UTC) Received: from smtprelay06.ispgateway.de (smtprelay06.ispgateway.de [80.67.18.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 70167F38 for ; Wed, 11 Mar 2015 13:59:56 +0000 (UTC) Received: from [92.204.54.227] (helo=localhost) by smtprelay06.ispgateway.de with esmtpsa (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.84) (envelope-from ) id 1YVhAO-0002ps-27 for freebsd-questions@freebsd.org; Wed, 11 Mar 2015 14:59:20 +0100 From: 1126 (Christian Lask) To: "Questions" Subject: Jail with bitblee running, connection timed out User-Agent: Notmuch/0.19 (http://notmuchmail.org) Emacs/24.4.2 (x86_64-unknown-linux-gnu) Date: Wed, 11 Mar 2015 14:59:19 +0100 Message-ID: <87vbi7zlc8.fsf@piet.i-did-not-set--mail-host-address--so-tickle-me> MIME-Version: 1.0 Content-Type: text/plain X-Df-Sender: bWFpbEBlbGZzZWNoc3VuZHp3YW56aWcuZGU= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Mar 2015 13:59:56 -0000 Hello there! This might just be my first posting ever to this very mailinglist. :) I am currently deploying FreeBSD 10.1 on a spare server to learn how that works and - if everything works out - use this server for a manifold of tasks. One of them would be and currently is to run a Weechat instance in a jail to which I then connect via SSH. This is working just fine including NAT via PF and everything. Yesterday I tried to add bitlbee to the mix to connect to Twitter and Jabber via this Weechat instance. This however did not work. I configured bitlbee to run as ForkDeamon and by the user bitlbee and started it via `service bitlbee start`. `stockstat -l4p 6667` reveals that it is indeed listening on the jails IP on port 6667. In Weechat then I added a new server (localhost/6667) and tried to connect to it. This connection however is never established and times out. I do not know how to debug this properly and have no idea what is wrong here. Configuration of both seems pretty straightforward, so I don't know what I am doing wrong here. Maybe one of you could point me in the right direction? Thanks in advance! --