Quote
But it seems odd that simply pinging a bunch of ip addresses on the network would make the Obi go south.
No, you proved that this is
not the cause of the problem.You
have proven that some other function (not the pings) of your particular network security product is causing the problem. Nobody here has that same equipment, which is what would be required to perform more in-depth testing.
Quote
But! I'm sure the developer of the utility would like to know what's going on so it can be addressed.
That company's engineers would be the only ones who could determine what's going on. They'd need to obtain an OBi, or work with you, to enable detailed debugging/logging on their product, and then study what behavior (ports being opened, protocols being used, etc.) are being interpreted by their equipment as an intrusion that needs to be blocked. You claim that their product is merely pinging the network, but you haven't instrumented your network to truly know that's the case. Modern network security software/hardware uses a variety of (sometimes proprietary) techniques to attempt to protect the network. I had suggested taking the OBi to some other network location as another data point to confirm that your network gear is, in fact, the culprit.
Quote
Aren't you curious as to why this happens?
I'm curious about a lot of things, among them:
- What causes Alzheimer's disease, why do some people get it and not others, and what can be done to prevent it?
- How many other planets have intelligent life? Why haven't we found one yet?
- Why do house cats mysteriously go into a frenzy sometimes, running around the house aroused, and then calm down?
- Why are so many people interested in the Kardashians?
I'm not curious why your particular network gear disrupts OBi use, since this has not been a widespread issue impacting OBi users. Perhaps somebody else is curious.
Since you have apparently found a compromise solution that will enable your devices to coexist (put the OBi in a VLAN), then I'd say it's a non-issue.