Solved ifconfig inside a jail

[balanga]

I thought I'd managed to setup a jail yesterday, but coming back to it to day, starting from scratch thngs don't work.

What should I expect to see when running ifconfig inside the jail?

I only see lo0. Outside I see also see em0 and bridge0.

 

[atax1a]

how did you set up the jail? jail.conf? if so, what is your config file?

 

[balanga]

how did you set up the jail? jail.conf? if so, what is your config file?

I followed the instructions here

Same instructions as yesterday, but obviously something missed out today.

iocage create -n "myjail" -r latest --thickjail vnet="on" allow_raw_sockets="1" boot="on" defaultrouter="192.168.1.1"

iocage set ip4_addr="em0|192.168.1.99/24" myjail

Maybe I didn't set up bridge0 correctly.

There seems to be plenty of scope for error.

 

[skhal]

Assuming there is a bridge0 setup on the host environment (showing relevant parts only):

iocage create \
  vnet="on" \
  ip4_addr="vnet0|192.168.1.99/24" \
  interfaces="vnet0:bridge0" \
  ...

References:
- doc: iocage networking
- forum: iocage jail with vnet

 

[balanga]

After all my different attempts, I found that this worked.

iocage create -r 15.0-RELEASE -n testjail dhcp=on boot=on

It creates a jail and am able to ping the outside world.

Amazingly simple if you manage to stumble across it.

ifconfig shows epair0b although I'm not sure where that came from.

 

[atax1a]

we've never used iocage, but our vnet jails have an lo and an epair1a interface. the b side of the epair goes into the bridge on the host, which bridges to our DMZ VLAN. So, this is to be expected for a vnet jail. Also, the a/b side difference is immaterial to the functionality.