<?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[Show IP in dashboard]]></title><description><![CDATA[<p dir="auto">Newbie here... don't shoot!  <img src="https://forum.netxms.org/assets/plugins/nodebb-plugin-emoji/emoji/android/1f609.png?v=72b86a538fc" class="not-responsive emoji emoji-android emoji--wink" style="height:1.4em;width:auto;vertical-align:middle" title=";)" alt="😉" /></p>
<p dir="auto">I want to monitor my lousy TP-Link TL-R480T+ multiband router. I have 2 wan and sometimes one of them releases it public IP and goes to 0.0.0.0. So I created an alert. But I also want to show both WAN IPs on the dashboard. I can see the IP in the overview of the interface, but I don't know how to READ it.<br />
How can I do this?</p>
]]></description><link>https://forum.netxms.org/topic/5125/show-ip-in-dashboard</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 14:01:13 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/5125.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 28 Jun 2017 20:10:53 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Show IP in dashboard on Mon, 02 Oct 2017 19:27:23 GMT]]></title><description><![CDATA[<p dir="auto">Thanks</p>
<p dir="auto">I've changed my old router. Now I have a MikroTik. I'll try first with SNMP.</p>
<p dir="auto">Regards,<br />
FSO</p>
]]></description><link>https://forum.netxms.org/post/23137</link><guid isPermaLink="true">https://forum.netxms.org/post/23137</guid><dc:creator><![CDATA[Djago]]></dc:creator><pubDate>Mon, 02 Oct 2017 19:27:23 GMT</pubDate></item><item><title><![CDATA[Reply to Show IP in dashboard on Tue, 19 Sep 2017 19:00:18 GMT]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">you mean you see IP in interface overview in NetXMS UI? Then you can use script to get it into your message/DCI/etc. Function <a href="https://wiki.netxms.org/wiki/NXSL:GetInterfaceObject" rel="nofollow ugc">GetInterfaceObject</a> can give you <a href="https://wiki.netxms.org/wiki/NXSL:Interface" rel="nofollow ugc">Interface</a> object, which contains list of IP addresses.</p>
<p dir="auto">Best regards,<br />
Victor</p>
]]></description><link>https://forum.netxms.org/post/23101</link><guid isPermaLink="true">https://forum.netxms.org/post/23101</guid><dc:creator><![CDATA[victor]]></dc:creator><pubDate>Tue, 19 Sep 2017 19:00:18 GMT</pubDate></item><item><title><![CDATA[Reply to Show IP in dashboard on Mon, 04 Sep 2017 11:05:57 GMT]]></title><description><![CDATA[<p dir="auto">TP-Link doesn't like SNMP. Documentation is scarse and bad. So it's very difficult to read most parameters. That's why I'm hoping to use the parameters I CAN read...</p>
]]></description><link>https://forum.netxms.org/post/23038</link><guid isPermaLink="true">https://forum.netxms.org/post/23038</guid><dc:creator><![CDATA[Djago]]></dc:creator><pubDate>Mon, 04 Sep 2017 11:05:57 GMT</pubDate></item><item><title><![CDATA[Reply to Show IP in dashboard on Mon, 04 Sep 2017 07:03:34 GMT]]></title><description><![CDATA[<p dir="auto">Working with dynamic public IP's I found it best to setup SNMP traps on the device in question.</p>
<p dir="auto">I did the exact same setup on fortigate 80c that sends traps if the IP changed on the interfaces selected.</p>
<p dir="auto">However it depends on SNMP on the device in question.</p>
]]></description><link>https://forum.netxms.org/post/23036</link><guid isPermaLink="true">https://forum.netxms.org/post/23036</guid><dc:creator><![CDATA[duanebutler]]></dc:creator><pubDate>Mon, 04 Sep 2017 07:03:34 GMT</pubDate></item><item><title><![CDATA[Reply to Show IP in dashboard on Thu, 17 Aug 2017 20:37:11 GMT]]></title><description><![CDATA[<p dir="auto">Anyone?</p>
]]></description><link>https://forum.netxms.org/post/22954</link><guid isPermaLink="true">https://forum.netxms.org/post/22954</guid><dc:creator><![CDATA[Djago]]></dc:creator><pubDate>Thu, 17 Aug 2017 20:37:11 GMT</pubDate></item></channel></rss>