NDP active force: unable to send second SONMP packet on real device

[dragoangel]

This is an example of bug report. Try to adapt it to your case.

Bug description

Steps to reproduce the problem

1. Compile lldpd with ./configure --localstatedir=/var --with-snmp && make.

2. Install with sudo make install.

3. Run /usr/local/sbin/lldpd -d -ll -ss -I 'vtnet0' -C 'vtnet0' -m '192.168.3.4'.

Expected outcome

lldpd should work without errors in output log.

Current outcome

After executing the above steps with NDP active and force, lldpd working, but throw warning each ~30sec per each active interface. Sample error from log:

unable to send second SONMP packet on real device for vtnet0: Operation not permitted

If NDP set to work in active only mode this error will not occur.

Additional information

• Output of lldpd -vv:

lldpd 1.0.4
  Built on 2020-01-31T16:59:27Z

Additional LLDP features:    LLDP-MED, Dot1, Dot3, Custom TLV
Additional protocols:        CDP, FDP, EDP, SONMP
SNMP support:                yes
Privilege separation:        enabled
Privilege separation user:   _lldpd
Privilege separation group:  _lldpd
Privilege separation chroot: /var/empty
Configuration directory:     /usr/local/etc

C compiler command: cc  -Wunknown-warning-option -fdiagnostics-show-option -fdiagnostics-color=auto -pipe -Wall -W -Wextra -Wformat -Wformat-security -Wimplicit-fallthrough -Wfatal-errors -Wcast-align -Wheader-guard -Wdocumentation -Winline -Wpointer-arith -fno-omit-frame-pointer -Wno-unused-parameter -Wno-missing-field-initializers -Wno-sign-compare -fstack-protector -fstack-protector-all -fstack-protector-strong  -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -O2 -pipe  -fstack-protector-strong -fno-strict-aliasing -std=gnu99
Linker command:     /usr/bin/ld  -Wl,-z,relro -Wl,-z,now    -fstack-protector-strong

• Output of uname -sro:

FreeBSD 11.3-STABLE

[vincentbernat]

In daemon/protocols/sonmp.c, could you add a sleep(1) on line 264, before the second interfaces_send_helper(). It's to check if it's a problem of sending packets too fast.

[vktg]

correct is:
If NDP set to work in passive only mode this error will not occur.

[dragoangel]

Hi @vktg I was written the label which pfSense use. Maybe you right about passive.

[dragoangel]

@vincentbernat sorry I can't, I use this precompiled package on pfsense, @vktg can you help with this please?

[rbgarga]

@dragoangel I applied the change suggested by @vincentbernat and bumped port revision. You will see lldpd-1.0.4_1 available on pfSense 2.5.0 in the next hours

[dragoangel]

Hi @rbgarga thank you, but I'm on 2.4.5_1 and due to fact all people working remotely I can't now update to devel version to test this, sorry :(

[rbgarga]

@dragoangel I applied the change suggested by @vincentbernat and bumped port revision. You will see lldpd-1.0.4_1 available on pfSense 2.5.0 in the next hours

@vincentbernat according https://redmine.pfsense.org/issues/10502#note-12 adding that sleep(1) didn't help

[vincentbernat]

Well, I really don't know what could happen here... The second packet is very similar to the first one.