Hi,
I am subscribed to the list, so no need to CC me explicitly.

On 2015-08-21 20:18, Paul Jakma wrote:
Hi,

Thanks for putting those into a git tree. Havn't looked yet.

I'm wondering if, instead of defining a new realm ID for a peer or set
on routes, is there any scope for using an existing BGP protocol
number and just sending that as a context ID down to zebra?

E.g.... BGP community value?

No, I don't think it is possible, because the realm has different meaning (see [1] for example use) and there could be multiple communities, but just a single realm. From the example [1]: I set a community for both the traffic type (national or international) and peer (AS or some other ID), then on the remote I use one or the other depending on what is the router's role

[1] https://lists.quagga.net/pipermail/quagga-dev/2015-June/012896.html


regards,

Paul

On Fri, 10 Jul 2015, Kaloyan Kovachev wrote:

Hello,

On 2015-07-02 03:03, Donald Sharp wrote:

My original point about breaking up the patches into separate changes still stands.

And it's done:
https://github.com/KaloNK/quagga/compare/master...realms_patchset

I have split the patch in 3 steps:
1. Initial support (conditional compile options and ./lib changes) - https://github.com/KaloNK/quagga/commit/3861c3c7f6ddbb9cb983ef5effda9bb4b3315aed 2. Zebra changes - https://github.com/KaloNK/quagga/commit/4b792bd00c9539c5487a78be2031193909fcca85 3. BGPD changes - https://github.com/KaloNK/quagga/commit/3113b7aa4dba8d3614bcd304614f48d26d09db5f

And the two unrelated (single line) patches to debug messages:
1. Fix _netlink_route_debug message - https://github.com/KaloNK/quagga/commit/1037020f7708c599ce9c9c8b2e36463e532aaa98 2. Show command string in addition to node on install failure - https://github.com/KaloNK/quagga/commit/106cc40af363f5dff686aa8dda98ba02ad519b09

_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev


_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev

Reply via email to