![](https://sh.itjust.works/pictrs/image/5ded51e3-b5b5-4832-bea0-1b30c0adb2f6.png)
![](https://lemmy.dbzer0.com/pictrs/image/a18b0c69-23c9-4b2a-b8e0-3aca0172390d.png)
The android ways is revanced.app
In fact, this is actively worse than doing nothing at all. Remote peers will download a block, see that it’s corrupted, discard it, and blacklist op for sending them bad blocks.
Me neither. But it’s worth saying anyway.
Nope. Just commenting to let you know that on Linux, you should check the 2Gb of ram box because the installer behaves in a way that can make it crash on Linux if you don’t and well, clicking the box is a simple fix.
It requires an LTE capable gateway and a data plan. As for the rest you can simply write your routing tables so that if the main gateway doesn’t work, use the secondary gateway with lower prio.
Postgres in general is a considerably better db engine than SQLite in every metric except portability. Whenever you need more than a simple config storage, I heavily recommend using postgres. If it’s good enough for gitlab, it’s good enough for me.
Indeed, but in that case an off-the-shelf SMTP relay works fine.
So to be clear, you want traffic coming out of your VPS to have a source address that is your home IP?
let’s go back to fundamentals and assume for a second that your VPS provider allows these packets out and your VPS initiates a TCP connection like that. It sends a TCP SYN with source: home address and dest: remote.
The packet gets routed to the remote. The remote accepts and responds SYN/ACK with source: remote and dest: home address.
Where do you think this packet will get routed? When it gets there, do you think the receiving server (and NAT gateways in between) will accept this random SYN/ACK that doesn’t appear to have a corresponding outgoing packets sent first? If so, how?
You need a proxy for outgoing to avoid your source server being on a residential adress, which all but guarantees all mailservers using spamhaus etc will block you by default. DKIM and DMARC are needed in their own right but an SPF fail will already make your mail fall into spam.
Not really. Your VPS’s public IP is not yours to change, for obvious reasons, and it’s unlikely that your hosting provider will let you send packets from your VPS using a source address that is incorrect. if they let you, then any replies to those packets will evidently get routed to the actual IP, ie your home IP. If you really want to forward SMTP to your VPS (which has less chance of being on a Blocklist by virtue of not being a residential IP), I suggest declaring your VPS as your SMTP sender in SPF, instead of declaring your home IP and trying to make that work with the VPS IP. The VPS can then be configured as an SMTP relay (this is a key feature of SMTP) to your home instance, or you could forward all traffic on the appropriate ports at the TCP level, but I don’t advise doing this.
I hope you understand that if what you’re asking was possible, I could rent a VPS, spoof your IP and receive traffic meant for your IP without any issues. For the same reasons, I think the other commenter mentioning x-forwarded-for headers is wrong if you’re not using DKIM (and even then it’s iffy). Otherwise I could just write a payload with mailto: whatever, from:you@yourdomain and x-forwarded-for: your home IP and pass SPF checks without having control over your IP.
if you’re still confused about SMTP feel free to ask more questions
Idrac, wake on lan, and plug-in behavior: power in bios are all great options here.
It exists, but it’s generally really small shops that I wouldn’t feel comfortable recommending.
The bigger hosting providers are fine with the status quo, because it means their support tickets are from people who at least know something about anything rather than complete noobies who need help resetting their password (not that there’s anything wrong with that, it’s just higher volume and not what hetzner staff is trained on)
It’s unclear to me how the blue ones are supposed to work? Are you just going to wire stray wires to the appropriate places and put mostfets there? That sounds dreadful. Soldering to the already tinty pads next to the processor with a ribbon cable was already a pain, I don’t see a reason your should pay more to subject yourself to a worse experience.
I heavily suggest using a ribbon cable model such as this (I haven’t tested that particular vendor, the one I used is gone, this is just an example): https://fr.aliexpress.com/item/1005005989694443.html
Ribbon cable models have all the parts premounted, you just need to solder it in place which is hard enough. It’s also unclear to me how the emmc stuff happens without a ribbon cable.
Other things I bought according to my AliExpress history:
There are several remotely controlled torrent clients, transmission comes to mind. It has web interface and state of the art is that the webpage registers itself as a magnet: link handler so clocking one adds it to the remote server (disclaimer: I don’t actually know that that is a feature of transmission. I use a client that is integrated with my router and it has this despite the router not being particularly nice)
Its on the low side but still within reason. Its not just an OS, it’s an OS, a full steam install, a web browser( actually 2 of them because steam also packs an embedded browser), a desktop environment, HD animations, HD wallpapers (several of them) and it adds up quick.
I dont know if it support roomba devices at all but Valetudo is an alternative firmware for some autonomous vacuums.
Nice idea if you actually have the rest of the redundant network, uplink and all that jazz (otherwise you’re wasting time and money).
the reason this won’t ever be a product is because if you’re serious about your redundancy you’re installing extra NICs inside the servers, which are ideally not second-hand. the only people who would be the target market of such a product is just you.
also: do these servers not have pcie slots inside? is there truly no way of adding nics inside?
I use magnetico and have no need for the bells and whistles, but that seems really interesting!
It should work just fine. the proxmox just sets up a bridge to the virtual interface when you install it and after that, VMs you deploy will appear in to everything else on the network as if connected through a switch.
However, watch out about it your routing tables. If the pihole isn’t on the same network (regardless of if it is virtualized or not), you have to tell other computers on the network how to reach that other network, by making changes to their routing table, or the one in your router (that is literally its job, after all).