I recently added support for automatically configuring MetalLB in BGP mode in the dev env by running inv dev-env with --protocol bgp or -p bgp. It would be helpful to add similar support for configuring MetalLB in layer2 mode. It would be run with --protocol layer2 or -p layer2.

What I would expect this to do is to configure MetalLB with a minimal ConfigMap that includes a small p

In zebra/rt_netlink.c, we call vrf_lookup_by_id() when we get a route to find the associated vrf object for that table.

This should be improved to be a hash table mapping of Table ID to zebra_vrf object.

You would need to create a hash table probably in zebra/zebra_vrf.h that uses the table_id hash as a key and then update the code in vrf_lookup_by_id() to use this.

This shoul

Add a prometheus exporter! Example outputs:

• Layer 2
• Layer 3
• TCP LoadBalancer
• IPVS LoadBalancer (once @yastij implements it ;)
• Control Pane HA

When running the Docker image behind a Proxy the page will show for example:

Your IP address: 172.17.0.1

Although the (Apache) proxy does send the X-Forwarded-For header the Apache instance running inside the Docker container doesn't do anything with it.

Enabling and configuring mod_remote_ip in the Docker container should solve this: https://httpd.apache.org/docs/2.4/mod/mod_r