I’ll try when I log back in
I tried shopt -s nullglob and shopt -u nullglob, same error. Its getting late, I’m going to nuke the VM and tray again with newer instructions.
I installed AMS on Ubuntu 16.04, everything works fine. If you still can’t, try going up. Start with 16.04 + AMS and then only distro up.
I think the problem @Token is having is there is an undocumented dependency, which he doesn’t have. When I tried again last night I almost got AMS installed in a virtual machine. I think I got it to run, but when I tried to run it this morning AMS wouldn’t run. I think I know what is missing, need to run more tests. I don’t have time right now to test, I need to finish my taxes and get them mailed.
@Token are you having any better luck with AMS?
I’m going to try 16.04 per @TimHolus but I’m installing XCP-NG right quick on a server to put a 10G card to use.
It works when grabbing that release. Getting the zip from the (I donno, git homepage of the project?) seems to be a bad release or something.
Thanks @TimHolus
Followed their vid to load up a utility module something-or-nother:
Used Reolink rtsp instructions for streaming to VLC:
Progress:
Congrats @Token for getting AMS to work or at least to install.
I was able to install and get AMS running on Kubuntu 20.4, but since I don’t have any IP cameras, this is as far as I can go. Thanks, @TimHolus for posting about AMS.
It is very good that there is progress. Add ssl and you’re right at the finish. Port forwarding and the fw rule will probably be a simple matter for you. Anyway, I already drew it earlier as if something …
This thread hits me in the feels
I’m still working out if I’m sticking with xcp-ng or going back to ESXi. When I have that fingered out I’ll be working on this again. Feels like I’m at the 10 yard line thanks to everyone here.
This.
Also, be aware that any admin worth his salt will notice large amounts of video traffic coming in via a port he does not expect, from a location he does not expect, direct to your workstation.
I know that as an admin if I saw an end user essentially punching holes in my network with SSH, I’d be taking action to stop it either via better firewall (one that does content inspection for instance if they don’t have one already) or a LART.
Where LART = blunt stick, management complaint, etc.
It’s a lot easier to claim “I didn’t know I was doing anything wrong” if you’ve only done basic stuff and haven’t been warned yet. But if you have been warned against this or told “no you can’t do that” and then go figuring it out and knowingly working around security policy… that’s entirely different
As an invisible solution, as a half joke half seriously earlier I suggested broadcasting these cameras to youtube or something similar. Then admin will have to scratch his head heavily
Of course, if someone has no problem with privacy even if such a camera would be reachable only through a private url, this is also a solution and I know such solutions in the wild but there is no wonder when we live in an age of people who use the Ring … etc.
Notify us of future project progress.
This wouldn’t be totally off the table, these are not indoor cameras. My paranoid side says not to play with the 1% chance some bored 4chan soldier stumbles on it and makes it a purpose to find the location and maybe even some trolling.
For sure. Currently chasing a Splunk squirrel right now and I might need to make my xcp-ng setup the VM would be on more permanent first.