[GH-ISSUE #807] Support for custom veth interface names for --net=bridge_interface #548

Closed
opened 2026-05-05 06:06:22 -06:00 by gitea-mirror · 1 comment
Owner

Originally created by @naturalspringwater on GitHub (Sep 24, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/807

Hello,
I use the --net=bridge_interface option which works fine, but I cannot find a way to specify the name of the veth interface created. It is always auto-generated, e.g., "veth4772eth0" ($ ip addr).

I need custom names to enforce bridge port IPs using ebtables outside the sandbox, e.g. similar to what is done by libvirt, and for other mapping purposes as well.

Thank you for this software

Originally created by @naturalspringwater on GitHub (Sep 24, 2016). Original GitHub issue: https://github.com/netblue30/firejail/issues/807 Hello, I use the --net=bridge_interface option which works fine, but I cannot find a way to specify the name of the veth interface created. It is always auto-generated, e.g., "veth4772eth0" ($ ip addr). I need custom names to enforce bridge port IPs using ebtables outside the sandbox, e.g. similar to what is done by libvirt, and for other mapping purposes as well. Thank you for this software
gitea-mirror 2026-05-05 06:06:22 -06:00
Author
Owner

@netblue30 commented on GitHub (Sep 28, 2016):

All done, use --veth-name=...

<!-- gh-comment-id:250235480 --> @netblue30 commented on GitHub (Sep 28, 2016): All done, use --veth-name=...
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#548
No description provided.