this post was submitted on 28 Nov 2023
1 points (100.0% liked)
Homelab
380 readers
9 users here now
Rules
- Be Civil.
- Post about your homelab, discussion of your homelab, questions you may have, or general discussion about transition your skill from the homelab to the workplace.
- No memes or potato images.
- We love detailed homelab builds, especially network diagrams!
- Report any posts that you feel should be brought to our attention.
- Please no shitposting or blogspam.
- No Referral Linking.
- Keep piracy discussion off of this community
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Simple solution would be a RPI or router that connects back to your home with wireguard/openvpn so you have a device that you can ping
Alternatively - if your hosting a public webpage - have a cronsctipt run every 2mins that curl PUSH's to your webpage as a check-in mechinisum. After 6mins - no checkin assume its offline?
We do something like this at scale (about 80k devices) and use a combination or reverse tunnel's and push notifications. These probes allow tunneling backwards (when enabled) and also do some other local device monitoring. All running on RPI type devices with local wan or 4g
edit: assuming your internet route has a public ip (not behind nat) you could whitelist your own IP and allow it to be pingable? That ofc depends on:
a) having a router that supports that level of custimization
b) having a public ip
Thanks for your reply, this was my initial idea but then I thought it'd be a lot less moving parts to ping the router wan itself. However I realize if the router loses power that i.p could very well get served to someone else and then I'd just be pinging them instead lol.
Probably will end up doing this. In this case I would ping the wireguard i.p. of the device from another wireguard enabled device, correct?
Not sure what you mean exactly by tunneling backwards, could you elaborate?
Thanks again!