Is there is a proper guidance to update metallb version? I want to upgrade metallb from v0.8.1 to v0.9.3

Thank you

VM's provisioned on OpenStack have anti-spoofing measures which will drop packets if the source address is not matching to the assigned VM's ip. This prevents pod-to-pod traffic across the nodes getting routed when kube-router is used in direct routing mode.

Following are options to overcome this limitation:

• configure OpenStack to allo pod-to-pod traffic. Steps are documented for kubespray

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

We should add a CLI argument to add extra lines of configuration when the bootstrap configuration is applied to the device.

vrnetlab has no aspiration of becoming a generic configuration management system. The focus has always been, and will continue to be, on doing the minimal amount of configuration so that the router can then be configured through NETCONF/YANG. vrnetlab configures this boots

http://cnp3book.info.ucl.ac.be/2nd/html/principles/reliability.html#reliable-data-transfer-on-top-of-an-imperfect-link

A first glance, loosing frames might seem strange on single link.

should be:

A first glance, losing frames might seem strange on single link.

I think it would be useful to have a step-by-step tutorial (in the documentation) about how to install and integrate Alerta with BGPalerter.

Who can help with this? @mirceaulinic ?

Greetings,

is there a way to customize the output display of the routers? Preferably I would like to have the output as a full regular text displayed in-between current header & footer, instead of a scrollable window. also my custom vtysh at some cases outputs some html code that it doesn't get displayed in the output window.

Hey!

The documentation doesn't really deal with how expiration should be handled in Kafka. For example, if all topics are set to expire in 24 hours, new consumers don't have most information to be able to bootstrap. A simple solution is to restart the collector every 24 hour. Maybe a openbmpd could force a rolling disconnect instead? Or maybe I am missing another solution?

We keep messing up the Markdown documentation files. To avoid that, we should add markdownlint to the Travis build script.

First, thanks a lot for the application, its really great.

I just wanted to suggest to add in the Readme.md file the default URL of the application when launched

Environment

• Python version: 3.6.9
• Peering Manager version: master