This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Ring Doorbell stops working after a short while / long running tcp sessions

Hi all,

We use a Ring Doorbell which has run perfectly for 2 years. What I have noticed is when I upgrade from v18.5 MR1 to MR2 that initially everything works correctly. But after a short while (one or several hours) the Ring does not send out notifications anymore and no video is sent out. When I revert to MR1 it runs ok continuously (for days).

When I run a trace in MR2, the only thing that strikes me is that I see several TCP Window Full / ZeroWindow messages when I ‘start a ring event’, while I do not see this when I run MR1. This does not necessarily indicate a problem I understand. I have not run tcpdump long enough to see if anything went wrong already before that point.

Have any of you run into a similar issue with long-running connections since 18.5 MR2?

This thread was automatically locked due to age.

0 Ferdinand van Aesch over 2 years ago

Did you manage to resolve this? I seem to be having the same issue.
Cancel
Vote Up 0 Vote Down

Cancel
0 Danny den Hartog over 2 years ago in reply to Ferdinand van Aesch

Well, recently I decided to upgrade to v19 eap, hoping it would solve the issue. The issue hasn’t occurred since.
Cancel
Vote Up 0 Vote Down

Cancel
0 Ferdinand van Aesch over 2 years ago in reply to Danny den Hartog

That’s interesting. I might have to do the same. I currently route it through a Linux box with a simple NAT and it works fine. Ugly workaround.
Cancel
Vote Up 0 Vote Down

Cancel