Re: Netonix goes down with a "Discovery Device" Scan.
Posted: Wed Dec 20, 2017 2:34 pm
I edited your post and changed the way your image was loaded, please follow the instructions in my post signature on how to upload images. Linking external images is not a good idea because then it is not permeniate to the forums if you ever delete it and it does not scale well on the screen.
Eric is away today and I plan to discuss this with him when he returns.
It is possible that the Discovery TAB will simply not function properly on large flat segments like this. The CPU in the switches that runs the UI/CLI and these Daemons (not packet forwarding which is handled in the core) is simply too small. Plus when you send out this broadcast looking for devices to discover on a LARGE segment like this can cause a storm of responses.
I asked Eric to put this feature in against his wishes as I thought it would be cool and since I run a routed network at my WISP the switch only sees devices located at that tower.
I also recently noticed the discovery is not working as before since the latest UBNT firmware upgrade so Eric will need to look at that as well.
For now if someone is having issues with Discovery TAB simply DISABLE the Discovery TAB on the Device/Config TAB and do not use it until we figure this out.
Eric is away today and I plan to discuss this with him when he returns.
It is possible that the Discovery TAB will simply not function properly on large flat segments like this. The CPU in the switches that runs the UI/CLI and these Daemons (not packet forwarding which is handled in the core) is simply too small. Plus when you send out this broadcast looking for devices to discover on a LARGE segment like this can cause a storm of responses.
I asked Eric to put this feature in against his wishes as I thought it would be cool and since I run a routed network at my WISP the switch only sees devices located at that tower.
I also recently noticed the discovery is not working as before since the latest UBNT firmware upgrade so Eric will need to look at that as well.
For now if someone is having issues with Discovery TAB simply DISABLE the Discovery TAB on the Device/Config TAB and do not use it until we figure this out.