BORIStheBLADE
Getting comfortable
Ha! Yes it is set for 200AM on Sundays. I'll turn it off and see how things go.
New Reolink Wired POE Doorbell Cam ?
- Thread starter Elton Noway
- Start date
Ahhh, I thought I saw it at one point, when I turned Auto Reboot back On it confirmed I am not crazy, well maybe a little
I turned it back Off, it defaults to On when you first setup the DB.
Oh and I just connected the DB to my spare transformer, just got home from church/lunch.
Looks like 24V output and .5A
My Spare Transformer is 16V and 10VA so it is pretty close to Load on the Supplied P/S brick:
Look what I found, I exported my Log file and opened it with Notepad, it is just a text file. There is a slew of info in it. I am going to comb through it to see if anything stands out.
My Log File (Partial):
More confirmation my DB is Not getting out to the Internet (See Highlighted Sites, Reolink and Google):
192.168.50.1 is a VLAN Gateway on my pfSense router:
Wonder if the 16% packet loss to the Gateway is a clue?
My Log File (Partial):
More confirmation my DB is Not getting out to the Internet (See Highlighted Sites, Reolink and Google):
192.168.50.1 is a VLAN Gateway on my pfSense router:
Wonder if the 16% packet loss to the Gateway is a clue?
BORIStheBLADE
Getting comfortable
Does the log only store info from last power cycle? I'll check mine out when I get a chance.
BORIStheBLADE
Getting comfortable
I don't have the log option either in firmware -
Firmware Versionv3.0.0.1459_22102808
BORIStheBLADE
Getting comfortable
From what I can tell it creates the Log (Info) file at the time you hit Export Button, it takes about 15-20 secs. I had to delete the previous file first before it it would allow me to create a new one, it errored when trying to Export a new file while one exist.
So, creates the file upon request, no history, or log file like we are use to. More of an info file...
Here is some interesting info in the file, again there is ALOT of info, everything from hardware info, network info, etc. I would share it all but have not gone through it all yet.
Booting Linux on physical CPU 0x0
Linux version 4.19.91 (ypy@ubuntu) (gcc version 8.4.0 (Buildroot 2020.02.9-3-g58c1c2e-dirty)) #5 PREEMPT Thu Apr 7 12:25:03 CST 2022
CPU: ARMv7 Processor [414fc091] revision 1 (ARMv7), cr=10c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
OF: fdt: Machine model: Novatek NA51089
Memory policy: Data cache writeback
OF: fdt: Reserved memory: failed to reserve memory for node 'cma0@0x01A00000': base 0x01a00000, size 0 MiB
On node 0 totalpages: 17920
Normal zone: 140 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 17920 pages, LIFO batch:3
CPU: All CPU(s) started in SVC mode.
random: get_random_bytes called from start_kernel+0x80/0x494 with crng_init=0
pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
pcpu-alloc: [0] 0
Built 1 zonelists, mobility grouping on. Total pages: 17780
Kernel command line: earlyprintk console=ttyS0,115200 rootwait nprofile_irq_duration=on root=ubi0:rootfs rootfstype=ubifs ubi.fm_autoconvert=1 init=/linuxrc ubi.mtd=6 ro bootts=176486,872104 resume_addr=0x00200088 user_debug=0xff
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 65896K/71680K available (3509K kernel code, 229K rwdata, 852K rodata, 176K init, 139K bss, 5784K reserved, 0K cma-reserved)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0x84800000 - 0xff800000 (1968 MB)
lowmem : 0x80000000 - 0x84600000 ( 70 MB)
modules : 0x7f000000 - 0x80000000 ( 16 MB)
.text : 0x80008000 - 0x803756a8 (3510 kB)
.init : 0x8044c000 - 0x80478000 ( 176 kB)
.data : 0x80478000 - 0x804b1660 ( 230 kB)
.bss : 0x804b1660 - 0x804d4524 ( 140 kB)
SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
rcu: Preemptible hierarchical RCU implementation.
Tasks RCU enabled.
NR_IRQS: 384
This file is 1000 lines/rows long...
Last edited:
No Auto Upgrade or Online Upgrade Option?
Did you scan your QR code or use their phone App during setup? I did not let either DB (POE or WiFi) touch the Internet...
BORIStheBLADE
Getting comfortable
No auto upgrade.
I did use the phone app for the initial setup them got the ip from that.
Hmmm...Just trying to see what is different. We have the same firmware.
Yours:
Mine:
Maybe I have a different hardware version? This Log/Info file seems to have enough info for troubleshooting. Maybe I got a Test DB.
So the Power Supply test did not stop the Signal Losses...
And that person has wings!
<loud screams of terror>
Went ahead and plugged my POE DB back in and it also has the Diagnostic Logs:
Still wondering if something changed when you guys setup via their App. You could always do a hard reset and see if that brings back these options...
Looks like my POE came with a newer build 22102808, I first ordered it directly from Reolink, my WiFi came later from Amazon...
Still wondering if something changed when you guys setup via their App. You could always do a hard reset and see if that brings back these options...
Looks like my POE came with a newer build 22102808, I first ordered it directly from Reolink, my WiFi came later from Amazon...
Last edited:
So you guys are going to rib me for this one...Wow,..me and my Static IPs...well sort of...
So when I added my Camera VLAN to my AP my switch setup a Route with the same IP as I was setting my WiFi DB with. The No Signals was from my switch since it had an IP conflict with my DB. Too wild, that was not in my troubleshooting thoughts through all of this. VLANs can me a bit tricky, well that is a VLAN on a switch, of course, becomes another LAN and needs an IP for each so your Router can send traffic properly.
How I found it was I was changing IPs on my DBs, since the POE DB will one day be permanently installed I tried to set the Static IP on the POE DB with the same IP I was using on the WiFi DB (which I had powered Off) and it kept failing. Why is it failing and why can I ping the address, I checked my router's ARP table, it was there but had a direct MAC address, when I looked up the MAC address in my Excel IP spreadsheet, there it was, my switch that my AP is connected to. Bang...that was it, the WiFi DB was conflicting with my switch the AP is connected to. Wow, talk about feeling old...
In my defense, sort of, I run an Enterprise network with 5 Managed Switches with 5 VLANs. I am old school so I have several Static IPs on my devices, which is all good but it can cause problems, like what I have been playing with these last few weeks. I set a DHCP Static Mapped IP via the MAC of the DB for the WiFi DB, problem was the IP I picked happened to be the new IP (Route) the Switch set for the new VLAN I had to setup on the port my AP was on.
I just checked the ARP table on my switch and found the VLAN IPs the switch creates under a Proxy ARP section. New to me...the section that is:
There it is, the IP I Mapped on my pfSense Router that I used for my WiFi DB, 192.168.50.3
So when I thought I was just pinging the WiFi DB I was actually pinging the WiFi DB and my switch at the same time, I am sure packets were flying all over the place, LOL
I want to thank everyone who gave me suggestions to fix my self inflicted issue. Also, forgive me for posting my journey here, was not trying to hijack this Thread, was actually thinking I was posting to maybe help others with any problems. My post did help me keep track of all the steps I took too.
So when I added my Camera VLAN to my AP my switch setup a Route with the same IP as I was setting my WiFi DB with. The No Signals was from my switch since it had an IP conflict with my DB. Too wild, that was not in my troubleshooting thoughts through all of this. VLANs can me a bit tricky, well that is a VLAN on a switch, of course, becomes another LAN and needs an IP for each so your Router can send traffic properly.
How I found it was I was changing IPs on my DBs, since the POE DB will one day be permanently installed I tried to set the Static IP on the POE DB with the same IP I was using on the WiFi DB (which I had powered Off) and it kept failing. Why is it failing and why can I ping the address, I checked my router's ARP table, it was there but had a direct MAC address, when I looked up the MAC address in my Excel IP spreadsheet, there it was, my switch that my AP is connected to. Bang...that was it, the WiFi DB was conflicting with my switch the AP is connected to. Wow, talk about feeling old...
In my defense, sort of, I run an Enterprise network with 5 Managed Switches with 5 VLANs. I am old school so I have several Static IPs on my devices, which is all good but it can cause problems, like what I have been playing with these last few weeks. I set a DHCP Static Mapped IP via the MAC of the DB for the WiFi DB, problem was the IP I picked happened to be the new IP (Route) the Switch set for the new VLAN I had to setup on the port my AP was on.
I just checked the ARP table on my switch and found the VLAN IPs the switch creates under a Proxy ARP section. New to me...the section that is:
There it is, the IP I Mapped on my pfSense Router that I used for my WiFi DB, 192.168.50.3
So when I thought I was just pinging the WiFi DB I was actually pinging the WiFi DB and my switch at the same time, I am sure packets were flying all over the place, LOL
I want to thank everyone who gave me suggestions to fix my self inflicted issue. Also, forgive me for posting my journey here, was not trying to hijack this Thread, was actually thinking I was posting to maybe help others with any problems. My post did help me keep track of all the steps I took too.
Last edited: