This page is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
I have just commented out a pile of links, please review the links by having a look at WP:WPSPAM , WP:NOT#LINK and WP:EL and only return the ones that need to be in the article. Peachey88 ( Talk Page | Contribs) 05:27, 17 January 2008 (UTC)
What is the current RFC reference for the WKPs and the ports >1023? I'd think that something like this should be in the 1st paragraph. 198.24.6.134 ( talk) 22:56, 12 February 2008 (UTC)
Hi there, we reverted each others edit in List of TCP and UDP port numbers and I like to comment a little bit: I suggest to add references and not external links ( WP:MOS), secondly I would be in favour of removing all external links as they only attract commercial link spam over time. Cheers - 83.254.215.235 ( talk) 23:57, 1 March 2008 (UTC)
In March 2007 it was proposed to merge the stub article at Port 666 into this page. The Port 666 article was an unsourced and orphaned stub which simply noted an association with first-person shooters and viruses.
As there was no opposition to the merge over the following 12 months, I've now carried it out and redirected that page name here. There was no need to merge the Doom reference (it was already in this article) and the virus claim was unsourced.
This seems an uncontroversial merge but if others think otherwise I'm happy to discuss. Euryalus ( talk) 05:35, 12 March 2008 (UTC)
The IANA PORT NUMBERS list shows 5190-5193 allocated to AOL - 5190 does not list ICQ. The ICQ article notes "...the protocol is proprietary...". Just because AOL owns ICQ these days (via their purchase of Mirabilis) doesn't make the ICQ use of 5190 "Official". I plan to make a change in a day or so to show ICQ as "Unofficial" and in conflict on port 5190. -- Joe Sperrazza ( talk) 05:10, 17 April 2008 (UTC)
protocol-name-from-IANA-list-in-case-used-there, expansion of protocol-name into text if needed (expansion of acronyms if any) "protocol" - brief description of protocol
These are just my thoughts, let me know what you think. Thanks, -- Joe Sperrazza ( talk) 14:18, 23 April 2008 (UTC)
I'm hoping someone knows more about these ports than I do, but I noticed they weren't in the list so I figured I would mention them to see if someone would be willing to research and add them to the list.
They both appear to be part of a torrent network, as the packets being uploaded/downloaded are accessing numerous IP addresses worldwide and seem to be a considerable drag on my network. Best Asptard ( talk) 13:26, 2 May 2008 (UTC)
There is a problem in the table for port numbers 9119 to 9800. The ports are listed as 9119, 9418, 9535, 9535, 9443, 9535, and 9800. I'm not sure whether "9443" is in the wrong place, or the first two "9535"s should be "9435"s, but something is amiss.
Sorry I don't know enough to correct it...
-- Tinkerer1359 ( talk) 17:26, 8 May 2008 (UTC)
8646/TCP www.SmartSystemsLLC.com Used by Smart Sale® 5.0 Backup service
is there a reason why this is appended to the last table? looks like advertising to me, especially since it's out of order, and references the URL... is there a particular reason why SmartSystemsLLC is noteable?
69.251.64.102 ( talk) 20:04, 6 December 2008 (UTC)
Is this article really come across by people looking for infomation about seaports?? Is that disambiguation link at the top of the article really neccessary? —Preceding unsigned comment added by Mespinola ( talk • contribs) 16:24, 29 January 2009 (UTC)
Port 694 should be changed to "Official". According to this http://moin.linux-ha.org/lha/ha.cf/UdpportDirective which states that it is IANA registered. —Preceding unsigned comment added by 80.192.120.114 ( talk) 11:58, 6 May 2009 (UTC)
The link for this unofficial port designation is broken. I note that nmap reports this port as belonging to this same service, but I cannot find any supporting refrences. Comments?
May 12, 2009 Bjjohns ( talk) 12:09, 12 May 2009 (UTC)
Microsoft uses port 379 for exchange services ( http://support.microsoft.com/kb/278339). I'm not sure what it should be documented as, but it should probably be added to the list. —Preceding unsigned comment added by 76.77.16.176 ( talk) 16:52, 28 May 2009 (UTC)
http://www.cyberciti.biz/faq/centos-linux-ipsec-firewall-rules/
* 50 is Encap Security Payload (esp / IPSEC-ESP ) protocol * 51 is IPSEC-AH - Authentication Header protocol
Should these be added to this list?
This list really needs to be split, not jsut because of wikipedia guideliones on size ie it approaching 100kb size, but not least because with udp and tcp in one it quite confussing, i understand it but if i take out my network knowledge it very hard ot understand. Any views or ideas?-- Andrewcrawford ( talk) 20:37, 15 May 2009 (UTC)
hmm. go for it. andyzweb ( talk) 15:51, 28 October 2009 (UTC)
Ports ?? —Preceding unsigned comment added by Seb-Gibbs ( talk • contribs) 18:31, 13 November 2009 (UTC)
The "gpsd" wikipedia article says port 2947 is used for it. Should that be added to the list? Michael9422 ( talk) 19:14, 1 February 2010 (UTC)
All of the ports VMware uses are conflicts with registered ports, and those have been registered in in the iana list for years. Why aren't they listed here? I went ahead and added 902 thisafternoon, since that's the most common conflict you see reported when installing VMWare server. Is there any good reason not to list all of them? —Preceding unsigned comment added by 38.124.2.254 ( talk) 15:52, 3 March 2010 (UTC)
Econet was a networking service - protocol and hardware - used by Acorn Computers Ltd of England in their microcomputers. With the adoption of Ethernet, they implemented "AUN" (Acorn Universal Networking) which encapsulated the econet packets within UDP packets, on port 32768.
Although Acorn bit the dust a long time ago, their hardware soldiers on in many places, and over the last few years, emulators such as BeebEm now support the networking protocols. Robirrelevant ( talk) 08:41, 3 April 2010 (UTC)
heloo —Preceding unsigned comment added by 202.138.120.37 ( talk) 14:43, 8 May 2010 (UTC)
hi ,
i ill tell u a story of a man whose was geneous in its own way .
if u really wants to succced u need to be in touch with good smart people .
and for that u neeed to do friendship with people like me .
so why r u waiting .come and join me.--------arun. —Preceding
unsigned comment added by
202.138.120.37 (
talk) 14:46, 8 May 2010 (UTC)
Hello, just passing by - saw this page didn't have the Mumble added. I put it in and cited an official source for it; I think I got the formatting right, feel free to improve! 75.72.168.44 ( talk) 23:20, 20 July 2010 (UTC)
I agree with the editor who noted the use of Bare URLs in the article. They all should be changed to proper templates. I'll work on doing so over time. Help from others would be most appreciated. JoeSperrazza ( talk) 03:36, 27 December 2010 (UTC)
WTF is Shains Throbber Protocol TCP 40 LOL LOL LOL Amists ( talk) 12:43, 22 March 2011 (UTC)
Whoops, there is port 1222 in the well-known ports section. Well-known-ports range from 0 to 1023 only, so it must be some kind of mistake here. Anyone here who is willing to fix this? Thanx in advance... -- 93.245.188.157 ( talk) 21:17, 30 January 2011 (UTC)
I added this port 34567 that I have registered with iana.org, which you can see at http://www.iana.org/assignments/port-numbers but someone reverted it. Please add it after verifying the iana page. —Preceding unsigned comment added by 122.164.53.66 ( talk) 20:53, 26 April 2011 (UTC)
Since we're not listing all known usage of ports, identifying conflicts appears to be problematic. Identifying conflicts also flirts with WP:OR. I propose to remove the Conflict legend and add a short paragraph either here or at Port number describing port conflicts. -- Kvng ( talk) 16:42, 11 July 2011 (UTC)
I would agree that the conflict markings should be removed. Conflicts only occur when two services are actually installed on the same system, but this happens so rarely with most of these obscure services that it does not constitute a problem worth marking. In addition, there are many more ports in use by all kinds of applications which are nowhere notably documented. Kbrose ( talk) 03:05, 2 August 2011 (UTC)
For what it's worth, I was confused on reading this article with the three color highlights. The yellow highlight represents conflict (i.e, two protocols having same port #). Although this has nothing to do with which protocol is official/unofficial for that port, yellow highlight seems to trump white/blue in the table. Maybe just highlight the port number in yellow rather than the whole row? — Preceding unsigned comment added by 69.46.103.131 ( talk) 23:03, 19 October 2011 (UTC)
How should we add port numbers that are only reserved for SCTP protocol (not used in tcp/udp) I was considering adding 36412 S1-Control Plane (3GPP) (officially registered by IANA) but current table has colums for tcp and udp but it's not clear how to add sctp only ports Umbeebmu ( talk) 13:29, 25 October 2011 (UTC)
List of TCP and UDP port numbers
. Now there are 2 other Protocols we are trying to squeeze in. With significant editing effort, we could create 2 new columns for
SCTP and
DCCP. I'd suggest that approach is not worth the effort. Plus, with a new row for the DCCP entry - the table may be sorted on that column (using UDP for both UDP and DCCP), putting the DCCP entries together. That's my 2 cents. --
Unixguy (
talk) 01:09, 21 November 2011 (UTC)What is the criteria for inclusion in this list? The IANA list contains more assignments than listed here. -- Kvng ( talk) 15:40, 8 July 2011 (UTC)
I really have to disagree with your criteria as to what ports you include in your list. It is quite confusing to look for what you believe is a defined user port and then discover that you are "wrong". You have to go to the IANA website in order to realise that it actually is Wikipedia that is wrong. If you do not want to correct the page, certainly it should be clearly stated somewhere that the list is neither complete nor accurate. — Preceding unsigned comment added by 80.63.2.124 ( talk) 12:59, 5 December 2011 (UTC)
In both of the wiki tables on the main page I lined up the Port number, TCP and UDP columns using spaces as padding. The reason for this is for wiki markup readability only. It does not affect the browser rendering of the page. -- Unixguy ( talk) 00:38, 21 November 2011 (UTC)
this isn't my area but this link 1 shows 2425 for Fujitsu App Manager. [I could not access the iana.org site]...-- Billymac00 ( talk) 06:57, 30 December 2011 (UTC)
I noticed the entry for rsync (873/T) is marked "Official USA Only". Huh? Unless I'm missing something, ports are either registered or not; there is no "you're registered for Russia only" or "you're registered for use everywhere but Scotland".
Plus, I can't find any sources supporting such an assertion.
Thoughts, anyone? Unless someone knows of a good source for this claim, I will remove it as unsupported.
Thanks! — UncleBubba ( T @ C ) 18:01, 3 July 2012 (UTC)
I just added a description for this port. If you look at the IANA record for this port, [2] you'll see that I am the assignee for it. I guess that makes me an authority. :-) Donpayette ( talk) 16:23, 14 August 2012 (UTC)
We should also add a column listing the official registered names of ports as well. [ http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xml listings] -- 64.4.68.234 ( talk) 16:56, 6 February 2013 (UTC)
How do we deal with RFC references to cite where it is defined as official? Do we put a citation after the name? or next the word official? Or do we do as is done on port 13 and put the RFC as a link in parentheses?
Davidgumberg ( talk) 00:24, 10 May 2013 (UTC)
There has been repeated vandalism to the low port numbers on this page, surely only official uses should be listed for the well known ports, or splitting it as per below. — Preceding unsigned comment added by 101.166.57.152 ( talk) 20:37, 4 June 2013 (UTC)
Is it correct to add WebSocket to TCP port 80? -- Abdull ( talk) 11:53, 6 August 2013 (UTC)
I think unofficial uses should be listed separately from official uses. Also, if official uses are listed it should be an exhaustive list seeing as the information is easily available at IANA's website. — Preceding unsigned comment added by 96.225.101.25 ( talk) 00:37, 13 March 2013 (UTC)
A using reading this pages wants to see what protocols are used on a certain port. Having to go to 2 different list is counter-productive and many less experienced users won't even do that. Please keep them together. — Preceding unsigned comment added by 89.181.160.102 ( talk) 12:33, 6 August 2013 (UTC)
Adding a column for date (as well as a column for the RFC) is useful. The date should be the official RFC publication date (for official ports). For unoffcial ports, the date could be the first usage reported. — Preceding unsigned comment added by 89.181.160.102 ( talk) 12:36, 6 August 2013 (UTC)
What about FEAR Combat game using 27888 port? 62.152.145.53 ( talk) 00:33, 3 January 2014 (UTC)
Maybe range 0-1023 can be included (as a link ?)... — Preceding unsigned comment added by 2A01:E34:EE0F:C40:B8BA:F7C0:7D39:70BB ( talk) 10:33, 4 March 2014 (UTC)
Some items add this in the description, so might be nice to pull out into a column.
50.199.243.89 ( talk) 16:05, 19 August 2014 (UTC)
- Steve
I'm not sure where to put this, just wanted to throw it out there. The bios on certain machines lists connections to port 6910 for the Dell Cloud Desktop server. It appears to be a Wyse product. — Preceding unsigned comment added by Family Guy Guy ( talk • contribs) 21:47, 16 December 2014 (UTC)
TCP services with port numbers 6541 and 6542 appear between 5632 and 5655, so they may be mistyped and could mean 5641 and 5642. I didn't find any conclusive information about MirrorOp2, but it could very well be a remote desktop application, similar to pcAnyWhere which seems to use ports 5641 (TCP) and 5642 (UDP).
Chaotix63 ( talk) 15:38, 25 March 2015 (UTC)
All Unnoficial port numbers needs sources (just as the official ones do, but we already have them).
I'll be removing all unreferenced information within some months.-- damiens.rf 01:36, 25 June 2015 (UTC)
Hello fellow Wikipedians,
I have just added archive links to 5 external links on
List of TCP and UDP port numbers. Please take a moment to review
my edit. If necessary, add {{
cbignore}}
after the link to keep me from modifying it. Alternatively, you can add {{
nobots|deny=InternetArchiveBot}}
to keep me off the page altogether. I made the following changes:
When you have finished reviewing my changes, please set the checked parameter below to true to let others know.
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).
Cheers. — cyberbot II Talk to my owner:Online 11:36, 18 October 2015 (UTC)
NetApp / SANtricity port is 2463 not 2643. — Preceding unsigned comment added by 195.190.86.68 ( talk) 16:22, 14 December 2015 (UTC)
Multi-use port color coding is lacking/not sufficient. The issue being that we have color coding for official, unofficial, and multi-use. What color code do we use when it is both multi-use official? multi-use unofficial? And best yet multi-use official/unofficial? With the last likely being the most common. I'm not sure of the best solution but here are two possible solutions:
1) Add a column: multi-use - true/false or yes/no I don't think this will work very well as new rows are added old rows would also have to be edited.
2) Each port is a single row. List each service is as row in a service column that has sub columns of TCP | UDP | Description | Status example:
port | service | TCP | UDP | Description | Status ____________________________________________________ 9 | TCP | UDP | Discard Protocol | Offical | | UDP | Wake-on-LAN | Unofficial
Thoughts? MichaelLeeHobbs ( talk) 13:03, 20 December 2015 (UTC)
Hello fellow Wikipedians,
I have just added archive links to 2 external links on
List of TCP and UDP port numbers. Please take a moment to review
my edit. If necessary, add {{
cbignore}}
after the link to keep me from modifying it. Alternatively, you can add {{
nobots|deny=InternetArchiveBot}}
to keep me off the page altogether. I made the following changes:
When you have finished reviewing my changes, please set the checked parameter below to true to let others know.
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).
Cheers.— cyberbot II Talk to my owner:Online 01:02, 6 January 2016 (UTC)
Hello fellow Wikipedians,
I have just added archive links to 8 external links on
List of TCP and UDP port numbers. Please take a moment to review
my edit. If necessary, add {{
cbignore}}
after the link to keep me from modifying it. Alternatively, you can add {{
nobots|deny=InternetArchiveBot}}
to keep me off the page altogether. I made the following changes:
When you have finished reviewing my changes, please set the checked parameter below to true to let others know.
An editor has reviewed this edit and fixed any errors that were found.
Cheers.— cyberbot II Talk to my owner:Online 17:54, 8 February 2016 (UTC)
Hello fellow Wikipedians,
I have just added archive links to 8 external links on
List of TCP and UDP port numbers. Please take a moment to review
my edit. If necessary, add {{
cbignore}}
after the link to keep me from modifying it. Alternatively, you can add {{
nobots|deny=InternetArchiveBot}}
to keep me off the page altogether. I made the following changes:
An editor has reviewed this edit and fixed any errors that were found.
An editor has reviewed this edit and fixed any errors that were found.
An editor has determined that the edit contains an error somewhere. Please follow the instructions below and mark the |checked=
to true
An editor has determined that the edit contains an error somewhere. Please follow the instructions below and mark the |checked=
to true
An editor has reviewed this edit and fixed any errors that were found.
An editor has reviewed this edit and fixed any errors that were found.
An editor has reviewed this edit and fixed any errors that were found.
An editor has reviewed this edit and fixed any errors that were found.
When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at {{ Sourcecheck}}).
Cheers.—
cyberbot II
Talk to my owner:Online 07:25, 28 February 2016 (UTC)
Hello fellow Wikipedians,
I have just added archive links to 2 external links on
List of TCP and UDP port numbers. Please take a moment to review
my edit. If necessary, add {{
cbignore}}
after the link to keep me from modifying it. Alternatively, you can add {{
nobots|deny=InternetArchiveBot}}
to keep me off the page altogether. I made the following changes:
When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at {{
Sourcecheck}}
).
An editor has reviewed this edit and fixed any errors that were found.
Cheers.— cyberbot II Talk to my owner:Online 00:33, 19 March 2016 (UTC)
See Special:Diff/745891794. I found these issues with the reference to Laravel documentation:
PHP's built-in development server, which makes me question if this is specific to Laravel at all.
While Laravel itself may be notable enough for inclusion by Wikipedia's standards, unless there's reliable third-party sources to verify and tell me what port 8000 is about, I don't see this happening. 80.221.159.67 ( talk) 00:31, 24 October 2016 (UTC)
There's a to-do list at the top of this talk page.
There's been little to no enforcement of common selection criteria before August 2016, when I started editing. Even as I clean up the list, there are articles which I can verify to exist, but am unable to assess if they are notable enough for inclusion (in scope) when they may not have a Wikipedia article, or specific parts of the protocol are not described in the main article of the port topic. There even exists list items which are unofficial, unnotable and unsourced.
Some list items are or have been just technical jargon, such as
SQL Services
or Print-srv, Network
PostScript
, almost like directly from IANA's list. Even as an example
Border Gateway Protocol (BGP)
may need more description to explain in short terms what the protocol is about (without opening the self-reference wikilink), and there are many more of these.
I have generally taken the stance that if a company itself is notable, but their products don't have a Wikipedia article (or a notable section about the product in the company's article), I have removed it from the list.
The table legend colors can be difficult to maintain. There also seems not to be an exact criteria what qualifies as multiple use
: If a port is unassigned at IANA, does that mean an unofficial application using that port is multiple use
or not?
More issues with the table come from the fact that IANA may have assigned both TCP and UDP, but commonly the protocol only uses one by design or specification. This sometimes leads to editors removing (blanking) the other protocol, while it is still "valid" to mention both.
I would also suggest bringing up the use of Template:Yes, Template:No and similar templates to make the table easier to read.
I don't think WP:TNT to be appropriate at this point as the existing ports (especially unofficial ones) are a great base for modification, but lots of cleanup is still to be done.
I also believe it would be a good idea to use pending changes protection level 1 after the cleanup is done. It is not appropriate while the cleanup is ongoing, as it could cause undue load on the reviewers.
And for what little it's worth, the daily pageviews have increased about 2,000+ after the cleanup started. I could call this rewrite/cleanup very useful indeed. (Personally, I'm doing it for the fun of learning the every obscure protocol out there.) 80.221.159.67 ( talk) 22:51, 17 October 2016 (UTC)
Some technical expertise ({{
Expert needed}}
) may also be needed (later). I am knowledgeable of networking and can help.
80.221.159.67 (
talk) 22:55, 17 October 2016 (UTC)
I have also added some citations, which may be duplicated or not very accurate (e.g. not anchoring to right page where multiple things are being referenced at once) in places. Some of these I have marked with <!-- XXX: Comment -->
.
80.221.159.67 (
talk) 22:58, 17 October 2016 (UTC)
Special:Diff/749839962. This was the third time removing this from the list. If you believe first-defense is notable enough, create an article for it or provide a reliable source to establish notability in real use. 80.221.159.67 ( talk) 12:43, 16 November 2016 (UTC) (edited: 12:50, 16 November 2016 (UTC))
I'd like to discuss the removal of my edit (diff is linked below) [3] Cited reason for removal: Visual edit, unclear notability, lacking a better source) A few points I'd like clarification on; 1) If visual edit mode is frowned upon, why is it enabled? 2) Unclear notability - How does one get notability if one's edits are removed? 3) I thought that the www.iana.org website itself would be confirmation enough for a registered port - if this is not the case, could someone please explain to me where I have gone wrong? Thankyou, Jambulance ( talk) 05:36, 3 June 2017 (UTC)
@ Jambulance: Sorry, I didn't see your message earlier. You seem to be talking about Special:Diff/783082575.
I can say the scope is not very clearly defined in the lead paragraph of the article. That's something to improve upon. 84.250.0.210 ( talk) 22:20, 22 June 2017 (UTC)
Question: Which one of these mentioned templates is more appropriate here?
I also wonder if the following templates should be tagged to the article:
Template:Refimprove may be enough for now to cover the two, but I'm up for a discussion.
84.250.0.210 ( talk) 05:16, 30 June 2017 (UTC)
Minor topic not likely to justify an independent article. Could be summarize in the target article. - Mr X 14:10, 5 July 2017 (UTC)
I've tagged it with speedy deletion, since there isn't enough context and references to verify notability. The same article has also been previously speedy deleted. 84.250.0.210 ( talk) 01:33, 6 July 2017 (UTC)
There also isn't anything to merge. The source article has had its listed items copied directly from the target article. If you'd like, you can add references to the target article to support those claims. Notably I haven't sweeped yet through port range 7000 – 7999 to establish notability and references, as pointed out in the to-do list at top of the talk page. 84.250.0.210 ( talk) 01:44, 6 July 2017 (UTC)
In example, Special:Diff/789995279 attempted to add Mosh (mobile shell) UDP ports 60000–61000 to the article. Currently, we don't have a table for notable ports operating in dynamic/private port ranges.
Should we add a table to the dynamic/private ports section for additions like these? What would be the criteria for verification and inclusion, since they are not in the scope of IANA? 2001:2003:54FA:D2:0:0:0:1 ( talk) 05:29, 12 July 2017 (UTC)
Special:Diff/794677559 added port 2099 for League of Legends ( PVP.net). The source given only supports the statement of that port being used for PVP.net, while League of Legends uses UDP ports 5000–5500. In comparison to something like Battle.net, I don't quite understand or see how PVP.net would meet notability of its own (or if they're even comparable). Thus, I reverted the edit with Special:Diff/794845836.
League of Legends itself is notable for inclusion, so I'll be adding ports 5000–5500 to the list shortly. 2001:2003:54FA:D2:0:0:0:1 ( talk) 11:16, 10 August 2017 (UTC)
The current table implies that most protocols use both TCP and UDP. It seems that the IANA frequenly assigned both TCP and UDP ports to a protocol even if it only actually used one or the other. Any thoughts on how best to handle this. — Preceding unsigned comment added by Plugwash ( talk • contribs) 13:52, 24 July 2017 (UTC)
Thanks for starting this discussion. I don't think there's an easy solution, or it's not an appropriate time to solve due to burden of unnotable entries. This has also been noted before at § Rewriting this list.
IANA did indeed historically assign both TCP and UDP to ports, even if only one was ever used by design (e.g. TCPMUX). Currently (to my belief), IANA seems to assign only one protocol (TCP or UDP) on a port (if requested) and mark the other as reserved
.
I took a bold move earlier to tag some of these cases with {{
Available|Assigned}}
. {{
Yes-No}}
could also be used, but I can't come into an agreement with myself which one to use. I'd like to see the table converted to use {{
Yes}}
and {{
No}}
sometime for some consistency and readability, but I'm unsure when the right time to do this would be. Other noteworthy thing is ports 2375–2380 in example: There is no consistent practice of marking them as reserved ({{
N/A|Reserved}}
), or if they qualify as multiple use
or not. It'd require substantial effort to verify both assignment and actual use, and there's no easy way to say if some software uses the other protocol when the mainstream doesn't.
I think the scope or table legend may need to be clarified. Ideas are welcome.
2001:2003:54FA:D2:0:0:0:1 ( talk) 21:27, 25 July 2017 (UTC)The following table is an example and may not be factually accurate or current. |
Port | TCP | UDP | Description | Status |
---|---|---|---|---|
0 | Reserved | Reserved | Reserved | Official |
1 | Yes | Assigned | TCP Port Service Multiplexer (TCPMUX). Historic. Both TCP and UDP have been assigned to TCPMUX by IANA, [1] but by design only TCP is specified. [2] | Official |
9 |
|
Yes | Discard Protocol [4] | Official |
No | Yes | Wake-on-LAN [5] | Unofficial | |
20 | Yes | Maybe | File Transfer Protocol (FTP) data transfer [6] [3] | Official |
100 | — | — | Unassigned (with known unauthorized use further explanation needed) [1] | Official |
1314 | ? | ? | Festival Speech Synthesis System server [7] | Unofficial |
60000–61000 | Port 22 | Yes | Mosh – a remote terminal application similar to SSH – typically assigns ports for ongoing sessions between Mosh servers and Mosh clients. [8] | — |
References
{{
citation}}
: Unknown parameter |month=
ignored (
help)
{{
citation}}
: Unknown parameter |month=
ignored (
help)
{{
citation}}
: Unknown parameter |month=
ignored (
help)
... The default port for the wake-up transmission is UDP port 9. ...
{{
cite web}}
: Unknown parameter |dead-url=
ignored (|url-status=
suggested) (
help)
apple-kb-HT202944
was invoked but never defined (see the
help page).... Festival waits for clients on a known port (the value of server_port
, default is 1314). ...
{{
cite book}}
: |website=
ignored (
help); Unknown parameter |dead-url=
ignored (|url-status=
suggested) (
help)
self-published source?
Official Unofficial Multiple use | ||||
---|---|---|---|---|
Port | TCP | UDP | Description | Status |
0 | Reserved | Reserved | Reserved | Official |
Port | TCP | UDP | Description | Status |
---|---|---|---|---|
0 | Reserved | Reserved | Reserved | Official |
Thoughts on this proposal? There is currently no accessible way to insert the table legend into <caption>
that I know of (true and tested).
2001:2003:54FA:D2:0:0:0:1 (
talk) 01:40, 28 July 2017 (UTC)
<caption>...</caption>
s. I'm also aware the color boxes don't really convey the message semantically, but there's seemingly a limitation preventing use of block elements in table captions on MediaWiki. (Ideally, the legend in caption should be a {{
flatlist}}
.) Feedback wanted.
2001:2003:54FA:D2:0:0:0:1 (
talk) 02:45, 28 July 2017 (UTC)A new contributor added Mouse without borders to the article twice without reliable sources. On the second chance, I gave it a benefit of doubt and went digging for sources myself.
The references from CNET News and PC Magazine read out like a review. Betanews is more news-like, but uncertain for me if it's a notable publication. It only briefly mentions MWB.
The main issue however is what appears to be original research: Ports 15100 and 15101 and TCP were not referenced at all by the original contributor, and I could not also find reliable sources to support this statement.
WP:CSC also has a criteria Every entry meets the
notability criteria for its own non-
redirect article in the English Wikipedia.
. Since
MWB is a redirect to a section of
Microsoft Garage where
MWB is only a short list entry, I'm unsure if it meets the criteria for inclusion.
2001:2003:54FA:2F79:0:0:0:1 (
talk) 06:16, 23 August 2017 (UTC)
@ Truong2D: Welcome to Wikipedia. Because Wikipedia is an encyclopedia and not an indiscriminate collection of information, Wikipedia cannot accept contributions for which no reliable sources exist ( original research). A reliable source is a previously published source, preferably from a (peer-reviewed) secondary/third-party source. Reliable sources are needed for an encyclopedia to be verifiable, and self-published sources are also largely not acceptable.
As the aclaimed author of MWB, please read this guide to Wikipedia's conflict of interest guideline. If you are getting paid to edit or create articles where you may have a conflict of interest, please also read Wikipedia:Paid-contribution disclosure before making any more edits to articles.
For more help on editing at Wikipedia, Wikipedia:Teahouse and Wikipedia:Help desk are glad to help you in need. 2001:2003:54FA:2F79:0:0:0:1 ( talk) 08:25, 24 August 2017 (UTC)
These are not measurements of quality and should be taken as a grain of salt. I hope someone has better use for this data to improve the article.
(Not exactly one year, but I didn't want to wait any longer.)
A possible explanation for unknown/undetermined statuses is a lack of consistency or typos. The method of examination was a simple text search using
grep
.
If someone points out my math is wrong, that's fine.
I used toollabs:pageviews for this one. The decline may be explained by Wikipedia's overall decline(?) and less web search results landing on this page after cleaning "all that crap".
There was a positive increase in daily pageviews until October 2016. On the last days of year 2016, pageviews dropped substantially and returned immediately after the new year started.
Big positive peaks in pageviews occurred on 28 September, 2016 and in mid-May 2017.
Personally, I contributed this much (with the help of toollabs:xtools-articleinfo and something else):
A total of 370 edits, added +76,080 and deleted -44,806. Overall this accounts for +31,274, which is 71.06 % of all text in this one year? I'm almost sure I also forgot one IP-address, but I can't find it. Wish I had better data to show.
Please consider contributing! It makes an impact, there's not a lot of volunteers working on this (semi-)actively. I'm sure there's also other contibutors to thank a lot, but I can't name any from top of my head. 2001:2003:54FA:2F79:0:0:0:1 ( talk) 10:53, 24 August 2017 (UTC)
Xfire died last year. I tried using both web search engine and Wayback Machine on Xfire's official website to find any kind of citation for port 25999, but was unable to. So,
I removed Xfire (and others) from the list. This is kind of a shame, but I felt like {{
Citation needed}}
would've not helped.
84.250.17.211 (
talk) 14:35, 10 November 2017 (UTC)
Hello fellow Wikipedians,
I have just modified 9 external links on List of TCP and UDP port numbers. 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:
{{
dead link}}
tag to
http://www.vmware.com/community/message.jspa?messageID=425783When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
An editor has reviewed this edit and fixed any errors that were found.
The help request has been answered. To reactivate, replace "helped" with your help request.
Cheers.— InternetArchiveBot ( Report bug) 00:36, 4 September 2017 (UTC)
{{
Cite IETF}}
hack on ports 1027 and 7542, also seen previously at
Special:Diff/781179064.
2001:2003:54FA:2751:0:0:0:1 (
talk) 02:11, 6 September 2017 (UTC)
{{Cite IETF}}
ones are troubled, as explained here.Because
Template:Cite IETF has well-known and previously reported bugs
[1] where archive-url
or dead-url
parameters with any alias are not well respected,
[2]
User:GreenC opted to add
Template:Webarchive after the reference instead (at my suggestion).
[3] It's a hack, of course.
This bot keeps repeatedly replacing {{Webarchive}}
with {{
Cite web}}
and unknown dead-url
status, after the first {{Cite web}}
inside the same reference. In other words, there's now two different {{Cite web}}
templates inside one reference and it's not pretty (two "Retrieved" dates).
Using {{Cite web}}
in full form with a working dead-url
implementation would also work, but I don't find it more semantic or shorter to use. This list makes heavy use of {{Cite IETF}}
for all the convenience.
[4]
Is there a way to make IABot exclude these individual references using the links listed above (which require a registered account) without excluding the bot altogether, or an alternative way to exclude the bot per line?
The most ideal solution would be fixing Template:Cite IETF and converting it to a Lua module, but failing that I'd probably like to deprecate that "stupid" template in favor for Template:Cite web. 2001:2003:54FA:2751:0:0:0:1 ( talk) 02:48, 6 September 2017 (UTC)
{{
cbignore}}
--
Green
C 03:39, 6 September 2017 (UTC)
{{cbignore}}
or bots exclusion. Would it be better to use {{cbignore}}
, manage URLs of the bot or report a bug?
2001:2003:54FA:2751:0:0:0:1 (
talk) 04:26, 6 September 2017 (UTC)archive-url
support, see
Special:Diff/799477541.
2001:2003:54FA:2751:0:0:0:1 (
talk) 23:41, 7 September 2017 (UTC)References
{{Cite IETF}}
vs 180 × {{Cite web}}
, and a total of 22% of all 318 references use {{Cite IETF}}
.
Artemis: Spaceship Bridge Simulator. A dispute between me and @ NoseyNick.
{{
Dunno}}
(question marks on assignments/use of protocols), but we both lack
reliable sources to demonstrate them.running the game and monitoring traffic presumably counts as "original research"on their talk page. I agree.
84.250.17.211 ( talk) 16:20, 10 November 2017 (UTC); edited 16:22, 10 November 2017 (UTC)
; SETTING: networkPort ; USE: listening port that Artemis connects on ; ACCEPTABLE: acceptable TCP ports networkPort=2010
{{
Dunno}}
just because we can't find more appropriately citable sources.WRT conflict of interest, for the record: I have no "external relationship to Artemis" other than that I enjoy playing it, with other local people who also enjoy playing it. I also enjoy reverse-engineering some of the protocols - which (unless you count USB/serial DMX) are all on TCP port 2010, in case you hadn't guessed. None of my current or previous employers have anything to do with Artemis. I do not receive, or expect to receive, any compensation with respect to Artemis, never mind any Wikipedia edits relating to it. I have no financial relationship with Artemis other than having bought a copy of it a few years ago. Artemis is but one, of many, hobbies. I would certainly consider myself an SME, but purely on a hobby basis, just like I'm a hobbyist Wikipedia editor.
NoseyNick ( talk) 21:21, 10 November 2017 (UTC)
@ NoseyNick: Thank you. You make some good arguments.
I feel like this subject list is having a hard time with verifiability and notability of examples (as seen by the to-do list on this talk page), but Artemis does fit the description of WP:CSC for inclusion. Having a hard time is the reason why I felt cautious to your edit: Less "issues" (maintenance templates) is usually for the better.
As a compromise, I'm willing to agree to that quote from artemis.ini as an additional reference, with the caveat of tagging it with {{
Better source}}
because it's not easy, obvious or "reliable" to verify. I also don't have Windows operating system or easy means to verify the existence of this file from ArtemisDEMOInstall.exe on an Unix-like operating system I'm using, but with little user-generated sources you've linked and the artemis.ini quote I can assume in good faith it to be correct (in lieu of demonstration of it being incorrect).
The wiki and Steam community post may be subject to change at any time and may have little to no editorial oversight, so I'd reject those as references.
In addition to {{Better source}}
, would it be good to use {{
Yes}}
, {{Yes|Yes?}}
or {{
Maybe}}
in place of TCP, and {{
No}}
for UDP? It's been my goal to disambiguate in the table what "TCP" and "UDP" mean (real-use or port assignments only). "?" for uncertainty.
–– 84.250.17.211 ( talk) 20:28, 12 November 2017 (UTC)
References
The request made for a
Third Opinion has been removed (i.e. rejected) because like all other moderated content
dispute resolution venues at Wikipedia, 3O DRN requires thorough talk page discussion before seeking assistance. However, having said that, let me note that the 3O request said, "Disagreement on verifiability/whether an editor's contribution with user-generated sources provides more value to the article than no information at all." If that's a fair description of the dispute, then Wikipedia's position is very clear: If the
Verifiability policy requires a fact to have a source (and it does if the information is challenged or likely to be challenged, both of which apply in this case) it must be supported by a
reliable source as defined by Wikipedia and if it cannot be so supported then it should not be in the encyclopedia. Satisfaction of the Verifiability policy is the threshold to inclusion. That rule applies even if the information is objectively absolutely true and vitally important.
Self-published sources are not, with a few exceptions (click on that link to see them, along with the information in the section after that one), reliable sources. One of those exceptions, the one in that next section, which might be important here is the one which says that self published sources can be reliable sources for information about themselves if certain criteria are met (see the section for details), which might apply to the game's manual, but then there's one more factor to consider: The manual is not only self-published but is a primary source and the
primary source policy says, "Do not analyze, evaluate, interpret, or synthesize material found in a primary source yourself; instead, refer to reliable secondary sources that do so." From what's been said, above, it would appear that the manual does not refer to TCP but only to connections, which requires impermissible analysis, evaluation, or interpretation to connect that to TCP. It would appear that the manual cannot be used as a source. As for looking in code, the purpose of citations in Wikipedia is so that an average person can look up the cite and verify that something is true. I would argue that the average person cannot do so with code, but perhaps more important, even if they could then the code is itself a primary source and I would argue that you cannot take a snippet of code out of context and say that it necessarily means something without impermissibly analyzing, evaluating, and interpreting it in the context of the entire program (for a couple of gross examples, how does one know that it's not buried in a chunk of code that's been commented out or jumped over by a goto or if or other conditional branching station) and/or impermissibly analyzing, evaluating, and interpreting with knowledge of how the code is supposed to work. —
TransporterMan (
TALK) 20:30, 12 November 2017 (UTC)
Hello fellow Wikipedians,
I have just modified 4 external links on List of TCP and UDP port numbers. 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:
{{
dead link}}
tag to
http://support.drobo.com/app/answers/detail/a_id/405/~/how-can-i-troubleshoot-my-droboshare%3F{{
dead link}}
tag to
https://support.vonage.com/app/answers/detail/a_id/690/~/port-forwardingWhen you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
An editor has determined that the edit contains an error somewhere. Please follow the instructions below and mark the |checked=
to true
Cheers.— InternetArchiveBot ( Report bug) 10:14, 20 November 2017 (UTC)
{{
Cite IETF}}
. This is now what, a fourth time? Pinging @
Balon Greyjoy to let you know.
84.250.17.211 (
talk) 13:42, 21 November 2017 (UTC)
Hello fellow Wikipedians,
I have just modified one external link on List of TCP and UDP port numbers. 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.
An editor has reviewed this edit and fixed any errors that were found.
Cheers.— InternetArchiveBot ( Report bug) 14:03, 27 December 2017 (UTC)
This page is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
I have just commented out a pile of links, please review the links by having a look at WP:WPSPAM , WP:NOT#LINK and WP:EL and only return the ones that need to be in the article. Peachey88 ( Talk Page | Contribs) 05:27, 17 January 2008 (UTC)
What is the current RFC reference for the WKPs and the ports >1023? I'd think that something like this should be in the 1st paragraph. 198.24.6.134 ( talk) 22:56, 12 February 2008 (UTC)
Hi there, we reverted each others edit in List of TCP and UDP port numbers and I like to comment a little bit: I suggest to add references and not external links ( WP:MOS), secondly I would be in favour of removing all external links as they only attract commercial link spam over time. Cheers - 83.254.215.235 ( talk) 23:57, 1 March 2008 (UTC)
In March 2007 it was proposed to merge the stub article at Port 666 into this page. The Port 666 article was an unsourced and orphaned stub which simply noted an association with first-person shooters and viruses.
As there was no opposition to the merge over the following 12 months, I've now carried it out and redirected that page name here. There was no need to merge the Doom reference (it was already in this article) and the virus claim was unsourced.
This seems an uncontroversial merge but if others think otherwise I'm happy to discuss. Euryalus ( talk) 05:35, 12 March 2008 (UTC)
The IANA PORT NUMBERS list shows 5190-5193 allocated to AOL - 5190 does not list ICQ. The ICQ article notes "...the protocol is proprietary...". Just because AOL owns ICQ these days (via their purchase of Mirabilis) doesn't make the ICQ use of 5190 "Official". I plan to make a change in a day or so to show ICQ as "Unofficial" and in conflict on port 5190. -- Joe Sperrazza ( talk) 05:10, 17 April 2008 (UTC)
protocol-name-from-IANA-list-in-case-used-there, expansion of protocol-name into text if needed (expansion of acronyms if any) "protocol" - brief description of protocol
These are just my thoughts, let me know what you think. Thanks, -- Joe Sperrazza ( talk) 14:18, 23 April 2008 (UTC)
I'm hoping someone knows more about these ports than I do, but I noticed they weren't in the list so I figured I would mention them to see if someone would be willing to research and add them to the list.
They both appear to be part of a torrent network, as the packets being uploaded/downloaded are accessing numerous IP addresses worldwide and seem to be a considerable drag on my network. Best Asptard ( talk) 13:26, 2 May 2008 (UTC)
There is a problem in the table for port numbers 9119 to 9800. The ports are listed as 9119, 9418, 9535, 9535, 9443, 9535, and 9800. I'm not sure whether "9443" is in the wrong place, or the first two "9535"s should be "9435"s, but something is amiss.
Sorry I don't know enough to correct it...
-- Tinkerer1359 ( talk) 17:26, 8 May 2008 (UTC)
8646/TCP www.SmartSystemsLLC.com Used by Smart Sale® 5.0 Backup service
is there a reason why this is appended to the last table? looks like advertising to me, especially since it's out of order, and references the URL... is there a particular reason why SmartSystemsLLC is noteable?
69.251.64.102 ( talk) 20:04, 6 December 2008 (UTC)
Is this article really come across by people looking for infomation about seaports?? Is that disambiguation link at the top of the article really neccessary? —Preceding unsigned comment added by Mespinola ( talk • contribs) 16:24, 29 January 2009 (UTC)
Port 694 should be changed to "Official". According to this http://moin.linux-ha.org/lha/ha.cf/UdpportDirective which states that it is IANA registered. —Preceding unsigned comment added by 80.192.120.114 ( talk) 11:58, 6 May 2009 (UTC)
The link for this unofficial port designation is broken. I note that nmap reports this port as belonging to this same service, but I cannot find any supporting refrences. Comments?
May 12, 2009 Bjjohns ( talk) 12:09, 12 May 2009 (UTC)
Microsoft uses port 379 for exchange services ( http://support.microsoft.com/kb/278339). I'm not sure what it should be documented as, but it should probably be added to the list. —Preceding unsigned comment added by 76.77.16.176 ( talk) 16:52, 28 May 2009 (UTC)
http://www.cyberciti.biz/faq/centos-linux-ipsec-firewall-rules/
* 50 is Encap Security Payload (esp / IPSEC-ESP ) protocol * 51 is IPSEC-AH - Authentication Header protocol
Should these be added to this list?
This list really needs to be split, not jsut because of wikipedia guideliones on size ie it approaching 100kb size, but not least because with udp and tcp in one it quite confussing, i understand it but if i take out my network knowledge it very hard ot understand. Any views or ideas?-- Andrewcrawford ( talk) 20:37, 15 May 2009 (UTC)
hmm. go for it. andyzweb ( talk) 15:51, 28 October 2009 (UTC)
Ports ?? —Preceding unsigned comment added by Seb-Gibbs ( talk • contribs) 18:31, 13 November 2009 (UTC)
The "gpsd" wikipedia article says port 2947 is used for it. Should that be added to the list? Michael9422 ( talk) 19:14, 1 February 2010 (UTC)
All of the ports VMware uses are conflicts with registered ports, and those have been registered in in the iana list for years. Why aren't they listed here? I went ahead and added 902 thisafternoon, since that's the most common conflict you see reported when installing VMWare server. Is there any good reason not to list all of them? —Preceding unsigned comment added by 38.124.2.254 ( talk) 15:52, 3 March 2010 (UTC)
Econet was a networking service - protocol and hardware - used by Acorn Computers Ltd of England in their microcomputers. With the adoption of Ethernet, they implemented "AUN" (Acorn Universal Networking) which encapsulated the econet packets within UDP packets, on port 32768.
Although Acorn bit the dust a long time ago, their hardware soldiers on in many places, and over the last few years, emulators such as BeebEm now support the networking protocols. Robirrelevant ( talk) 08:41, 3 April 2010 (UTC)
heloo —Preceding unsigned comment added by 202.138.120.37 ( talk) 14:43, 8 May 2010 (UTC)
hi ,
i ill tell u a story of a man whose was geneous in its own way .
if u really wants to succced u need to be in touch with good smart people .
and for that u neeed to do friendship with people like me .
so why r u waiting .come and join me.--------arun. —Preceding
unsigned comment added by
202.138.120.37 (
talk) 14:46, 8 May 2010 (UTC)
Hello, just passing by - saw this page didn't have the Mumble added. I put it in and cited an official source for it; I think I got the formatting right, feel free to improve! 75.72.168.44 ( talk) 23:20, 20 July 2010 (UTC)
I agree with the editor who noted the use of Bare URLs in the article. They all should be changed to proper templates. I'll work on doing so over time. Help from others would be most appreciated. JoeSperrazza ( talk) 03:36, 27 December 2010 (UTC)
WTF is Shains Throbber Protocol TCP 40 LOL LOL LOL Amists ( talk) 12:43, 22 March 2011 (UTC)
Whoops, there is port 1222 in the well-known ports section. Well-known-ports range from 0 to 1023 only, so it must be some kind of mistake here. Anyone here who is willing to fix this? Thanx in advance... -- 93.245.188.157 ( talk) 21:17, 30 January 2011 (UTC)
I added this port 34567 that I have registered with iana.org, which you can see at http://www.iana.org/assignments/port-numbers but someone reverted it. Please add it after verifying the iana page. —Preceding unsigned comment added by 122.164.53.66 ( talk) 20:53, 26 April 2011 (UTC)
Since we're not listing all known usage of ports, identifying conflicts appears to be problematic. Identifying conflicts also flirts with WP:OR. I propose to remove the Conflict legend and add a short paragraph either here or at Port number describing port conflicts. -- Kvng ( talk) 16:42, 11 July 2011 (UTC)
I would agree that the conflict markings should be removed. Conflicts only occur when two services are actually installed on the same system, but this happens so rarely with most of these obscure services that it does not constitute a problem worth marking. In addition, there are many more ports in use by all kinds of applications which are nowhere notably documented. Kbrose ( talk) 03:05, 2 August 2011 (UTC)
For what it's worth, I was confused on reading this article with the three color highlights. The yellow highlight represents conflict (i.e, two protocols having same port #). Although this has nothing to do with which protocol is official/unofficial for that port, yellow highlight seems to trump white/blue in the table. Maybe just highlight the port number in yellow rather than the whole row? — Preceding unsigned comment added by 69.46.103.131 ( talk) 23:03, 19 October 2011 (UTC)
How should we add port numbers that are only reserved for SCTP protocol (not used in tcp/udp) I was considering adding 36412 S1-Control Plane (3GPP) (officially registered by IANA) but current table has colums for tcp and udp but it's not clear how to add sctp only ports Umbeebmu ( talk) 13:29, 25 October 2011 (UTC)
List of TCP and UDP port numbers
. Now there are 2 other Protocols we are trying to squeeze in. With significant editing effort, we could create 2 new columns for
SCTP and
DCCP. I'd suggest that approach is not worth the effort. Plus, with a new row for the DCCP entry - the table may be sorted on that column (using UDP for both UDP and DCCP), putting the DCCP entries together. That's my 2 cents. --
Unixguy (
talk) 01:09, 21 November 2011 (UTC)What is the criteria for inclusion in this list? The IANA list contains more assignments than listed here. -- Kvng ( talk) 15:40, 8 July 2011 (UTC)
I really have to disagree with your criteria as to what ports you include in your list. It is quite confusing to look for what you believe is a defined user port and then discover that you are "wrong". You have to go to the IANA website in order to realise that it actually is Wikipedia that is wrong. If you do not want to correct the page, certainly it should be clearly stated somewhere that the list is neither complete nor accurate. — Preceding unsigned comment added by 80.63.2.124 ( talk) 12:59, 5 December 2011 (UTC)
In both of the wiki tables on the main page I lined up the Port number, TCP and UDP columns using spaces as padding. The reason for this is for wiki markup readability only. It does not affect the browser rendering of the page. -- Unixguy ( talk) 00:38, 21 November 2011 (UTC)
this isn't my area but this link 1 shows 2425 for Fujitsu App Manager. [I could not access the iana.org site]...-- Billymac00 ( talk) 06:57, 30 December 2011 (UTC)
I noticed the entry for rsync (873/T) is marked "Official USA Only". Huh? Unless I'm missing something, ports are either registered or not; there is no "you're registered for Russia only" or "you're registered for use everywhere but Scotland".
Plus, I can't find any sources supporting such an assertion.
Thoughts, anyone? Unless someone knows of a good source for this claim, I will remove it as unsupported.
Thanks! — UncleBubba ( T @ C ) 18:01, 3 July 2012 (UTC)
I just added a description for this port. If you look at the IANA record for this port, [2] you'll see that I am the assignee for it. I guess that makes me an authority. :-) Donpayette ( talk) 16:23, 14 August 2012 (UTC)
We should also add a column listing the official registered names of ports as well. [ http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xml listings] -- 64.4.68.234 ( talk) 16:56, 6 February 2013 (UTC)
How do we deal with RFC references to cite where it is defined as official? Do we put a citation after the name? or next the word official? Or do we do as is done on port 13 and put the RFC as a link in parentheses?
Davidgumberg ( talk) 00:24, 10 May 2013 (UTC)
There has been repeated vandalism to the low port numbers on this page, surely only official uses should be listed for the well known ports, or splitting it as per below. — Preceding unsigned comment added by 101.166.57.152 ( talk) 20:37, 4 June 2013 (UTC)
Is it correct to add WebSocket to TCP port 80? -- Abdull ( talk) 11:53, 6 August 2013 (UTC)
I think unofficial uses should be listed separately from official uses. Also, if official uses are listed it should be an exhaustive list seeing as the information is easily available at IANA's website. — Preceding unsigned comment added by 96.225.101.25 ( talk) 00:37, 13 March 2013 (UTC)
A using reading this pages wants to see what protocols are used on a certain port. Having to go to 2 different list is counter-productive and many less experienced users won't even do that. Please keep them together. — Preceding unsigned comment added by 89.181.160.102 ( talk) 12:33, 6 August 2013 (UTC)
Adding a column for date (as well as a column for the RFC) is useful. The date should be the official RFC publication date (for official ports). For unoffcial ports, the date could be the first usage reported. — Preceding unsigned comment added by 89.181.160.102 ( talk) 12:36, 6 August 2013 (UTC)
What about FEAR Combat game using 27888 port? 62.152.145.53 ( talk) 00:33, 3 January 2014 (UTC)
Maybe range 0-1023 can be included (as a link ?)... — Preceding unsigned comment added by 2A01:E34:EE0F:C40:B8BA:F7C0:7D39:70BB ( talk) 10:33, 4 March 2014 (UTC)
Some items add this in the description, so might be nice to pull out into a column.
50.199.243.89 ( talk) 16:05, 19 August 2014 (UTC)
- Steve
I'm not sure where to put this, just wanted to throw it out there. The bios on certain machines lists connections to port 6910 for the Dell Cloud Desktop server. It appears to be a Wyse product. — Preceding unsigned comment added by Family Guy Guy ( talk • contribs) 21:47, 16 December 2014 (UTC)
TCP services with port numbers 6541 and 6542 appear between 5632 and 5655, so they may be mistyped and could mean 5641 and 5642. I didn't find any conclusive information about MirrorOp2, but it could very well be a remote desktop application, similar to pcAnyWhere which seems to use ports 5641 (TCP) and 5642 (UDP).
Chaotix63 ( talk) 15:38, 25 March 2015 (UTC)
All Unnoficial port numbers needs sources (just as the official ones do, but we already have them).
I'll be removing all unreferenced information within some months.-- damiens.rf 01:36, 25 June 2015 (UTC)
Hello fellow Wikipedians,
I have just added archive links to 5 external links on
List of TCP and UDP port numbers. Please take a moment to review
my edit. If necessary, add {{
cbignore}}
after the link to keep me from modifying it. Alternatively, you can add {{
nobots|deny=InternetArchiveBot}}
to keep me off the page altogether. I made the following changes:
When you have finished reviewing my changes, please set the checked parameter below to true to let others know.
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).
Cheers. — cyberbot II Talk to my owner:Online 11:36, 18 October 2015 (UTC)
NetApp / SANtricity port is 2463 not 2643. — Preceding unsigned comment added by 195.190.86.68 ( talk) 16:22, 14 December 2015 (UTC)
Multi-use port color coding is lacking/not sufficient. The issue being that we have color coding for official, unofficial, and multi-use. What color code do we use when it is both multi-use official? multi-use unofficial? And best yet multi-use official/unofficial? With the last likely being the most common. I'm not sure of the best solution but here are two possible solutions:
1) Add a column: multi-use - true/false or yes/no I don't think this will work very well as new rows are added old rows would also have to be edited.
2) Each port is a single row. List each service is as row in a service column that has sub columns of TCP | UDP | Description | Status example:
port | service | TCP | UDP | Description | Status ____________________________________________________ 9 | TCP | UDP | Discard Protocol | Offical | | UDP | Wake-on-LAN | Unofficial
Thoughts? MichaelLeeHobbs ( talk) 13:03, 20 December 2015 (UTC)
Hello fellow Wikipedians,
I have just added archive links to 2 external links on
List of TCP and UDP port numbers. Please take a moment to review
my edit. If necessary, add {{
cbignore}}
after the link to keep me from modifying it. Alternatively, you can add {{
nobots|deny=InternetArchiveBot}}
to keep me off the page altogether. I made the following changes:
When you have finished reviewing my changes, please set the checked parameter below to true to let others know.
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).
Cheers.— cyberbot II Talk to my owner:Online 01:02, 6 January 2016 (UTC)
Hello fellow Wikipedians,
I have just added archive links to 8 external links on
List of TCP and UDP port numbers. Please take a moment to review
my edit. If necessary, add {{
cbignore}}
after the link to keep me from modifying it. Alternatively, you can add {{
nobots|deny=InternetArchiveBot}}
to keep me off the page altogether. I made the following changes:
When you have finished reviewing my changes, please set the checked parameter below to true to let others know.
An editor has reviewed this edit and fixed any errors that were found.
Cheers.— cyberbot II Talk to my owner:Online 17:54, 8 February 2016 (UTC)
Hello fellow Wikipedians,
I have just added archive links to 8 external links on
List of TCP and UDP port numbers. Please take a moment to review
my edit. If necessary, add {{
cbignore}}
after the link to keep me from modifying it. Alternatively, you can add {{
nobots|deny=InternetArchiveBot}}
to keep me off the page altogether. I made the following changes:
An editor has reviewed this edit and fixed any errors that were found.
An editor has reviewed this edit and fixed any errors that were found.
An editor has determined that the edit contains an error somewhere. Please follow the instructions below and mark the |checked=
to true
An editor has determined that the edit contains an error somewhere. Please follow the instructions below and mark the |checked=
to true
An editor has reviewed this edit and fixed any errors that were found.
An editor has reviewed this edit and fixed any errors that were found.
An editor has reviewed this edit and fixed any errors that were found.
An editor has reviewed this edit and fixed any errors that were found.
When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at {{ Sourcecheck}}).
Cheers.—
cyberbot II
Talk to my owner:Online 07:25, 28 February 2016 (UTC)
Hello fellow Wikipedians,
I have just added archive links to 2 external links on
List of TCP and UDP port numbers. Please take a moment to review
my edit. If necessary, add {{
cbignore}}
after the link to keep me from modifying it. Alternatively, you can add {{
nobots|deny=InternetArchiveBot}}
to keep me off the page altogether. I made the following changes:
When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at {{
Sourcecheck}}
).
An editor has reviewed this edit and fixed any errors that were found.
Cheers.— cyberbot II Talk to my owner:Online 00:33, 19 March 2016 (UTC)
See Special:Diff/745891794. I found these issues with the reference to Laravel documentation:
PHP's built-in development server, which makes me question if this is specific to Laravel at all.
While Laravel itself may be notable enough for inclusion by Wikipedia's standards, unless there's reliable third-party sources to verify and tell me what port 8000 is about, I don't see this happening. 80.221.159.67 ( talk) 00:31, 24 October 2016 (UTC)
There's a to-do list at the top of this talk page.
There's been little to no enforcement of common selection criteria before August 2016, when I started editing. Even as I clean up the list, there are articles which I can verify to exist, but am unable to assess if they are notable enough for inclusion (in scope) when they may not have a Wikipedia article, or specific parts of the protocol are not described in the main article of the port topic. There even exists list items which are unofficial, unnotable and unsourced.
Some list items are or have been just technical jargon, such as
SQL Services
or Print-srv, Network
PostScript
, almost like directly from IANA's list. Even as an example
Border Gateway Protocol (BGP)
may need more description to explain in short terms what the protocol is about (without opening the self-reference wikilink), and there are many more of these.
I have generally taken the stance that if a company itself is notable, but their products don't have a Wikipedia article (or a notable section about the product in the company's article), I have removed it from the list.
The table legend colors can be difficult to maintain. There also seems not to be an exact criteria what qualifies as multiple use
: If a port is unassigned at IANA, does that mean an unofficial application using that port is multiple use
or not?
More issues with the table come from the fact that IANA may have assigned both TCP and UDP, but commonly the protocol only uses one by design or specification. This sometimes leads to editors removing (blanking) the other protocol, while it is still "valid" to mention both.
I would also suggest bringing up the use of Template:Yes, Template:No and similar templates to make the table easier to read.
I don't think WP:TNT to be appropriate at this point as the existing ports (especially unofficial ones) are a great base for modification, but lots of cleanup is still to be done.
I also believe it would be a good idea to use pending changes protection level 1 after the cleanup is done. It is not appropriate while the cleanup is ongoing, as it could cause undue load on the reviewers.
And for what little it's worth, the daily pageviews have increased about 2,000+ after the cleanup started. I could call this rewrite/cleanup very useful indeed. (Personally, I'm doing it for the fun of learning the every obscure protocol out there.) 80.221.159.67 ( talk) 22:51, 17 October 2016 (UTC)
Some technical expertise ({{
Expert needed}}
) may also be needed (later). I am knowledgeable of networking and can help.
80.221.159.67 (
talk) 22:55, 17 October 2016 (UTC)
I have also added some citations, which may be duplicated or not very accurate (e.g. not anchoring to right page where multiple things are being referenced at once) in places. Some of these I have marked with <!-- XXX: Comment -->
.
80.221.159.67 (
talk) 22:58, 17 October 2016 (UTC)
Special:Diff/749839962. This was the third time removing this from the list. If you believe first-defense is notable enough, create an article for it or provide a reliable source to establish notability in real use. 80.221.159.67 ( talk) 12:43, 16 November 2016 (UTC) (edited: 12:50, 16 November 2016 (UTC))
I'd like to discuss the removal of my edit (diff is linked below) [3] Cited reason for removal: Visual edit, unclear notability, lacking a better source) A few points I'd like clarification on; 1) If visual edit mode is frowned upon, why is it enabled? 2) Unclear notability - How does one get notability if one's edits are removed? 3) I thought that the www.iana.org website itself would be confirmation enough for a registered port - if this is not the case, could someone please explain to me where I have gone wrong? Thankyou, Jambulance ( talk) 05:36, 3 June 2017 (UTC)
@ Jambulance: Sorry, I didn't see your message earlier. You seem to be talking about Special:Diff/783082575.
I can say the scope is not very clearly defined in the lead paragraph of the article. That's something to improve upon. 84.250.0.210 ( talk) 22:20, 22 June 2017 (UTC)
Question: Which one of these mentioned templates is more appropriate here?
I also wonder if the following templates should be tagged to the article:
Template:Refimprove may be enough for now to cover the two, but I'm up for a discussion.
84.250.0.210 ( talk) 05:16, 30 June 2017 (UTC)
Minor topic not likely to justify an independent article. Could be summarize in the target article. - Mr X 14:10, 5 July 2017 (UTC)
I've tagged it with speedy deletion, since there isn't enough context and references to verify notability. The same article has also been previously speedy deleted. 84.250.0.210 ( talk) 01:33, 6 July 2017 (UTC)
There also isn't anything to merge. The source article has had its listed items copied directly from the target article. If you'd like, you can add references to the target article to support those claims. Notably I haven't sweeped yet through port range 7000 – 7999 to establish notability and references, as pointed out in the to-do list at top of the talk page. 84.250.0.210 ( talk) 01:44, 6 July 2017 (UTC)
In example, Special:Diff/789995279 attempted to add Mosh (mobile shell) UDP ports 60000–61000 to the article. Currently, we don't have a table for notable ports operating in dynamic/private port ranges.
Should we add a table to the dynamic/private ports section for additions like these? What would be the criteria for verification and inclusion, since they are not in the scope of IANA? 2001:2003:54FA:D2:0:0:0:1 ( talk) 05:29, 12 July 2017 (UTC)
Special:Diff/794677559 added port 2099 for League of Legends ( PVP.net). The source given only supports the statement of that port being used for PVP.net, while League of Legends uses UDP ports 5000–5500. In comparison to something like Battle.net, I don't quite understand or see how PVP.net would meet notability of its own (or if they're even comparable). Thus, I reverted the edit with Special:Diff/794845836.
League of Legends itself is notable for inclusion, so I'll be adding ports 5000–5500 to the list shortly. 2001:2003:54FA:D2:0:0:0:1 ( talk) 11:16, 10 August 2017 (UTC)
The current table implies that most protocols use both TCP and UDP. It seems that the IANA frequenly assigned both TCP and UDP ports to a protocol even if it only actually used one or the other. Any thoughts on how best to handle this. — Preceding unsigned comment added by Plugwash ( talk • contribs) 13:52, 24 July 2017 (UTC)
Thanks for starting this discussion. I don't think there's an easy solution, or it's not an appropriate time to solve due to burden of unnotable entries. This has also been noted before at § Rewriting this list.
IANA did indeed historically assign both TCP and UDP to ports, even if only one was ever used by design (e.g. TCPMUX). Currently (to my belief), IANA seems to assign only one protocol (TCP or UDP) on a port (if requested) and mark the other as reserved
.
I took a bold move earlier to tag some of these cases with {{
Available|Assigned}}
. {{
Yes-No}}
could also be used, but I can't come into an agreement with myself which one to use. I'd like to see the table converted to use {{
Yes}}
and {{
No}}
sometime for some consistency and readability, but I'm unsure when the right time to do this would be. Other noteworthy thing is ports 2375–2380 in example: There is no consistent practice of marking them as reserved ({{
N/A|Reserved}}
), or if they qualify as multiple use
or not. It'd require substantial effort to verify both assignment and actual use, and there's no easy way to say if some software uses the other protocol when the mainstream doesn't.
I think the scope or table legend may need to be clarified. Ideas are welcome.
2001:2003:54FA:D2:0:0:0:1 ( talk) 21:27, 25 July 2017 (UTC)The following table is an example and may not be factually accurate or current. |
Port | TCP | UDP | Description | Status |
---|---|---|---|---|
0 | Reserved | Reserved | Reserved | Official |
1 | Yes | Assigned | TCP Port Service Multiplexer (TCPMUX). Historic. Both TCP and UDP have been assigned to TCPMUX by IANA, [1] but by design only TCP is specified. [2] | Official |
9 |
|
Yes | Discard Protocol [4] | Official |
No | Yes | Wake-on-LAN [5] | Unofficial | |
20 | Yes | Maybe | File Transfer Protocol (FTP) data transfer [6] [3] | Official |
100 | — | — | Unassigned (with known unauthorized use further explanation needed) [1] | Official |
1314 | ? | ? | Festival Speech Synthesis System server [7] | Unofficial |
60000–61000 | Port 22 | Yes | Mosh – a remote terminal application similar to SSH – typically assigns ports for ongoing sessions between Mosh servers and Mosh clients. [8] | — |
References
{{
citation}}
: Unknown parameter |month=
ignored (
help)
{{
citation}}
: Unknown parameter |month=
ignored (
help)
{{
citation}}
: Unknown parameter |month=
ignored (
help)
... The default port for the wake-up transmission is UDP port 9. ...
{{
cite web}}
: Unknown parameter |dead-url=
ignored (|url-status=
suggested) (
help)
apple-kb-HT202944
was invoked but never defined (see the
help page).... Festival waits for clients on a known port (the value of server_port
, default is 1314). ...
{{
cite book}}
: |website=
ignored (
help); Unknown parameter |dead-url=
ignored (|url-status=
suggested) (
help)
self-published source?
Official Unofficial Multiple use | ||||
---|---|---|---|---|
Port | TCP | UDP | Description | Status |
0 | Reserved | Reserved | Reserved | Official |
Port | TCP | UDP | Description | Status |
---|---|---|---|---|
0 | Reserved | Reserved | Reserved | Official |
Thoughts on this proposal? There is currently no accessible way to insert the table legend into <caption>
that I know of (true and tested).
2001:2003:54FA:D2:0:0:0:1 (
talk) 01:40, 28 July 2017 (UTC)
<caption>...</caption>
s. I'm also aware the color boxes don't really convey the message semantically, but there's seemingly a limitation preventing use of block elements in table captions on MediaWiki. (Ideally, the legend in caption should be a {{
flatlist}}
.) Feedback wanted.
2001:2003:54FA:D2:0:0:0:1 (
talk) 02:45, 28 July 2017 (UTC)A new contributor added Mouse without borders to the article twice without reliable sources. On the second chance, I gave it a benefit of doubt and went digging for sources myself.
The references from CNET News and PC Magazine read out like a review. Betanews is more news-like, but uncertain for me if it's a notable publication. It only briefly mentions MWB.
The main issue however is what appears to be original research: Ports 15100 and 15101 and TCP were not referenced at all by the original contributor, and I could not also find reliable sources to support this statement.
WP:CSC also has a criteria Every entry meets the
notability criteria for its own non-
redirect article in the English Wikipedia.
. Since
MWB is a redirect to a section of
Microsoft Garage where
MWB is only a short list entry, I'm unsure if it meets the criteria for inclusion.
2001:2003:54FA:2F79:0:0:0:1 (
talk) 06:16, 23 August 2017 (UTC)
@ Truong2D: Welcome to Wikipedia. Because Wikipedia is an encyclopedia and not an indiscriminate collection of information, Wikipedia cannot accept contributions for which no reliable sources exist ( original research). A reliable source is a previously published source, preferably from a (peer-reviewed) secondary/third-party source. Reliable sources are needed for an encyclopedia to be verifiable, and self-published sources are also largely not acceptable.
As the aclaimed author of MWB, please read this guide to Wikipedia's conflict of interest guideline. If you are getting paid to edit or create articles where you may have a conflict of interest, please also read Wikipedia:Paid-contribution disclosure before making any more edits to articles.
For more help on editing at Wikipedia, Wikipedia:Teahouse and Wikipedia:Help desk are glad to help you in need. 2001:2003:54FA:2F79:0:0:0:1 ( talk) 08:25, 24 August 2017 (UTC)
These are not measurements of quality and should be taken as a grain of salt. I hope someone has better use for this data to improve the article.
(Not exactly one year, but I didn't want to wait any longer.)
A possible explanation for unknown/undetermined statuses is a lack of consistency or typos. The method of examination was a simple text search using
grep
.
If someone points out my math is wrong, that's fine.
I used toollabs:pageviews for this one. The decline may be explained by Wikipedia's overall decline(?) and less web search results landing on this page after cleaning "all that crap".
There was a positive increase in daily pageviews until October 2016. On the last days of year 2016, pageviews dropped substantially and returned immediately after the new year started.
Big positive peaks in pageviews occurred on 28 September, 2016 and in mid-May 2017.
Personally, I contributed this much (with the help of toollabs:xtools-articleinfo and something else):
A total of 370 edits, added +76,080 and deleted -44,806. Overall this accounts for +31,274, which is 71.06 % of all text in this one year? I'm almost sure I also forgot one IP-address, but I can't find it. Wish I had better data to show.
Please consider contributing! It makes an impact, there's not a lot of volunteers working on this (semi-)actively. I'm sure there's also other contibutors to thank a lot, but I can't name any from top of my head. 2001:2003:54FA:2F79:0:0:0:1 ( talk) 10:53, 24 August 2017 (UTC)
Xfire died last year. I tried using both web search engine and Wayback Machine on Xfire's official website to find any kind of citation for port 25999, but was unable to. So,
I removed Xfire (and others) from the list. This is kind of a shame, but I felt like {{
Citation needed}}
would've not helped.
84.250.17.211 (
talk) 14:35, 10 November 2017 (UTC)
Hello fellow Wikipedians,
I have just modified 9 external links on List of TCP and UDP port numbers. 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:
{{
dead link}}
tag to
http://www.vmware.com/community/message.jspa?messageID=425783When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
An editor has reviewed this edit and fixed any errors that were found.
The help request has been answered. To reactivate, replace "helped" with your help request.
Cheers.— InternetArchiveBot ( Report bug) 00:36, 4 September 2017 (UTC)
{{
Cite IETF}}
hack on ports 1027 and 7542, also seen previously at
Special:Diff/781179064.
2001:2003:54FA:2751:0:0:0:1 (
talk) 02:11, 6 September 2017 (UTC)
{{Cite IETF}}
ones are troubled, as explained here.Because
Template:Cite IETF has well-known and previously reported bugs
[1] where archive-url
or dead-url
parameters with any alias are not well respected,
[2]
User:GreenC opted to add
Template:Webarchive after the reference instead (at my suggestion).
[3] It's a hack, of course.
This bot keeps repeatedly replacing {{Webarchive}}
with {{
Cite web}}
and unknown dead-url
status, after the first {{Cite web}}
inside the same reference. In other words, there's now two different {{Cite web}}
templates inside one reference and it's not pretty (two "Retrieved" dates).
Using {{Cite web}}
in full form with a working dead-url
implementation would also work, but I don't find it more semantic or shorter to use. This list makes heavy use of {{Cite IETF}}
for all the convenience.
[4]
Is there a way to make IABot exclude these individual references using the links listed above (which require a registered account) without excluding the bot altogether, or an alternative way to exclude the bot per line?
The most ideal solution would be fixing Template:Cite IETF and converting it to a Lua module, but failing that I'd probably like to deprecate that "stupid" template in favor for Template:Cite web. 2001:2003:54FA:2751:0:0:0:1 ( talk) 02:48, 6 September 2017 (UTC)
{{
cbignore}}
--
Green
C 03:39, 6 September 2017 (UTC)
{{cbignore}}
or bots exclusion. Would it be better to use {{cbignore}}
, manage URLs of the bot or report a bug?
2001:2003:54FA:2751:0:0:0:1 (
talk) 04:26, 6 September 2017 (UTC)archive-url
support, see
Special:Diff/799477541.
2001:2003:54FA:2751:0:0:0:1 (
talk) 23:41, 7 September 2017 (UTC)References
{{Cite IETF}}
vs 180 × {{Cite web}}
, and a total of 22% of all 318 references use {{Cite IETF}}
.
Artemis: Spaceship Bridge Simulator. A dispute between me and @ NoseyNick.
{{
Dunno}}
(question marks on assignments/use of protocols), but we both lack
reliable sources to demonstrate them.running the game and monitoring traffic presumably counts as "original research"on their talk page. I agree.
84.250.17.211 ( talk) 16:20, 10 November 2017 (UTC); edited 16:22, 10 November 2017 (UTC)
; SETTING: networkPort ; USE: listening port that Artemis connects on ; ACCEPTABLE: acceptable TCP ports networkPort=2010
{{
Dunno}}
just because we can't find more appropriately citable sources.WRT conflict of interest, for the record: I have no "external relationship to Artemis" other than that I enjoy playing it, with other local people who also enjoy playing it. I also enjoy reverse-engineering some of the protocols - which (unless you count USB/serial DMX) are all on TCP port 2010, in case you hadn't guessed. None of my current or previous employers have anything to do with Artemis. I do not receive, or expect to receive, any compensation with respect to Artemis, never mind any Wikipedia edits relating to it. I have no financial relationship with Artemis other than having bought a copy of it a few years ago. Artemis is but one, of many, hobbies. I would certainly consider myself an SME, but purely on a hobby basis, just like I'm a hobbyist Wikipedia editor.
NoseyNick ( talk) 21:21, 10 November 2017 (UTC)
@ NoseyNick: Thank you. You make some good arguments.
I feel like this subject list is having a hard time with verifiability and notability of examples (as seen by the to-do list on this talk page), but Artemis does fit the description of WP:CSC for inclusion. Having a hard time is the reason why I felt cautious to your edit: Less "issues" (maintenance templates) is usually for the better.
As a compromise, I'm willing to agree to that quote from artemis.ini as an additional reference, with the caveat of tagging it with {{
Better source}}
because it's not easy, obvious or "reliable" to verify. I also don't have Windows operating system or easy means to verify the existence of this file from ArtemisDEMOInstall.exe on an Unix-like operating system I'm using, but with little user-generated sources you've linked and the artemis.ini quote I can assume in good faith it to be correct (in lieu of demonstration of it being incorrect).
The wiki and Steam community post may be subject to change at any time and may have little to no editorial oversight, so I'd reject those as references.
In addition to {{Better source}}
, would it be good to use {{
Yes}}
, {{Yes|Yes?}}
or {{
Maybe}}
in place of TCP, and {{
No}}
for UDP? It's been my goal to disambiguate in the table what "TCP" and "UDP" mean (real-use or port assignments only). "?" for uncertainty.
–– 84.250.17.211 ( talk) 20:28, 12 November 2017 (UTC)
References
The request made for a
Third Opinion has been removed (i.e. rejected) because like all other moderated content
dispute resolution venues at Wikipedia, 3O DRN requires thorough talk page discussion before seeking assistance. However, having said that, let me note that the 3O request said, "Disagreement on verifiability/whether an editor's contribution with user-generated sources provides more value to the article than no information at all." If that's a fair description of the dispute, then Wikipedia's position is very clear: If the
Verifiability policy requires a fact to have a source (and it does if the information is challenged or likely to be challenged, both of which apply in this case) it must be supported by a
reliable source as defined by Wikipedia and if it cannot be so supported then it should not be in the encyclopedia. Satisfaction of the Verifiability policy is the threshold to inclusion. That rule applies even if the information is objectively absolutely true and vitally important.
Self-published sources are not, with a few exceptions (click on that link to see them, along with the information in the section after that one), reliable sources. One of those exceptions, the one in that next section, which might be important here is the one which says that self published sources can be reliable sources for information about themselves if certain criteria are met (see the section for details), which might apply to the game's manual, but then there's one more factor to consider: The manual is not only self-published but is a primary source and the
primary source policy says, "Do not analyze, evaluate, interpret, or synthesize material found in a primary source yourself; instead, refer to reliable secondary sources that do so." From what's been said, above, it would appear that the manual does not refer to TCP but only to connections, which requires impermissible analysis, evaluation, or interpretation to connect that to TCP. It would appear that the manual cannot be used as a source. As for looking in code, the purpose of citations in Wikipedia is so that an average person can look up the cite and verify that something is true. I would argue that the average person cannot do so with code, but perhaps more important, even if they could then the code is itself a primary source and I would argue that you cannot take a snippet of code out of context and say that it necessarily means something without impermissibly analyzing, evaluating, and interpreting it in the context of the entire program (for a couple of gross examples, how does one know that it's not buried in a chunk of code that's been commented out or jumped over by a goto or if or other conditional branching station) and/or impermissibly analyzing, evaluating, and interpreting with knowledge of how the code is supposed to work. —
TransporterMan (
TALK) 20:30, 12 November 2017 (UTC)
Hello fellow Wikipedians,
I have just modified 4 external links on List of TCP and UDP port numbers. 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:
{{
dead link}}
tag to
http://support.drobo.com/app/answers/detail/a_id/405/~/how-can-i-troubleshoot-my-droboshare%3F{{
dead link}}
tag to
https://support.vonage.com/app/answers/detail/a_id/690/~/port-forwardingWhen you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
An editor has determined that the edit contains an error somewhere. Please follow the instructions below and mark the |checked=
to true
Cheers.— InternetArchiveBot ( Report bug) 10:14, 20 November 2017 (UTC)
{{
Cite IETF}}
. This is now what, a fourth time? Pinging @
Balon Greyjoy to let you know.
84.250.17.211 (
talk) 13:42, 21 November 2017 (UTC)
Hello fellow Wikipedians,
I have just modified one external link on List of TCP and UDP port numbers. 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.
An editor has reviewed this edit and fixed any errors that were found.
Cheers.— InternetArchiveBot ( Report bug) 14:03, 27 December 2017 (UTC)