Finally getting back to this.  So I tried what you suggested, running the command from the config for vtysh.  The good news is the announcements of the other subnets are now seen by the other routers, the bad news is on the announcing router, the routes are shown as a blackhole and therefore disgarded.  So while the other networks now know where to send traffic for the local subnets, it cannot reach anything in those subnets with the exception of, the network the frr router is in.  Even though I set the ip route to Null0 for it, it does not black hole it.  Here is what I see for each on the local frr router now:

blackhole 10.223.112.0/22 proto 196 metric 20
10.223.119.0/24 dev ens5 proto kernel scope link src 10.223.119.4 metric 100
blackhole 10.223.120.0/22 proto 196 metric 20
blackhole 10.223.127.0/24 proto 196 metric 20

If I remove those ip route statements from the config, the announcment of these black holed networks just go away and they cannot be found.


Doug Tucker
Sr. Director of Networking and Linux Operations

o: 817.975.5832  
e: doug.tucker@navigaglobal.com  


Newscycle Solutions is now Naviga. Learn more.


CONFIDENTIALITY NOTICE: The contents of this email message and any attachments are intended solely for the addressee(s) and may contain confidential and/or privileged information and may be legally protected from disclosure. If you are not the intended recipient of this message or their agent, or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibite


From: Leonardo <leonardo.porto@iw.net.br>
Sent: Thursday, July 25, 2024 4:58 PM
To: Doug Tucker <doug.tucker@navigaglobal.com>; Donald Sharp <donaldsharp72@gmail.com>
Cc: frog@lists.frrouting.org <frog@lists.frrouting.org>
Subject: Re: [FROG] Migration scripts for FRR from Quagga
 
You don't often get email from leonardo.porto@iw.net.br. Learn why this is important

Are you using a single configuration file?
Quagga used to have separated files and daemons so the sintaxes had differences between them.


My FRR is version 8.3.1 using a single file and vtysh:


# conf t
FRR(config)# ip route ?
  A.B.C.D    IP destination prefix
  A.B.C.D/M  IP destination prefix (e.g. 10.0.0.0/8)


FRR(config)# ip route 1.1.1.1/24 ?
  A.B.C.D    IP gateway address
  INTERFACE  IP gateway interface name
     eth0 eth1 eth2 eth3 eth4 eth5 eth6 lo
  Null0      Null interface
  blackhole  Silently discard pkts when matched
  reject     Emit an ICMP unreachable when matched


Em 25/07/2024 19:47, Doug Tucker escreveu:
ip route help doesn't show that syntax as correct...any chance you have where you set that so it wasn't lost on a reboot and what it looks like?

Usage: ip route { list | flush } SELECTOR
       ip route save SELECTOR
       ip route restore
       ip route showdump
       ip route get [ ROUTE_GET_FLAGS ] ADDRESS
                            [ from ADDRESS iif STRING ]
                            [ oif STRING ] [ tos TOS ]
                            [ mark NUMBER ] [ vrf NAME ]
                            [ uid NUMBER ] [ ipproto PROTOCOL ]
                            [ sport NUMBER ] [ dport NUMBER ]
       ip route { add | del | change | append | replace } ROUTE

Assuming "add" is needed, it doesn't like the Null0 at the end.

 ip route add 10.223.0.0/22 Null0
Error: either "to" is duplicate, or "Null0" is a garbage.

Doug Tucker
Sr. Director of Networking and Linux Operations

o: 817.975.5832  
e: doug.tucker@navigaglobal.com  


Newscycle Solutions is now Naviga. Learn more.


CONFIDENTIALITY NOTICE: The contents of this email message and any attachments are intended solely for the addressee(s) and may contain confidential and/or privileged information and may be legally protected from disclosure. If you are not the intended recipient of this message or their agent, or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibite


From: Leonardo <leonardo.porto@iw.net.br>
Sent: Thursday, July 25, 2024 3:01 PM
To: Doug Tucker <doug.tucker@navigaglobal.com>; Donald Sharp <donaldsharp72@gmail.com>
Cc: frog@lists.frrouting.org <frog@lists.frrouting.org>
Subject: Re: [FROG] Migration scripts for FRR from Quagga
 

Hi Doug, I had a similar problem migrating from Quagga to FRR, I had to declare static routes (null destination) for the networks I was announcing:


For example:
ip route X.0.10.0/23 Null0
ip route X.0.20.0/23 Null0

ip route X.0.30.0/23 Null0



Em 25/07/2024 12:58, Doug Tucker escreveu:
I am under a time crunch now and have to get things going.  So with one of my routers, I copied the full bgpd.conf into frr.conf.  I am receiving all routes from the remote peer, however, the only outgoing route they are getting from this config is the /24 subnet that the frr router lives in.  The other 3 subnets that I have defined are not being propogated.  Any ideas what would cause this and how to resolve would be appriciated.  I've been searching for a frr.conf sample file on google I could use to compare to mine but coming up empty.

Doug Tucker
Sr. Director of Networking and Linux Operations

o: 817.975.5832  
e: doug.tucker@navigaglobal.com  


Newscycle Solutions is now Naviga. Learn more.


CONFIDENTIALITY NOTICE: The contents of this email message and any attachments are intended solely for the addressee(s) and may contain confidential and/or privileged information and may be legally protected from disclosure. If you are not the intended recipient of this message or their agent, or if this message has been addressed to you in error, please immediately alert the sender by reply email and then delete this message and any attachments. If you are not the intended recipient, you are hereby notified that any use, dissemination, copying, or storage of this message or its attachments is strictly prohibite


From: frog <frog-bounces+doug.tucker=navigaglobal.com@lists.frrouting.org> on behalf of Doug Tucker via frog <frog@lists.frrouting.org>
Sent: Wednesday, June 12, 2024 12:39 PM
To: Donald Sharp <donaldsharp72@gmail.com>
Cc: frog@lists.frrouting.org <frog@lists.frrouting.org>
Subject: Re: [FROG] Migration scripts for FRR from Quagga
 
Naviga WARNING: External email. Please verify sender before opening attachments or clicking on links.


_______________________________________________
frog mailing list
frog@lists.frrouting.org
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.frrouting.org%2Flistinfo%2Ffrog&data=05%7C02%7Cdoug.tucker%40navigaglobal.com%7C8f350f5a59ab458b8dff08dc8b12a04e%7C648867724322451bb3f5240270eb4e86%7C0%7C0%7C638538159342426343%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=Cp%2BCeOEZSN%2BR5wZwFVdsIDPT%2BAUKPpBL9vtdqximVps%3D&reserved=0