LLDPCLI(8)

🎀 LLDPCLI(8) 🎀

System Manager's Manual — bestie, this is the lldpcli / lldpctl page and we're gonna get through it together 💅 (this is part 1 of 4, so buckle up, we're not even done)

✨ NAME ✨

lldpcli, lldpctl — control LLDP daemon 🦋

✨ SYNOPSIS ✨

lldpcli [-dv] [-u socket] [-f format] [-c file] [command ...]
lldpctl [-dv] [-u socket] [-f format] [interfaces ...]

✨ DESCRIPTION ✨

okay so the lldpcli program controls the lldpd(8) daemon. that's the whole vibe. 👑

When you don't specify any command, lldpcli starts an interactive shell where you can type arbitrary commands exactly as if you'd put them on the command line. This interactive shell should give you completion and history support — iykyk, it's giving main character energy.

The options are as follows:

• -d — enable more debugging information. This flag can be repeated, so go off, stack 'em 🔥
• -u socket — specify the Unix-domain socket used for communication with lldpd(8).
• -v — show lldpcli version. When repeated, show more build information.
• -f format — choose the output format. Currently plain, xml, json, json0 and keyvalue formats are available. The default is plain. json0 is more verbose than json but the structure of the JSON object is not affected by the number of interfaces or the number of neighbors. It's therefore easier to parse. ngl that's the one you want if you're scripting 💅
• -c file — read the given configuration file. This option may be repeated several times. If a directory is provided, each file therein suffixed with .conf will be read. Order is alphabetical. 🗂️

When invoked as lldpctl, lldpcli will display detailed information about each neighbor on the specified interfaces, or on all interfaces if none are specified. This command is mostly kept for backward compatibility with older versions. vintage but make it functional 🫶

---

The following commands are supported by lldpcli. When there's no ambiguity, the keywords can be abbreviated — literally so chill of them. For example, show neighbors ports eth0 summary and sh neigh p eth0 sum are the same command. ✨

exit

Quit lldpcli. bye bestie 👋

help [...]

Display general help or help about a specific command. Also, you can get help using the completion or by pressing the ? key. Completion and inline help may be unavailable, however, if lldpcli was compiled without readline support — but the help command is always available. 💚

show neighbors [ports ethX [,...]] [details | summary] [hidden]

Display information about each neighbor known by the lldpd(8) daemon. With summary, only the name and the port description of each remote host will be displayed. On the other hand, with details, all available information will be displayed, giving a verbose view. When using hidden, also display remote ports hidden by the smart filter. When specifying one or several ports, the information displayed is limited to the given list of ports. 🔍

show interfaces [ports ethX [,...]] [details | summary] [hidden]

Display information about each local interface known by the lldpd(8) daemon. With summary, only the name and the port description of each local interface will be displayed. On the other hand, with details, all available information will be displayed, giving a verbose view. When using hidden, also display local ports hidden by the smart filter. When specifying one or several ports, the information displayed is limited to the given list of ports. 🧚

show chassis [details | summary]

Display information about local chassis. With summary, most details are skipped. On the other hand, with details, all available information will be displayed, giving a verbose view. 👑

watch [ports ethX [,...]] [details | summary] [hidden] [limit X]

Watch for any neighbor changes and report them as soon as they happen — it's giving live commentary fr. When specifying ports, the changes are only reported when happening on the given ports. hidden, summary and details have the same meaning as previously described. If limit is specified, lldpcli will exit after receiving the specified number of events. 🍓

show configuration

Display global configuration of the lldpd(8) daemon.

show statistics [ports ethX [,...]] [summary]

Report LLDP-related statistics, like the number of LLDPDU transmitted, received, discarded or unrecognized. When specifying ports, only the statistics from the given port are reported. With summary the statistics of each port are summed. 📊

update

Make lldpd(8) update its information and send new LLDP PDU on all interfaces. slay, refresh ✨

reset

Restore the configuration lldpd(8) was started with. Every setting changed at runtime, whether with configure or unconfigure commands or through configuration files, is discarded. This includes global settings, local chassis settings and per-port settings (port ID and description, MED, Dot3 power, custom TLVs, ...). Command-line options given to lldpd(8) are kept, as well as the paused state. Changes already applied to the system, like interface descriptions or promiscuous mode, are not reverted. To reload configuration files without restarting lldpd(8), issue this command and then read the files again, for example with:

lldpcli -c /etc/lldpd.conf -c /etc/lldpd.d

configure system hostname name

Override system hostname with the provided value. By default, the system name is the FQDN found from the resolved value of uname -n. As a special value, use . (dot) to use the short hostname instead of a FQDN. 💅

unconfigure system hostname

Do not override system hostname and restore the use of the node name. undo era 🙈

configure system description description

Override chassis description with the provided value instead of using kernel name, node name, kernel version, build date and architecture.

unconfigure system description

Do not override chassis description and use a value computed from node name, kernel name, kernel version, build date and architecture instead.

configure system chassisid description

Override chassis ID with the provided value instead of using MAC address from one interface or host name.

unconfigure system chassisid

Do not override chassis ID, but instead use a value computed from one of the interface MAC addresses (or host name if none is found).

configure system platform description

Override platform description with the provided value instead of using kernel name. This value is currently only used for CDP.

unconfigure system platform

Do not override platform description and use the kernel name. This option undoes the previous one.

configure system capabilities enabled capabilities

Override system capabilities with the provided value instead of using kernel information. Several capabilities can be specified, separated by commas. Only available capabilities can be enabled. Valid capabilities are:

• bridge
• docsis
• other
• repeater
• router
• station
• telephone
• wlan

Here's an example of use:

configure system capabilities enabled bridge,router

unconfigure system capabilities enabled

Do not override capabilities, but instead use the kernel information. This option undoes the previous one.

configure system interface pattern pattern

Specify as comma separated values (CSV) which interfaces to listen upon and send LLDPDU from. Without this option, lldpd will use all available physical interfaces. This option can use wildcards. Several interfaces can be specified separated by commas. It's also possible to remove an interface by prefixing it with an exclamation mark. It's possible to allow an interface by prefixing it with two exclamation marks. An allowed interface beats a forbidden interface which beats a simple matched interface. For example, with eth*,!eth1,!eth2 lldpd will only use interfaces starting with eth with the exception of eth1 and eth2. While with *,!eth*,!!eth1 lldpcli will use all interfaces, except interfaces starting with eth with the exception of eth1. When an exact match is found, it will circumvent some tests. For example, if eth0.12 is specified, it will be accepted even if this is a VLAN interface. 🦋

unconfigure system interface pattern

Remove any previously configured interface pattern and use all physical interfaces. This option undoes the previous one.

configure system interface permanent pattern

Specify interfaces whose configuration is permanently kept by lldpd. By default, lldpd disregards any data about interfaces when they are removed from the system (statistics, custom configuration). This option allows one to specify a pattern similar to the interface pattern. If an interface disappears but matches the pattern, its data is kept in memory and reused if the interface reappears at some point. For example, on Linux, one could use the pattern eth*,eno*,enp*, which should match fixed interfaces on most systems. 💜

unconfigure system interface permanent

Remove any previously configured permanent interface pattern. Any interface removed from the system will be forgotten. This option undoes the previous one.

configure system interface description

Some OSes allow the user to set a description for an interface. Setting this option will enable lldpd to override this description with the name of the peer neighbor if one is found, or with the number of neighbors found. 🎀

unconfigure system interface description

Do not update interface description with the name of the peer neighbor. This option undoes the previous one.

configure system interface promiscuous

Enable promiscuous mode on managed interfaces.

⚠️ ngl this next bit matters: when the interface is not managed any more (or when quitting lldpd), the interface is left in promiscuous mode as it is difficult to know if someone else also put the interface in promiscuous mode. so like, it stays that way. no cap. 💀

Totally, so — about that first bit 🙈 this option is literally known to be useful when the remote switch is a Cisco 2960 and your local network card has VLAN hardware acceleration on. In that case, you might not receive LLDP frames from the remote switch at all. The most plausible explanation? The frame is tagged with some VLAN (usually VLAN 1) and your network card filters VLANs. 😤

And no, that's not the only available solution to work around this problem. If you're worried about performance issues, you can also tag VLAN 1 on each interface instead. Options, bestie — you've got them. ✨

Currently, this option has no effect on anything other than Linux. On other OSes, either disable VLAN acceleration, tag VLAN 1 or enable promiscuous mode manually on the interface.

• unconfigure system interface promiscuous — do not set promiscuous mode on managed interfaces. Heads up though: this option does not disable promiscuous mode on interfaces already using this mode. It's giving "no takebacks" 💅
• configure system ip management pattern pattern — specify the management addresses of this system as comma separated values (CSV). As for interfaces (described above), this option can use wildcards and inversions. Without this option, the first IPv4 and the first IPv6 are used. If an exact IP address is provided, it is used as a management address without any check. If only negative patterns are provided, only one IPv4 and one IPv6 address are chosen. Otherwise, many of them can be selected. To remove IPv6 addresses, use !*:*. If an interface name is matched, the first IPv4 address and the first IPv6 address associated with this interface will be chosen.
• unconfigure system ip management pattern — unset any specific pattern for matching management addresses. This option undoes the previous one. Undo button, but make it config 🫶
• configure system bond-slave-src-mac-type value — set the type of src mac in lldp frames sent on bond slaves. Valid types are:
  • real — slave real mac
  • zero — all zero mac
  • fixed — an arbitrary fixed value (00:60:08:69:97:ef)
  • local — real mac with locally administered bit set. If the real mac already has the locally administered bit set, fall back to the fixed value.

Default value for bond-slave-src-mac-type is local. Some switches may complain when using one of the two other possible values (either because 00:00:00:00:00:00 is not a valid MAC or because the MAC address is flapping from one port to another). Using local might lead to a duplicate MAC address on the network (but this is quite unlikely). 😌

• configure system max-neighbors neighbors — change the maximum number of neighbors accepted (for each protocol) on an interface. This is a global value. The default is 32. This setting only applies to future neighbors — past you already made their choices, no retroactive edits 💀
• configure lldp agent-type nearest-bridge | nearest-non-tpmr-bridge | nearest-customer-bridge — the destination MAC address used to send LLDPDU allows an agent to control the propagation of LLDPDUs. By default, the 01:80:c2:00:00:0e MAC address is used and limits the propagation of the LLDPDU to the nearest bridge (nearest-bridge). To instruct lldpd to use the 01:80:c2:00:00:03 MAC address instead, use nearest-nontpmr-bridge instead. To use the 01:80:c2:00:00:00 MAC address instead, use nearest-customer-bridge instead.
• configure lldp capabilities-advertisements — enable advertisements of the chassis capabilities TLV. Currently the default. Slay, it's on already ✨
• unconfigure lldp capabilities-advertisements — disable advertisements of the chassis capabilities TLV.
• configure lldp management-addresses-advertisements — enable advertisements of the management address TLV. Currently the default.
• unconfigure lldp management-addresses-advertisements — disable advertisements of the management address TLV.
• configure lldp portidsubtype ifname | macaddress
• configure [ports ethX [,...]] lldp portidsubtype local value

Force port ID subtype. By default, lldpd will use the MAC address as port identifier and the interface name as port description, unless the interface has an alias. In this case, the interface name will be used as port identifier and the description will be the interface alias. With this command, you can force the port identifier to be the interface name (with ifname), the MAC address (with macaddress) or a local value (with value). In the latest case, the local value should be provided. Pick your fighter 👑

• configure lldp portdescription-source auto | ifname | alias — select the source used for the port description TLV. This setting affects how the port description is determined when it is not explicitly provided (e.g. with portidsubtype local and a description).

Valid values are:

• auto — use the interface alias as port description when the alias is available and the port ID subtype is not set to macaddress. Otherwise, use the interface name. This is the default and preserves the historical behavior.
• ifname — always use the interface name as port description.
• alias — use the interface alias as port description when available, regardless of port ID subtype. Falls back to the interface name when no alias is set.

• configure [ports ethX [,...]] lldp portdescription description — force port description to the provided string. You say what it is, it says what it is. Periodt 💅
• configure lldp tx-interval interval — change transmit delay to the specified value in seconds. The transmit delay is the delay between two transmissions of LLDP PDU. The valid range is 1 through 3600 in seconds. The default value is 30 seconds. Note: lldpd also starts another system based refresh timer on each port to detect changes such as a hostname. This is the value of the tx-interval multiplied by 20.

You can specify an interval value in milliseconds by appending a "ms" suffix to the figure (e.g. "configure lldp tx-interval 1500ms" is 1.5s, not 1500s). In this case the TTL for received and sent LLDP frames is rounded up to the next second. Note: the effective interval can be limited by the operating system capabilities and CPU speed. 😭 yes, your CPU has opinions

• configure lldp tx-hold hold — change transmit hold value to the specified value. This value is used to compute the TTL of transmitted packets which is the product of this value and of the transmit delay. The valid range is 1 through 100. The default value is 4 and therefore the default TTL is 120 seconds. Math, but make it networking 🧮✨
• configure [ports ethX [,...]] lldp status rx-and-tx | rx-only | tx-only | disabled — configure the administrative status of the given port. By default, all ports are configured to be in rx-and-tx mode. This means they can receive and transmit LLDP frames (as well as other protocols if needed). In rx-only mode, they won't emit any frames and in tx-only mode, they won't receive any frames. In disabled mode, no frame will be sent and any incoming frame will be discarded. This setting does not override the operational mode of the main daemon. If it is configured in receive-only mode (with the -r flag), setting any transmit mode won't have any effect. Rude, but true 🙈
• configure [ports ethX [,...]] lldp vlan-tx vlan_id [prio priority [dei dei]] — configure the given port to send LLDP frames over a specified VLAN. With VLAN Identifier (VID) as vlan_id, Priority Code Point (PCP) as priority, and Drop Eligible Indicator (DEI) as dei. lldpd accepts LLDP frames on all VLANs. All the VLANs. It's very accepting 🦋
• configure [ports ethX [,...]] lldp custom-tlv [add | replace] oui subtype subtype [oui-info content] — emit a custom TLV for OUI oui, with subtype subtype and optionally with the bytes specified in content. Both oui and content shall be a comma-separated list of bytes in hex format. oui must be exactly 3 bytes long. If add is specified then the TLV will be added. This is the default action. If replace is specified then all TLVs with the same oui and subtype will be replaced.
• unconfigure [ports ethX [,...]] lldp custom-tlv [oui oui] [subtype subtype] — when no oui is specified, remove all previously configured custom TLV. When OUI oui and subtype subtype is specified, remove specific instances of custom TLV. Declutter era 🎀
• configure [ports ethX [,...]] lldp vlan-advertisements pattern pattern — configure VLAN advertisements for the given port as a comma separated values (CSV). As for interfaces (described above), this option can use wildcards and inversions. Without this option, lldpd will advertise all VLANS.
• unconfigure [ports ethX [,...]] lldp vlan-advertisements pattern — remove any previously configured VLAN advertisements pattern for the given port.
• configure lldp fast-start enable | tx-interval interval — configure LLDP fast start mechanism. When a new LLDP neighbor is detected, fast start allows lldpd to shorten the interval between two LLDPDU. enable should enable LLDP fast start while tx-interval specifies the interval between two LLDPDU in seconds. The valid interval range is 1 through 3600 in seconds. The default interval is 1 second. Once 4 LLDPDU have been sent, the fast start mechanism is disabled until a new neighbor is detected. New friend energy → speedrun era → back to normal 🔥
• unconfigure lldp fast-start — disable LLDP fast start mechanism.
• configure [ports ethX [,...]] med location coordinate latitude latitude longitude longitude altitude altitude unit unit datum datum

…so like, this command advertises a coordinate-based location on the ports you name — or on all the ports if you don't name any 💖 Here's the format tea:

• latitude — a decimal floating point number followed by either N or S
• longitude — a decimal floating point number followed by either E or W
• altitude — a decimal floating point number followed by either m (when it's in meters) or f (when it's in floors)
• there is a space expected between the floating point number and the unit, ok bestie? 117.47 m, not 117.47m
• datum — one of these values:
  • WGS84
  • NAD83
  • NAD83/MLLW

A valid use of this command is, and yes this is literally how it goes:

configure ports eth0 med location coordinate latitude 48.85667N longitude 2.2014E altitude 117.47 m datum WGS84

---

• configure [ports ethX [,...]] med location address country country [type value [...]] — advertise a civic address on the given ports (or on all ports if no port is specified 🫶). country is the two-letter code representing the country. The remaining arguments should be paired up to form the address — the first member of each pair says what type the second member is, and the second member is free-form text. Here's the guest list of valid types:
  • language
  • country-subdivision
  • county
  • city
  • city-division
  • block
  • street
  • direction
  • trailing-street-suffix
  • street-suffix
  • number
  • number-suffix
  • landmark
  • additional
  • name
  • zip
  • building
  • unit
  • floor
  • room
  • place-type
  • script

A valid use of this command is:

configure ports eth1 med location address country US street "Commercial Road" city "Roseville"

• configure [ports ethX [,...]] med location elin number — advertise the availability of an ELIN number 🚨 This one is for setting up emergency calls, so like, kind of important. If the number you provide is too small, it gets padded with 0 (no cap, it just adds zeros). Here's an example of use:

configure ports eth2 med location elin 911

---

• configure [ports ethX [,...]] med policy application application [unknown] [tagged] [vlan vlan] [priority priority] [dscp dscp] — advertise a specific network policy for the given ports (or for all ports if no port was provided ✨). Only the application type is mandatory. application should be one of these:
  • voice
  • voice-signaling
  • guest-voice
  • guest-voice-signaling
  • softphone-voice
  • video-conferencing
  • streaming-video
  • video-signaling

The unknown flag tells that the network policy for the specified application type is required by the device but is currently unknown 🤷‍♀️ This one is used by Endpoint Devices, not by Network Connectivity Devices. If you don't specify it, the network policy for the given application type is defined.

A VLAN given with vlan tells which 802.1q VLAN ID has to be advertised for the network policy — a valid value is between 1 and 4094. And tagged tells that the VLAN should be tagged for the specified application type 🎀

priority lets you specify the IEEE 802.1d / IEEE 802.1p Layer 2 Priority, also known as Class of Service (CoS), to be used for the specified application type. This field is usually ignored if no VLAN is specified. The names match the 802.1D-2004 standard (table G-2) — some more recent standards may use different labels, so only the numeric values should be relied upon ngl. The accepted labels are:

• 1 — background
• 0 — best-effort
• 2 — excellent-effort
• 3 — critical-applications
• 4 — video
• 5 — voice
• 6 — internetwork-control
• 7 — network-control

dscp represents the DSCP value to be advertised for the given network policy 💅 That's the DiffServ/Differentiated Services Code Point (DSCP) value as defined in IETF RFC 2474 for the specified application type. Value: 0 (default per RFC 2475) through 63. Note: the class selector DSCP values are backwards compatible for devices that only support the old IP precedence Type of Service (ToS) format. (See the RFCs for what these values mean, bestie ✨)

A valid use of this command is:

configure med policy application voice vlan 500 priority voice dscp 46

---

🎀 inventory vibes 🎀

• configure inventory hardware-revision value — override hardware-revision with the value you provide. By default, hardware-revision is fetched from /sys/class/dmi
• unconfigure inventory hardware-revision — do not override hardware-revision, and restore the use of the /sys/class/dmi value 🫶
• configure inventory software-revision value — override software-revision with the provided value. By default, software-revision is fetched from uname
• unconfigure inventory software-revision — do not override software-revision, and restore the use of the uname value.
• configure inventory firmware-revision value — override firmware-revision with the provided value. By default, firmware-revision is fetched from /sys/class/dmi
• unconfigure inventory firmware-revision — do not override firmware-revision, and restore the use of the /sys/class/dmi value.
• configure inventory serial-number value — override serial-number with the provided value. By default, serial-number is fetched from /sys/class/dmi
• unconfigure inventory serial-number — do not override serial-number, and restore the use of the /sys/class/dmi value.
• configure inventory manufacturer value — override manufacturer with the provided value. By default, manufacturer is fetched from /sys/class/dmi
• unconfigure inventory manufacturer — do not override manufacturer, and restore the use of the /sys/class/dmi value.
• configure inventory model value — override model with the provided value. By default, model is fetched from /sys/class/dmi
• unconfigure inventory model — do not override model, and restore the use of the /sys/class/dmi value.
• configure inventory asset value — override asset with the provided value. By default, asset is fetched from /sys/class/dmi
• unconfigure inventory asset — do not override asset, and restore the use of the /sys/class/dmi value.

---

⚡ power, part one: MED ⚡

• configure [ports ethX [,...]] med power pse | pd source source priority priority value value — advertise the LLDP-MED POE-MDI TLV for the given ports, or for all interfaces if no port is provided 🔥 You can act as a PD (power consumer) or a PSE (power provider).

⚠️ No check is done on the validity of the parameters while LLDP-MED requires some restrictions, so listen up: - PD shall never request more power than physical 802.3af class. - PD shall never draw more than the maximum power advertised by PSE. - PSE shall not reduce power allocated to PD when this power is in use. - PSE may request reduced power using conservation mode - Being PSE or PD is a global parameter, not a per-port parameter. lldpcli does not enforce this — a port can be set as PD or PSE 😭 LLDP-MED also requires a PSE to have only one power source (primary or backup). Again, lldpcli does not enforce this. Each port can have its own power source. The same applies for PD and power priority. LLDP-MED MIB does not allow this kind of representation.

Valid types are:

• pse — Power Sourcing Entity (power provider)
• pd — Power Device (power consumer)

Valid sources are:

• unknown — Unknown
• primary — For PSE, the power source is the primary power source.
• backup — For PSE, the power source is the backup power source, or a power conservation mode is requested (the PSE may be running on UPS for example).
• pse — For PD, the power source is the PSE.
• local — For PD, the power source is a local source.
• both — For PD, the power source is both the PSE and a local source.

Valid priorities are:

• unknown — Unknown priority
• critical — Critical
• high — High
• low — Low

value should be the total power in milliwatts required by the PD device or available by the PSE device 💜

Here is an example of use:

configure med power pd source pse priority high value 5000

---

⚡ power, part two: dot3 ⚡

• configure [ports ethX [,...]] dot3 power pse | pd [supported] [enabled] [paircontrol] powerpairs powerpairs [class class] [type type source source priority priority requested requested allocated allocated] — advertise the Dot3 POE-MDI TLV for the given port, or for all ports if none was provided 🌈 You can act as a PD (power consumer) or a PSE (power provider).

Heads up: this configuration is distinct from the configuration of the transmission of the LLDP-MED POE-MDI TLV, but you the user should make sure those two configurations stay coherent with each other if you're using them together 👀

supported means MDI power is supported on the given port, while enabled means MDI power is enabled. paircontrol is used to indicate whether pair selection can be controlled. Valid values for powerpairs are:

• signal — The signal pairs only are in use.
• spare — The spare pairs only are in use.

When specified, class is class-, suffixed with a number from 0 to 4. E.g. class-0, class-1, class-2, class-3, class-4 ✨

Okay so for 802.3at, the classes go like this — memorize them or keep this open, bestie:

• 0 — Default (Unspecified), PD 0.44-12.95 W, PSE 15.4 W
• 1 — Very Low Power Device, PD 0.44-3.84 W, PSE 4.0 W
• 2 — Low Power Device, PD 3.84-6.49 W, PSE 7.0 W
• 3 — Mid Power Device, PD 6.49-12.95 W, PSE 15.4 W
• 4 — High Power Device (PoE+), PD 12.95-25.5 W, PSE 30.0 W

The remaining parameters are in conformance with 802.3at and are optional, no pressure 💅. type should be either 1 or 2, indicating whether the device conforms to 802.3at type 1 or 802.3at type 2. Values of source and priority are the same as for LLDP-MED POE-MDI TLV. requested and allocated are expressed in milliwats.

Here are two valid uses of this command, fr fr these both work:

configure ports eth3 dot3 power pse supported enabled paircontrol powerpairs spare class class-3
configure dot3 power pd supported enabled powerpairs spare class class-3 type 1 source pse priority low requested 10000 allocated 15000

---

🧊 pause

Pause lldpd operations. lldpd will not send or receive any more frames. This can be undone with resume command. This only works interactively as lldpd asks lldpcli to unpause after reading the configuration file.

Heads up bestie 🫶 — that interactive-only bit is the whole vibe check here. Don't expect it to just chill in your config file.

▶️ resume

Resume lldpd operations. lldpd will start to send and receive frames. This command is issued internally after processing the configuration but can be used at any time if a manual pause command is issued.

---

🌸 FILES 🌸

• /run/lldpd/lldpd.socket — Unix-domain socket used for communication with lldpd(8). that's the little gossip line between lldpcli and lldpd, iykyk

---

🦋 SEE ALSO 🦋

• lldpd(8) — the main character of this whole story 👑

---

🎀 AUTHORS 🎀

The lldpcli program was written by Vincent Bernat <bernat@luffy.cx>. shoutout to the icon who built this, we stan 💖

---

and that's the whole page bestie, you made it 🎉 This one's a Debian joint, dated July 16, 2008, filed under LLDPCLI(8) — go forth and configure with confidence, mwah 💋