Talk:IP address/Archive 4

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
Archive 1 Archive 2 Archive 3 Archive 4

IP Address

I'm an IP address. — Preceding unsigned comment added by 2601:98A:400:82F8:D5C4:6D59:62DB:9BC7 (talk) 22:02, 1 November 2017 (UTC)

External links modified

Hello fellow Wikipedians,

I have just modified one external link on IP address. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 18 January 2022).

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 08:32, 10 November 2017 (UTC)

Incomplete table

#Private addresses has an incomplete table. The left-most column has no header text and fits several data into the one column. The paragraph after the table uses the notation "192.168.0.0/24" however interpreting that /24 (or what it would be for Class A and Class B networks) is not mentioned in that section of the article.

The article Private network has a great table, providing all these data. It is linked to from IP address but I think copying its table into IP address (replacing the current one) would significantly improve this article. 101.174.193.172 (talk) 23:44, 18 November 2017 (UTC)

Variety is good and the current table is fine. I suppose "Description" or similar could be inserted as the header for the first column, but the current table has certain benefits, including being simpler to comprehend. It's true that some work in understanding what /24 means is required, but if someone hasn't mastered that they are not going to get much from any IP article. Johnuniq (talk) 00:35, 19 November 2017 (UTC)
Nonsense.
Besides, the screenshot in the lede shows the much more common "255.255.255.0" format for declaring the subnet. Only when navigating to Private network are the mask bits clarified. The table at #Private addresses shows /8, /12, and /16 (as prefix, not mask). The reader encountering "192.168.0.0/24" won't find /24 in the table immediately above it.
"It's true that some work in understanding what /24 means is required" for definitions of "some work" which match "already having former knowledge of". Using the /24 format in this section without explaining / tabulating it, or linking it to somewhere that does, is unhelpful. People are going to get out of an article what it provides; the only way people won't get information from the article is if it does not provide it. That's the authors' failing, not the readership's. 101.174.193.172 (talk) 11:07, 20 November 2017 (UTC)
I agree that some explanation of both netmask and CIDR notation is required in this article. IPv4 and maybe other articles?, would also benefit from a small paragraph on that subject, with a link to a relevant detailed explanation. IMO, the explanation in CIDR could serve that purpose, although the section on subnet masks needs some improvement.
I wouldn't know whether netmask notation is more common or not - the mere fact that MS-Windows uses it in its main IP4 configuration dialog makes it common as it is the dominant end-user operating system, but it's still just one OS. However, CIDR notation is shorter and simpler, and it is also used for IPv6, so I favor that. Anyway, if both are adequately explained, then the choice is mainly a matter of taste.
WRT the table: the texts '/24 prefix' etc. would be better placed in their own column. The texts '1 x A' etc. will be cryptic to most people, unless they have actually read the entire preceding section, and make the connection. If included at all (they are only of historic significance), they should also be in their own column.
RogierA7 (talk) 10:11, 23 November 2017 (UTC)
I have removed the first column and added a reference to the table. ~Kvng (talk) 15:02, 27 November 2017 (UTC)

Semi-protected edit request on 21 April 2018

Change

to

209.52.88.54 (talk) 22:13, 21 April 2018 (UTC)

 Done L293D ( • ) 22:42, 21 April 2018 (UTC)

Semi-protected edit request on 3 June 2018

Please change the first sentence to this: IP address is a unique set of characters and numbers that defines a device. It is specific to a device and cannot change. 2A02:C7F:C22C:A000:41A1:46F5:9E25:765 (talk) 11:59, 3 June 2018 (UTC)

 Partly done: I removed "numerical" from the lead sentence but did not make the change proposed because it is not accurate. Despite appearances, even IPv6 addresses are numerical labels. They use 32-bit numbers which look like a mixture of letters and numbers, however, so "numerical label" can confuse those who expect only decimal numbers, as in this request. Eggishorn (talk) (contrib) 16:27, 3 June 2018 (UTC)

Semi-protected edit request on 6 June 2018 — main article.

iP_address#IP_versions: Please add the following template to that secton:

IChance2 (talk) 19:13, 6 June 2018 (UTC)

 Partly done: I used the {{seealso}} hatnote instead of {{main article}}. I personally believe that this hatnote is unncessary given that IPv4 address exhaustion is already wikilinked in the second paragraph of that section, but I went ahead and added it anyways because this is a benign addition that isn't meant to be prevented by semi-protection. —KuyaBriBriTalk 21:07, 6 June 2018 (UTC)

Semi-protected edit request on 22 April 2019

What is my IP Address?

Your IP address is something you probably rarely think about, but it's vitally important to your online lifestyle. Without an IP address, you wouldn't be able to get today's weather, check the latest news or look at videos online.

As time goes by, there's a lot of free Geolocation tools [1] that you can use on how you are able to determine your ip address [2], ISP [3], security type and other crucial ip address data is available through this tool. At some point, this kind of tools was a big help for you to know their location and other information you may want to know. Rektdata (talk) 06:39, 22 April 2019 (UTC)

References

  1. ^ IPDetectives, A Free IP Geolocation Tool (April 2019)
  2. ^ IP Address?, Internet Protocol, Version 4 & 6 (IPv4, IPv6)
  3. ^ MyIP, Internet Service Provider Tool
I don't see how this fits into the article. It doesn't strike me as encyclopedic content, at least not as written. Please feel free to elaborate and reopen this request if needed. ‑‑ElHef (Meep?) 13:31, 22 April 2019 (UTC)

Semi-protected edit request on 7 May 2019

Hello there,

Just want to inform you that you have broken link on the "Diagnostic Tootls -- lanstat", I'm glad if you let my link as replacement to the broken link. It's a free IP Lookup tool (https://ipdetectives.io/). Hope you will let me to replace my web page. Thank you! Rektdata (talk) 07:49, 7 May 2019 (UTC)

The best thing to do would be to write the article Lanstat, but we can't add external links in the body text (see Wikipedia:External links). Your tool looks great, but we rarely link to tools. – Þjarkur (talk) 10:30, 7 May 2019 (UTC)

Semi-protected edit request on 28 May 2019

When the link-local IPv4 address block was reserved, no standards existed for mechanisms of address autoconfiguration. Filling the void, Microsoft developed a protocol called Automatic Private IP Addressing (APIPA), whose first public implementation appeared in Windows 98.[11] APIPA has been deployed on millions of machines and became a de facto standard in the industry. Many years later, in May 2005, the IETF defined a formal standard for it.[12]


Could you remove "Many years later" from the last sentence? No other dates are given, and this phrase isn't really useful if nothing talks about the original date. 208.95.51.53 (talk) 13:20, 28 May 2019 (UTC)

 Done NiciVampireHeart 13:25, 28 May 2019 (UTC)

Semi-protected edit request on 13 September 2019

Could u please make it shorter it will take a lifetime for me and my friends to read it96.81.60.145 (talk) 15:50, 13 September 2019 (UTC)

 Not done, It should be easy to read. It's only 31,778 bytes so it is short already.--SharabSalam (talk) 17:06, 13 September 2019 (UTC)
4000 words is not exactly brief. ~Kvng (talk) 14:13, 16 September 2019 (UTC)
Maybe not brief, but quite readable in the current size. Not to mention that you usually don't have to read 100% of the article. BernardoSulzbach (talk) 16:21, 16 September 2019 (UTC)

Semi-protected edit request on 29 April 2020

37.104.199.79 (talk) 00:42, 29 April 2020 (UTC)
 Not done: it's not clear what changes you want to be made. Please mention the specific changes in a "change X to Y" format and provide a reliable source if appropriate. GoingBatty (talk) 00:49, 29 April 2020 (UTC)

"IP地址" listed at Redirects for discussion

A discussion is taking place to address the redirect IP地址. The discussion will occur at Wikipedia:Redirects for discussion/Log/2020 May 2#IP地址 until a consensus is reached, and readers of this page are welcome to contribute to the discussion. 1.Ayana (talk) 19:16, 2 May 2020 (UTC)

Semi-protected edit request on 3 September 2020

In the external links sections, you should add a link similar to this.

There's an existing link to Curlie's IP Addressing Page, which has links to many IP address (and subnet) related online tools and tutorials. Some of those links are really good, but many of them are pretty old (just HTTP too) and do not cater to the needs to modern world fast paced networking requirements.

For example, take a look at the following requirements which are not covered by Curlie provided links, and there are only a few ones on the internet which does so, I think reference to such tools (better if on the same page) would be pretty useful for cloud and network engineers, and developers:

   1. Subnet creation:
       Not just cloud engineers with limited networking experience, but network engineers too, many a times struggle to create subnets (say plan IP addressing scheme) in an orderly manner.
   2. Finding overlapping address
   3. Creating supernets
   4. Verify if an IP or subnet already exists in a network


Your thoughts on this?

HTH 2409:4072:6C9D:8B98:89F3:DC0E:2A64:7393 (talk) 12:19, 3 September 2020 (UTC)

Not done, we try to only link to high quality sites in that section, rarely do we link to tools. However you are correct that all the links on that Curie site are outdated and very unhelpful, so I've also removed that. – Thjarkur (talk) 20:02, 3 September 2020 (UTC)

Could you provide any references from Wiki which directs us to do so and any references on how to gauge the quality of a website? I believed that the quality of content matters on Wiki, not the name of a website, may be I was wrong. And when does that rare condition occur when you would want to link to tools? Thanks 157.50.4.123 (talk) 07:38, 4 September 2020 (UTC)

See WP:RS and this list. When there is a disagreement among editors, we most frequently use WP:BRD to decide what gets included in articles. ~Kvng (talk) 16:32, 7 September 2020 (UTC)
There is some information at WP:LINKSTOAVOID and WP:NOTDIRECTORY. This particular website is something self-published, and it's to specific to be of much help to most readers. – Thjarkur (talk) 22:10, 7 September 2020 (UTC)

Formatting problem with section header

On android mobile wikipedia app, section header appears normal in article, but has additional css (?) formatting on "sidebar" outline of article 137.165.174.34 (talk) 16:09, 14 November 2021 (UTC)

Fix typo in "IP Versions" section

The second sentence of the fourth paragraph of the "IP Versions" section would make more sense if it said "as there was no separate IP specification at the time" instead of "as there was to separate IP specification at the time".— Preceding unsigned comment added by 174.92.125.69 (talkcontribs)

 Done Mindmatrix 17:33, 25 January 2022 (UTC)

Edit request to the description of IP assignment in Overview part

in the overview part, there is a sentence says "Only one of the RIRs still has a supply for local assignments in Africa." This should be updated. Currently 3 RIRs (APNIC, LACNIC, AFRNIC) can still assign new IPv4 addresses according to there policies. [1] — Preceding unsigned comment added by みゆきかがみ (talkcontribs) 00:30, 12 February 2022 (UTC)

References

  1. ^ "en IPv4 exhaustion". APNIC. Retrieved 2022-02-11.

Semi-protected edit request on 13 August 2022

Please change the first sentence to: An Internet Protocol address (IP address) is a numerical label such as 192.0.2.1 that is connected to a computer network that uses the Internet Protocol for communication and represents a client. 185.53.198.141 (talk) 15:39, 13 August 2022 (UTC)

Servers have IP addresses as well; not all IP addresses represent clients. Guy Harris (talk) 19:26, 13 August 2022 (UTC)
And peer-to-peer communication without intervening servers is also possible over IP. Guy Harris (talk) 20:13, 13 August 2022 (UTC)
This proposal needs to be discussed before an edit request. As mentioned above, the proposed wording is not adequate as "client" is not the point. The current wording is unclear and should be fixed. However, the curse of wanting to be 100% accurate under all circumstances makes it difficult to produce a digestible definition. The key words "assigned to each device" were present in April 2021 but were removed for some reason presumably with arguments like it's not a device, it's an interface on a device, along with but there can be multiple IPs on an interface and/or one IP may be load-distributed to many interfaces/devices. Johnuniq (talk) 23:31, 13 August 2022 (UTC)
 Not done - as noted, the proposal would cause the text to be incomplete and, as a result, incorrect. Guy Harris (talk) 08:03, 14 August 2022 (UTC)

What about "end of a connection"? — Preceding unsigned comment added by 178.138.96.208 (talk) 17:10, 15 August 2022 (UTC)

What's a "connection"? It's not an IP connection, as IP is a connectionless protocol, and it's not a TCP connection, as connectionless transport protocols such as UDP can run on top of IP, and at least some protocols using UDP, such as DNS, are also connectionless. Guy Harris (talk) 18:59, 15 August 2022 (UTC)

"IP" as shorthand for "IP address" ?

This is maybe more of a day job question: I see "IP" used as shorthand for "IP address". My inclination is to always correct this, but I'm curious if there is any consideration for this to ever be used in a formal document.

(If "yes", there possibly should be a mention of that usage here; if "no", my thought is not to add a proscription here, since Wikipedia isn't affirmatively a manual of style.) -- NapoliRoma (talk) 18:08, 12 December 2022 (UTC)