Would the drive by down voter, care to enlighten me. I would like to know what I am doing wrong.

@TOOGAM I am not writing for experts, I am writing for idiots like me (that is what answers are for). I did not know this until a few minutes before. I read something about the wide range of loop-back addresses, and wondered if I could use them. I have added example of how I created 2 docker services, and 2 python services, all some port, but different loop-back address. Also I added which OS I am using. It may not work for your OS.

@ctrl-alt-delor - Here I thought you were writing answers for the community. As for the reason I issued the downvote. Your answer reads more like you telling the problem you faced and how you fixed it. Which of course doesn't answer the author's question (in my opinion).

@Ramhound, yes I used 127.0.0.2 to solve a problem. That is what it is for. If it could not be used to solve problem, then it would have no use.

I am still confused by how your answer, answers the author's question, in some significant way by adding information that wasn't already provided. Anyways, you wanted to know the reason a downvote was issued and I have been kind enough to explain my reasoning.

@Ramhound the range was added, because it is wrong it the other answer (out by one). I would edit, but don't have the rep. The rest is not in the other answer. It shows why 127.0.0.1 is not enough for all use cases, by showing that you can add several (4 in my example) server, on the same port, and only on the loop-back interface. This is useful, when testing servers. and answers the question “What is 1270.0.0.2 for?”. Everything else in the question is context, and why the question was asked.

The accepted answer isn't inaccurate. What’s the Difference Between 127.0.0.0 and 127.0.0.1?

one

one, what?

127.0.0.0 is the network address. You can not connect to it. If you listen to it then you listen to the whole range, of addresses that are you.

The difference is one.

Well that accepted answer isn't saying you should configured any application to listen to 127.0.0.0

I also don't agree that listening to 127.0.0.0 would configure the application to listen to the entire 127.0.0.0/8 subnet.

The other answer (not accepted) says “The most commonly used IP address on the loopback device is 127.0.0.1 for IPv4, although any address in the range 127.0.0.0 to 127.255.255.255 is mapped to it.”

0.0.0.0 is normally reserved for that purpose.

Any event you are taking the your quoted statement far to literally. I believe the author could have simply used 127.0.0.0/8 syntax instead and it would have meant the samething.

Could have, but did not. But most of my answer is not about this little error. It is about answering the question, “What is 127.0.0.2 for?”, by giving an example of its usage.

Anyways I don't really care anymore, you have given a good faith effort to improve the answer, although i don't see the relevance of your usage case, it just isn't worth my time to discuss it further so I just reversed my vote.

Good day

I won't be discussing this further.

Worth pointing out you have more then enough reputation to propose an edit to that existing answer.

I went ahead and submitted an edit to the current accepted answer. It took me awhile to verify not only did was the original quote from the Wikipedia article changed to something else entirely (which I updated) the correct range is indeed 127.0.0.1 to 127.255.255.254 not what the original quote indicated.