-
Notifications
You must be signed in to change notification settings - Fork 145
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] VNET Jails with static MAC network not reachable #821
Comments
Although I'm not sure why this is happening, the default behaviour has been returned to bastille. It is now necessary to specify -M if the user does want a static MAC to be assigned to the jail. This will be in the next release. Current head has this already. |
@subnetspider can you test the github version to see if it is fixed for you. |
Can you test it with IPv4? Wondering if the IPv6 has anything to do with it. |
Is there a special branch or have you updated the main branch?
I did with DHCP, it kept broadcasting DHCP requests but they never arrived at the firewall. |
main branch test please |
Update:On a second host, I have created another VNET jail with the static MAC enabled, and it runs without issue: FreeBSD host:
FreeBSD VNET jail
On the host with the issue, the network setup is a little bit more complicated:
On this host, it's a lot simpler:
@bmac2 and I suspect that either the lagg or the vlan interface are what's causing this. |
em0bridge looks like an automatically created bridge. Did you create that with "ifconfig bridge create"? What happens when you try with a bridge created using the above command? |
For now this issue is kind of on hold until we can get some better data on what is going on. If there is a lagg issue we can isolate we will look at fixing the code for that. For now this one should not hold up the release or any additional work. |
This issue is because we are missing the "up" parameter inside the "generate_vnet_block" It should be fixed in the next release when #792 is included. |
[MANDATORY] Describe the bug [MANDATORY]
Networking on VNET jails with a static MAC address set on the epair_b interface does not work.
[MANDATORY] Bastille and FreeBSD version (paste
bastille -v && freebsd-version -kru
output)[MANDATORY] How did you install bastille? (port/pkg/git)
pkg
[optional] Steps to reproduce?
bastille
pkg (version0.12.20250111
)bastille.conf
, bootstrap 14.2-RELEASE.bastille create -B test 14.2-RELEASE SLAAC bridge60
bastille create -V test 14.2-RELEASE SLAAC vlan60
[optional] Expected behavior
The VNET jail with a static MAC should be able to send an receive network traffic like VNET jails without a static MAC.
[optional] Actual behavior
The VNET jail with a static MAC can:
bridge60
.bridge60
.bridge60
.epair15b
isn't overridden, the VNET jail is running as expected.[optional] Screenshots
[optional] Additional context
FreeBSD Jail Host
The
pf
Firewall is disabled./etc/rc.conf
:ifconfig
: (limited)VNET Jail `tlsproxy01
jail.conf
:ifconfig
:/etc/rc.conf
I'm not sure what to make of this, I tried the VNET jail with a static MAC on two physical FreeBSD hosts, one with VLAN and one without, as well as on a FreeBSD VM with VLANs.
The text was updated successfully, but these errors were encountered: