Community discussions

MikroTik App
  4. RouterOS
  5. RouterOS beta

"Feature" request: Improve discovery (LLDP) compatibility with TP-Link

Post Reply
 
g22113
just joined
Topic Author
Posts: 11
Joined: Sat Aug 19, 2017 3:21 pm

"Feature" request: Improve discovery (LLDP) compatibility with TP-Link

Thu Jun 22, 2023 6:52 pm

We use TP-Link JetStream switches, and they appear to be sending NUL-padded device name (identity) field in LLDP. This is even with latest switch firmware; newer models only add more padding (presumably to support longer switch names). Because of this, the default tabular view of /ip/neighbor/print becomes useless as the "IDENTITY" column doesn't fit at all (and RouterOS just omits it instead of truncating).

It would be nice if RouterOS could ignore \00 NUL padding for compatibility with these devices.
Code: Select all
14 interface=ether5 address=10.128.x.x address4=10.128.x.x
   mac-address=B0:4E:26:xx:xx:xx
   identity="UK-SW-Bas56-Net\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\0
         0\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\0
         0" 
   platform="" version="" unpack=none age=7s interface-name="GigabitEthernet1/0/19" 
   system-description="JetStream 24-Port Gigabit L2 Managed Switch with 4 SFP Slots" 
   system-caps=bridge,router system-caps-enabled=bridge,router discovered-by=lldp 

 5 interface=ether1-uk address=10.128.x.x address4=10.128.x.x
   mac-address=30:DE:4B:xx:xx:xx
   identity="UK-SW-Bas56-Serv\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\
         00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\
         00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\
         00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\
         00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\
         00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\
         00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\
         00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\
         00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00" 
   platform="" version="" unpack=none age=16s interface-name="gigabitEthernet 1/0/20" 
   system-description="JetStream 24-Port Gigabit L2+ Managed Switch with 4 10GE SFP+ Slots" 
   system-caps=bridge,router system-caps-enabled=bridge,router discovered-by=lldp
Top
 
rplant
Member
Member
Posts: 314
Joined: Fri Sep 29, 2017 11:42 am

Re: "Feature" request: Improve discovery (LLDP) compatibility with TP-Link

Wed Jun 28, 2023 7:21 am

While Mikrotik are looking into this :)

I have a Xirrus AP, the Mikrotik seems to see it only with LLDP, while the Xirrus is also sending CDP.
Also, the Xirrus provides a system description entry that is only visible from the CLI, not from winbox
or webfig (Not sure how it should be displayed, perhaps like a comment on a line by itself as it is quite big)

system-description="Xirrus XD2-240, 1.0GB (1.0GHz), Version: Xirrus AOS 8.7.0
(Feb 24 2023), Build: 8176"
Top
Post Reply

Who is online

Users browsing this forum: No registered users and 5 guests
  4. RouterOS
  5. RouterOS beta