Video Doorbell can't connect to internet

[isiddiqi]

Are you behind a VPN? I had the same problem and had whitelist the device in the VPN director. Like you mine worked fine for several years and then after a firmware update, it just stopped. After giving the camera module unfiltered VPN traffic all was good. Of course this only make sense if you are using a VPN on your router, just a thought. Last resort would be factory reset but at least you get a fresh start. Lastly make backups. Good Luck

Yes I am using VPN, and using VPN Director. But I only route certain static IPs, and that does not include this device.

I assume you meant you had to explicitly tell VPN Director to use WAN for this device. I will try that next and report back here, but then why only this device is a head scratcher.

 

[isiddiqi]

Are you behind a VPN? I had the same problem and had whitelist the device in the VPN director. Like you mine worked fine for several years and then after a firmware update, it just stopped. After giving the camera module unfiltered VPN traffic all was good. Of course this only make sense if you are using a VPN on your router, just a thought. Last resort would be factory reset but at least you get a fresh start. Lastly make backups. Good Luck

So I tried adding an all client rule to VPN Director to route through WAN, and only selective devices via VPN. I don't route any IoT via VPN tunnel including Eufy. But still no go.

Attached is my VPN Director screen shot. Am I doing it right?

 

[custmblt]

Yes I am using VPN, and using VPN Director. But I only route certain static IPs, and that does not include this device.

I assume you meant you had to explicitly tell VON Director to use WAN for this device. I will try that next and report back here, but then why only this device is a head scratcher.

So I tried adding an all client rule to VPN Director to route through WAN, and only selective devices via VPN. I don't route any IoT via VPN tunnel including Eufy. But still no go.

Attached is my VPN Director screen shot. Am I doing it right?

I have mine setup as all say WAN in the IFACE column with the only one exception being your VPN all devices (10.0.1.1/24) Then on devices that connected to the subnet with be behind the VPN. Then all devices that you don't want to be covered bu the VPN add them in the same windows like you did and make sure the left hand side X icons are green(meaning) VPN is protecting that device and if you click it it will turn to a dark X (meaning) VPN is not protecting that device. Also click the upper tab in your windows (VPN CLIENT) scroll down to (Redirect Internet Traffic Through Tunnel) and make sure you select VPN Director (policy rules) in the drop down menu.click apply, reboot and try again.

 

[custmblt]

I forgot to mention that the subnet you are using maybe in conflict with your VPN provider. I have seen this before with PIA and others. I would recommend you stick with 192.168.50.1 as I believe that's default for you anyways. Also when you add the 10.0.1.1/24 in your VPN director you only need to add clients or devices there that you don't want to be covered by the VPN because any devices that connects will be behind the VPN by default. I'm sure there is other ways to do this but maybe some else could chime in. Good luck these things are irritating to say the least.

 

[custmblt]

So I tried adding an all client rule to VPN Director to route through WAN, and only selective devices via VPN. I don't route any IoT via VPN tunnel including Eufy. But still no go.

Attached is my VPN Director screen shot. Am I doing it right?

I figured a picture might be helpful, In the VPN Director it should look like this but in your case it would be 10.0.1.0 subnet notice the 3 at the bottom that say OVPN1 you will have only one( 10.0.1.0/24) for the local IP and your (VPN) connection for IFACE. I have two others because I have chosen to have my VPN to cover the Guest Network and IOT Network as well.

 

[isiddiqi]

I forgot to mention that the subnet you are using maybe in conflict with your VPN provider. I have seen this before with PIA and others. I would recommend you stick with 192.168.50.1 as I believe that's default for you anyways. Also when you add the 10.0.1.1/24 in your VPN director you only need to add clients or devices there that you don't want to be covered by the VPN because any devices that connects will be behind the VPN by default. I'm sure there is other ways to do this but maybe some else could chime in. Good luck these things are irritating to say the least.

Ok so I made a few changes, but still cannot connect Chime. Can you suggest what's wrong with this? I don't want to have all VPN and selective WAN, I wanted to setup the opposite way, all WAN, and a few VPN. Ofcourse I do use Wireguard and OpenVPN both.

My main DHCP starts from 10.0.1.2 to 10.0.1.254

Router address is 10.0.1.1

1. I first only added the All Connection, and rebooted the Router and tried to connect chime. No go.

2. To #1 above, I added All Guest that is at 192.168.52.1, tried to connect the Chime. No go

3. To #2 above, I added a static IP address of Eufy Chime and tried to connect. Still a no go

I defined Chime in DHCP to get this address based on Mac Address.

Chime still connects perfectly to Guest network.

Minus the #1,#2,#3, entire setup used to work perfectly, then I updated to latest Merlin. Could it be that ASUS added some bug?

 

[custmblt]

Ok so I made a few changes, but still cannot connect Chime. Can you suggest what's wrong with this? I don't want to have all VPN and selective WAN, I wanted to setup the opposite way, all WAN, and a few VPN. Ofcourse I do use Wireguard and OpenVPN both.

My main DHCP starts from 10.0.1.2 to 10.0.1.254

Router address is 10.0.1.1

1. I first only added the All Connection, and rebooted the Router and tried to connect chime. No go.

2. To #1 above, I added All Guest that is at 192.168.52.1, tried to connect the Chime. No go

3. To #2 above, I added a static IP address of Eufy Chime and tried to connect. Still a no go

I defined Chime in DHCP to get this address based on Mac Address.

Chime still connects perfectly to Guest network.

Minus the #1,#2,#3, entire setup used to work perfectly, then I updated to latest Merlin. Could it be that ASUS added so

Ok so I made a few changes, but still cannot connect Chime. Can you suggest what's wrong with this? I don't want to have all VPN and selective WAN, I wanted to setup the opposite way, all WAN, and a few VPN. Ofcourse I do use Wireguard and OpenVPN both.

My main DHCP starts from 10.0.1.2 to 10.0.1.254

Router address is 10.0.1.1

1. I first only added the All Connection, and rebooted the Router and tried to connect chime. No go.

2. To #1 above, I added All Guest that is at 192.168.52.1, tried to connect the Chime. No go

3. To #2 above, I added a static IP address of Eufy Chime and tried to connect. Still a no go

I defined Chime in DHCP to get this address based on Mac Address.

Chime still connects perfectly to Guest network.

Minus the #1,#2,#3, entire setup used to work perfectly, then I updated to latest Merlin. Could it be that ASUS added some bug?

Im not entirely sure what's going on. It maybe easier to just reinstall the factory firmware. Its possible your iptables are just all messed up, maybe some else can chime in with some ideas. As far as only using vpn on specific devices and not all? I don't know, never set up like that I'm sure its possible. I have a few clients that I just run the vpn app on the device and just passthrough vpn traffic for that said device. Im gonna stand behind my recommendation to factory reset and leave subnet at factory and only install necessary 3rd party scrips after you have confirmed it working or not. Lastly this may seem obvious but have you contacted support for your hardware(door chime and or cameras). I will say that they all seem to not to want to help soon as you tell them you are behind a VPN. That said make sure you are not before calling otherwise they will blame the vpn. Im curious how this works out for you. Good luck.

 

[isiddiqi]

Im not entirely sure what's going on. It maybe easier to just reinstall the factory firmware. Its possible your iptables are just all messed up, maybe some else can chime in with some ideas. As far as only using vpn on specific devices and not all? I don't know, never set up like that I'm sure its possible. I have a few clients that I just run the vpn app on the device and just passthrough vpn traffic for that said device. Im gonna stand behind my recommendation to factory reset and leave subnet at factory and only install necessary 3rd party scrips after you have confirmed it working or not. Lastly this may seem obvious but have you contacted support for your hardware(door chime and or cameras). I will say that they all seem to not to want to help soon as you tell them you are behind a VPN. That said make sure you are not before calling otherwise they will blame the vpn. Im curious how this works out for you. Good luck.

I had just done factory reset and did not put any scripts back on a week ago or so, and everything was again working until just now.

I think when I get a chance, I will do another factory reset and leave the default IPs alone.

Infact in my setup, I did not have to do #1, #2,#3 to access WAN. That was the default behavior by the router. My suspicion is this FW has some bug, as my setup had been working for over a year.

Let's see if anyone else has any other suggestion, but for now I am using Eufy alone with Guest account, rest everything works as expected.

 

[ZebMcKayhan]

Ok so I made a few changes, but still cannot connect Chime. Can you suggest what's wrong with this? I don't want to have all VPN and selective WAN, I wanted to setup the opposite way, all WAN, and a few VPN. Ofcourse I do use Wireguard and OpenVPN both.

Note: I don't have a BE router and have not tested the new routing scheme. Below is how it used to work but it may not apply anymore.

Wan rules always have higher priority than vpn rules. So putting your entire lan to wan will nullify all other lan rules (or GN to wan will nullify further GN ip to vpn).

Any ip not matching any rules will naturally go to wan. So if you only want some ip to use vpn then just add these ip to vpn and nothing else.

There is a priority between ovpn and wireguard but can't remember which way. But that should not matter unless you include same ip in both rules.

 

[prosperot]

Ive had a simular problem with devices. It turned out that my router was low on DHCP adreases.. enlarging the DCHP address range solved my problems

 

[isiddiqi]

Note: I don't have a BE router and have not tested the new routing scheme. Below is how it used to work but it may not apply anymore.

Wan rules always have higher priority than vpn rules. So putting your entire lan to wan will nullify all other lan rules (or GN to wan will nullify further GN ip to vpn).

Any ip not matching any rules will naturally go to wan. So if you only want some ip to use vpn then just add these ip to vpn and nothing else.

There is a priority between ovpn and wireguard but can't remember which way. But that should not matter unless you include same ip in both rules.

Yes this makes sense to me as everything was routed perfectly earlier.

 

[isiddiqi]

Note: I don't have a BE router and have not tested the new routing scheme. Below is how it used to work but it may not apply anymore.

Wan rules always have higher priority than vpn rules. So putting your entire lan to wan will nullify all other lan rules (or GN to wan will nullify further GN ip to vpn).

Any ip not matching any rules will naturally go to wan. So if you only want some ip to use vpn then just add these ip to vpn and nothing else.

There is a priority between ovpn and wireguard but can't remember which way. But that should not matter unless you include same ip in both rules.

Yes this makes sense to me as everything was routed perfectly earlier

Ive had a simular problem with devices. It turned out that my router was low on DHCP adreases.. enlarging the DCHP address range solved my problems

I have plenty of IPs available. Thanks.

 

[isiddiqi]

Ok just reset the router again to factory, and all working again for now. Let's see when it starts again. Also reverted the gateway to default 192.168.50.1, I wonder if there is some bug when you change it. If Eufy has no issue this time, that will verify it