Notice: Any messages purporting to come from this site telling you that your password has expired, or that you need to verify your details, confirm your email, resolve issues, making threats, or asking for money, are
spam. We do not email users with any such messages. If you have lost your password you can obtain a new one by using the
password reset link.
Entire forum
➜ MUSHclient
➜ Bug reports
➜ new world: default port
It is now over 60 days since the last post. This thread is closed.
Refresh page
| Posted by
| Xtian
(53 posts) Bio
|
| Date
| Wed 26 Nov 2008 07:09 AM (UTC) |
| Message
| Mushclient 4.37:
When creating a new world the port should default to the port on which most MUDs are accessible nowadays, which should be the default telnet port 23.
At the moment the initial value is port 4000. I'm not sure which MUD uses this, but it is definitively a very specialized case. | | Top |
|
| Posted by
| Nick Gammon
Australia (23,120 posts) Bio
Forum Administrator |
| Date
| Reply #1 on Wed 26 Nov 2008 09:21 AM (UTC) |
| Message
| I did a random check of MUDs on mudconnector.com, and none of them used port 23.
On what basis do you make this claim?
The default for SMAUG is 4000 or 4020, and I believe 4000 is fairly popular.
The thing is that ports below 1024 are reserved for system use, so MUDs typically used a port number higher than that. |
- Nick Gammon
www.gammon.com.au, www.mushclient.com | | Top |
|
| Posted by
| Xtian
(53 posts) Bio
|
| Date
| Reply #2 on Wed 26 Nov 2008 09:35 AM (UTC) |
| Message
| Thanks for the quick reply.
The thing is (I'm a mud administrator at avalon.mud.de) no one is using the telnet port for system administration any more, so MUDs startet redirecting port 23 to their gameport, so that players can just simply type: "telnet avalon.mud.de". It is mainly a usability thing.
If MUDs don't officially list port 23 then that could be because it's not their main port - or just a lazy legacy thing.
I can tell you that the major German MUDs allow connections over port 23, and I did a quick cross-check at an Iron Realm and I can connect over port 23.
For me this seems to be the largest common denominator, but I can understand if you want to recheck this on a greater basis. I thought it would be a nice little usability improvement for users. | | Top |
|
| Posted by
| Nick Gammon
Australia (23,120 posts) Bio
Forum Administrator |
| Date
| Reply #3 on Thu 27 Nov 2008 05:43 AM (UTC) |
| Message
| I understand what you are saying, however for MUDs that are implemented on generic hired servers, they can't all be using port 23. So your suggestion would only be specific to MUDs where there is only one MUD on the server, and the admins don't use port 23 for administering the MUD (eg. by telnetting in to do compiles).
I am inclined to think that, if you advertise a MUD as being on <ip address> and <port> and the player has trouble understanding that level of detail, they will also have trouble understanding the quests, and the basic instructions that appear when they connect. |
- Nick Gammon
www.gammon.com.au, www.mushclient.com | | Top |
|
| Posted by
| Zeno
USA (2,871 posts) Bio
|
| Date
| Reply #4 on Thu 27 Nov 2008 03:26 PM (UTC) |
| Message
| Right.
I don't think there's a single MUD host that would allow use of port 23. And even if they did, it would only be for one MUD out of all the MUDs hosted there. |
Zeno McDohl,
Owner of Bleached InuYasha Galaxy
http://www.biyg.org | | Top |
|
| Posted by
| Worstje
Netherlands (899 posts) Bio
|
| Date
| Reply #5 on Thu 27 Nov 2008 05:14 PM (UTC) |
| Message
| I think I need to agree with Xtian.
Port 23 has become a sort of standard for a lot of muds to listen to, also due to the disuse of actual system maintenance through telnet.
Most people who start mudding, will tend to do so on a more publicized server. Simply because smaller ones do not get any exposure other than topmudsites/mudconnector, and that isn't where newbies to the genre come. A good number of muds has a java or flash client for people to use, and they tend to become insufficient for people because they're restrictive in normal stuff (resizing a window, changing a font, remembering certain simple settings, etc). So then they download a client.
Problem is, those people aren't stupid. Just not used to the concept of ports. In their webbrowser, port 80 is the standard. For ftp, 21. People never see ports. So for as far they know, all they need to do is type the server to connect to, and then they assume the default port is what they need. Then it doesn't, and they may do some research to actually figure out the connection information which holds the port. But a lot of newbies will check the address they typed and ignore the port, and give up because it doesn't work. Akin to pressing reconnect in their messenger or retyping user/pass if it doesn't work.
The fact is those people may be stellar roleplays, awesome at hack and slashes, but just like with cars where people know how to refill their gasoline, many won't know how to change their oil because it is either done by their garage or an acquaintance the one time it needs doing.
In my eyes, the default port should be the port that has the biggest chance of establishing a succesful connection, especially for the group who's newer to mudding (after all: once you're hooked you'll try a bit harder to solve your problems :D). Port 4000 can only be used by one mud at a time, so once there's more than one mud on a server (which might be a reason 23 isn't open) you still have to be specific. But 4000 isn't used by many muds at all in my experience, atleast not compared to 23.
Sure, port 23 is not advertised most of the time. But it is used for convenience. I bet that if you were to make a weighted graph with muds weighted depending on their average players, that port 23 would rank quite high. Non-port-23 muds would as a whole also rank quite high, and sure, in numbers they would probably swarm the use-port-23 muds, but the ones that do use 23 are quite likely to contain the biggest muds out there. As such, for the group with least know-how of ports , 23 would give a bigger successrate in connecting. (Someone should try to run such a test on all muds in the databases mentioned above, I'm curious now.)
Besides, it's just a default port. ^^
.. p.s.: I type too much. | | Top |
|
| Posted by
| Nick Gammon
Australia (23,120 posts) Bio
Forum Administrator |
| Date
| Reply #6 on Thu 27 Nov 2008 08:57 PM (UTC) |
| Message
| I have done a quick check of about 500 MUDs on MudConnector (from their listing page). According to that, these are the port numbers in use (the number on the right is the number of times it is used):
347 1
443 1
1000 1
1026 1
1069 1
1111 1
1138 1
1215 1
1223 1
1240 1
1246 1
1250 1
1258 1
1313 1
1350 1
1357 1
1414 1
1615 1
1685 1
1801 1
1869 1
1874 1
1880 1
1892 1
1969 1
1975 1
1982 1
1983 1
1992 1
1994 1
1996 1
1999 1
2002 1
2006 1
2007 1
2008 1
2010 1
2012 1
2021 1
2039 1
2050 1
2063 1
2065 1
2112 1
2120 1
2150 1
2160 1
2252 1
2300 1
2323 1
2345 1
2447 1
2453 1
2474 1
2518 1
2525 1
2569 1
2626 1
2700 1
2834 1
3005 1
3065 1
3100 1
3232 1
3334 1
3336 1
3443 1
3456 1
3498 1
3523 1
3564 1
3778 1
3888 1
3939 1
3999 1
4003 1
4010 1
4045 1
4050 1
4123 1
4190 1
4208 1
4210 1
4255 1
4300 1
4354 1
4370 1
4400 1
4502 1
4510 1
4545 1
4550 1
4601 1
4626 1
4711 1
4739 1
4996 1
5001 1
5018 1
5051 1
5090 1
5190 1
5300 1
5400 1
5403 1
5454 1
5559 1
5566 1
5665 1
5757 1
5900 1
5969 1
6010 1
6069 1
6070 1
6100 1
6116 1
6132 1
6153 1
6161 1
6200 1
6212 1
6250 1
6251 1
6400 1
6500 1
6711 1
6717 1
6767 1
6777 1
6789 1
6886 1
6889 1
6996 1
6999 1
7004 1
7075 1
7115 1
7117 1
7200 1
7206 1
7325 1
7373 1
7500 1
7501 1
7575 1
7620 1
7674 1
7705 1
7725 1
7734 1
7773 1
7778 1
7878 1
7890 1
8002 1
8008 1
8080 1
8178 1
8500 1
8679 1
8800 1
8804 1
8810 1
8887 1
8889 1
8898 1
8900 1
9001 1
9009 1
9010 1
9025 1
9034 1
9091 1
9100 1
9476 1
9600 1
9669 1
9876 1
9911 1
9996 1
11111 1
20000 1
30003 1
40000 1
1236 2
1280 2
1820 2
2020 2
2424 2
2500 2
2860 2
3011 2
3600 2
4051 2
4567 2
4600 2
4999 2
5050 2
5678 2
6363 2
7007 2
8010 2
10000 2
1235 3
2001 3
3500 3
4001 3
4200 3
4321 3
4444 3
6660 3
6715 3
1701 4
6000 4
3333 5
4242 5
7000 5
6666 6
8000 6
4500 7
5555 7
1234 8
9999 8
2222 9
4201 10
6969 10
8888 10
2000 12
7777 12
9000 13
5000 16
23 18
3000 21
4000 61
Listing sorted in usage order, and in port order if usage order is the same.
Port 23 is used 18 times, however port 4000, the default in MUSHclient, is used 61 times. So it appears that a default of 4000 is reasonable.
|
- Nick Gammon
www.gammon.com.au, www.mushclient.com | | Top |
|
| Posted by
| Nick Gammon
Australia (23,120 posts) Bio
Forum Administrator |
| Date
| Reply #7 on Thu 27 Nov 2008 09:29 PM (UTC) |
| Message
| | BTW, some of the MUDs above (eg. Aardwolf) listed port 23 as their port, but also run from port 4000, so that is really another plus to port 4000. |
- Nick Gammon
www.gammon.com.au, www.mushclient.com | | Top |
|
| Posted by
| Worstje
Netherlands (899 posts) Bio
|
| Date
| Reply #8 on Thu 27 Nov 2008 10:29 PM (UTC) |
| Message
| Okay, seems my impressions were wrong then. :) Thanks for checking it out!
(Although I am still curious how things would look on a weighted list, where the amount of average players factors in to how heavy a mud weighs. I bet there's dozens of muds with a very small userbase, too.) | | Top |
|
| Posted by
| Xtian
(53 posts) Bio
|
| Date
| Reply #9 on Sat 29 Nov 2008 08:41 AM (UTC) |
| Message
| Hm, statistics ... I'm a bit astonished that port 23 isnt that common knowledge. Really, all the large MUDs I know use it nowadays.
I was setting out to test the bigger MUDs manually, but I found this listing:
http://www.mudconnect.com/mud-bin/adv_search.cgi?Mode=PORT23
Listing > 70 MUDs acception port 23 connections. I don't know how this list is generated, but I see a lot of mainstream MUDs there.
As I said above the MUDs using 23 are not necessarily advertising it, since the idea was to open up 23 as an alternative to ease the (initial?) login for newbies. This list would not necessarily be complete.
As a large part (all?) of the bigger MUDs have adhered to this inofficial standard Mushclient could use this fact and make life this tiny bit easier for MUD-newbies. That was my idea. | | Top |
|
| Posted by
| Xtian
(53 posts) Bio
|
| Date
| Reply #10 on Sat 29 Nov 2008 09:34 AM (UTC) |
| Message
| As for administrating over port 23. I think we are all agreed that nobody _should_ be using this and going for ssh instead. But in 2008 I think we can also say for sure that nobody _is_ using it for that purpose.
Offtopic: Which MUDs are implemented in a way that more than one (official) MUD is accessible over the same IP? I have never encountered this before. If you don't mind my asking: Are these even relevant - usercount-wise? From the administrator perspective: I can't understand why a mud-admin should want that. It would be alike to having a webpage: www.domain.com/~myuser/ in a way: Really not well-suited for advertising ones MUD. | | Top |
|
| Posted by
| Nick Gammon
Australia (23,120 posts) Bio
Forum Administrator |
| Date
| Reply #11 on Sat 29 Nov 2008 08:20 PM (UTC) Amended on Sat 29 Nov 2008 08:21 PM (UTC) by Nick Gammon
|
| Message
| After re-analyzing the data I got for the last listing, I found a small number seemed to use the same IP address.
For example:
- tangent.dune.net ( http://tangent.dune.net/ )
- slayn.net ( http://www.slayn.net/web/ )
- portent.genesismuds.com ( http://www.genesismuds.com/ )
Checking out their web sites, as I expected, they are sites that host MUDs. Thus they have to allocate different ports to each MUD, as they are on the same server.
There may well be more, most MUDs are listed by a domain name, and it is possible they took out a domain name and redirected it to a MUD host service.
|
- Nick Gammon
www.gammon.com.au, www.mushclient.com | | Top |
|
The dates and times for posts above are shown in Universal Co-ordinated Time (UTC).
To show them in your local time you can join the forum, and then set the 'time correction' field in your profile to the number of hours difference between your location and UTC time.
29,915 views.
It is now over 60 days since the last post. This thread is closed.
Refresh page
![[Go to top]](/images/gototop.gif)
top