BGP: Disallow AS Sets by default

For a long time, AS Sets have been considered obsolete
but they were still valid by the original RFC. Recently,
RFC 9774 flipped this and AS Sets are now formally deprecated.

Therefore, all BGP sessions will now by default reject routes
containing AS Sets in their AS Paths. If you want to keep the
old behavior, you may simply state

    allow as set;

in every BGP protocol configuration where you want to accept AS Sets.

This closes #248.

diff --git a/proto/bgp/config.Y b/proto/bgp/config.Y
index 93df8f9660ac902311b591778a478bfabd8c68a8..d73c0317c10b3a113c66576a38118d7ff04e6d5b 100644 (file)
--- a/proto/bgp/config.Y
+++ b/proto/bgp/config.Y
@@ -73,7 +73,7 @@ bgp_proto_start: proto_start BGP {
      BGP_CFG->enable_hostname = 0;
      BGP_CFG->capabilities = 2;
      BGP_CFG->interpret_communities = 1;
-     BGP_CFG->allow_as_sets = 1;
+     BGP_CFG->allow_as_sets = 0;
      BGP_CFG->default_local_pref = 100;
      BGP_CFG->gr_mode = BGP_GR_AWARE;
      BGP_CFG->gr_time = 120;