Hello,
when we're talking about flowspec, we should keep in mind that another
possible address families exists already, while extending Bird. The code
should be more general - there're more AFI's comming from IETF (even
they're in draft phase currently).
With regards,
Daniel
On 10.6.2015 15:04,
Hello.
We have bird 1.4.5 on servers with CentOS 6.5.
We use it for advertise loopback sub-interfaces by OSPF. All subifs with /32
mask.
We use IPVS+keepalived to bring up and down loopback subifs.
Ifconfig:
# ifconfig
eth0.79 Link encap:Ethernet HWaddr 00:50:56:BA:37:70
inet addr:10
Thank you. its working fine after adding import in protocol direct.
Thanks,
Madhuri
On Thu, Jun 11, 2015 at 12:32 PM, wrote:
> We're using something like this.
>
> The important thing is that you need to see this as bird importing
> "protocol direct" routes into birds internal routing table, an
We're using something like this.
The important thing is that you need to see this as bird importing
"protocol direct" routes into birds internal routing table, and then you
need to export those to the ospf process.
By default i believe "import from protocol to bird" is allow any, but
"export f
