Date: Thu, 19 May 2016 14:57:04 +0000 From: Grzegorz Junka <list1@gjunka.com> To: freebsd-jail@freebsd.org Subject: Re: jails in different private subnets on the same host Message-ID: <3aaa36dc-c658-5760-c4bb-d0f991834194@gjunka.com> In-Reply-To: <beafbcae807260bf74db591044c44950@gritton.org> References: <faf9e698-baee-f988-df64-5bcda4b1c7c9@gjunka.com> <AF80A4F2-3605-43A0-81CD-B68659B694C4@lists.zabbadoz.net> <07d67bd5-206c-edd8-7f47-ef2b5c538e01@gjunka.com> <beafbcae807260bf74db591044c44950@gritton.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 19/05/2016 14:50, James Gritton wrote: > On 2016-05-18 09:08, Grzegorz Junka wrote: >> I just tried telnet 192.168.1.50 80 from the main host and from the >> 10.33.1.40 jail. From the main host it works without issues. From the >> jail it eventually connected after 15 or so seconds of waiting. > > That sounds like about the kind of timeout I'd expect from DNS > resolution not working. If you're adding a new subnet when the jail > is created, you'll need to do something to get a nameserver to listen > to it. > > - Jamie Why would it need to use the nameserver if I am telneting through IP? My nameserver is running in 192.168.1.60 but drill @192.168.1.60 from inside the 10.33.1.40 jail doesn't see it. I am using telnet with the IP specifically to avoid using the nameserver because I know the jail can't use the nameserver at this moment (until this is solved). Grzegorz
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3aaa36dc-c658-5760-c4bb-d0f991834194>