Comments (3)
snar
commented on July 20, 2024
On Tue, Jan 11, 2022 at 11:25:39AM -0800, Keenan Tims wrote:
Currently bgpq3 makes address family selection mutually exclusive. I propose
allowing generation of mixed lists.
What is the use-case for such lists ? Looks like my imagination fails
to find one:
- on BGP peering you shall have different sessions for different families
to make sure that next-hop is actually reachable (and it implies different
policies/prefix-lists per family)
- for filtering purposes, you shall have different filters applied
per family.
- something else ?
… I am not sure which underlying platforms support mixing address families, but
it is supported in JunOS both with prefix-lists and route-filters, and would
also be useful for external integration using e.g. JSON or user defined output
to not have to merge the lists externally. For platforms that don't support
combined lists, perhaps it could be implemented by generating the configuration
for the two lists in one pass.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.*Message ID:
***@***.***>
from bgpq3.
ktims
commented on July 20, 2024
We have built our existing templates around combined policy-statements. Usually other route policy is shared between address families (e.g. communities, any peer-specific policy tweaks, etc.), and I don't see any reason to double the amount of boilerplate and double the amount of work when policy changes are needed if the router can intelligently treat all prefixes generically as objects. If it's necessary to have AF-specific policy, it seems more logical to me to put that exception as a policy rule, rather than having an entirely separate policy. It seems to me to reduce the opportunity for human error and simplify/shrink the configuration to have one place that it all lives.
Our existing infrastructure for maintaining these filters is aging and unsupported, and I wanted to use bgpq3 to replace some existing manual procedures and as part of renewed automation, but without changing the templates entirely. Dealing with the limitation on the automation side is straightforward, but for manual use it's pretty cumbersome to manually stitch the lists together.
FWIW I do have several (uncommon) BGP sessions that carry both IPv6 and IPv4 routes for..legacy..reasons.
from bgpq3.
snar
commented on July 20, 2024
Ok, makes sense. Another scenario when such filters may make sense
is application-level access-lists (nginx, squid and so on), so, it's
implemented and uploaded to github head.
Notes:
- implemented for Juniper, JSON and User-Defined formats only
- is not compatible with minimum prefix length (-m) and more-specific
(-r/-R) filters.
- for Juniper, order of prefixes in generated prefix-list may be not
the same as in juniper output. Example: prefix-list generated with
bgpq3 -Jx as9002 ends with:
policy-options {
replace:
prefix-list NN {
[....]
195.133.47.0/24;
213.178.155.0/24;
213.226.112.0/24;
213.226.114.0/24;
2001:67c:2fe4::/48;
2a02:2d8::/32;
2a07:7940:fffc::/48;
}
}
(all ipv6 prefixes are placed after ipv4), however, show | compare on router
shows prefix 2001:67c:2fe4::/48 placed before 213.178.155.0/24:
+ 195.133.47.0/24;
+ 2001:67c:2fe4::/48;
+ 213.178.155.0/24;
+ 213.226.112.0/24;
+ 213.226.114.0/24;
+ 2a02:2d8::/32;
+ 2a07:7940:fffc::/48;
+ }
As the same misorder does not happen with route-filter-lists (-Jxz)
and route-filters, let me consider this as non-issue.
from bgpq3.
Related Issues (20)
- FATAL ERROR:EOF from RADB (dequeue, ripe) Exit Code 255 HOT 2
- Clarify Nokia (classic CLI) options HOT 2
- Feature Request: Do not print anything if 0 objects received HOT 4
- bgpq3 exit code is 255, stderr: b'FATAL ERROR:select timeout\n' HOT 2
- Limitations of bgpq3 -S HOT 1
- filter route and AS (possible feature request) HOT 2
- Rationale behind the recommended sources HOT 1
- Cisco IOS XR format lacks one space in indentation HOT 1
- Sequence numbers not respected with empty result HOT 1
- Subnet length wrong HOT 3
- Uncorrected as-patch filter for Huawei HOT 1
- Possibility of tagging a new release HOT 1
- Add BGPQ3 to Arista EOS HOT 5
- About the operation when multiple database sources are specified by'-S flag'
- BSD-3 files
- Invalid symbol in ASN errors HOT 1
- Certain prefixes that show up in the RIPE GUI don't get outputted by BGPq3 when the ASSet is queried HOT 8
- missing some prefixes HOT 11
- Install on ASR9K
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from bgpq3.