I believe the general population will have to become savvy enough to run their own VPNs from their personal VPSes. Also there are affordable seedbox providers which will let you have a decent amount of bandwidth for seeding, but yes I generally agree with your point. We need more upload bandwidth with seedboxes
In short, you need a reverse-proxy + traffic segregation with domain names (SNI).
I don’t remember much about ingresses, but this can be super easy to set up with Gateway API (I’m looking at it right now).
Basically, you can set up sftp.my.domain/ssh
to 192.168.1.40:22
, sftp.my.domain/sftp
to 192.168.1.40:121
(for example). Same with Forgejo, forgejo.my.domain/ssh
will point to 192.168.1.50:22
and forgejo.my.domain/gui
will point to 192.168.1.50:443
.
The Gateway API will simply send it over to the right k8s service.
About your home network: I think you could in theory open up a DMZ and everything should work. I would personally use a cheap VPS as a VPN server and NAT all traffic through it. About traffic from your router maintaining the SNI, that’s a different problem depending on your network setup. Yes, you’ll have to deal with port-mapping because at the end of the day, even Gateway API is NodePort-esque when exposing traffic outside.
You’d receive traffic on IP:PORT, that’s segregation right there. Slap on a DNS name for convenience.
I might have my MetalLB config lying around somewhere (it’s super easy, I copied most of it from their website), I can probably paste it here if you’d like.
Exposing services publicly on the Internet is a L3-L4/L7 networking problem, unfortunately I don’t know enough about your situation to comment.
Edit: the latter end of your post is correct. You could route to different end-points that way
Ingress controllers like Traefik come across as LB services to IPAM modules like MetalLB (I’ve never used Kube-VIP but I suppose it’s the same story). These plug-ins assign IP addresses to these LB services.
You can assign a specific IP to an instance of an “outward-facing route” with labels. I don’t remember technical terms relevant to Ingresses because I’ve been messing with the Gateway API recently.
There are providers who are OK with public trackers and don’t care about DMCAs.
In principle, torrenting over IPv6 is the same as doing it over IPv4, it’s just that there’s a lot of IPv6 addresses so you might find it cheaper to buy IPv6. Yes there are some differences in the technology but from purely an operational POV, it’s not very different.
The reason I mentioned bringing your own IPs is related to the reason why providers don’t like public torrents: it pollutes their IP space and puts their IP ranges on blacklists. But if you bring your own IPs, suddenly the provider (in theory) is safe and doesn’t care as much. YMMV of course, send an email to your provider of choice to ask more.
I have seen seedboxes with 3, or maybe 4TB of storage under $10 (don’t remember). And that’s recent (about a month ago). Yes, unlimited uploads are definitely an issue. Such cases are best combated with buying an IPv6 slot and putting that on a VPS with a provider friendly to such things (they exist at reasonable prices)
Use something that can do TCP, i.e. HAProxy, NGINX or Apache