Obi keeps going off line

<< < (4/6) > >>

Quote from: SteveInWA on July 11, 2015, 02:41:43 pm

Well, if you've proven that the above is the cause, then why do you expect that the problem would go away, as long as you're using that system?

You can take your OBi adapter to some other location (friend or family member's house for example) and confirm the theory.

I'm not sure I'm following you here. The first part, I don't expect the problem to magically disappear. I would like to understand why it's happening though. If it's just a ping then my experiment today would have crashed the device since I was pinging it once a second and the network intrusion monitor only pings once per minute. For the second part, what would I gain by bringing the device to a different network? What theory would I be confirming? Sorry. I'm not trying to be difficult. I really just don't quite understand what you're getting at.

What am I getting at?

You said:


I tracked the problem down to a network intrusion monitor that is part of my home automation system. It pings every address on the subnet every minute. Once I disabled this everything works fine.

We don't know what other things, pinging or otherwise, that your network monitor may or may not be doing, only that the network monitor is definitely the cause of the problem.  We don't know if the true, root cause is the constant pinging by the monitor, or something else it does - that was your assumption, which you then disproved by running manual pings.  But, you proved that disabling the monitor stopped the problem, so it's incompatible with your OBi device.  Nobody else here on the forum has chimed in to report that they happen to have the same system, and here is why it is incompatible; we have no idea.

So:  it's like going to the auto mechanic.  You say, "I have a moat around my house.  When I try to drive through it, my car's engine dies.  The mechanic replies:  "Well then, don't do that."

Well yes, of course. I have disabled the network monitor. The phone is more important to me. But! I'm sure the developer of the utility would like to know what's going on so it can be addressed. I removed the ip of the Obi from the eyes of the network monitor and it still took down the Obi. And of course, the ping experiment today showed that pinging it doesn't kill it. So it must be something to do with the rest of the network.

Aren't you curious as to why this happens? No other devices on the network fall over like this. Not the Unifi APs or the switch or anything. If I can't get to the bottom of this I'm probably just going to toss the Obi on a VLAN and call it a day so I can keep using the network monitor. But it seems odd that simply pinging a bunch of ip addresses on the network would make the Obi go south.

If I were that mechanic I would have said something along the lines of "build a drawbridge". If you want your moat and to put your car in the garage we have time tested technology to get you there. In my case, I can't see the moat to know it for what it is. All I know is that my car stalls when I try to come home. :(

Oh. And I should add. The network monitor does absolutely nothing more than ping. It does send out multiple pings at once but it doesn't do anything else.

It might be worth starting a syslog & enabling the Obi to report to it:

You'll need another device (such as a windows PC) running on your network to run the syslog - once the syslog is running & reporting enabled on the Obi, re-enable the network monitor & see if anything interesting is reported before the Obi becomes unresponsive to the network.

If the network monitor can be so configured, try reducing the ping frequency to every 5 minutes & see if that has any affect.

Your router's own system log might also have some clues, though this depends on the router.


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.


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.


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.


[0] Message Index

[#] Next page

[*] Previous page