Editing Quagga in VE
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
− | Quagga inside a | + | Quagga inside a VE requires 3 Linux capabilities configured for the container on the hostnode: |
− | vzctl set | + | vzctl set 24 --capability net_admin:on --save |
− | vzctl set | + | vzctl set 24 --capability net_raw:on --save |
− | vzctl set | + | vzctl set 24 --capability sys_admin:on --save |
When they are not configured, you'll see the following symptoms when starting up zebra: | When they are not configured, you'll see the following symptoms when starting up zebra: | ||
Line 19: | Line 19: | ||
exit_group(1) = ? | exit_group(1) = ? | ||
− | + | Note: granting capabilities for a container can have reduced security implications - ensure you fully understand the repercussions of granting any of the above capabilities before using in production. | |
[[Category: Networking]] | [[Category: Networking]] |