On Fri, Mar 23, 2018 at 08:17:27PM +0100, joerg_surmann wrote: > Hi, > > thanks for yor help. > > I can't find a solution. > > But i have find a starnge ip config. > > in rc.conf on Host(not jail) > > ifconfig_vmx0_alias1="inet 192.168.100.2 netmask 255.255.255.0" > ifconfig_em0="inet 213.70.80.92 netmask 255.255.255.0" > > ifconfig on host say: > inet 213.70.80.92 netmask 0xffffffff broadcast 213.70.80.92 > inet 192.168.100.2 netmask 0xffffffff broadcast 192.168.100.2 > > ifconfig say to both ip's /32. > > Maby that's the reason for unavailable the apache. > > ifconfig iside the jail say the same. > > I'm a little bit confused. >
Please show also the output of: netstat -rn During startup, ezjail is adding one more IP address with /32 mask for each interface deployed to jail. Consider addressing interfaces on host these in these way: in /etc/rc.conf ifconfig_vmx0_alias1="inet 192.168.100.3 netmask 255.255.255.0" ifconfig_em0="inet 213.70.80.93 netmask 255.255.255.0" then in /usr/local/etc/ezjail/myjail.conf export jail_myjail_ip="vmx0|192.168.100.2,em0|213.70.80.92" If you don't want to waste one more public IP for the host, try to setup jails from jail.conf(5) instead of ezjail management. You can also give a try to more sophisticated setup with vnet(9) jails where multiple fibs for the host will not be required. Best regards, -- Marek Zarychta
signature.asc
Description: PGP signature
