Date: Wed, 11 Mar 2015 15:17:52 +0100 From: Christian Lask <lists@elfsechsundzwanzig.de> To: Matthew Seaman <matthew@FreeBSD.org>, freebsd-questions@freebsd.org Subject: Re: Jail with bitblee running, connection timed out Message-ID: <87sidbzkhb.fsf@piet.i-did-not-set--mail-host-address--so-tickle-me> In-Reply-To: <55004C8E.5050407@FreeBSD.org> References: <87vbi7zlc8.fsf@piet.i-did-not-set--mail-host-address--so-tickle-me> <55004C8E.5050407@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Matthew Seaman <matthew@FreeBSD.org> writes: > On 2015/03/11 13:59, 1126 (Christian Lask) wrote: >> `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. > > Jails tend not to have localhost (ie. 127.0.0.1 or ::1) addresses > accessible to them[*]. Try logging into the jail and examine the output > of 'ifconfig -a' -- compare it with what you get on the host system. I see! Thanks, I didn't know that, but that explains a lot. > If you want some processes within the same jail to be able to > communicate through a network-like protocol, then unix domain sockets > are the way to go, assuming that the software you want to run supports > them. Failing that, you'll have to use the jail's allocated IP > number(s). I will look into it. I guess, I know now where to look and how to get it running. Thanks again! --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?87sidbzkhb.fsf>