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 --help gives you the bearer help and tipc --help gives 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, ib and eth identify a bearer with a DEVICE, while udp identifies a bearer with a LOCALIP and a NAME. slay.
    • ib โ€” Infiniband
    • eth โ€” Ethernet
    • udp โ€” User Datagram Protocol (UDP)
  • name NAME โ€” the logical bearer identifier, and she's only valid for bearers on udp media.
  • device DEVICE โ€” the physical bearer device, valid for bearers on eth and ib media.

๐ŸŒˆ 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 read tipc-link(8). ๐Ÿซถ
  • tolerance โ€” the default link tolerance inherited by all links subsequently established over a bearer. more info about link tolerance lives in tipc-link(8).
  • window โ€” the default link window inherited by all links subsequently established over a bearer. more info about the link window size is in tipc-link(8).

๐Ÿงš UDP bearer options

  • localip LOCALIP โ€” specify a local IPv4/IPv6 address for a udp bearer.
  • localport LOCALPORT โ€” specify the local port for a udp bearer. the default port 6118 gets used if you don't specify a port. iconic default behavior honestly.
  • remoteip REMOTEIP โ€” specify a remote IP for a udp bearer. if no remote IP is specified, a udp bearer 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, the udp bearer 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 a udp bearer. the default port 6118 is used if no port is specified. (yes, same default as localport, 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