TIPC-BEARER(8)
๐ TIPC-BEARER(8) ๐
okay bestie, welcome to the tipc-bearer page from the Linux manual, section 8 (that's the sysadmin section, we love her). this is literally all about showing off and modifying TIPC bearers. no cap. ๐ฆ
โจ NAME โจ
tipc-bearer โ show or modify TIPC bearers
๐ธ SYNOPSIS ๐ธ
tipc bearer add media udp name NAME remoteip REMOTEIP
tipc bearer enable [ domain DOMAIN ] [ priority PRIORITY ] media
{ { eth | ib } device DEVICE } |
{ udp name NAME localip LOCALIP [ localport LOCALPORT ] [
remoteip REMOTEIP ] [ remoteport REMOTEPORT ] }
tipc bearer disable media
{ { eth | ib } device DEVICE } |
{ udp name NAME }
tipc bearer set { priority PRIORITY | tolerance TOLERANCE | window
WINDOW } media
{ { eth | ib } device DEVICE } |
{ udp name NAME }
tipc bearer get [ priority | tolerance | window ] media
{ { eth | ib } device DEVICE } |
{ udp name NAME [ localip | localport | remoteip | remoteport ]
}
tipc bearer list
๐ OPTIONS ๐
so these are the options (aka flags, aka little guys) that you can drop anywhere in the command chain. yes, anywhere. the position is irrelevant, she's flexible like that.
-h,--helpโ shows help about the last valid command. like,tipc bearer --helpgives you the bearer help andtipc --helpgives you the general help. where you put the option in the string? literally doesn't matter. ๐โ๏ธ
๐ DESCRIPTION ๐
๐ Bearer identification
media MEDIAโ tells you which TIPC media type this particular bearer is gonna operate on. here's the tea: different media types identify a unique bearer in totally different ways. for example,ibandethidentify a bearer with aDEVICE, whileudpidentifies a bearer with aLOCALIPand aNAME. slay.ibโ Infinibandethโ Ethernetudpโ User Datagram Protocol (UDP)
name NAMEโ the logical bearer identifier, and she's only valid for bearers onudpmedia.device DEVICEโ the physical bearer device, valid for bearers onethandibmedia.
๐ Bearer properties
domainโ the addressing domain (region) where a bearer is gonna establish links and accept link establish requests. main character territory.priorityโ the default link priority that gets inherited by all links subsequently established over a bearer. okay so important detail: a single bearer can only host one link to a particular node. which means the default link priority for a bearer usually decides which bearer to use when you're talking to a particular node in a multi-bearer setup. want more info about link priority? go readtipc-link(8). ๐ซถtoleranceโ the default link tolerance inherited by all links subsequently established over a bearer. more info about link tolerance lives intipc-link(8).windowโ the default link window inherited by all links subsequently established over a bearer. more info about the link window size is intipc-link(8).
๐ง UDP bearer options
localip LOCALIPโ specify a local IPv4/IPv6 address for audpbearer.localport LOCALPORTโ specify the local port for audpbearer. the default port6118gets used if you don't specify a port. iconic default behavior honestly.remoteip REMOTEIPโ specify a remote IP for audpbearer. if no remote IP is specified, audpbearer runs in multicast mode and tries to auto-discover its neighbours. the multicast IP address is generated based on the TIPC network ID. if a remote IP is specified, theudpbearer runs in point-to-point mode.
you can add multiple remoteip addresses via the bearer add command. adding one or more unicast remoteip addresses to an existing udp bearer puts the bearer in replicast mode, where IP multicast is emulated by sending multiple unicast messages to each configured remoteip. and here's the cute part: when a peer sees a TIPC discovery message from an unknown peer, the peer address is automatically added to the remoteip (replicast) list โ so only one side of a link needs to be manually configured. ๐
โ ๏ธ a remoteip address cannot be added to a multicast bearer. periodt.
remoteport REMOTEPORTโ specify the remote port for audpbearer. the default port6118is used if no port is specified. (yes, same default aslocalport, they're twinning โจ)
๐ EXIT STATUS ๐
exit status is 0 if the command was successful, or a positive integer upon failure. so if you see a positive number, something went wrong bestie, go check yourself. ๐ญ
๐ SEE ALSO ๐
tipc(8), tipc-link(8), tipc-media(8), tipc-nametable(8), tipc-node(8), tipc-peer(8), tipc-socket(8)
๐ REPORTING BUGS ๐
found a bug? report it to the Network Developers mailing list <netdev@vger.kernel.org> โ that's where the development and maintenance is primarily done. and ngl, you do not have to be subscribed to the list to send a message there. so no excuses, go tell them. ๐
๐ AUTHOR ๐
Richard Alpe <richard.alpe@ericsson.com>
okay that's the whole page, you ate it up ๐
sign-off tea: this little gem comes from the iproute2 source, dated 02 Jun 2015, and the page itself is TIPC-BEARER(8). go forth and bearer responsibly, bestie ๐๐ฆ๐ธ
๐ฆ where this page comes from
- alpine 3.24: iproute2-doc 7.0.0-r0 ยท GPL-2.0-or-later
- arch rolling: iproute2 7.2.0-1
- arch rolling: iproute2 7.3.0-1 ยท GPL-2.0-or-later
- centos-stream 10: iproute 7.0.0-2.el10 ยท GPL-2.0-or-later AND NIST-PD
- nixos 26.05: iproute2 7.0.0
- nixpkgs unstable: iproute2 7.2.0
- ubuntu stonking: iproute2 7.2.0-1ubuntu1 ยท GPL-2.0-only
- ๐ girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms