>> (2) make sure that SADR routes and non-SADR routes can coexist in the
>> same routing table.
>
> Is that something that can be fixed in BIRD? Isn't it just a kernel
> problem?
Kernel may be fixed once. Or you may have two kernel protocols mapping
the BIRD's table to one kernel table with SADR a
Dean writes:
> On 03/07/2017 09:51 PM, Toke Høiland-Jørgensen wrote:
>> Dean writes:
>>
>>> On 03/07/2017 09:23 PM, Toke Høiland-Jørgensen wrote:
>>>
>>> Basically, I want to do the opposite: We are going to have several
>>> (well, at least two) protocols that understand source-specific rout
On 03/07/2017 09:51 PM, Toke Høiland-Jørgensen wrote:
Dean writes:
On 03/07/2017 09:23 PM, Toke Høiland-Jørgensen wrote:
Basically, I want to do the opposite: We are going to have several
(well, at least two) protocols that understand source-specific routing,
so the nest data structures
Dean writes:
> On 03/07/2017 09:23 PM, Toke Høiland-Jørgensen wrote:
>
> Basically, I want to do the opposite: We are going to have several
> (well, at least two) protocols that understand source-specific routing,
> so the nest data structures should work with both. And since Babel at
> l
On 03/07/2017 09:23 PM, Toke Høiland-Jørgensen wrote:
Basically, I want to do the opposite: We are going to have several
(well, at least two) protocols that understand source-specific routing,
so the nest data structures should work with both. And since Babel at
least is perfectly happy to mix s
Dean writes:
> On 03/07/2017 12:05 PM, Ondrej Zajicek wrote:
>> On Tue, Mar 07, 2017 at 12:56:26AM +0100, Dean Luga wrote:
>>> 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
>>>
Dean writes:
> On 03/07/2017 01:17 PM, Toke Høiland-Jørgensen wrote:
>> Dean Luga writes:
>>
>>> That is correct, it will not be compatible with other OSPF implementations.
>>>
>>> From what I've searched, there is no standard for supporting SADR in
>>> OSPF, only some IETF drafts (some of whic
> On Mar 7, 2017, at 1:16 PM, Thomas@PhaseHosting
> wrote:
>
> Supp,
>
> I want to send the med with eBGP to my hosts their routers so i can influence
> where the network traffic enters my virtual envirement. I have 3 hypervisors
> that run bird.
>
> I can only controll the traffic from my
I always use aspath stuffing rather than MED for this kind of thing.
After localpref, the next level of choice for a bgp route is the AS path
length, with shorter winning.
Say you want prefix 1 to always prefer hv1 and prefix2 to prefer hv2. On
hv2, prepend your AS onto prefix 1 and on hv1, pr
Hi Thomas,
You could also consider to prepend your AS in the path. Just some random
google result:
https://www.juniper.net/documentation/en_US/junos/topics/usage-guidelines/policy-prepending-as-numbers-to-bgp-as-paths.html
In Bird:
export filter {
if source = RTS_STATIC then {
On 03/07/2017 01:17 PM, Toke Høiland-Jørgensen wrote:
Dean Luga writes:
That is correct, it will not be compatible with other OSPF implementations.
From what I've searched, there is no standard for supporting SADR in
OSPF, only some IETF drafts (some of which expired) that describe the
desir
Supp,
I want to send the med with eBGP to my hosts their routers so i can
influence where the network traffic enters my virtual envirement. I have
3 hypervisors that run bird.
I can only controll the traffic from my virtual envirement to the
internet, because this runs on bird and ucarp. So
On 7 March 2017 at 05:57, Clément Guivy wrote:
> Hello, I am considering the setup of BIRD as a router to handle our
> internet traffic. One information I fail to find is hardware requirements.
>
Clément,
Let's just clear one thing up straight away -- BIRD is a daemon for routing
protocols, no
On 03/07/2017 12:05 PM, Ondrej Zajicek wrote:
On Tue, Mar 07, 2017 at 12:56:26AM +0100, Dean Luga wrote:
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} fun
On Tue, Mar 07, 2017 at 03:43:13PM +0100, Thomas@PhaseHosting wrote:
> Supp,
>
> thnqx for the reply,
>
> The BGP i have figured out and i have confirmation from my host they accept
> customer-set MEDs. Only i couldn't get these working and i found 2 posts on
> the internet with a different confi
Hello, Ondrej.
2017-03-07 20:32 GMT+03:00 Ondrej Zajicek :
> This is a correct way, but (135402, 101) is not a correct community -
> each field is 16b, so maximum is (65535, 65535). There are probably
> related error messages in the log.
Yeah. You're right. But with other community values I don't
On Tue, Mar 07, 2017 at 08:01:53PM +0300, Anton Danilov wrote:
> Hello folks.
> I have a strange desire to set the bgp community to static routes to
> implement the advanced route policy on my border router.
> I've written this configuration of additional static protocol with
> only default route t
Hello folks.
I have a strange desire to set the bgp community to static routes to
implement the advanced route policy on my border router.
I've written this configuration of additional static protocol with
only default route to advertise it to other peers:
protocol static def_route
{
route 0.0
Hi.
Here is a small patch which allows non-zero address scopes on
non-link-local addresses. This is required to create connections inside
a VRF domain, as the Linux kernel documentation states.
In combination with multiple RIBs and FIBs, this makes Bird completely
VRF-capable. Therefore, this pat
Supp,
thnqx for the reply,
The BGP i have figured out and i have confirmation from my host they
accept customer-set MEDs. Only i couldn't get these working and i found
2 posts on the internet with a different configuration and i don't know
which one is the right one, "med metric 10;" or "def
On Tue, Mar 7, 2017 at 12:17 AM, Ondrej Zajicek wrote:
> 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
>> war
Hello Clement, even the most entry level server these days will meet your
requirements. Bird is very lean, a system with 2 cores and 4 gbps of ram is
plenty for what you described.
The only thing I would suggest is you look at Intel NIC’s like the i340 or i350
which will help a great deal if y
Hi,
Here is my x86 router configuration:
OS: FreeBSD 10.2 64bit
Bird 1.6.3
CPU Intel E5-2609v2
Memory 16GB
Here is top result for bird:
27 processes: 1 running, 26 sleeping
CPU: 13.0% user, 0.0% nice, 1.8% system, 1.7% interrupt, 83.6% idle
Mem: 504M Active, 112M Inact, 875M Wired, 518M Buf
Hello, I am considering the setup of BIRD as a router to handle our internet
traffic. One information I fail to find is hardware requirements. My use
case is as follows :
- Two transit providers, each sending a full internet view
- Two peerings on an IXP (less than 100k routes e
Hello Thomas,
I’m a tiny bit confused by your question, but here is my best attempt to answer
it. In regards to multiple routers say you have .4 and .5 both with a HA
address of .1 when using eBGP it will likely be the “old first” as you say that
your host will pass the INBOUND data to. In rega
Dean Luga writes:
> That is correct, it will not be compatible with other OSPF implementations.
>
> From what I've searched, there is no standard for supporting SADR in
> OSPF, only some IETF drafts (some of which expired) that describe the
> desired behavior.
>
> One or two of these drafts plan
I see, I'll look into it.
On 7 Mar 2017 11:49, "Ondrej Zajicek" wrote:
> On Tue, Mar 07, 2017 at 12:56:25AM +0100, Dean Luga wrote:
> > From: dean
> >
> > It compiles with the macro SADR_OSPF defined.
> > ---
> > configure | 13 -
> > 1 file changed, 12 insertions(+), 1 deletion(-)
That is correct, it will not be compatible with other OSPF implementations.
>From what I've searched, there is no standard for supporting SADR in OSPF,
only some IETF drafts (some of which expired) that describe the desired
behavior.
One or two of these drafts plan to use OSPF extended LSAs to su
On Tue, Mar 07, 2017 at 12:56:26AM +0100, Dean Luga wrote:
> 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 sy
On Tue, Mar 07, 2017 at 12:56:25AM +0100, Dean Luga wrote:
> 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
Hi
The script 'configure' is autogenerated,
Dean Luga writes:
> I used the configure switch since SADR makes changes to the LSAs and
> it will slightly impact network traffic even with source 0::/0. If
> someone doesn't want that, they can disable it.
As in, when you enable SADR all routes announced now carry a SADR? Does
that mean bird w
I used the configure switch since SADR makes changes to the LSAs and it
will slightly impact network traffic even with source 0::/0. If someone
doesn't want that, they can disable it.
About the name, you are right, it should be changed.
On 7 Mar 2017 10:32, "Toke Høiland-Jørgensen" wrote:
Dean
Dean Luga writes:
> From: dean
>
> It compiles with the macro SADR_OSPF defined.
Quick comment (I'll look over the rest in more detail later): Why is
source address routing guarded by a configure switch? Shouldn't Bird be
able to understand source-specific routing always, and have the use of
th
33 matches
Mail list logo
