johnnychicago

joined 2 years ago
[–] johnnychicago@lemmy.world 3 points 4 weeks ago (1 children)

I'd like this to not be on the public internet, as general hygiene, really. Putting a weak little camera out there where it can be easily caught by an ip/port scan and get hammered seems neither smart for the device itself nor for the network it's in.

[–] johnnychicago@lemmy.world 1 points 4 weeks ago (1 children)

I've thought of bundling a small router, since I have a GLiNet lying around - but I am afraid power management will be challenging. Car battery and a few panels seem bulkier than I had in mind, and packaging that for weather is a challenge, too.

[–] johnnychicago@lemmy.world 1 points 4 weeks ago

OH this is nice. I did dabble with the original Wyze Cams and alternative firmware long time ago, I should try this!

 

Hello --

I know this is not a 100% fit for this community and I apologise - but I don't really know where to ask best. There's some selfhosting involved, so maybe the smart crowd here has some recommendations.

Here goes:

I want to mount a camera at a quite remote location. I have Wifi there that I can use (I pay for it, but its usage is shared, I don't monopolize it). I do not have power there. It's outside, mild in winter, quite warm in summer. I will not get there for months at a time. I want the camera to be private, not open to the world. Ideally I'd like a solar powered wifi camera that can connect to my home via Wireguard (I have that bit going, multiple roaming notebooks and phones connect to home, terminated in an Opnsense router).

I do not need any specific smart features on the camera - PTZ would be nice, but not even fully required.

I can come up with a configuration that involves a Raspberry Pi routing an off the shelf camera via a Wireguard tunnel, or similar, but that doubles the power issues I need to solve. I am not opposed to DIY a solution, but there's the challenge of getting it well packaged in a waterproof way.

Considering I can't really touch the wifi setup (cheap commercial router), I don't really see a way to have a private connection without having some sort of a VPN (I could do others than wireguard in a pinch).

If you'd like to help me chip away at one or the other bit of this problem, I'd be very grateful.

[–] johnnychicago@lemmy.world 2 points 2 years ago

Hey - lots of good points, thanks. I think I'll give this a try on a less used domain of mine, just to get a practical feel for it. I do appreciate the arguments against, but to an extent, if both my VPS's are down, so is basically everything served by the domain. I will have to make sure monitoring is taken care of, and I do have a completely remote email address from all of this.

knot seems to have a current docker image maintained by the project, so I'll give that one a try and see how it goes. Stay tuned for me coming back crying and repenting in a few day's time, I guess :)

If worst comes to worst, I can always go back to where I came from, it will have been a learning experience.

 

Hello --

I have my DNS with a cloud provider that I want to stop using, and was considering where to move it (a few domains with a handful entries each). At some point I was wondering if I should run it myself. I have two VPS' in different data centers with fixed IP addresses, and I read up a bit - seems like this is doable. I am not set on what software to use. I would like it to run in a container. Does anybody have any recommendations, positive or negative?

Thanks :)