http://wiki.amule.org/w/api.php?action=feedcontributions&user=62.82.173.150&feedformat=atomAMule Project FAQ - User contributions [en]2024-03-28T12:23:15ZUser contributionsMediaWiki 1.23.3http://wiki.amule.org/wiki/Test_portTest port2005-06-07T17:14:25Z<p>62.82.173.150: </p>
<hr />
<div>Having a [[FAQ_ed2k#What_is_LowID_and_HighID?|Low ID]] is a common problem in the [[FAQ_ed2k]] network. In [[Main_Page|this wiki]] you can find [[Firewall|several]] [[AMule_problems#aMule_connects_to_server,_but_it_is_always_given_Low-ID._Why?_and,_can_I_do_something_about_it?|articles]] which might help you to get a [[FAQ_ed2k#What_is_LowID_and_HighID?|High ID]].<br />
<br />
Since having a [[FAQ_ed2k#What_is_LowID_and_HighID?|Low ID]] is almost always due to having the [[FAQ_ed2k]] [[port]]s publicly unavailable, [[aMule]] has set up a web page so you can test your ports to see if that is your problem.<br />
<br />
Please visit http://www.amule.org/testport.php and test!</div>62.82.173.150http://wiki.amule.org/wiki/PacketPacket2005-06-07T17:04:25Z<p>62.82.173.150: </p>
<hr />
<div>A packet, in computer nets' context, is a small amount of data (in fact, a specific amount of bytes) which are sent to some other computer through a network.<br />
<br />
Packets contain, appart from the data itself, some meta-data which may vary depending on the network's specification but are usually, at least, the [[IP address]] where they pretend to be delivered to and the [[port]] which is waiting for it.</div>62.82.173.150http://wiki.amule.org/wiki/PortPort2005-06-07T16:59:15Z<p>62.82.173.150: </p>
<hr />
<div>== Description ==<br />
<br />
A port is a number between ''0'' and ''65535'' which allows a [[server]] or [[client]] to know which which application the remote connection is trying to connect.<br />
<br />
Together with an [[IP]] (which specifies the exact computer, either [[server]] or [[client]], with which some computer is trying to connect to) it specifies the exact destination the connection must get to. It is written in the form ''IP:PORT'' most commonly.<br />
<br />
== Examples ==<br />
<br />
For example, [[aMule]] usually uses port ''4662''. So let's suppose your [[IP]] is ''80.0.0.1''. Now let's say some computer somewhere sends a [[packet]] to ''80.0.0.1:4662''. This [[packet]] is going to be sent to ''80.0.0.1'', which is your computer, and once there, it will be delivered to port ''4662'', which most probably will be a port where [[aMule]] will be listening, so it will get to [[aMule]]. [[aMule]] will read the [[packet]] and act depending on what its content is.<br />
<br />
If the packet was sent to ''80.0.0.1:21'' it will also get to you, but (probably) not to [[aMule]] since [[aMule]] will no be listening on that port. If some other application is listening to it (possible some [http://www.faqs.org/rfcs/rfc959.html FTP] [[server]]), it will read its contents and act depending on what they are. If no application is listening to that port, then the [[packet]] will just fail to be delivered. Though it got to your computer, no application was waiting for it, so it will be refused.<br />
<br />
== Notes ==<br />
<br />
Other articles you might want to check:<br />
*[[Test port]]s<br />
*[[IP address]]es</div>62.82.173.150http://wiki.amule.org/wiki/IP_addressIP address2005-06-07T16:49:25Z<p>62.82.173.150: </p>
<hr />
<div>== Summary ==<br />
<br />
An [http://www.faqs.org/rfcs/rfc791.html IP] address is a unique value you are given when connecting to a net using the [http://www.faqs.org/rfcs/rfc791.html Internet Protocol].<br />
<br />
== [http://www.faqs.org/rfcs/rfc791.html IPv4] ==<br />
<br />
Internally, [http://www.faqs.org/rfcs/rfc791.html IP] addresses are 4 bytes numbers. Anyway, their common use is splitting this addresses into 1 byte numbers with a dot (''.'') between them. Since the range of values a 1 byte number can be is 0 - 255, the range of [http://www.faqs.org/rfcs/rfc791.html IP] addresses goes from ''0.0.0.0'' to ''255.255.255.255'' which makes up to 2^(4*8) possible [http://www.faqs.org/rfcs/rfc791.html IP] addresses.<br />
<br />
== [http://www.iana.org/assignments/ipv6-address-space IPv6] ==<br />
<br />
This is the new revised [http://www.faqs.org/rfcs/rfc791.html IP] protocol version, which is meant to replace the old limited [http://www.faqs.org/rfcs/rfc791.html IPv4].<br />
<br />
It is mostly compatible with [http://www.faqs.org/rfcs/rfc791.html IPv4], either directly or indirectly (through middle-way translators).<br />
<br />
[http://www.iana.org/assignments/ipv6-address-space IPv6] addresses are 16 bytes long and are normally written as eight groups of four hexadecimal digits, each group separated from the others by a colon ('':''). For example:<br />
<br />
34fe:3f25:8d34:0000:46d9:0903:47ef:32aa<br />
<br />
When all four hex digits in a group are 0s (''0000''), that group can be omitted or replaced by a single 0. For example:<br />
<br />
34fe:3f25:8d34::46d9:0903:47ef:32aa<br />
34fe:3f25:8d34:0:46d9:0903:47ef:32aa<br />
<br />
Leading 0s can be omitted. For example:<br />
<br />
34fe:3f25:8d34::46d9:903:47ef:32aa<br />
<br />
If more than one '''consecutive''' group has only digits with value 0, they may all be replaced by onyl two colons. For example:<br />
<br />
34fe:3f25:8d34:0000:0000:0000:0000:32aa<br />
<br />
would become<br />
<br />
34fe:3f25:8d34::32aa<br />
<br />
[http://www.faqs.org/rfcs/rfc791.html IPv4] addresses can be easily written in [http://www.iana.org/assignments/ipv6-address-space IPv6] by doing ''::ffff:[http://www.faqs.org/rfcs/rfc791.html IPv4]-address''. For example:<br />
<br />
::ffff:192.168.0.1''<br />
<br />
== Notes ==<br />
<br />
Don't confuse this number with the [[FAQ_eD2k-Kademlia#What_is_LowID_and_HighID?|eD2k IDs]]. [http://www.faqs.org/rfcs/rfc791.html IP] addresses are to identify you anywhere in the net you are connected to, while [[FAQ_eD2k-Kademlia#What_is_LowID_and_HighID?|eD2k ID's]] are only used to identify you on that [[FAQ_eD2k-Kademlia#What_is_ED2K?|eD2k]] [[server]] you are connected to.<br />
<br />
You might also want to check what [[port]]s are.</div>62.82.173.150http://wiki.amule.org/wiki/Server.met_fileServer.met file2005-06-07T16:44:37Z<p>62.82.173.150: </p>
<hr />
<div>== File ==<br />
<br />
'''Name:''' ''server.met''<br />
<br />
'''Location:''' ''~/.aMule/''<br />
<br />
== Description ==<br />
<br />
Binary file containing the list of [[server]]s known to [[aMule]].<br />
<br />
Because its in binary format, it must be changed within [[aMule]], or with other appropriate tools.<br />
<br />
The format description below is for development information purposes.<br />
<br />
== Format ==<br />
<br />
This file's fields are written in [[little endian]] order.<br />
<br />
'''Note:''' All digit fields are unsigned unless stated.<br />
<br />
*Met Header (1 Byte): With value ''Ox0E'', and is used in [[aMule]] to check for valid ''server.met'' files<br />
*Server Count (4 Bytes): Lists the number of [[server]]s that follow<br />
*Block of servers: Each [[server]] is constituted by the following fields:<br />
**[[Server]] [[IP]] (4 Bytes): Simply that. The [[server]]'s [[IP]].<br />
**[[Server]] [[Port]] (2 Bytes): Simply that. The [[port]] through which [[aMule]] will connect to the [[server]].<br />
**Tag Count (4 Bytes): Lists the number of [[server]] tags that follows.<br />
**Block of Tags: Each [[server]] can have a list of associated tags for further information about them. Each tag has the following format:<br />
<br />
== Example ==</div>62.82.173.150