<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Ubiquity Topology]]></title><description><![CDATA[<p dir="auto">I noticed UBNT devices do not provide acess to SNMP dot1Q briding information so topology polls always fail.  Is it possibel for us to hook into Topolgy poll to create our own custom poll ?  UBNT devices use bridge-utils  so all info can be displayed using brctl  I would like to be able port 1 is ath0 and port 2 is eth0 so I can figure out what devices are connected remotely but i would love to have it displayed in netxms topology.   Thanks</p>
<p dir="auto">WA# brctl showmacs br1<br />
port no mac addr                is local?       ageing timer<br />
  1     00:04:81:02:b8:62       no                 0.23<br />
  2     00:0c:42:6f:63:17       no                32.17<br />
  2     00:0c:42:6f:63:1a       no                35.92<br />
  2     00:0c:42:95:ec:03       no                17.08<br />
  2     00:0c:42:9d:d9:44       no                50.58<br />
  2     00:0c:42:9f:a6:e1       no                32.11<br />
  2     00:0c:42:9f:d0:31       no                56.66<br />
  2     00:0c:42:b5:b8:6b       no                31.38<br />
  2     00:0c:42:b6:2e:0d       no                17.76<br />
  2     00:0c:42:ba:f4:df       no                15.84<br />
  2     00:15:6d:65:54:27       no                 0.20<br />
  2     00:15:6d:67:34:ff       no                10.74<br />
  2     00:15:6d:69:67:ee       no                38.89<br />
  2     00:15:6d:69:67:fd       no                 2.65<br />
  2     00:15:6d:69:68:06       no                50.58<br />
  2     00:15:6d:69:68:83       no                17.76<br />
  2     00:15:6d:69:68:89       no                32.11<br />
  2     00:15:6d:69:68:8e       no                33.64<br />
  2     00:15:6d:6b:4b:93       no                51.55<br />
  2     00:15:6d:6b:4c:8a       no                17.55<br />
  2     00:15:6d:6b:4c:c9       no                32.17<br />
  2     00:15:6d:6b:4c:cc       no                15.84<br />
  2     00:15:6d:6b:4d:2d       no                 3.66<br />
  2     00:15:6d:6b:4d:51       no                33.60<br />
  2     00:15:6d:6b:56:2f       no                58.58<br />
  2     00:15:6d:6b:8c:e3       no                56.66<br />
  2     00:15:6d:6b:ff:21       no                 2.71<br />
  2     00:15:6d:6b:ff:29       no                13.69<br />
  2     00:15:6d:6b:ff:2a       no                47.96<br />
  2     00:15:6d:6b:ff:39       no                 7.23<br />
  2     00:15:6d:6c:22:cc       no                 7.01<br />
  2     00:15:6d:6c:22:cd       no                 7.05<br />
  2     00:15:6d:6c:22:ce       no                29.67<br />
  2     00:15:6d:6c:22:d5       no                15.25<br />
  2     00:15:6d:6c:22:db       no                35.93<br />
  2     00:15:6d:6c:b1:e0       no                 7.00<br />
  2     00:15:6d:6c:b1:f2       no                 0.81<br />
  2     00:15:6d:6c:b1:fd       no                 1.95<br />
  2     00:15:6d:6c:b1:fe       no                47.49<br />
  2     4c:5e:0c:7f:cf:36       no                 1.95<br />
  2     4c:5e:0c:84:70:e5       no                35.93<br />
  2     4c:5e:0c:84:cd:3a       no                10.74<br />
  2     4c:5e:0c:85:05:43       no                 7.01<br />
  2     4c:5e:0c:85:67:1d       no                26.69<br />
  2     4c:5e:0c:86:7e:f6       no                47.49<br />
  2     4c:5e:0c:87:07:12       no                 0.81<br />
  2     4c:5e:0c:8e:6a:62       no                 7.00<br />
  1     70:a7:41:48:9e:f5       yes                0.00<br />
  1     70:a7:41:48:a7:f5       no                 0.80<br />
  2     70:a7:41:49:9e:f5       yes                0.00<br />
  3     72:a7:41:49:9e:f5       yes                0.00<br />
  2     d4:ca:6d:9c:f0:1e       no                 2.71<br />
  2     d4:ca:6d:a1:3d:de       no                17.94<br />
  2     fc:96:43:6e:56:01       no                 0.01</p>
]]></description><link>https://forum.netxms.org/topic/7672/ubiquity-topology</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 17:54:38 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/7672.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 27 Apr 2023 21:14:42 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Ubiquity Topology on Tue, 13 Jun 2023 15:31:08 GMT]]></title><description><![CDATA[<p dir="auto">Yes, we have that "sponsor" button on github <img src="https://forum.netxms.org/assets/plugins/nodebb-plugin-emoji/emoji/android/1f642.png?v=72b86a538fc" class="not-responsive emoji emoji-android emoji--slightly_smiling_face" style="height:1.4em;width:auto;vertical-align:middle" title=":)" alt="🙂" /></p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/32519</link><guid isPermaLink="true">https://forum.netxms.org/post/32519</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Tue, 13 Jun 2023 15:31:08 GMT</pubDate></item><item><title><![CDATA[Reply to Ubiquity Topology on Mon, 29 May 2023 18:43:18 GMT]]></title><description><![CDATA[<p dir="auto">This feature would be awesome.. Thanks for all your hard work Victor.  Do we have the ability to sponsor this project on github ? If so I would gladly sponsor.</p>
<p dir="auto">Thanks</p>
]]></description><link>https://forum.netxms.org/post/32489</link><guid isPermaLink="true">https://forum.netxms.org/post/32489</guid><dc:creator><![CDATA[gmonk63]]></dc:creator><pubDate>Mon, 29 May 2023 18:43:18 GMT</pubDate></item><item><title><![CDATA[Reply to Ubiquity Topology on Mon, 29 May 2023 12:30:58 GMT]]></title><description><![CDATA[<p dir="auto">Currently it is not possible to inject topology information from hook script, but I see how that could be beneficial. Another option which I consider for some time already is to extend driver concept beyond SNMP, to allow SSH commands and possibly other protocols. This may help with reading VLAN information on Mikrotik switches for example, and probably lot of other cases with devices that have marginal SNMP support.<br />
Added note to myself to think about it for one of next releases <img src="https://forum.netxms.org/assets/plugins/nodebb-plugin-emoji/emoji/android/1f642.png?v=72b86a538fc" class="not-responsive emoji emoji-android emoji--slightly_smiling_face" style="height:1.4em;width:auto;vertical-align:middle" title=":)" alt="🙂" /></p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/32486</link><guid isPermaLink="true">https://forum.netxms.org/post/32486</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Mon, 29 May 2023 12:30:58 GMT</pubDate></item></channel></rss>