Live data from Hacker News

Making a Linux home server sleep on idle and wake on demand – the simple way

dgross.ca

51–60 of 244 posts

Re: Making a Linux home server sleep on idle and wake on demand – the simple way

#51
post #35
post #22

Earlier quoted context omitted.

Seems unlikely. The world has made its peace with NAT, and IPv4 is simpler and therefore easier to understand. IPv6 isn't happening.

Roughly 40% (and rising) of Google users use IPv6. https://www.google.com/intl/en/ipv6/statistics.html

Without realising and without having had to set it up themselves.

Re: Making a Linux home server sleep on idle and wake on demand – the simple way

#53
post #22

Earlier quoted context omitted.

Seems unlikely. The world has made its peace with NAT, and IPv4 is simpler and therefore easier to understand. IPv6 isn't happening.

Or is it just happening extremely slowly? I don't think we can count IPv6 out yet.

I hope you're right, if only so that cgNAT goes away someday. But I'm pessimistic on that front. cgNAT is too easy and works just well enough to make adopting something better too low a priority to ever happen.

Re: Making a Linux home server sleep on idle and wake on demand – the simple way

#54

> Disable IPv6: this approach relies on ARP, which IPv6 doesn't use I wish more people would care about IPv6.

I wish ISPs would care. CGNAT sucks.

I’m behind CGNAT for the last 1.5 years without issue. What am I missing? I actually prefer my router not being bombarded by connection attempts all day.

Re: Making a Linux home server sleep on idle and wake on demand – the simple way

#55
post #33

This looks like one of those home server infrastructure setup rabbit holes I would've bailed out of within the first 10 minutes of Googling to research the problem. I commend the author for their perseverance and the writeup - rabbit hole writeups are their own form of entertainment. That alone was worth it. I could never run anything that looks like such a conceptual pain the butt. A pain to maintain and troubleshoo…

However that requires the disk used for backup storage to also be always on.

Re: Making a Linux home server sleep on idle and wake on demand – the simple way

#56
post #33

This looks like one of those home server infrastructure setup rabbit holes I would've bailed out of within the first 10 minutes of Googling to research the problem. I commend the author for their perseverance and the writeup - rabbit hole writeups are their own form of entertainment. That alone was worth it. I could never run anything that looks like such a conceptual pain the butt. A pain to maintain and troubleshoo…

Ideally I would like the "wake-up / fake on" infrastructure to be a feature of my wifi router.

Re: Making a Linux home server sleep on idle and wake on demand – the simple way

#57
post #33

This looks like one of those home server infrastructure setup rabbit holes I would've bailed out of within the first 10 minutes of Googling to research the problem. I commend the author for their perseverance and the writeup - rabbit hole writeups are their own form of entertainment. That alone was worth it. I could never run anything that looks like such a conceptual pain the butt. A pain to maintain and troubleshoo…

i run an rpi to host stuff for cheap (the energy drain of the pi is low), my main machine goes to sleep after 15min to save costs. seemes like a neat trick to remotely wake it up

Re: Making a Linux home server sleep on idle and wake on demand – the simple way

#58
post #50

> Disable IPv6: this approach relies on ARP, which IPv6 doesn't use I wish more people would care about IPv6.

Especially when the reality is… you can almost go IPv6 only nowadays if you wanted to. I went down the rabbit hole recently, switching my network to IPv6 primary with IPv4 as the fallback. The ultimate test was disabling IPv4 for a weekend to see what, if anything, broke. I had set up DNS64, NAT64 and 464XLAT. The only weirdness is how Windows clients handle IPv6 literals in UNC paths, which is super ugly, and how so…

464XLAT should work fine with ipv4 literals, no? At least on macOS, this will get routed to a local 192.0.0.2 interface, which does the CLAT, translates it to an ipv6 64:ff9b:: address, and relays it to your nat64 server. The ipv4-only software doesn't know any different, and the only traffic going on your LAN is ipv6.

I'm not sure if windows works the same way though...

(Edit: Looks like windows can do this, but it only configures it for WWAN interfaces, go figure: https://techcommunity.microsoft.com/t5/windows-os-platform/c...)

Re: Making a Linux home server sleep on idle and wake on demand – the simple way

#59
post #33

This looks like one of those home server infrastructure setup rabbit holes I would've bailed out of within the first 10 minutes of Googling to research the problem. I commend the author for their perseverance and the writeup - rabbit hole writeups are their own form of entertainment. That alone was worth it. I could never run anything that looks like such a conceptual pain the butt. A pain to maintain and troubleshoo…

I agree, but you could argue that the Raspberry Pi is not performant enough during restores or browsing the backups. During the backup itself performance should not have to be that big of an issue as it's mostly a background operation you will not be waiting on.

You could also use the RPi as a stepping stone which syncs it's files to the 'real' backup server which is on a daily/weekly timer instead of on-demand setup.

I'm using this concept for the problem that I want to collect metrics all day long, but not have a power hungry server running 24/7. So my RPi collects all metrics and streams then directly to my server for me to view realtime. But whenever the server is unavailable (on schedule or for maintenance) the RPi just buffers the metrics until the server is available again.

Also worth considering is just not using a single server for a single purpose but just cramming it full with utility to justify the power costs.

Re: Making a Linux home server sleep on idle and wake on demand – the simple way

#60
post #55
post #33

This looks like one of those home server infrastructure setup rabbit holes I would've bailed out of within the first 10 minutes of Googling to research the problem. I commend the author for their perseverance and the writeup - rabbit hole writeups are their own form of entertainment. That alone was worth it. I could never run anything that looks like such a conceptual pain the butt. A pain to maintain and troubleshoo…

However that requires the disk used for backup storage to also be always on.

Disk have power modes and can be spun down to save energy. A Raspberry Pi can run the OS on an SD card and mount the disk for backup storage. Leaving it in low power for a long period of time.
Post reply on HN