Oliver Gorwits

Hi @acrow-geo and @mrquija unfortunately most of what MIKROTIK-MIB has for neighbors is not very useful. There are too many entries and I cannot see how to map them to...

Hi @acrow-geo no, I was talking about LLDP/neighbor data, and I can't get a clear picture either from the MIKROTIK-MIB or LLDP MIB data. Unfortunately the MIKROTIK-MIB is undocumented so...

it looks like SNMP::Info does not have a more specific device class for TP-Link, and maybe this is needed to extract some things like Vendor or other details. Hi @nmersi...

Hi @sgwoll many thanks and I'm sorry for the long time waiting on this I've added the updated fortiswitch mib in commit 35110d7 But to have this work in netdisco...

and yet the arpnip with debug shows use of ipNetToPhysicalPhysAddress, returning nothing: ```` SNMP::Info::_load_attr ip_n2p_phys_addr : IP-MIB::ipNetToPhysicalPhysAddress : .1.3.6.1.2.1.4.35.1.4 SNMP::Info::IPv6::ipv6_n2p_mac: data comes from IP-MIB. SNMP::Info::IPv6::ipv6_n2p_addr: data comes from IP-MIB. [40607]...

Thanks for the very clear report, @michaelcrandolph. My initial guess (not running any similar hardware myself) is that the changing port is the VPN tunnel which when re-established gets assigned...

When the Netdisco port name looks like "31902 (15)" it suggests that there is a duplicate in i_description as the (15) is the interface index being added in order to...

Hi @nomisunrider For collecting v4 addresses, the two methods at_paddr() and at_netaddr() are used. So, let's see what your device returns: `~/bin/netdisco-do show -d 1.2.3.4. -e at_paddr -DI` `~/bin/netdisco-do show...

The solution from @inphobia is fine (I would even be happy with an uptime() which returned "0"), but the problem with implementing it here is that this example seems to...

@JeroenvIS yes you are right! I realised later my error in thinking. The more specific device class is only assigned after initial connection, but if we need specific device class...