Supp,
I implemented bird in our Private cloud running proxmox to distribute
our public address with eBGP to our serverhost.
Through iBGP and a ucarp interface i have a HA gateway, the problem is
that our host receives the routes but there are multiple entry points to
our subnet ( the proxmox
From: dean
This last patch updates the function in OSPF that handles routing
table update notifications to use source information. Similar changes
are applied to the function that synchronizes OSPF routing tables with
nest's routing tables.
Finally, some work of area border routers (like decidin
From: dean
As with the previous LSAs, there won't be just simple destination
prefixes in the LSA, but pairs of (destination, source) prefixes
instead. The parsing and validation functions of external LSAs will
handle these changes.
The installation of the external routes in the OSPF routing tabl
From: dean
The add_network and ri_install_net functions that install networks
in the OSPF routing tables when processing intra-area and inter-area
routes were changed to use addr_data objects and support SADR entries.
The respective calls to these functions also use addr_data objects.
---
proto/
From: dean
Again with the same concept as for prefix LSAs, summary LSAs will
include pairs of (destination, source) prefixes instead of just
destination prefixes when SADR is enabled.
To match this change, the functions that handle the summary LSA
parsing and validation were also changed. Parsin
From: dean
Instead of prefix LSAs containing destination prefixes, they now
contain pairs of (destination, source) prefixes. Meaning there will
always be an even number of prefixes in the LSAs if SADR is enabled.
Functions that process the prefix LSAs now also take into account
that there are pa
From: dean
If SADR is enabled, to specify a source constraint for a route,
the RTA_SRC attribute, which contains the source address, is added
to the netlink message, and the source prefix length is set.
If SADR is enabled, the source attribute is also handled when
parsing routes in nl_parse_rout
From: dean
Two grammar rules were added that allow addition of source dependent
routes in the configuration of the static protocol.
route from via
route from via ""
Added a function that returns an addr_data object initialized from
a static_route object.
static_install and static_remove f
From: dean
When SADR is enabled, fib_node contains source address prefix
and prefix length.
A data structure addr_data was added to be passed to
fib_{get|find|route} and net_{get|find} functions and allow
the same call syntax for the functions, independently of
whether SADR is enabled. Two funct
Note: I used BIRD 1.6.2 when working on these patches. I don't know if
they will work on other versions.
The following patches extend the static and OSPFv3 protocol to support
Source Address Dependent Routing (SADR), also called Source Specific
Routing. This basically means that routing will t
From: dean
It compiles with the macro SADR_OSPF defined.
---
configure | 13 -
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/configure b/configure
index 09c6acf..ad92c7f 100755
--- a/configure
+++ b/configure
@@ -704,6 +704,7 @@ enable_debug
enable_memcheck
enable_c
On Sat, Mar 04, 2017 at 06:13:16PM +0100, Ruben Kerkhof wrote:
> The goal of this series is to make it possible to run autoreconf on a git
> checkout.
>
> It does this by moving configure.in to configure.ac and fixes deprecation
> warnings
> and errors generated by autoheader.
Hi
Thanks for th
Hi!
bgp_init() in proto/bgp/bgp.c does:
P->accept_ra_types = c->secondary ? RA_ACCEPTED : RA_OPTIMAL;
and then bgp_rx_open() in proto/bgp/packets.c does:
if (p->add_path_tx)
p->p.accept_ra_types = RA_ANY;
As bgp_init() seems to only be called at configuration time, this
means that if y
On 03/06/2017 12:40 PM, Dean wrote:
On 03/06/2017 12:10 PM, Toke Høiland-Jørgensen wrote:
Dean Luga writes:
Hmm, I have been running babeld with source-specific routes for quite
some time and never run into this problem. Are you sure you didn't
botch
the netlink calls? ;)
I don't thi
On 03/06/2017 12:10 PM, Toke Høiland-Jørgensen wrote:
Dean Luga writes:
Hmm, I have been running babeld with source-specific routes for quite
some time and never run into this problem. Are you sure you didn't botch
the netlink calls? ;)
I don't think so, I even tested inserting the rout
Dean Luga writes:
> Hmm, I have been running babeld with source-specific routes for quite
> some time and never run into this problem. Are you sure you didn't botch
> the netlink calls? ;)
>
> I don't think so, I even tested inserting the routes with ip route
> without running bird. It was a d
>
> Hmm, I have been running babeld with source-specific routes for quite
> some time and never run into this problem. Are you sure you didn't botch
> the netlink calls? ;)
I don't think so, I even tested inserting the routes with ip route without
running bird. It was a documented behavior in net
Dean writes:
> There is already an implementation for that here
> (https://github.com/jech/babeld), if you want to check. I think this supports
> both IPV6_SUBTREES and policy routing, not sure.
I meant for the Bird Babel implementation. And yeah, that was what I was
referring to with policy rou
There is already an implementation for that here
(https://github.com/jech/babeld), if you want to check. I think this
supports both IPV6_SUBTREES and policy routing, not sure.
And I encountered another problem with IPV6_SUBTREES yesterday. Having
source constrained routes and normal routes in
Dean writes:
> Static routes can be added in the configuration file with a source
>
> address constraint. To match an entry in the routing table, you have to
> match both the source and destination address. The same thing as running
> the command:
>
> ip -6 route add 2001:db9:1::/64 from 2001:db9
20 matches
Mail list logo
