Reolink Camera not working on VM

[f825_633]

Hello All.

I have a couple of Reolink cameras I have been given for test. When they were being used on a differnent connection they were viewable by the cloud app. Testing them on a VM connection they constanty disconnect from the app.

I've tried direct ethernet into the modem and via wireless.

I have also tried a EE 4G hotspot connecting them wirelessly and they are stable. its something odd with the VM internet connection.

Heres a traceroute ont he VM connection.

1 * * *
2 hers-core-2a-xe-810-0.network.virginmedia.net (80.3.33.113) 8.467 ms 12.502 ms 11.464 ms
3 * * *
4 tclo-ic-3-ae0-0.network.virginmedia.net (212.250.25.62) 8.458 ms 13.780 ms 8.364 ms
5 52.95.218.110 (52.95.218.110) 8.619 ms 9.586 ms 9.514 ms
6 54.239.100.134 (54.239.100.134) 16.926 ms 54.239.100.94 (54.239.100.94) 17.023 ms 54.239.100.54 (54.239.100.54) 17.524 ms
7 54.239.100.97 (54.239.100.97) 18.347 ms 54.239.100.163 (54.239.100.163) 30.076 ms 54.239.100.139 (54.239.100.139) 15.647 ms
8 54.239.45.227 (54.239.45.227) 35.032 ms 54.239.42.109 (54.239.42.109) 44.861 ms 54.239.42.107 (54.239.42.107) 24.001 ms
9 54.239.47.6 (54.239.47.6) 31.227 ms 52.93.128.160 (52.93.128.160) 28.339 ms 54.239.47.6 (54.239.47.6) 27.430 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 ec2-34-240-214-13.eu-west-1.compute.amazonaws.com (34.240.214.13) 23.995 ms * 20.667 ms

Heres the traceroute on the original connection. which is stable.

traceroute to 34.240.214.13 (34.240.214.13), 30 hops max, 60 byte packets
1 lo5-t6-bng1.router.uk.clara.net (80.168.0.6) 9.358 ms 9.275 ms 9.210 ms
2 tengige0-0-0-3-t6-mse1.router.uk.clara.net (195.157.0.1) 9.879 ms 9.830 ms 9.858 ms
3 be1-t40-mse1.router.uk.clara.net (195.157.3.18) 10.058 ms 11.883 ms 11.824 ms
4 be1-t40-mse1.router.uk.clara.net (195.157.3.18) 9.415 ms 9.422 ms 9.337 ms
5 195.66.225.175 (195.66.225.175) 10.021 ms 9.922 ms 9.907 ms
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 ec2-34-240-214-13.eu-west-1.compute.amazonaws.com (34.240.214.13) 18.550 ms 18.456 ms 20.294 ms

[f825_633]

That would make a certain amount of sense, I think it might be a little more specific that just general P2P though,

I use P2P for file syncing to the office and that works fine, we also monitor video streams at work for transmission and that uses P2P meshing to distibute the video amongst the engineers who are monitoring. P2P is a failry general protocol used for all sorts. if VM really are blocking this then they should be being more technical about it and targeting specific P2P traffic.

Our work firewalls have this feature to prevent people using our 100G circuits to download things we'd rather they didnt 😉

[akuz]

Yeah. Basically I wanted to say that it’s the problem with discovery of where the NVR is located (which Virgin Media interferes with in some way). They don’t seem to interfere with video traffic itself, if you can connect to the NVR in some other way (e.g. by IP address). Thanks for starting this topic! Otherwise I’d still be stuck 🙂

[Andy2610]

Sorry to barge in late to this.  I have what I think is a similar problem.

• House in Spain with a Reolink Argus Eco. All worked fine when we were in Spain and connected to the house wifi.
• Got to the airport and had a look using cellular data.  All worked fine.
• Got back home in the UK.  Failed to connect to the stream.
• Turned wifi off on my phone and used cellular data.  All worked fine.
• Turned the firewall off on my VM Hub 3, connected my phone to the wifi again.  All worked fine.
• Turned my firewall back on, restarted the app and the Windows client... still works fine on the phone and the laptop.  I don't know if this will last or if there is some sort of cache for the connection.

So, it might die again later.  I'll monitor it and see what happens.

[f825_633]

Hello.

Not withstanding that turning off a firewall even just for a few minutes is never wise.

I think the reason why it worked in your case is the device managed to establish a connection to the reolink server and when you then turned the firewall back on the connection states within the firewall didnt change. Which is why disabling a firewall even for a short time should be thought about carefully.

The test would be to reboot the firewall whcih will clear the state and the device and see if it all automatically all reestablishes.

[Andy2610]

That makes sense.

Just on the firewall...

I have the VM router in normal mode as opposed to modem mode.  But nothing is connected to it apart from my Netgear Nighthawk which does all the heavy lifting and also has a firewall enabled.  I did try setting it up in modem mode, which is how I had my old Hub 2, but just couldn't get it working.  So all the devices around the house connect to the Netgear, the Netgear is wired to a port on the VM hub.  I don't know enough about this... but let's say I left the VM firewall off and some bad guys found out.  How far would they get?  Would that open things up to the whole house network, or would they just get blocked by the Netgear firewall?

Just to add, I'm not planning on doing this.  I just wondered.

[Tudor]

You probably did not put the VM hub in modem mode in the correct way. Instructions:

How to put a VM hub into modem mode:

1) Access your hub on 192.168.0.1, sign on and put it into modem mode. On the Hub3 the bottom LED will change to magenta. Best done from a wired connection.

2) Turn off the hub and disconnect any Ethernet cables

3) Fully initialise your own router and make sure the WAN port is set to DHCP

4) Connect your router to the VM hub with an Ethernet cable, Cat5e or Cat6, any higher specification is a waste of money

5) Turn on the VM hub. 

6) You should now be able to access the internet and the hub will now be on 192.168.100.1

[Andy2610]

Thank you.  I might give it another try.  At the moment, everything is working just using the Netgear.  I don't know if there is any benefit in doing it now.

[Tudor]

Always better to have the hub in modem mode if you can. It puts a much lower load on the hub as it has a rather under powered CPU.

[legacy1]

Firewall does not work the way its meant too on VM hub disabling can block stuff that should be allowed or block stuff when enabled when it should be allowed besides NAT blocks traffic the NAT is not expecting.

[Andy2610]

@Tudor wrote:

There are 10 types of people: those who understand binary and those who don't and F people out of 10 who do not understand hexadecimal

---

And 11 out of A that don't understand octal OR hexadecimal