Feature
ExaBGP Compatibility
- Automatic detection and migration of ExaBGP configuration files
ze exabgp pluginruns ExaBGP processes with ze as the BGP engine- Two modes: standalone (stdin/stdout) for development, TLS connect-back when launched by engine
- Bidirectional translation: ze JSON events to ExaBGP JSON, ExaBGP text commands to ze commands
- Forward-barrier flush injected after route commands for ordering guarantees
ze exabgp migrateconverts ExaBGP configs to ze formatze exabgp migrate --envconverts ExaBGP INI environment files to ze config- An omitted or empty ExaBGP
familyblock migrates to all address families registered in the current binary. An explicit block keeps only the named families; migration does not replace ExaBGP's implicit all-family behavior with Ze's IPv4-unicast default. - An ExaBGP per-family ADD-PATH limit (
add-path { ipv4 unicast limit 10; }) migrates to the receive half of Ze's limit,family { ipv4/unicast { limit { receive 10; } } }. ExaBGP's limit is the receive request its OPEN advertises (PATHS-LIMIT), and ExaBGP has no send-side limit, so the migration writes nosendleaf. A family named without a limit migrates with nolimitcontainer.