Solved New jail resets host networking

L

Luke Crooks

So, I am back on FreeBSD after 4 years (we had to support an old database which had no FreeBSD driver and were forced to switch our web servers over to Linux, anyway....)

I am creating some jails, all is working absolutely fine, as per thing guide https://www.freebsd.org/doc/handbook/jails-ezjail.html

Now, when I go to create a jail, I run...

Code: 
# ezjail-admin create -c zfs dnsjail 'lo1|127.0.1.1,igb0|172.10.10.240'

Where lo1 is my new loopback interface (and I want the jail to run on 127.0.1.1), and igb0 is my network interface, connected on 172.10.10.240.

This works fine and creates my jail, I then start my jail:

Code: 
# ezjail-admin start dnsjail

This for some reason breaks the networking on igb0 and closes my ssh connection, I then need to go over to the rack and manually restart the network on igb0 (through dhclient, I tried also using a manual configuration, and this had the same problems/issues). After I have restarted the networking on igb0 everything works fine and dandy, I can access the jail, configure resolv.conf and the networking works fine in the jail and on the host. This is obviously not normal behavior and I would like to try and solve it, before configuring my new jails.

EDIT: The reason that this is also a big problem, is that when the server reboots it causes networking to fail on igb0 and I have to manually re run dhclient on igb0 for it to pick up a network address, which is obviously not suitable for a production server.

EDIT2: I have also tried running the Jail IP on the same subnet as the host network (suggested on IRC) with no luck.
 
Thanks to "fillis" in #ezjail who provided a working solution... remove the interfaces...

Code: 
# ezjail-admin create -c zfs dnsjail '127.0.1.1,172.10.10.240'
 
You must log in or register to reply here.
Back
Top