<![CDATA[Possible Bug]]>We have a new temperature/humidity sensor  from WebRelay (X-410) which has been added to netxms to monitor temps. The weird thing is for each config poll a different address is seen and interface eth0 is changed to this external address which is not the address we assigned to the device and is external. The device has a single ethernet port and  still responds to the internal address we originally assigned. I have checked with another MIB browser with the IP and IF oids and I don't  see where this address is coming from. Is it possible netxms is generating these addresses ?  I am curious as to what the PING3 driver is and how it determined this device needed that driver.

Thanks

configpoll.png

]]>https://forum.netxms.org/topic/8208/possible-bugRSS for NodeFri, 13 Nov 2026 09:22:58 GMTWed, 02 Jul 2025 16:15:25 GMT60<![CDATA[Reply to Possible Bug on Tue, 08 Jul 2025 10:45:22 GMT]]>PING3 is something niche and yes, looks that it's being auto-detected incorrectly. You can put PING3 into NetworkDeviceDrivers.BlackList server configuration parameter, this will prevent the auto-detection

]]>https://forum.netxms.org/post/34599https://forum.netxms.org/post/34599Tue, 08 Jul 2025 10:45:22 GMT