[quagga-users 14247] Re: BGP Replay Tool

Eng. Bahaa bahaaqm at yahoo.com
Fri Mar 4 04:03:56 GMT 2016


Hi Donald,
BGP Replay Tool v0.1 is available now!

Technical report is available on: http://caia.swin.edu.au/reports/160304A/CAIA-TR-160304A.pdf
BRT-v0.1 is available on: http://caia.swin.edu.au/tools/bgp/brt-0.1.tgz

Regards

Bahaa

      From: "quagga-users-request at lists.quagga.net" <quagga-users-request at lists.quagga.net>
 To: quagga-users at lists.quagga.net 
 Sent: Saturday, October 10, 2015 10:00 PM
 Subject: Quagga-users Digest, Vol 147, Issue 3
   
Send Quagga-users mailing list submissions to
    quagga-users at lists.quagga.net

To subscribe or unsubscribe via the World Wide Web, visit
    https://lists.quagga.net/mailman/listinfo/quagga-users

You can reach the person managing the list at
    quagga-users-owner at lists.quagga.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Quagga-users digest..."


Today's Topics:

  1. [quagga-users 14152] Re: BGP replay (Donald Sharp)
  2. [quagga-users 14153] Re: default routes from BGP & nothing in
      kernel routing table (Donald Sharp)


----------------------------------------------------------------------

Message: 1
Date: Fri, 9 Oct 2015 09:51:19 -0400
From: Donald Sharp <sharpd at cumulusnetworks.com>
To: "Eng. Bahaa" <bahaaqm at yahoo.com>
Cc: "quagga-users at lists.quagga.net" <quagga-users at lists.quagga.net>
Subject: [quagga-users 14152] Re: BGP replay
Message-ID:
    <CAK989ycKeEr_H9RjaJUK3JPZJs305H2eHhciuZKVr2-NPDmDkg at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Bahaa -

I'm not aware of any other tools out there that can do this either.

Implementing what you proposed sounds awesome.

donald

On Thu, Oct 8, 2015 at 9:58 PM, Eng. Bahaa <bahaaqm at yahoo.com> wrote:

> Hi everyone,
> I am interesting to replay historical BGP events into my testbed.
> As I know, there are two tools available: MRT dump file manipulation
> toolkit (MDFMT) and bgpsimple.
> while the MDFMT is a BGP replay tool with python, bgsimple is a an
> injection tool with perl.
> Both of them have limitation with community attribute. In addition, the
> MDFMT is not compatible with new version of python and required
> modification in the kernel.
> Is anyone know about other tools which I can use it; otherwise, I am going
> to modify or develop bgpsimple to be a replay tool instead of injecting
> tool and try to fix the community attribute issue as well.
>
> Regards
>
> Bahaa
>
>
>
> _______________________________________________
> Quagga-users mailing list
> Quagga-users at lists.quagga.net
> https://lists.quagga.net/mailman/listinfo/quagga-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quagga.net/pipermail/quagga-users/attachments/20151009/d050bd63/attachment-0001.html>

------------------------------

Message: 2
Date: Fri, 9 Oct 2015 09:56:19 -0400
From: Donald Sharp <sharpd at cumulusnetworks.com>
To: "Christopher J. Umina" <chris+quagga at uminac.com>
Cc: quagga-users <quagga-users at lists.quagga.net>
Subject: [quagga-users 14153] Re: default routes from BGP & nothing in
    kernel routing table
Message-ID:
    <CAK989yfa4THYDBTA01UVdk_AL=dCRMPMkDh1ZPm68CEFKpPVBA at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Christopher -

Turn on 'debug zebra events' and 'debug 'zebra kernel' and 'debug zebra
rib'.

What do the log files tell you when the default route is injected by bgp
into zebra?

donald

On Thu, Oct 1, 2015 at 1:38 PM, Christopher J. Umina <
chris+quagga at uminac.com> wrote:

> Hello everybody,
>
> I'm running a very basic configuration on my internal network with some
> anycast DNS servers. On each server, I run FreeBSD and quagga. The server
> lives in a /29 with two upstream Cisco L3 switches. From each L3 switch the
> server receives a default route only. This all works as expected.
>
> The problem is that although the BGP sessions come up and the routes are
> in the BGP routing table on the server, a default route is never injected
> into the server's kernel routing table.
>
> Have I missed some configuration here, or is this a bug?
>
> Some information:
>
> # show version
> Quagga 0.99.24.1 ().
> Copyright 1996-2005 Kunihiro Ishiguro, et al.
> configured with:
>    --enable-user=quagga --enable-group=quagga
> --sysconfdir=/usr/local/etc/quagga --localstatedir=/var/run/quagga
> --enable-vtysh --disable-irdb --enable-isisd --disable-isis-topology
> --enable-bgp-announce --enable-opaque-lsa --without-libpam --enable-pimd
> --enable-rtadv --disable-snmp --disable-tcp-zebra --prefix=/usr/local
> --mandir=/usr/local/man --infodir=/usr/local/info/
> --build=amd64-portbld-freebsd10.1
> # show run
> Building configuration...
>
> Current configuration:
> !
> log syslog
> !
> interface em0
>  ipv6 nd suppress-ra
>  no link-detect
> !
> interface lo0
>  no link-detect
> !
> router bgp 64625
>  bgp router-id 10.0.20.142
>  bgp log-neighbor-changes
>  no bgp default ipv4-unicast
>  network 10.1.1.0/32
>  network 10.1.2.0/32
>  neighbor 10.0.20.138 remote-as 64624
>  neighbor 10.0.20.138 description 'csw01.wkf01'
>  neighbor 10.0.20.138 activate
>  neighbor 10.0.20.139 remote-as 64624
>  neighbor 10.0.20.139 description 'csw02.wkf01'
>  neighbor 10.0.20.139 activate
> !
> line vty
> !
> end
> # show ip bgp
> BGP table version is 0, local router ID is 10.0.20.142
> Status codes: s suppressed, d damped, h history, * valid, > best, =
> multipath,
>              i internal, r RIB-failure, S Stale, R Removed
> Origin codes: i - IGP, e - EGP, ? - incomplete
>
>    Network          Next Hop            Metric LocPrf Weight Path
> *  0.0.0.0          10.0.20.138                            0 64624 i
> *>                  10.0.20.139                            0 64624 i
> *> 10.1.1.0/32
>                    0.0.0.0                  0        32768 i
> *> 10.1.2.0/32
>                    0.0.0.0                  0        32768 i
> # show ip route
> Codes: K - kernel route, C - connected, S - static, R - RIP,
>        O - OSPF, I - IS-IS, B - BGP, P - PIM, A - Babel,
>        > - selected route, * - FIB route
>
> C>* 10.0.20.136/29 is directly connected, em0
> C>* 10.1.1.0/32 is directly connected, lo0
> C>* 10.1.2.0/32 is directly connected, lo0
> C>* 127.0.0.0/8 is directly connected, lo0
> # exit
> # uname -or
> FreeBSD 10.2-RELEASE
>
> Thank you!
>
> _______________________________________________
> Quagga-users mailing list
> Quagga-users at lists.quagga.net
> https://lists.quagga.net/mailman/listinfo/quagga-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quagga.net/pipermail/quagga-users/attachments/20151009/8c6b98e6/attachment-0001.html>

------------------------------

_______________________________________________
Quagga-users mailing list
Quagga-users at lists.quagga.net
https://lists.quagga.net/mailman/listinfo/quagga-users


End of Quagga-users Digest, Vol 147, Issue 3
********************************************


  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quagga.net/pipermail/quagga-users/attachments/20160304/a1276097/attachment-0001.html>


More information about the Quagga-users mailing list