You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[MANDATORY] Describe the bug [MANDATORY]
Bastille does not create an entry in the pf-table jails when starting a VNET jail.
[MANDATORY] Bastille and FreeBSD version (paste bastille -v && freebsd-version -kru output)
0.8.20210115
12.2-RELEASE-p3
12.2-RELEASE-p3
12.2-RELEASE-p3
[MANDATORY] How did you install bastille? (port/pkg/git)
pkg
[optional] Steps to reproduce?
Create a new VNET jail using bastille create --vnet alcatraz 12.2-RELEASE 10.0.1.10/24 em0, then display the jails-table using pfctl -t jails -T show.
[optional] Expected behavior
Bastille should add the jail's IP to the jails-table upon start.
[optional] Screenshots
None
[optional] Additional context
My current workaround is to use nat on $ext_if from em0bridge:network to any -> $ext_if as generic rule, but a table based solution would be better IMO.
Maybe this bug is related to #80, however the bastille version used is much newer than 0.5.20191128.
The text was updated successfully, but these errors were encountered:
[MANDATORY] Describe the bug [MANDATORY]
Bastille does not create an entry in the
pf
-tablejails
when starting a VNET jail.[MANDATORY] Bastille and FreeBSD version (paste
bastille -v && freebsd-version -kru
output)0.8.20210115
12.2-RELEASE-p3
12.2-RELEASE-p3
12.2-RELEASE-p3
[MANDATORY] How did you install bastille? (port/pkg/git)
pkg
[optional] Steps to reproduce?
Create a new VNET jail using
bastille create --vnet alcatraz 12.2-RELEASE 10.0.1.10/24 em0
, then display thejails
-table usingpfctl -t jails -T show
.[optional] Expected behavior
Bastille should add the jail's IP to the
jails
-table upon start.[optional] Screenshots
None
[optional] Additional context
My current workaround is to use
nat on $ext_if from em0bridge:network to any -> $ext_if
as generic rule, but a table based solution would be better IMO.Maybe this bug is related to #80, however the bastille version used is much newer than
0.5.20191128
.The text was updated successfully, but these errors were encountered: