So, from the sounds of it most are saying for low cost, the way to go would be a software router, which I was trying to avoid. To answer the bandwidth question, we would have three 10G ports with three different carriers and at max push 10Gbps of total traffic to start. I think this leaves me with hardware routers that can support full BGP tables. So, who actually sells full bgp routers. So far on my list I have: Juniper MX Series Brocade MLXe or CER Cisco ASR 9K Huawei NE40E-X1-M4 ZTE, not sure which model? ALU 7750 Besides the above, am I missing anyone else that makes a true carrier grade hardware router? On Wed, May 20, 2015 at 9:54 AM, Pavel Odintsov <pavel.odintsov@gmail.com> wrote:
Hello!
Yes, we could run route add / route del when we got any announce from external world with ExaBGP directly. I have implemented custom custom Firewall (netmap-ipfw) management tool which implement in similar manner. But I'm working with BGP flow spec. It's so complex, standard BGP is much times simpler.
And I could share my ExaBGP configuration and hook scripts.
ExaBGP config: https://github.com/FastVPSEestiOu/fastnetmon/blob/master/src/scripts/exabgp_...
Hook script which put all announces to Redis Queue:
https://github.com/FastVPSEestiOu/fastnetmon/blob/master/src/scripts/exabgp_...
But full BGP route table is enough big and need external processing.
But yes, with some Python code is possible to implement route server with ExaBGP.
On Wed, May 20, 2015 at 5:25 PM, Aled Morris <aledm@qix.co.uk> wrote:
On 20 May 2015 at 15:00, Pavel Odintsov <pavel.odintsov@gmail.com> wrote:
Yes, you could do filtering with Quagga. But Quagga is pretty old tool without multiple dynamic features. But with ExaBGP you could do really any significant route table transformations with Python in few lines of code. But it's definitely add additional point of failure/bug.
Couldn't your back-end scripts running under ExaBGP also manage the FIB, using standard Unix tools/APIs?
Managing the FIB is basically just "route add" and "route delete" right?
Aled
-- Sincerely yours, Pavel Odintsov