New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
127.0.0....2?
raindog308
Administrator, Veteran
in General
We all use 127.0.0.1
I don't think I've ever used 127.0.0.2 or any of the rest of the /8
Have you?
Comments
10.0.X.X All day.
127.0.0.53 for systemd-resolved.
I use that one amongst other resolvers as a resolver in NGINX when using SSL stapling.
Gulp..
Excellent question! I've only used other than 1 when configuring a router.
I forget for what, but something in the last few months I came across mentioned using 127.0.0.2-127.0.0.8 for something or another. I didn't go that route, but it was enterprise related.
Until recently, I had an HTTP application server running on 127.1.67.74.
The frontend reverse proxy then connects to that IP.
I don't want to bind to 127.0.0.1 with a port number because it's more likely to have a conflict in port number than in internal IP.
We had an issue with OVZ 6 a few years back with a build which made 127.0.0.1 unavailable at random times so had to ask people to use 127.0.0.2 or others. Restarting the node solved the problem but sooner or later ( a few days) it would have appeared again.
127 no, but I use 10.0.0.0/16 for virtual networking
240,0,0.1 works well as a blackhole
Yes...
SSH port forwarding I sometimes will.
NTP uses various 127.0.0.0/8 addresses to access different clock drivers and locations.
What will happen if https://blog.apnic.net/2022/05/31/cutting-down-on-ip-address-waste/ ?
That can't happen.. There are way, way too many hosts that won't get updates required for that to work..
Then, do you think APNIC is crazy?
I 100% support this along with ARINs proposal to ban leasing.
Networks operators should own their IP space, not lease and there's no good reason not to use those 100m of IPs reserved for future use. If someone decided to block IPs reserved for future use it's their fault.
youtube.com/watch?v=MEKNvIQrUhQ&t=4380s
I prefer ::1 instead.
Probably the only use case where migrating to IPv6 actually saves keystrokes.
Yes, it fully is their fault, Microsoft's IP stack is the biggest issue that I am aware of, Windows 95 right through 11, including NT and all the server versions.. But you know they are not going to patch it.
I wasn't aware of this.. Source?
https://www.arin.net/participate/policy/proposals/2022/ARIN_prop_308_orig/
There was a vote to allow leasing if you attended recent meeting. 30 something against 0 for.
"ARIN allocate and assign Internet resources in a delegation scheme, with an annual validity, renewable as long as the requirements specified by the policies in force at the time of renewal are met, and especially the justification of the need.
"
If it passes or not I don't know. But if it passes by the looks of it people who are leasing ip space will have it revoked if they are not using it themselves
Like all drafts, you have to make your opinion heard at the ARIN Meetings (virtual and physical).
Interesting
30 something against the proposal you linked? Or 0 against?
No. 30 against this https://www.arin.net/participate/policy/drafts/2021_6/
The proposal to ban leasing has not yet been introduced, it's still a draft
To allow leases to be counted as justification to be put on the waiting list..
Very different...
I think leasing and selling, etc. is something not originally planned. The IPs should be managed by the people who have this duty not by random companies, it is a public resource.
how do I use them? @raindog308
OpenShift used to use 127.0.xxx.yyy for containers inside single node.
Some DNS based filters give out different 127.0.0.x addresses depending on why the name lookup was filtered, which you can then hook a different response to via a local web server. Tinckered with that some time ago. Less useful now unless you also muck about with your own CA for resigning certificates on-the-fly, as HTTPS requests will fail due to an invalid/non-existent cert otherwise.
I've also seen the range used (or at least suggested) for a private network between containers on the same host, but I'd not risk issues with components being confused by that and instead use a sub-range of 10.x.x.x or one of the other official private ranges for that.
I don't know.
Real-Time Blacklists. I forgot about them.. Use them constantly for some servers..
100%
To suggest this, in this decade, they would have to be...
Microsoft's IP stack has refused to use/interact with the Class E addresses since Windows 95 and NT.. Every M$ OS to date would need a patch because there are still some of those systems in use...
There are others, but M$ is the biggest one..
I want to give a smack upside the head to whomever at M$ thought it was a good idea to blacklist the 'For future use' IPs..
Am I missing something here? 10.0.0.0/16 is just a regular routable private IP range. What's that got to do with loopback?
Debogon needed.
And why not switch to IPv6 instead of pushing more patches to keep IPv4 afloat
That doesn't make sense. If those old ass systems are in place and working today, they don't need any updates. They aren't working with modern encryption or the Internet in general.
Only new stuff going forward would need it, and then obviously only supported stuff. It's not the first time saying "well, you're too old, buy new".
Also, Microsoft OS's, and desktop ones at that, don't tend to be edge routers. The 2012 server versions and later would be fine.
That's how it works (future reserved use, duh). Glad you aren't in charge, either.