[FROG] Migration scripts for FRR from Quagga

[Donald Sharp]

https://docs.frrouting.org/en/latest/bgp.html#require-policy-on-ebgp

On Wed, May 22, 2024 at 7:33 PM Doug Tucker <doug.tucker at navigaglobal.com>
wrote:

> Thanks Donald, and sorry for the late response.  I am just getting back to
> this.  I found this in the documentation:
>
> Configuration for the daemon should be saved in the FRR integrated
> configuration file located in /etc/frr/frr.conf, see Integrated Config
> File <https://docs.frrouting.org/en/latest/basic.html#config-file> for
> more information on system configuration.
> Prior versions of FRR supported reading and writing per-daemon config
> files; however, with the introduction of the centralized management daemon
> mgmtd this could no longer be supported.
> The interesting thing is it did seem to read my zebra.conf, but completely
> skipped the bgpd.conf.  So I tried copying the contents of the bgpd.conf
> into frr.conf and the daemon starts, and doing a show run it looks pretty
> identical to quagga system side by side with a few caveates (hostname for
> instance shows up twice with 2 different values).  But, I'm not getting the
> advertised routes from remote.  The logs are showing me this.  So it sees
> them, but something is missing that wasn't needed in quagga.
> 2024/05/22 23:04:45 BGP: [RZMGQ-A03CG] 169.254.244.13(Unknown) rcvd UPDATE
> about 10.0.0.0/8 IPv4 unicast -- DENIED due to: inbound policy missing
> 2024/05/22 23:04:45 BGP: [RZMGQ-A03CG] 169.254.244.13(Unknown) rcvd UPDATE
> about 192.168.0.0/16 IPv4 unicast -- DENIED due to: inbound policy missing
>
> 2024/05/22 23:04:45 BGP: [RZMGQ-A03CG] 169.254.244.13(Unknown) rcvd UPDATE
> about 172.16.0.0/12 IPv4 unicast -- DENIED due to: inbound policy missing
>
> I've been reading for a while now but not finding an resolution.
>
>
> *Doug Tucker*
>
> ------------------------------
> *From:* Donald Sharp <donaldsharp72 at gmail.com>
> *Sent:* Wednesday, April 17, 2024 2:35 PM
> *To:* Doug Tucker <doug.tucker at navigaglobal.com>
> *Cc:* frog at lists.frrouting.org <frog at lists.frrouting.org>
> *Subject:* Re: [FROG] Migration scripts for FRR from Quagga
>
> You don't often get email from donaldsharp72 at gmail.com. Learn why this is
> important <https://aka.ms/LearnAboutSenderIdentification>
>
> Naviga WARNING: External email. Please verify sender before opening
> attachments or clicking on links.
>
> In general you should just be able to use the Quagga configs directly in
> FRR(There are a couple caveats of course ).  I am not aware of any
> conversion/migration scripts though.  Have you tried just loading the
> config and seeing what happens? Then comparing a show run to the saved
> config?
>
> donald
>
> On Wed, Apr 17, 2024 at 4:29 PM Doug Tucker via frog <
> frog at lists.frrouting.org> wrote:
>
>
>
>
> ---------- Forwarded message ----------
> From: Doug Tucker <doug.tucker at navigaglobal.com>
> To: "frog at lists.frrouting.org" <frog at lists.frrouting.org>
> Cc:
> Bcc:
> Date: Wed, 17 Apr 2024 19:23:33 +0000
> Subject: Migration scripts for FRR from Quagga
> I am needing to undertake migrating from all of my quagga instances to
> frr.  I have read through the general documentation but before I started
> from scratch I thought I would see if there were some migration/conversion
> scripts available for existing quagga installations.  Thank you for your
> assistance.
>
> *Doug Tucker*
>
>
>
>
> ---------- Forwarded message ----------
> From: Doug Tucker via frog <frog at lists.frrouting.org>
> To: "frog at lists.frrouting.org" <frog at lists.frrouting.org>
> Cc:
> Bcc:
> Date: Wed, 17 Apr 2024 19:23:33 +0000
> Subject: [FROG] Migration scripts for FRR from Quagga
> _______________________________________________
> frog mailing list
> frog at lists.frrouting.org
> https://lists.frrouting.org/listinfo/frog
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.frrouting.org/pipermail/frog/attachments/20240523/3bef10ea/attachment.htm>