Re: jails in different private subnets on the same host
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 ___ freebsd-jail@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-jail To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"
Re: jails in different private subnets on the same host
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 ___ freebsd-jail@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-jail To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"
Re: jails in different private subnets on the same host
Hi! > Why would it need to use the nameserver if I am telneting through IP? Use telnet -N to avoid DNS lookups. -- p...@opsec.eu+49 171 3101372 4 years to go ! ___ freebsd-jail@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-jail To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"
Re: jails in different private subnets on the same host
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 You have not copied the hosts /etc/resolv.conf to the jail in question. ___ freebsd-jail@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-jail To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"
Re: jails in different private subnets on the same host
On 19/05/2016 15:40, Ernie Luzar wrote: 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 You have not copied the hosts /etc/resolv.conf to the jail in question. Of course I did. root@somehost:/# cat /etc/resolv.conf search somehost.somedomain.com nameserver 192.168.1.60 nameserver 8.8.8.8 I installed the jail using bsdinstall and it copies that automatically. Grzegorz ___ freebsd-jail@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-jail To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"
