Date: Sun, 04 Dec 2016 08:51:45 +0800 From: Ernie Luzar <luzar722@gmail.com> To: doug@safeport.com Cc: freebsd-questions@FreeBSD.org Subject: Re: Can't ping in jail Message-ID: <584368A1.5080206@gmail.com> In-Reply-To: <alpine.BSF.2.20.1612031801220.33158@fledge.watson.org> References: <alpine.BSF.2.20.1612030234030.77272@fledge.watson.org> <alpine.BSF.2.20.1612031801220.33158@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
doug wrote: > On Sat, 3 Dec 2016, doug wrote: > >> This is a 9.3-RELEASE-p49 system. In the jail: >> >> gaia:~> sysctl security.jail.allow_raw_sockets >> security.jail.allow_raw_sockets: 1 >> >> gaia:~> ifconfig >> em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 >> >> options=4219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO> >> >> ether c8:9c:dc:eb:ab:fb >> inet 192.168.2.110 netmask 0xffffffff broadcast 192.168.2.110 >> media: Ethernet autoselect (100baseTX <full-duplex>) >> status: active >> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384 >> options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6> >> >> and as root >> >> gaia:/home/doug# ping -c 2 192.168.2.102 >> PING 192.168.2.102 (192.168.2.102): 56 data bytes >> ping: sendto: Can't assign requested address >> ping: sendto: Can't assign requested address >> ^C >> --- 192.168.2.102 ping statistics --- >> 2 packets transmitted, 0 packets received, 100.0% packet loss >> >> ctrl-c is required to end the command. This is without a loopback >> defined. If I define the loopback I can ping 127.0.0.1 but nothing >> else. What am I missing? > > Okay after lots of reading: handbook, man pages, wiki's, and google (I > did RTFM) I an pretty sure I have a routing issue and that > security.jail.allow_raw_sockets works. That said, I give up. The host > was getting its IP via DHCP so I changed that, defined the host as a > gateway, did what I know how to so with netmasks and set all the > sysctl's that seemed remotely related to this in the host. At the end of > the day virtually all combinations of the aforementioned allow the jail > to ping its own IP and localhost. Now moving on to stuff that pays the > rent. Any thoughts welcomed though. Hello Doug. Your asking for help, but providing a very small amount of information about how you created your jails and the network surrounding your host. Are your jails defined using the legacy method with definition statements in /etc/rc.conf or the modern way using /etc/jail.conf? Is this a single host with isp assigned dynamic ip addresses? Is there a LAN behind the host with real computers attached, or are you using an second NIC just to address the jails? Do you have a firewall doing NAT for the jail's [non public routeable ip address]? How did you create your jail directory tree? Are you using nullfs? Did you use any of the port utilities for creating your jail environment? The above will give you plenty to think about. ****************************************************************** First off 9.3 reaches EOL [end of life] next month. There has been a lot of changes to jail(8) between 9.3 and 11.0. You should have moved to 11.0 already. Your not going to get jail support for an EOL system. I strongly suggest you install the package named jail-primer it will go a long way filling in the background info you seem to be lacking about jails in general. Once your on 11.0 then install the package named qjail It automates jail management in a very user friendly manner automatically doing all the little details for you. First you have to get the host communicating with the public network before you start playing with jails. As a general rule there is no need to be using any sysctl nibs. At a bare minimum you need this in rc.conf hostname="doughost.com" gateway_enable="YES" ifconfig_em0="DHCP" After doing your homework and having played with qjail, if you need help then post here again but give greater details about your environment. Good Luck.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?584368A1.5080206>