Today we will learn about loopback addresses that can be reached from the outside via routing. This is useful for running services on a router In a previous post, I talked about the loopback interface and how we can locally bind services to any address in the range 127.0.
Old article I found in my bookmarks. Although I didn’t have the use for it, I thought it was interesting.
In case if you e.g. have eth0 and eth1 and neither is guaranteed to be up. It’s more of a router setup, though (Cisco routers are well-known to use the loopback interface like this).
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
That seems like a terrible idea.
Why not just assign multiple IPs to eth0 instead? Or create a virtual interface?
In case if you e.g. have eth0 and eth1 and neither is guaranteed to be up. It’s more of a router setup, though (Cisco routers are well-known to use the loopback interface like this).
Ahh, interesting.