Posts made by FongJeng Kum_34673838378

Hi,

I'm not sure which NTP server you are trying to sync your time, but if that NTP server is a Linux system, you need to make sure it's NTP config file is configured to allow your IPC camera IP address to query to it.

Here's my snippet of my Linux's /etc/ntp.conf, my IPC camera addresses are in 192.168.x.x:

# /etc/ntp.conf, configuration for ntpd; see ntp.conf(5) for help

driftfile /var/lib/ntp/ntp.drift

# Enable this if you want statistics to be logged.
#statsdir /var/log/ntpstats/

statistics loopstats peerstats clockstats
filegen loopstats file loopstats type day enable
filegen peerstats file peerstats type day enable
filegen clockstats file clockstats type day enable

# Specify one or more NTP servers.
server 0.asia.pool.ntp.org
server 1.asia.pool.ntp.org
server 2.asia.pool.ntp.org

# Use servers from the NTP Pool Project. Approved by Ubuntu Technical Board
# on 2011-02-08 (LP: #104525). See http://www.pool.ntp.org/join.html for
# more information.
pool 0.ubuntu.pool.ntp.org iburst
pool 1.ubuntu.pool.ntp.org iburst
pool 2.ubuntu.pool.ntp.org iburst
pool 3.ubuntu.pool.ntp.org iburst

# Use Ubuntu's ntp server as a fallback.
pool ntp.ubuntu.com

# Access control configuration; see /usr/share/doc/ntp-doc/html/accopt.html for
# details. The web page <http://support.ntp.org/bin/view/Support/AccessRestrictions>
# might also be helpful.
#
# Note that "restrict" applies to both servers and clients, so a configuration
# that might be intended to block requests from certain clients could also end
# up blocking replies from your own upstream servers.

# By default, exchange time with everybody, but don't allow configuration.
restrict -4 default kod notrap nomodify nopeer noquery limited
restrict -6 default kod notrap nomodify nopeer noquery limited

# Local users may interrogate the ntp server more closely.
restrict 127.0.0.1
restrict ::1

# Needed for adding pool entries
restrict source notrap nomodify noquery

# Clients from this (example!) subnet have unlimited access, but only if
# cryptographically authenticated.
#restrict 192.168.123.0 mask 255.255.255.0 notrust

restrict 192.168.0.0 mask 255.255.255.0 nomodify notrap

# If you want to provide time to your local subnet, change the next line.
# (Again, the address is an example only.)
broadcast 192.168.255.255

Hi,

Can RLC-410 and RLC-410S IPC support H.265 codec in the next firmware?

Maybe you can share that diagram over here?

Thanks.

Well, if your local network is within your own home, then that's fine.
Accessing anything outside the internet, you need to be extra careful.

Hope it helps for your end too.

Becareful using that RTSP, it might be able to tap the plain password on the network.

Yes, you can buy that from Amazon website.
I got mine for free when I purchased some devices that come with it.

It's not an expensive unit.

This is the ferrite attached to the ethernet cable.


IMG_20170725_190159.jpg

I can just confirm that RTMP is not secure. I just did a capture of the packet and I can see it!
I have not tried RTSP yet, Will find time to confirm RTSP is also sending plaintext.

Yes, I just wanted to post this news to REOLINK.
We definitely need HTML5 in the upcoming firmware.

I think what you need is to have more no-ip addresses registered.

Thank You for clarifying.

Hi,

I am using VLC player on my PC to access to RTMP stream of my IPC. Can I find out from you, is this secure?
Cuz the URI that I use is of following:

rtmp://ipcaddr/bcs/channel0_ext.bcs?channel=0&stream=2&user=admin&password=plainpassword

Is the "password" field able to be seen if someone uses WireShark or some monitoring software to see it?
Or is this encrypted?

Hi,

I used to have this issue, but after I place a ferrite to the ethernet cable on the PoE injector and I don't get that humming sound anymore.

You can give that a try.

Thanks for the quick reply!
That's fine with me.

Hope to hear more updates on the upcoming firmware!

Hi,

I noticed that both my camera are reported with the same Input Channel No.


Selection_024.png
Selection_025.png

Or VLC which is platform independent player. Works on Android, Windows, Linux, and even Mac!

I'm sorry, everything is sorted out now. It was my silly mistake when doing the port forwarding.

Hi,

I have set port forwarding of the following ports for my 1st IPC:
Media: 9000
RTSP: 554
RTMP: 1935
HTTP: 80

I am able to access video streaming for my 1st IPC, however, I am not able to do that for my 2nd IPC
with the following port forward:
Media: 9001
RTSP: 555
RTMP:1936
HTTP: 81

Please help.


Selection_023.png

If you do a FAQ search, you will get plenty of info there.
I have also read through some Amazon.com reviews that provides feedback on this as well.

Just do some search.