Date: Wed, 11 Mar 2015 14:09:18 +0000 From: Matthew Seaman <matthew@FreeBSD.org> To: freebsd-questions@freebsd.org Subject: Re: Jail with bitblee running, connection timed out Message-ID: <55004C8E.5050407@FreeBSD.org> In-Reply-To: <87vbi7zlc8.fsf@piet.i-did-not-set--mail-host-address--so-tickle-me> References: <87vbi7zlc8.fsf@piet.i-did-not-set--mail-host-address--so-tickle-me>
next in thread | previous in thread | raw e-mail | index | archive | help
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. 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). Cheers, Matthew [*] There is a new alternative style of jail, called a VNET jail, which you could use and that do have their own loopback interfaces and localhost addresses, but these are still fairly new, somewhat more complicated to setup and still not thoroughly debugged. Last I checked, they also required you to run a custom kernel.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55004C8E.5050407>