O. Hartmann wrote:
I struggle with setting up jails on most recent CURRENT.
The machine containing the jails has two NICs (bce0 and bce1). the host itself
is supposed to own NIC bce0 exclusively - means, the services running on that
NIC - syslogd, named and others - are bound to that NIC and should not be
shared with the bce1 or jails bound to bce1.
I followed the instructions given in the most recent version of the handbook
setting up a jail. So far, so good. The NIC bce1 (the second one) is "aliased"
with IPs from the local network. forwarding is disabled
Setup of each jail is straigh forward, with "ip4.addr=" set to the specific IP
Within a jail, I can not reach an IP on the same network, not even the gateway
by pinging or doing name resolutions using the DNS server on the local net! The
curious thing is, by setting "nameserver 220.127.116.11" in /etc/resolv.conf, I can
ping "outer world systems" and performing name resolutions as well - this
implies, that the IP pakets are delegated to the local gateway and then further
to the DNS of Google's. But pinging the local gateway directly (192.168.0.1)
seems to be prohibited as well as pinging or reching any other IP on the net,
including the bce0 of the same host (via default gateway?) or any other aliased
Since I'm new to jails and the complicated handling with networks, I miss
something here which is probably not well documented. I found some notes on the
forum about setfib, FIB, but I lack in the correct manpage to read more about
this concept, the meaning for a jail and its probable impact in my situation.
Following the suggestion setting
in /boot/loader.conf seems to be senseless - after a reboot this OID is always
set back to 1 (net.add_addr_allfibs=1).
maybe someone has an idea what's wrong in principle with my attempts.
thanks in advance for your patience,
First of all trying to teach your self about LAN & jail usage using
[CURRENT] is the wrong version of FreeBSD to be using because it's the
bleeding edge where all the OS updates are tested. You should be using
10.3 or soon to be published 11.0. With CURRENT you can't tell if
problems are caused by you not configuring something correctly or you
fell into a OS bug.
Now if you have a LAN & jail setup working on a RELEASE version and you
really think your problem is caused by a bug in CURRENT then you need to
come out and state that. But based on the tone of your post that is not
Secondly, the "current" list is the incorrect list to be posting this
type of question. You should post this to the "questions" or the "jail"
The ping command from within a jail is a considered a security risk and
disabled by jail(8) design.
It seems to me that you are mixing 2 separate problems, LAN
configuration and jail configuration. You need to first get your LAN
nodes talking to each other and with the host, before you add jail(8)
into the mix.
The standard LAN configuration runs a DHCP server on the host to assign
private IP address to the LAN PC's when they power on.
Since your host box functions as a [gateway box] with a LAN behind it
you need to have gateway_enable="YES" in your hosts rc.conf file.
You also need a firewall to NAT the private LAN IP addresses to the
hosts public ISP issued IP address. I recommend ipfilter which is in the
base system, it's open source and runs on most all other Unix flavored
OS's making it very easy to use the same firewall rule set across other
After you have your LAN nodes being able to ping the host and other
nodes on the LAN, and also access the pubic internet, Then is the time
to play with jails.
I recommend you use the jail utility sysutil/qjail port. It simplifies
jail management and is very user friendly. Be sure not to assign private
IP addresses to jails that are controlled by DHCP or the LAN node will
stop working when the jail starts using the same IP address.
A detailed description of how you intend to us jails would go a long way
to customizing any additional help you may require from posts to the
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"