-
Notifications
You must be signed in to change notification settings - Fork 8
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
lldpad: Introduce changed config file interface
This patch modifies all interface functions to get and set config file values to use the agent type. The agent type will determine in which section of the config file the values are located. The result is that now there are 3 sections in lldpad.conf for LLDP: - "lldp" or "nearest_bridge" (if newly created) - "nearest_customer_bridge" - "nearest_nontpmr_bridge" So lldpad.conf will look similar like lldp { ... } nearest_customer_bridge { ... } nearest_nontmpr_bridge { ... } It also introduces a new lldptool parameter -g <agent>. Valid values for <agent> are - "nearest_bridge" or "nb" - "nearest_customer_bridge" or "ncb" - "neareast_nontpmr_bridge" or "nntpmrb" E.g. to enable the evbCfg TLV for the agent "nearest customer bridge" one would use "lldptool -T -i eth8 -g ncb -V evbCfg -c enableTx=yes" If no -g parameter is specified, this is assumed to remain "nearest bridge" to preserve the existing behaviour. It modifies the lldp_mod_* functions to supply the agent where appropriate. JF: updated to default to nearest bridge if '-g' is not specified. Signed-off-by: Jens Osterkamp <[email protected]> Signed-off-by: John Fastabend <[email protected]>
- Loading branch information
Jens Osterkamp
authored and
John Fastabend
committed
Oct 5, 2011
1 parent
99fedf7
commit 714c678
Showing
25 changed files
with
579 additions
and
525 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.