ipaggmanip

Combine labels equal in their high-order bits

$ ipaggmanip [[-p|--prefix]] [16] [path/to/file]

$ ipaggmanip --cut-smaller [100] --cull-labels [5] [path/to/file]

$ ipaggmanip [[-P|--posterize]] [path/to/file]

ipaggmanip NET/MASK [ table TABLE_ID ] [ OPTIONS ]

NET/MASK
    The destination network prefix of the aggregate route to be manipulated, specified in CIDR notation (e.g., 192.168.1.0/24).

table TABLE_ID
    Specifies the routing table ID where the aggregate route resides. If omitted, the default table (main) is assumed.

metric METRIC
    Sets the preference value for the route. Routes with lower metrics are preferred.

dev DEVICE
    Specifies the output network device for the aggregate route.

via GATEWAY
    Specifies the address of the gateway to which packets for this aggregate should be forwarded.

src SOURCE_IP
    Specifies the source address to be used when sending packets via this aggregate route.

proto PROTOCOL
    Sets the routing protocol identifier, such as kernel, boot, static, etc.

scope SCOPE
    Defines the scope of the destination address, e.g., host, link, or global.

flags FLAGS
    Allows setting various route flags (e.g., onlink, connected) that influence route behavior. Specific flags supported would depend on kernel and iproute2 versions.

ipaggmanip is a highly specialized, low-level utility associated with the iproute2 suite, primarily designed for direct manipulation of IP aggregate routes within the Linux kernel's Forwarding Information Base (FIB). Unlike common ip route commands, which primarily manage individual routes or create aggregates, ipaggmanip appears to target the modification of properties of already existing aggregated routes. It is not a widely documented or commonly used command for typical network administration, and its functionality may overlap with or be superseded by more general ip route commands in recent kernel and iproute2 versions. It likely serves a niche role, possibly for debugging, internal testing, or advanced, programmatic control over aggregate routing behavior, allowing administrators to change attributes like metrics, output devices, or flags on aggregates without necessitating their complete deletion and re-creation. Due to its obscure nature, detailed public documentation is scarce.

ipaggmanip is an extremely obscure utility and is not typically part of standard ip(8) man pages or common Linux distributions' user-facing binaries. Its exact functionality, parameters, and expected behavior are poorly documented in public resources. It is likely an internal or highly specialized tool for kernel or iproute2 developers, or for very specific, advanced routing scenarios. Users should exercise extreme caution and verify its existence and behavior in their specific system environment before attempting to use it, as its behavior may be unpredictable or its functionality deprecated.

Given its specialized nature, ipaggmanip would typically be used in environments requiring precise, programmatic control over aggregated IP routes, potentially in conjunction with custom routing daemons or scripts. It is not intended for general interactive use by system administrators.

This command interacts directly with the Linux kernel's FIB (Forwarding Information Base) to modify existing aggregate route entries. Any changes made are live and affect kernel's packet forwarding decisions instantly.

The command ipaggmanip originates from the iproute2 project, which is the standard collection of utilities for network configuration in Linux. Its development is tied to the evolution of the Linux kernel's networking stack, particularly the handling of IP routing and aggregation. While the core iproute2 utilities like ip are widely used, ipaggmanip appears to be a more experimental or niche tool, likely developed to address specific challenges or provide fine-grained control over aggregate routes that might not be exposed through higher-level ip route aggregate commands. Its usage and relevance have likely shifted over time as the iproute2 suite and kernel routing capabilities matured, potentially leading to its functionality being integrated elsewhere or becoming less critical as a standalone binary.

ip(8), ip-route(8), ip-link(8)