Live data from Hacker News

Kubernetes Home – what do you do if your ISP changes your IP addresses?

vegard.blog.engen.priv.no

81–90 of 105 posts

Re: Kubernetes Home – what do you do if your ISP changes your IP addresses?

#81
post #20

Earlier quoted context omitted.

What defeats what purpose? I don't run k8s out of some love of ... managing external IPs?

Are you even running a real homelab if you're not running MetalLB in BGP mode?! Sarcasm obviously, but it's a fun exercise, especially if you get a real (v6, probably) net to announce.

Right?! Get some free IP space from he.net tunnel broker and build your own IPv6 AnyCast network using Quagga for BGP.

Kidding about building your own AnyCast network (although you really could…), but he.net tunnel broker is GOAT.

Re: Kubernetes Home – what do you do if your ISP changes your IP addresses?

#82
post #20

Earlier quoted context omitted.

Are you even running a real homelab if you're not running MetalLB in BGP mode?! Sarcasm obviously, but it's a fun exercise, especially if you get a real (v6, probably) net to announce.

Right?! Get some free IP space from he.net tunnel broker and build your own IPv6 AnyCast network using Quagga for BGP. Kidding about building your own AnyCast network (although you really could…), but he.net tunnel broker is GOAT.

I wish Happy Eyeballs worked better or let me absolutely prefer IPv4, because every time I set up a free v6 tunnel I get banned about 2 days layer for pushing a few terrabytes over it, when all I wanted was to be able to SSH into every one of my containers on a cheap VPS separately. Or the tunnel is so slow, I'm degrading my entire internet connectivity.

Re: Kubernetes Home – what do you do if your ISP changes your IP addresses?

#83

Earlier quoted context omitted.

Docker is OS-level virtualization. VMs are hardware virtualization. Different layers.

It’s not virtualization, it’s namespaces. Docker makes use of Linux kernel features; started out with cgroups and now uses libcontainer. Each container is running in its own isolated(ish) namespace on the same host kernel. It’s _very_ different technology than virtualization. You don’t need docker to make a container on Linux (or Solaris for that matter).

>It’s not virtualization

You are incorrect, this is OS-level virtualization:

"OS-level virtualization is an operating system (OS) virtualization paradigm in which the kernel allows the existence of multiple isolated user space instances, including containers (LXC, Solaris Containers, AIX WPARs, HP-UX SRP Containers, Docker, Podman)..."[0].

>it’s namespaces. Docker makes use of Linux kernel features; started out with cgroups and now uses libcontainer. Each container is running in its own isolated(ish) namespace on the same host kernel.

Yes, OS-level virtualization.

>It’s _very_ different technology than virtualization.

Incorrect, this is a virtualization technology.

>You don’t need docker to make a container on Linux (or Solaris for that matter).

No one claimed otherwise.

[0] https://en.m.wikipedia.org/wiki/OS-level_virtualization

Re: Kubernetes Home – what do you do if your ISP changes your IP addresses?

#84
post #63

Earlier quoted context omitted.

>That isn't even true You are incorrect, this is true: "OS-level virtualization is an operating system (OS) virtualization paradigm in which the kernel allows the existence of multiple isolated user space instances, including containers (LXC, Solaris Containers, AIX WPARs, HP-UX SRP Containers, Docker, Podman)..." [0]. >you share your host kernel Kernel != OS >There are parts of the kernel that aren't namespaced as w…

You can call it what you want but absolutely no one considers chroot virtualization in any meaningful sense. Nothing is being virtualized, containers are just regular processes on the host system. "OS Virtualization" != "OS" "Virtualization"

>You can call it what you want

I call it as it is.

>but absolutely no one considers chroot virtualization in any meaningful sense.

Absolutely everyone who's knowledgable in virtualization considers chroot to be a type of OS-level virtualization.

>Nothing is being virtualized, containers are just regular processes on the host system.

Wrong, "...OS-level virtualization is an operating system (OS) virtualization paradigm in which the kernel allows the existence of multiple isolated user space instances..."

"OS Virtualization" == "OS " + "Virtualization"

Re: Kubernetes Home – what do you do if your ISP changes your IP addresses?

#85

> what do you do if your ISP changes your IP addresses? I update the DNS record. Manually. It's a once in a blue moon thing, and I assume the probability of it is low enough that it will not occur when I'm so far from home that "it can wait until I get home" doesn't suffice. 15+ years or so now, and that strategy has worked just fine. … TFA's intro could do with explaining why the IP is so hard coded in the cluster,…

MikroTik has dynamic DNS that is based on random unique number for their router. I just point my DNS record to that dynamic DNS address and everything just works.

eero also offers this, but only if you pay for their Plus subscription.

Re: Kubernetes Home – what do you do if your ISP changes your IP addresses?

#86
post #82

Earlier quoted context omitted.

Right?! Get some free IP space from he.net tunnel broker and build your own IPv6 AnyCast network using Quagga for BGP. Kidding about building your own AnyCast network (although you really could…), but he.net tunnel broker is GOAT.

I wish Happy Eyeballs worked better or let me absolutely prefer IPv4, because every time I set up a free v6 tunnel I get banned about 2 days layer for pushing a few terrabytes over it, when all I wanted was to be able to SSH into every one of my containers on a cheap VPS separately. Or the tunnel is so slow, I'm degrading my entire internet connectivity.

>free v6 tunnel

There's your problem. You need some form of cost attached to some identity assets, anything under the IANA umbrella, ips/domain names. This is in order to prevent sybil attacks. This is all well studied under he hashcash bitcoin era as PoW.

So yeah, you actually need to spend some money not in exchange of something here, but as the very thing you need, you need to distinguish yourself from those that spend 0$, not because they are cheap, but because they may do it 1000 times and ruin it your pooled reputation.

Re: Kubernetes Home – what do you do if your ISP changes your IP addresses?

#88
post #68

Earlier quoted context omitted.

What's a better option than DDNS that doesn't add a bunch of latency to every connection?

Static, dedicated ip address

Sorry, I thought the context was an environment in which static IPs aren't an option.

For example, my home internet provider offers them, but the connection is guaranteed to go down once a month for maintenance. So I think DDNS is strictly better in this situation.

Re: Kubernetes Home – what do you do if your ISP changes your IP addresses?

#89
post #82

Earlier quoted context omitted.

Right?! Get some free IP space from he.net tunnel broker and build your own IPv6 AnyCast network using Quagga for BGP. Kidding about building your own AnyCast network (although you really could…), but he.net tunnel broker is GOAT.

I wish Happy Eyeballs worked better or let me absolutely prefer IPv4, because every time I set up a free v6 tunnel I get banned about 2 days layer for pushing a few terrabytes over it, when all I wanted was to be able to SSH into every one of my containers on a cheap VPS separately. Or the tunnel is so slow, I'm degrading my entire internet connectivity.

> because every time I set up a free v6 tunnel I get banned about 2 days layer for pushing a few terrabytes over it, when all I wanted was to be able to SSH into every one of my containers

can you describe a bit more? I cannot connect the dots here on how terabytes are tied to free v6 tunnel - likely I'm missing some details. Thank you in advance.

Re: Kubernetes Home – what do you do if your ISP changes your IP addresses?

#90
post #82

Earlier quoted context omitted.

I wish Happy Eyeballs worked better or let me absolutely prefer IPv4, because every time I set up a free v6 tunnel I get banned about 2 days layer for pushing a few terrabytes over it, when all I wanted was to be able to SSH into every one of my containers on a cheap VPS separately. Or the tunnel is so slow, I'm degrading my entire internet connectivity.

> because every time I set up a free v6 tunnel I get banned about 2 days layer for pushing a few terrabytes over it, when all I wanted was to be able to SSH into every one of my containers can you describe a bit more? I cannot connect the dots here on how terabytes are tied to free v6 tunnel - likely I'm missing some details. Thank you in advance.

If someone else provides IPv6 connectivity to you, you use their bandwidth. Some apps like Steam see IPv6 connectivity and use it regardless of what you'd prefer it to use, hinting mechanisms and all. So while I just wanted to use the tunnel for things that IPv4 does not provide, I always end up tunneling half my traffic over it, which free services don't like.
Post reply on HN