Replies: 2 comments 1 reply
-
|
A quick fix would be to disable lldpcli configuration with |
Beta Was this translation helpful? Give feedback.
-
|
Thanks Vincent. Yes, we could implement our own parsing of these config files in our service that connects our power controller to lldpd. However, it would be even easier (for us) if it was possible for lldpd to read in the configuration files in /run/lldp-confd/ before it starts the lldpd-API. |
Beta Was this translation helpful? Give feedback.
-
|
Configuration is done using the API and there is no thread in lldpd, so it's not easy. The readiness signal could be moved later in lldpd to workaround that. You don't need to reimplement a lot, just to execute lldpcli yourself with |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
We are using the lldpd API to gather info on POE status, and to request power using POE. However, we have a problem that during boot, lldpd is reconfigured a few times with added device name and port filtering. When this happens, it seems like the lldpd API freezes, and gives bad responses.
We did not find any way to get information (through any callback or similar) in the API that a reconfiguration has made lldpd API stop working.
I am thinking of the time between these prints:
We have been discussing that maybe if we control everything from the process that uses the lldpd API, we may get rid of these problems since we can control when it is done. But this will cause a bit of work which we haven't started on yet.
What is your proposal for these cases @vincentbernat?
Beta Was this translation helpful? Give feedback.
All reactions