

As others have said, get something that works with OpenWRT. It’s unbelievably flexible and the OpenWRT forum can be really helpful, both for finding ways to implement things and for solving problems.
As others have said, get something that works with OpenWRT. It’s unbelievably flexible and the OpenWRT forum can be really helpful, both for finding ways to implement things and for solving problems.
Debian 12, Mint, Pi OS, Windows 11, Android. Works perfectly on all of them.
Also check out Syncthing. I have it running on my Pi5, PCs and my Android phone. The phone’s photos directory and lots of other files are automatically synced to my server and computers. No open firewall port is needed, everything is encrypted in transit and it supports trusted and untrusted hosts. Syncthing supports pretty much any topology, but I’ve found using star topology is easiest to manage.
Prices in Canada and Mexico didn’t increase anywhere near this much even at the height of the pandemic.
Maybe Bird Flu is refusing to cross international borders. Or maybe U.S. monopolies no longer need to even pretend to compete and the producers are raking in record profits.
I have everything route through the tunnel and my router. Along with allowing instant access to everything I self-host and my home server through VNC, it allows me to use Adguard Home for phone DNS lookups no matter where I am. Theoretically my cell carrier should no longer be able to see any of my Internet traffic which I consider an added bonus. I’ve found no downside except some weirdness from Google if I’m out of the country for an extended period.
I self-host various applications and have been really happy with Wireguard. After watching just how hard my firewall gets hammered when I have any detectable open ports I finally shut down everything else. The WG protocol is designed to be as silent as possible and doesn’t respond to remote traffic unless it receives the correct key, and the open WG port is difficult to detect when the firewall is configured correctly.
Everything - SSH, HTTP, VNC and any other protocol it must first go through my WG tunnel and running it on an OpenWRT router instead of a server means if the router is working, WG is working. Using Tasker on Android automatically brings the tunnel up whenever I leave my house and makes everything in my home instantly accessible no matter what I’m doing.
Another thing to consider is there’s no corporation involved with WG use. So many companies have suddenly decided to start charging for “free for personal use” products and services, IMO it has made anything requiring an account worth avoiding.
I need a separate router and AP, but given a choice I’d ditch the AP. IMO there’s no reason to have two devices if one provides sufficient features and wifi coverage, and it’s one less thing to manage.
Regarding DD-WRT vs OpenWRT, after years of use my DD-WRT routers began intermittently losing their configurations when reset and I was unable to resolve the problem. The switch to OpenWRT was difficult but worth it because the firmware is so flexible and well supported. It has been rock solid.
Take a look at the GL-iNet Flint 2. It runs OpenWRT and should easily support everything you mention and more.
Would you look at that! 22 of the of 25 cities on the list are in red states.
Must be a coincidence.
AtariDump@lemmy.world wrote:
Great; how do I get my Mother to do that over the phone?
That’s not going to scale as I share out my server.
Are you incapable of recognizing that in this context my comment was a joke? What the fuck is wrong with you?
That’s not going to scale…
How many mothers do you have?
It’s not a cake walk, but I’ve something similar for a friend who can barely turn on his PC.
The OpenWRT router was fully configured before shipping it to him and the existing router’s needed Wireguard port was opened by me using the Comcast Android app. All he had to do was connect his TV to a new wifi network. That wasn’t easy, but he ultimately succeeded.
3 - An OpenWRT router with Wireguard connecting to another router 1000 miles away will do the trick.
When I bought this laptop the cheap thin clients came with eMMC storage. Keyboard and display are convenient for installations, backups and occasionally other uses. A decent size UPS is more than $100, uses power even when it’s in standby and still doesn’t last anywhere near the 7+ hours of the laptop battery when the power fails. I’m away for 3-4 weeks at a time and have had repeated power failures completely corrupt my server SSD during that time. Not everyone can fix a server problem within a few hours.
The laptop cost significantly less than a thin client, plus a gpu, plus a UPS and came with that nice keyboard and display, and a warranty. It only uses about 6-8 watts the majority of the time, important to me for a device that’s always on.
Different people have different use cases than you do. Some of us even know what works best for us.
Different people have different use cases. A thin client doesn’t work for video object recognition, nor does it come with a keyboard, display, SSD or battery backup.
I’m aware it can still be run, but as I stated in my previous comment my platform and installation were specifically purchased and configured to be fully supported and I would like to keep it that way.
This is really disappointing. My HA Supervised install was running fine last year on an old laptop and unsupported distro. In order to move to a supported installation of HA I purchased a very efficient fanless laptop specifically sized to run Debian 12 and HA Supervised. This install has been rock solid and the opposite of “Hacky” (despite Howtogeek’s clickbait title), and I expected it to easily last 5+ years. It’s been 8 months.
Of course Home Assistant developers need to sometimes EOL specific configurations and dropping 32bit hardware support was overdue (the last 32 bit Raspberry Pi was released over 10 years ago), but 6 months is an absurdly short amount of notice to give users of supported configurations on supported hardware that they’re going to be forced to migrate to something else.
A lack of empathy is a conservative hallmark.
Elon Musk , “The fundamental weakness of Western civilization is empathy,”
The bulb resets are known to TP-Link and they created a firmware version that fixed it. The company didn’t release the update and now TP-Link support reps deny that the new firmware exists, so obviously the communication failures and resets are design intent.
https://community.tp-link.com/en/home/forum/topic/666612 - post #7
Just bought some Third Reality bulbs to replace TP-Link wifi bulbs a couple of weeks ago. (The TP-Link bulbs require continual communication with TP-Link’s Chinese servers or they reset every few seconds.)
Zigbee2MQTT detects the Third Reality bulbs immediately and they have been working perfectly. The same goes for TR power monitoring smart plugs.
If I’m understanding what you want to do, I have this set up on an OpenWRT router with multiple remote endpoints used for different devices. Our phones go to a hosted Wireguard server in one city, PCs to an OpenWRT router in a different location, and IOT devices that aren’t blocked and guest devices exit access the Internet locally. With some additional work you should also be able to have remote devices connected via WG exit wherever you like.
Policy Based Routing on OpenWRT makes this possible and it should be doable as long as the devices you want to allow to exit the remote server are included in that server’s “Allowed IPs” setting. (Maybe there’s a way around that, but I haven’t had to deal with it.)