Great Project!
I just wish, their HDB would enable filtering on which cameras have Ethernet, and/or the data-lines connected on the USB-Power-Plug, so that I could equip them with USB NIC (for the ones that don't have ethernet), and then run them with a POE-Splitter.
Having the data pins connected would also enable lots of other nifty use-cases.
Also, have they managed to forward port the drivers to a recent mainline kernel in the meantime, or are they still on ancient vendor SDK kernel versions?
Or upgrade them to modern OpenWrt, which has supported the near identical (minus USB port) D-Link DIR-882 since 2021: https://openwrt.org/toh/d-link/dir-882_a1 , as User 6SixTy has hinted at.
Is there a table of supported hardware, that contains info about the USB-connection (or ethernet) on these devices. Like, which have data-lines connected, can the device electrically do host and device mode? Can I use a POE2USBC adapter, that presents itself as a USB-network device to the camera?
Ability to filter on those columns would be great.
Is thingino using the Ingenic linux kernel 3.ancient SDK version, or do they have/use something newer?
The manual, as OP said, does not offer any explanation, why the device might show up with an additional MAC/IP at the upstream switch port, and which services it might offer. OP sounds knowledgeable enough to be able to exclude the possibility, that the additional MAC/IP could be from one of the PCs, like e.g. when playing with VMs using an internal bridge in the Hypervisor.
Maybe the device has a bigger "cousin" device, that includes "control via APP", and this feature was not properly/fully disabled on this one.
Was the network port bridged to both PCs all the time (as the description makes it sound, or did only the "active" PC get a functioning network connection?
Could you tell from the FDB of the upstream device, if there were more than two MAC addresses active on the port?
Did you (hopefully) open it up and make PCB pictures before chucking it?
Many a soundcard supports changing jack "direction". Here's a StackExchange answer from 2012, on how to do it with the GUI tool `hdajackretask` : https://askubuntu.com/a/911961
Why did you not just login to the device, and switched off "Broadcast to multicast", or changed the destination address?
Edit: Some brands of Network-KVM use this, so that you can control the target device from another device, like e.g. an App on a tablet. That way you don't have to stand next to the target device in the noisy and cold machine room
Yes, more free beta-testing for Apple, Netflix, Cisco, Sony, and other large commercial users is definitely needed and beneficial to the development of the free world. Or so I've been told
From the DTS posted in another thread here, the board looks to be running a 5.10 Linux kernel. OpenWrt proper runs much newer kernel versions, so the board looks to be running a vendor fork of OpenWrt branched of already a while ago.
Maybe they are planning to catch back up to regular/normal/mainline OpenWrt at some point.
How "trustworthy" is the "dedicated network processing accelerator (NPU) (supports L2/L3 hardware processing, IPv4/IPv6 dual stack, 20Gbps switching capacity, full byte wire-speed forwarding)"? Is it fully "hardware", auditable, or does/could it run some blob firmware with unknown/undocumented "features"?
Having the data pins connected would also enable lots of other nifty use-cases.
Also, have they managed to forward port the drivers to a recent mainline kernel in the meantime, or are they still on ancient vendor SDK kernel versions?