ADCPortal Wiki - Recent changes [en]

NATT - NAT traversal

2010-09-07T09:56:43Z

NATT - NAT traversal:

← Older revision		Revision as of 09:56, 7 September 2010
(2 intermediate revisions not shown)
Line 1:		Line 1:
	===NATT - NAT traversal===		===NATT - NAT traversal===
-	NAT traversal allow two passive clients to connect to each other. For more information about NAT traversal<ref>[https://dcpp.wordpress.com/2010/06/15/nat-traversal-constraints/ NAT Traversal Constraints by Cologic (Jun 15, 2010)]</ref>.	+	NAT traversal allow two passive clients to connect to each other. For more information about NAT traversal<ref>[https://dcpp.wordpress.com/2010/06/15/nat-traversal-constraints/ NAT Traversal Constraints by Cologic (Jun 15, 2010)]</ref><ref>[https://dcpp.wordpress.com/2010/02/13/passive-mode-c-c-connections-and-nat-traversal/ Passive Mode C-C Connections and NAT Traversal by Cologic (Feb 13, 2010)]</ref>.

	If a client does not support TCP4 or TCP6, it will send an RCM to the client it is trying to connect to. If the other client also doesn't support TCP4 (or TCP6 correspondingly), NAT traversal may instead be used. The feature should be signalled in SUP as NATT.		If a client does not support TCP4 or TCP6, it will send an RCM to the client it is trying to connect to. If the other client also doesn't support TCP4 (or TCP6 correspondingly), NAT traversal may instead be used. The feature should be signalled in SUP as NATT.
Line 44:		Line 44:
	!		!
	! <Client B connects to client A's IP address and port 1000>		! <Client B connects to client A's IP address and port 1000>
-	\|}:	+	\|}

	==References==		==References==
	<references/>		<references/>
		+	==Links==
		+	[https://dcpp.wordpress.com/2010/06/14/nat-traversal-compatibility-survey/\| NAT Traversal Compatibility Survey]
	<noinclude>== See Also ==		<noinclude>== See Also ==
	[[Category:Protocol]]		[[Category:Protocol]]
	</noinclude>		</noinclude>

Proposed Extensions

2010-09-07T09:51:56Z

TYPE:

← Older revision		Revision as of 09:51, 7 September 2010
(One intermediate revision not shown)
Line 29:		Line 29:
	Contexts: F, T		Contexts: F, T

-	TPN code	+	'''TPN code'''

	Codes:		Codes:
-		+	{\| class="wikitable" border="0"
-	00 - gone (closed tab, minimised window, etc..)	+	\|-
-	01 - inactive (changed tab, window became unfocused (but not closed/minimised), etc)	+	\| 00 - gone (closed tab, minimised window, etc..)
-	02 - paused (paused typing)	+	\|-
-	10 - active (now in this tab, reading message, actively participating in the chat session)	+	\| 01 - inactive (changed tab, window became unfocused (but not closed/minimised), etc)
-	11 - composing (now typing a message)	+	\|-
		+	\| 02 - paused (paused typing)
		+	\|-
		+	\| 10 - active (now in this tab, reading message, actively participating in the chat session)
		+	\|-
		+	\| 11 - composing (now typing a message)
		+	\|}

	All TPN messages are sent when event occurs. 00, 01, 02 - client should send; 10, 11 - client must send.		All TPN messages are sent when event occurs. 00, 01, 02 - client should send; 10, 11 - client must send.
Line 115:		Line 121:
	To ensure that the hubs and clients alike can read the supplement orders, and the hubs and in the client to display the SUP: ADFEED as support, as well as the client command in the INF SU field should also indicate this.		To ensure that the hubs and clients alike can read the supplement orders, and the hubs and in the client to display the SUP: ADFEED as support, as well as the client command in the INF SU field should also indicate this.

-	Client HSUP … ADFEED	+	{\| class="wikitable" border="0"
-	Hub ISUP … ADFEED	+	\|-
-	Hub ISID …	+	\| Client: HSUP … ADFEED
-	Hub IINF …	+	\| Hub: ISUP … ADFEED
-	Client BINF … SUFEED,…	+	\|-
-	Hub BINF …	+	\|
-	Hub BINF … SUFEED,…	+	\| Hub: ISID …
-	Hub IRSS http://example.com/rss FNExample\\sfeed	+	\|-
		+	\|
		+	\| Hub: IINF …
		+	\|-
		+	\| Client: BINF … SUFEED,…
		+	\| Hub: BINF …
		+	\|-
		+	\|
		+	\| Hub: BINF … SUFEED,…
		+	\|-
		+	\|
		+	\| Hub: IRSS http://example.com/rss FNExample\\sfeed
		+	\|}

	====RSS====		====RSS====
Line 134:		Line 152:
	The command in the following table named fields can be used:		The command in the following table named fields can be used:

-	Code Description	+	{\| class="wikitable" border="0"
-	CH in the channel, where the content is sent in	+	\|-
-	CR content of the sender name of the user, ie the author of the entry	+	! Code
-	~~But~~ the content brief summary	+	! Description
-	~~Submit~~ the DT term UNIX formating	+	\|-
-	FD Feed Description	+	\| '''CH'''
-	FN Feed Name	+	\| in the channel, where the content is sent in
-	LI Direct link to the entry	+	\|-
-	~~The~~ RM value of 1 if the feed has been removed from aggregator.	+	\| '''CR'''
-	The posts from TI	+	\| content of the sender name of the user, ie the author of the entry but the content brief summary submit the DT term UNIX formating
-		+	\|-
		+	\| '''FD'''
		+	\| Feed Description
		+	\|-
		+	\| '''FN'''
		+	\| Feed Name
		+	\|-
		+	\| '''LI'''
		+	\| Direct link to the entry
		+	\|-
		+	\| '''RM'''
		+	\| value of 1 if the feed has been removed from aggregator.
		+	\|-
		+	\| '''TI'''
		+	\| The posts from TI
		+	\|}

	====Examples====		====Examples====

	If any operator picks up a new feed you a generator hub, the hub will notify users about the event:		If any operator picks up a new feed you a generator hub, the hub will notify users about the event:
-	Hub IRSS http://example.com/rss FNExample\\sfeed	+	{\| class="wikitable" border="0"
		+	\|-
		+	\| Hub: IRSS http://example.com/rss FNExample\\sfeed
		+	\|}
		+

	Of course you can also send notifications to the hub, where one operator delete a feed you:		Of course you can also send notifications to the hub, where one operator delete a feed you:
-	Hub IRSS http://example.com/rss RM1	+	{\| class="wikitable" border="0"
		+	\|-
		+	\| Hub: IRSS http://example.com/rss RM1
		+	\|}


	If a client would like to share with others in a feed entry, you must send the following command hubnak what the hub and then all of a client of the Forward, which supports the extension of the FEED.		If a client would like to share with others in a feed entry, you must send the following command hubnak what the hub and then all of a client of the Forward, which supports the extension of the FEED.
-	Client FRSS … +FEED http://example.com/rss TINew\\sfeed\\sentry DEThis\\sis\\sa\\stest\\sfeed\\sentry LIhttp://example.com/entries/new_feed_entry DT1253628000 CRCyB	+	{\| class="wikitable" border="0"
		+	\|-
		+	\|Client FRSS … +FEED http://example.com/rss TINew\\sfeed\\sentry DEThis\\sis\\sa\\stest\\sfeed\\sentry LIhttp://example.com/entries/new_feed_entry DT1253628000 CRCyB
		+	\|}


	If the hub share the same entry is:		If the hub share the same entry is:
-	Hub IRSS http://example.com/rss TINew\\sfeed\\sentry DEThis\\sis\\sa\\stest\\sfeed\\sentry LIhttp://example.com/entries/new_feed_entry DT1253628000 CRCyB	+	{\| class="wikitable" border="0"
		+	\|-
		+	\| Hub IRSS http://example.com/rss TINew\\sfeed\\sentry DEThis\\sis\\sa\\stest\\sfeed\\sentry LIhttp://example.com/entries/new_feed_entry DT1253628000 CRCyB
		+	\|}

	=== KEYP ===		=== KEYP ===

NATT - NAT traversal

2010-09-07T09:34:04Z

Example:

← Older revision		Revision as of 09:34, 7 September 2010
Line 33:		Line 33:


-	~~'''~~Client A: DRCM AAAA BBBB ADC/1.0 foobar~~'''~~	+	{\| class="wikitable" border="0"
-		+	\|-
-	~~'''~~Client B: DNAT BBBB AAAA ADC/1.0 2000 foobar~~'''~~	+	\| Client A: DRCM AAAA BBBB ADC/1.0 foobar
-		+	\| Client B: DNAT BBBB AAAA ADC/1.0 2000 foobar
-	~~'''~~<Client A connects to client B's IP address and port 2000>~~'''~~	+	\|-
-		+	! <Client A connects to client B's IP address and port 2000>
-	~~'''~~Client A: DRNT AAAA BBBB ADC/1.0 1000 foobar~~'''~~	+	\|-
-		+	\| Client A: DRNT AAAA BBBB ADC/1.0 1000 foobar
-	~~'''~~<Client B connects to client A's IP address and port 1000>~~'''~~	+	\|-
		+	!
		+	! <Client B connects to client A's IP address and port 1000>
		+	\|}:

	==References==		==References==

Main Page

2010-09-07T09:28:20Z

← Older revision		Revision as of 09:28, 7 September 2010
Line 7:		Line 7:
	{{1. Design\|2. Feature articled\|3. Information box\|4. Wiki News\|5. Article box\|6. Additional box\|7. Help section box}}		{{1. Design\|2. Feature articled\|3. Information box\|4. Wiki News\|5. Article box\|6. Additional box\|7. Help section box}}
	-->		-->
-	{{MainColumns\|~~SUDP~~\|ADCPortal Info\|ADCPortal Wiki:Current events\|Article Links\|Extra Links\|Help:Contents}}	+	{{MainColumns\|NATT_-_NAT_traversal\|ADCPortal Info\|ADCPortal Wiki:Current events\|Article Links\|Extra Links\|Help:Contents}}

	[[Category:Wiki]]		[[Category:Wiki]]

NATT - NAT traversal

2010-09-07T09:28:02Z

Example:

New page

===NATT - NAT traversal===
NAT traversal allow two passive clients to connect to each other. For more information about NAT traversal<ref>[https://dcpp.wordpress.com/2010/06/15/nat-traversal-constraints/ NAT Traversal Constraints by Cologic (Jun 15, 2010)]</ref>.

If a client does not support TCP4 or TCP6, it will send an RCM to the client it is trying to connect to. If the other client also doesn't support TCP4 (or TCP6 correspondingly), NAT traversal may instead be used. The feature should be signalled in SUP as NATT.

Do note that the hub must forward I4 or I6 for respective clients' INF.

====BASE RCM updates====
When receiving an RCM and the client does not support TCP4 or TCP6, and if NAT-T is supported in the remote client, a NAT command should be sent repeating the protocol and token. The port shall be the outbound port to the connected hub.

====NAT====

'''NAT protocol port token'''

Contexts: T

States: NORMAL

Upon receiving this, try and connect to the specified port. An RNT command should be sent repeating the protocol and token. The port shall be the outbound port to the connected hub. Upon receiving this, try and connect to the specified port.

====RNT====

'''RNT protocol port token'''

Contexts: T

States: NORMAL

Upon receiving this, try and connect to the specified port.

====Example====
Client A is connected to hub A with the outbound port 1000 and client B is connected to hub A with the outbound port 2000. Client A has the SID AAAA and client B has the SID BBBB.

'''Client A: DRCM AAAA BBBB ADC/1.0 foobar'''

'''Client B: DNAT BBBB AAAA ADC/1.0 2000 foobar'''

'''<Client A connects to client B's IP address and port 2000>'''

'''Client A: DRNT AAAA BBBB ADC/1.0 1000 foobar'''

'''<Client B connects to client A's IP address and port 1000>'''

==References==
<references/>
<noinclude>== See Also ==
[[Category:Protocol]]
</noinclude>

Main Page

2010-09-07T09:19:25Z

← Older revision		Revision as of 09:19, 7 September 2010
(2 intermediate revisions not shown)

Template:Latest stable software release/DCBouncer

2010-09-07T09:17:08Z

← Older revision		Revision as of 09:17, 7 September 2010
Line 1:		Line 1:
	{{LSR		{{LSR
	\| article = DCBouncer		\| article = DCBouncer
-	\| latest_release_version = rev ~~138~~	+	\| latest_release_version = rev 143
-	\| latest_release_date = {{release date and age\|2010\|01\|28}}	+	\| latest_release_date = {{release date and age\|2010\|08\|21}}
	}}<noinclude>[[Category:Software Release Templates]]</noinclude>		}}<noinclude>[[Category:Software Release Templates]]</noinclude>

Template:Latest stable software release/ApexDC++

2010-09-07T09:13:01Z

← Older revision		Revision as of 09:13, 7 September 2010
(3 intermediate revisions not shown)
Line 1:		Line 1:
	{{LSR		{{LSR
	\| article = ApexDC++		\| article = ApexDC++
-	\| latest_release_version = 1.2.2	+	\| latest_release_version = 1.3.6
-	\| latest_release_date = {{release date and age\|~~2009~~\|10\|20}}	+	\| latest_release_date = {{release date and age\|2010\|09\|05}}
	}}<noinclude>[[Category:Software Release Templates]]</noinclude>		}}<noinclude>[[Category:Software Release Templates]]</noinclude>

Proposed Extensions

2010-09-06T19:27:56Z

ADCS:

Show changes

Luadch

2010-09-06T18:58:14Z

← Older revision		Revision as of 18:58, 6 September 2010
Line 1:		Line 1:
		+	{{DiscontinuedProject}}
	{{Infobox Software		{{Infobox Software
	\| name = Luadch		\| name = Luadch

ADC Software List

2010-09-06T18:57:09Z

Luadch:

← Older revision		Revision as of 18:57, 6 September 2010
(One intermediate revision not shown)
Line 28:		Line 28:
	[http://github.com/JLarky/eadc-hub/tree/master eadc-hub Website]		[http://github.com/JLarky/eadc-hub/tree/master eadc-hub Website]

-	=== eHub ===	+	=== [[Image:Alert.svg\|18px\|Discontinued Software]] eHub ===
	eHub is a software written in java that supports jabber and rss feeds.		eHub is a software written in java that supports jabber and rss feeds.

Line 37:		Line 37:
	[https://launchpad.net/ehub/ eHub Website]		[https://launchpad.net/ehub/ eHub Website]

-	=== Luadch ===	+	=== [[Image:Alert.svg\|18px\|Discontinued Software]] Luadch ===
	''Main article: [[Luadch\|Luadch]]		''Main article: [[Luadch\|Luadch]]

Template:Latest preview software release/ADCH++

2010-09-06T18:54:28Z

← Older revision		Revision as of 18:54, 6 September 2010
Line 1:		Line 1:
	{{LPR		{{LPR
	\| article = ADCH++		\| article = ADCH++
-	\| latest_release_version = 2.5	+	\| latest_release_version = 2.5.2
-	\| latest_release_date = {{release date and age\|2010\|05\|05}}	+	\| latest_release_date = {{release date and age\|2010\|08\|01}}
	}}<noinclude>[[Category:Software Release Templates]]</noinclude>		}}<noinclude>[[Category:Software Release Templates]]</noinclude>

BLOM

2010-09-06T18:50:09Z

Test Vectors:

← Older revision		Revision as of 18:50, 6 September 2010
(One intermediate revision not shown)
Line 66:		Line 66:

	=====Tiger=====		=====Tiger=====
-	For TTH roots, b is 192 and a reasonable value for h is 24, giving a maximum k = 8 which means that m = 8 * n / ln 2 ≈ 11.5 * n. The required bandwidth then becomes 11.5 * n / 8 bytes, so approximately 1.44 bytes per file in the users share. For 20000 files, m should then be 230016 (taking into account the modulo 64 requirement), giving a p = 0.004, in other words ~99.6% of all searches that don't match a users share would not be sent, saving valuable upload bandwidth for the hub. The client calculates i valid positions, if x is an array of bytes containing the hash of the file, on a little-endian machine, by doing pos = x[0+ih/8] \| (x[1+ih/8] << 8) \| (x[2+i*h/8] << 16) for i = [0;k). This is of course a special case where h % 8 = 0, the actual algorithm has to take into consideration values for h where the integer crosses byte boundaries.	+	For TTH roots, b is 192 and a reasonable value for h is 24, giving a maximum k = 8 which means that m = 8 * n / ln 2 ≈ 11.5 * n. The required bandwidth then becomes 11.5 * n / 8 bytes, so approximately 1.44 bytes per file in the users share. For 20000 files, m should then be 230016 (taking into account the modulo 64 requirement), giving a p = 0.004, in other words ~99.6% of all searches that don't match a users share would not be sent, saving valuable upload bandwidth for the hub. The client calculates i valid positions, if x is an array of bytes containing the hash of the file, on a little-endian machine, by doing pos = x[0+ih/8] \| (x[1+ih/8] << 8) \| (x[2+i*h/8] << 16) for i = [0;k). This is of course a special case where h % 8 = 0, the actual algorithm has to take into consideration values for h where the integer crosses byte boundaries.
-		+
-	~~For test vectors, see the [http://www.adcportal.com/wiki/index.php/Talk:BLOM\|ADC wiki talk page].~~	+
-		+

	== Test Vectors ==		== Test Vectors ==
-	To allow implementing the above description of a Bloomfilter here is a link to some testvectors to check your implementation. ~~<br>~~	+	To allow implementing the above description of a Bloomfilter here is a link to some testvectors to check your implementation. As the Links below may implement a bloomfilter though may or may not be the Bloomfilter specified in the above description.
-	~~[http://www.jucy.eu/misc/demo.txt Bloom Textvectors]<br>~~	+	[http://www.adcportal.com/wiki/index.php/Talk:BLOM Bloom Discussion]<br>
-	As the Links below may implement a bloomfilter though may or may not be the Bloomfilter specified in the above description.	+

	== Links ==		== Links ==