NetworkManager/src/libnm-lldp/nm-lldp-network.h

/* SPDX-License-Identifier: LGPL-2.1-or-later */
#ifndef __NM_LLDP_NETWORK_H__
#define __NM_LLDP_NETWORK_H__

#define NM_ETHERTYPE_LLDP 0x88cc

int nm_lldp_network_bind_raw_socket(int ifindex);

#endif /* __NM_LLDP_NETWORK_H__ */
lldp: add libnm-lldp as fork of systemd's sd_lldp_rx We currently use the systemd LLDP client, which we consume by forking systemd code. That is a maintenance burden, because it's not a self-contained, stable library that we use. Hence there is a need for an individual library or properly integrating the fork in our tree. Optimally, we would create a new nettools project with an LLDP library. That was not done because: - nettools may want to be dual licensed with LGPL-2.1+ and Apache. Systemd code is LGPL-2.1+ so it is fine for NetworkManager but possibly not for nettools. - nettools provides independent librares, as such they don't have an event loop, instead they expose an epoll file descriptor and the user needs to integrate it. Systemd and NetworkManager on the other hand have their established event loop (sd_event and GMainContext, respectively). It's simpler to implement the library on those terms, in particular porting the systemd library from sd_event to GMainContext. - NetworkManager uses glib and has various helper utils. While it's possible to do without them, it's more work. The main reason to not write a new NetworkManager-agnostic library from scratch, is that it's much simpler to fork the systemd library and make it part of NetworkManager, than making it a nettools library. Do it. 2022-09-06 13:33:18 +02:00			`/* SPDX-License-Identifier: LGPL-2.1-or-later */`
			`#ifndef __NM_LLDP_NETWORK_H__`
			`#define __NM_LLDP_NETWORK_H__`

			`#define NM_ETHERTYPE_LLDP 0x88cc`

			`int nm_lldp_network_bind_raw_socket(int ifindex);`

			`#endif /* __NM_LLDP_NETWORK_H__ */`