ROSE - Revision history

DL5RB: /* See also */ Add RFCs about X.25-over-TCP and IP-over-X.25

2015-06-15T23:20:01Z

See also: Add RFCs about X.25-over-TCP and IP-over-X.25

← Older revision		Revision as of 23:20, 15 June 2015
Line 78:		Line 78:
	* http://www.itu.int/rec/T-REC-X.121-200010-I/E Recommendation ITU-T X.121 (10/00)		* http://www.itu.int/rec/T-REC-X.121-200010-I/E Recommendation ITU-T X.121 (10/00)
	* [http://web.archive.org/web/*/http://www.rats.org/ RATS website] on [http://www.archive.org archive.org]		* [http://web.archive.org/web/*/http://www.rats.org/ RATS website] on [http://www.archive.org archive.org]
			* [http://www.rfc-editor.org/rfc/rfc1356.txt RFC1356] ''Multiprotocol Interconnect on X.25 and ISDN in the Packet Mode''
			* [http://www.rfc-editor.org/rfc/rfc1613.txt RFC1613] ''Cisco Systems X.25 over TCP (XOT)''

DL5RB: /* See also */ Remove stray `]' bracket.

2015-06-15T22:39:28Z

DL5RB: Link ITU-T and X.121 to Wikipedia.

2011-07-07T09:20:02Z

Link ITU-T and X.121 to Wikipedia.

← Older revision		Revision as of 09:20, 7 July 2011
Line 1:		Line 1:
	The '''ROSE''' (RATS Open Systems Environment) protocol was conceived and first implemented by Tom Moulton W2VY and is an implementation of the [[X.25]] [[packet layer protocol]] ([[PLP]]) and is designed to operate with [[AX.25]] as its datalink layer protocol. It too provides a network layer. ROSE addresses take the form of 10 digit numbers. The first four digits are called the [[Data Network Identification Code]] ([[DNIC]]) and are taken from Appendix B of the [[ITU-T]] [[X.121]] recommendation. The kernel based ROSE support is a modified version of the [http://rose.fpac.free.fr/rubrique.php3?id_rubrique=1 FPAC] Rose implementation. Installing FPAC as a wrapper around ROSE makes for a much		The '''ROSE''' (RATS Open Systems Environment) protocol was conceived and first implemented by Tom Moulton W2VY and is an implementation of the [[X.25]] [[packet layer protocol]] ([[PLP]]) and is designed to operate with [[AX.25]] as its datalink layer protocol. It too provides a network layer. ROSE addresses take the form of 10 digit numbers. The first four digits are called the [[Data Network Identification Code]] ([[DNIC]]) and are taken from Appendix B of the [[Wikipedia:ITU-T ITU-T]] [[Wikipedia:X.121\|X.121]] recommendation. The kernel based ROSE support is a modified version of the [http://rose.fpac.free.fr/rubrique.php3?id_rubrique=1 FPAC] Rose implementation. Installing FPAC as a wrapper around ROSE makes for a much
	easier use and operation of the protocol, there is also ongoing work on FPAC under Linux.		easier use and operation of the protocol, there is also ongoing work on FPAC under Linux.

DL5RB: Expand ''ROSE'' acronym

2011-07-07T09:04:41Z

Expand ''ROSE'' acronym

← Older revision		Revision as of 09:04, 7 July 2011
Line 1:		Line 1:
	The '''ROSE''' protocol was conceived and first implemented by Tom Moulton W2VY and is an implementation of the [[X.25]] [[packet layer protocol]] ([[PLP]]) and is designed to operate with [[AX.25]] as its datalink layer protocol. It too provides a network layer. ROSE addresses take the form of 10 digit numbers. The first four digits are called the [[Data Network Identification Code]] ([[DNIC]]) and are taken from Appendix B of the [[ITU-T]] [[X.121]] recommendation. The kernel based ROSE support is a modified version of the [http://rose.fpac.free.fr/rubrique.php3?id_rubrique=1 FPAC] Rose implementation. Installing FPAC as a wrapper around ROSE makes for a much		The '''ROSE''' (RATS Open Systems Environment) protocol was conceived and first implemented by Tom Moulton W2VY and is an implementation of the [[X.25]] [[packet layer protocol]] ([[PLP]]) and is designed to operate with [[AX.25]] as its datalink layer protocol. It too provides a network layer. ROSE addresses take the form of 10 digit numbers. The first four digits are called the [[Data Network Identification Code]] ([[DNIC]]) and are taken from Appendix B of the [[ITU-T]] [[X.121]] recommendation. The kernel based ROSE support is a modified version of the [http://rose.fpac.free.fr/rubrique.php3?id_rubrique=1 FPAC] Rose implementation. Installing FPAC as a wrapper around ROSE makes for a much
	easier use and operation of the protocol, there is also ongoing work on FPAC under Linux.		easier use and operation of the protocol, there is also ongoing work on FPAC under Linux.

DL5RB: Fix spelling mistakes; put emphasis on ''rare'' protocol

2011-07-07T08:55:54Z

Fix spelling mistakes; put emphasis on ''rare'' protocol

← Older revision		Revision as of 08:55, 7 July 2011
Line 2:		Line 2:
	easier use and operation of the protocol, there is also ongoing work on FPAC under Linux.		easier use and operation of the protocol, there is also ongoing work on FPAC under Linux.

	These days ROSE is a rare protocol; islands in Australia, France and ~~Unitied~~ States (Florida and Michigan) are known to still use the ~~protcol~~.		These days ROSE is a ''rare'' protocol; islands in Australia, France and the United States (Florida and Michigan) are known to still use the protocol.

	The ROSE packet layer protocol protocol relies on, and uses the AX.25 ports you have created. The ROSE protocol rides on top of the AX.25 protocol. To configure ROSE you must create a configuration file that describes the ROSE ports you want. You can create multiple ROSE ports if you wish, the same procedure applies for each.		The ROSE packet layer protocol protocol relies on, and uses the AX.25 ports you have created. The ROSE protocol rides on top of the AX.25 protocol. To configure ROSE you must create a configuration file that describes the ROSE ports you want. You can create multiple ROSE ports if you wish, the same procedure applies for each.

Kp4djt at 23:43, 24 March 2007

2007-03-24T23:43:29Z

← Older revision		Revision as of 23:43, 24 March 2007
Line 1:		Line 1:
	The '''ROSE''' protocol was conceived and first implemented by Tom Moulton W2VY and is an implementation of the [[X.25]] [[packet layer protocol]] ([[PLP]]) and is designed to operate with [[AX.25]] as its datalink layer protocol. It too provides a network layer. ROSE addresses take the form of 10 digit numbers. The first four digits are called the [[Data Network Identification Code]] ([[DNIC]]) and are taken from Appendix B of the [[ITU-T]] [[X.121]] recommendation. The kernel based ROSE support is a modified version of the [http://rose.fpac.free.fr/rubrique.php3?id_rubrique=1 FPAC] Rose implementation.		The '''ROSE''' protocol was conceived and first implemented by Tom Moulton W2VY and is an implementation of the [[X.25]] [[packet layer protocol]] ([[PLP]]) and is designed to operate with [[AX.25]] as its datalink layer protocol. It too provides a network layer. ROSE addresses take the form of 10 digit numbers. The first four digits are called the [[Data Network Identification Code]] ([[DNIC]]) and are taken from Appendix B of the [[ITU-T]] [[X.121]] recommendation. The kernel based ROSE support is a modified version of the [http://rose.fpac.free.fr/rubrique.php3?id_rubrique=1 FPAC] Rose implementation. Installing FPAC as a wrapper around ROSE makes for a much
			easier use and operation of the protocol, there is also ongoing work on FPAC under Linux.

	These days ROSE is a rare protocol; islands in France and Florida are known to still use the protcol.		These days ROSE is a rare protocol; islands in Australia, France and Unitied States (Florida and Michigan) are known to still use the protcol.

	The ROSE packet layer protocol protocol relies on, and uses the AX.25 ports you have created. The ROSE protocol rides on top of the AX.25 protocol. To configure ROSE you must create a configuration file that describes the ROSE ports you want. You can create multiple ROSE ports if you wish, the same procedure applies for each.		The ROSE packet layer protocol protocol relies on, and uses the AX.25 ports you have created. The ROSE protocol rides on top of the AX.25 protocol. To configure ROSE you must create a configuration file that describes the ROSE ports you want. You can create multiple ROSE ports if you wish, the same procedure applies for each.


	== Configuring /etc/ax25/rsports ==		== Configuring /etc/ax25/rsports ==

Kp4djt: Changed fpac page to F6BVP's working pages with the FPAC Mini-how to in FR and EN.

2007-03-24T23:39:09Z

Changed fpac page to F6BVP's working pages with the FPAC Mini-how to in FR and EN.

← Older revision		Revision as of 23:39, 24 March 2007
Line 1:		Line 1:
	The '''ROSE''' protocol was conceived and first implemented by Tom Moulton W2VY and is an implementation of the [[X.25]] [[packet layer protocol]] ([[PLP]]) and is designed to operate with [[AX.25]] as its datalink layer protocol. It too provides a network layer. ROSE addresses take the form of 10 digit numbers. The first four digits are called the [[Data Network Identification Code]] ([[DNIC]]) and are taken from Appendix B of the [[ITU-T]] [[X.121]] recommendation. The kernel based ROSE support is a modified version of the [http://fpac.~~lmi.ecp~~.fr/~~f1oat/f1oat~~.~~html~~ FPAC] Rose implementation.		The '''ROSE''' protocol was conceived and first implemented by Tom Moulton W2VY and is an implementation of the [[X.25]] [[packet layer protocol]] ([[PLP]]) and is designed to operate with [[AX.25]] as its datalink layer protocol. It too provides a network layer. ROSE addresses take the form of 10 digit numbers. The first four digits are called the [[Data Network Identification Code]] ([[DNIC]]) and are taken from Appendix B of the [[ITU-T]] [[X.121]] recommendation. The kernel based ROSE support is a modified version of the [http://rose.fpac.free.fr/rubrique.php3?id_rubrique=1 FPAC] Rose implementation.

	These days ROSE is a rare protocol; islands in France and Florida are known to still use the protcol.		These days ROSE is a rare protocol; islands in France and Florida are known to still use the protcol.

DL5RB: Speeling.

2006-04-18T13:32:22Z

Speeling.

← Older revision		Revision as of 13:32, 18 April 2006
Line 1:		Line 1:
	The '''ROSE''' protocol was conceived and first implemented by Tom Moulton W2VY and is an implementation of the [[X.25]] [[packet layer protocol]] ([[PLP]]) and is designed to operate with [[AX.25]] as its datalink layer protocol. It too provides a network layer. ROSE addresses take the form of 10 digit numbers. The first four digits are called the [[Data Network Identification Code]] ([[DNIC]]) and are taken from Appendix B of the [[ITU-T]] [[X.121]] recommendation. The kernel based ROSE support is a modified version of the [http://fpac.lmi.ecp.fr/f1oat/f1oat.html FPAC] Rose implementation.		The '''ROSE''' protocol was conceived and first implemented by Tom Moulton W2VY and is an implementation of the [[X.25]] [[packet layer protocol]] ([[PLP]]) and is designed to operate with [[AX.25]] as its datalink layer protocol. It too provides a network layer. ROSE addresses take the form of 10 digit numbers. The first four digits are called the [[Data Network Identification Code]] ([[DNIC]]) and are taken from Appendix B of the [[ITU-T]] [[X.121]] recommendation. The kernel based ROSE support is a modified version of the [http://fpac.lmi.ecp.fr/f1oat/f1oat.html FPAC] Rose implementation.

	These days ROSE is a rare protocol; ~~Islands~~ in France and Florida are ~~know~~ to still use the protcol.		These days ROSE is a rare protocol; islands in France and Florida are known to still use the protcol.

	The ROSE packet layer protocol protocol relies on, and uses the AX.25 ports you have created. The ROSE protocol rides on top of the AX.25 protocol. To configure ROSE you must create a configuration file that describes the ROSE ports you want. You can create multiple ROSE ports if you wish, the same procedure applies for each.		The ROSE packet layer protocol protocol relies on, and uses the AX.25 ports you have created. The ROSE protocol rides on top of the AX.25 protocol. To configure ROSE you must create a configuration file that describes the ROSE ports you want. You can create multiple ROSE ports if you wish, the same procedure applies for each.

DL5RB: Fold "Editing Configuring a ROSE port" into ROSE page.

2006-04-18T13:27:29Z

Fold "Editing Configuring a ROSE port" into ROSE page.

← Older revision		Revision as of 13:27, 18 April 2006
Line 1:		Line 1:
	The '''ROSE''' protocol was conceived and first implemented by Tom Moulton W2VY and is an implementation of the [[X.25]] [[packet layer protocol]] ([[PLP]]) and is designed to operate with [[AX.25]] as its datalink layer protocol. It too provides a network layer. ROSE addresses take the form of 10 digit numbers. The first four digits are called the [[Data Network Identification Code]] ([[DNIC]]) and are taken from Appendix B of the [[ITU-T]] [[X.121]] recommendation.		The '''ROSE''' protocol was conceived and first implemented by Tom Moulton W2VY and is an implementation of the [[X.25]] [[packet layer protocol]] ([[PLP]]) and is designed to operate with [[AX.25]] as its datalink layer protocol. It too provides a network layer. ROSE addresses take the form of 10 digit numbers. The first four digits are called the [[Data Network Identification Code]] ([[DNIC]]) and are taken from Appendix B of the [[ITU-T]] [[X.121]] recommendation. The kernel based ROSE support is a modified version of the [http://fpac.lmi.ecp.fr/f1oat/f1oat.html FPAC] Rose implementation.

	These days ROSE is a rare protocol; Islands in France and Florida are know to still use the protcol.		These days ROSE is a rare protocol; Islands in France and Florida are know to still use the protcol.

	* [[Configuring a ROSE port]]		The ROSE packet layer protocol protocol relies on, and uses the AX.25 ports you have created. The ROSE protocol rides on top of the AX.25 protocol. To configure ROSE you must create a configuration file that describes the ROSE ports you want. You can create multiple ROSE ports if you wish, the same procedure applies for each.

			== Configuring /etc/ax25/rsports ==

			The file where you configure your ROSE interfaces is the /etc/ax25/rsports file. This file describes the ROSE port in much the same way as the /etc/ax25/axports file describes the AX.25 ports.

			This file is formatted as follows:

			name address description

			Where:

			; name : is the text name that you wish to refer to the port by.
			; address : is the 10 digit ROSE address you wish to assign to this port.
			; description : is a free text description of the port.

			An example would look something like the following:

			rose 5050294760 Rose Port

			Note that ROSE will use the default callsign/ssid configured on each AX.25 port unless you specify otherwise.

			To configure a separate callsign/ssid for ROSE to use on each port you use the rsparms command as follows:

			<pre>
			# /usr/sbin/rsprams -call VK2KTJ-10
			</pre>

			This example would make Linux listen for and use the callsign/ssid VK2KTJ-10 on all of the configured AX.25 ports for ROSE calls.

			== Creating the ROSE Network device ==

			When you have created the /etc/ax25/rsports file you may create the ROSE device in much the same way as you did for the AX.25 devices. This time you use the rsattach command. The rsattach command creates network devices named `rose[0-5]'. The first time you use the rsattach command it create the `rose0' device, the second time it creates the `rose1' device etc. For example:

			<pre>
			# rsattach rose
			</pre>

			This command would start the ROSE device (rose0) configured with the details specified in the /etc/ax25/rsports file for the entry named `rose'.

			== Configuring ROSE Routing ==

			The ROSE protocol currently supports only static routing. The rsparms utility allows you to configure your ROSE routing table under Linux.

			For example:

			<pre>
			# rsparms -nodes add 5050295502 radio vk2xlz
			</pre>

			would add a route to ROSE node 5050295502 via an AX.25 port named `radio' in your /etc/ax25/axports file to a neighbour with the callsign VK2XLZ.

			You may specify a route with a mask to capture a number of ROSE destinations into a single routing entry. The syntax looks like:

			<pre>
			# rsparms -nodes add 5050295502/4 radio vk2xlz
			</pre>

			which would be identical to the previous example except that it would match any destination address that matched the first four digits supplied, in this case any address commencing with the digits 5050. An alternate form for this command is:

			<pre>
			# rsparms -nodes add 5050/4 radio vk2xlz
			</pre>

			which is probably the less ambiguous form.

	== See also ==		== See also ==

DL5RB: /* See also */

2006-04-15T23:59:56Z

← Older revision		Revision as of 22:39, 15 June 2015
Line 77:		Line 77:
	* http://www.itu.int/rec/T-REC-X.25-199809-I!Cor1/E Recommendation ITU-T X.25 (10/96) Corrigendum 1		* http://www.itu.int/rec/T-REC-X.25-199809-I!Cor1/E Recommendation ITU-T X.25 (10/96) Corrigendum 1
	* http://www.itu.int/rec/T-REC-X.121-200010-I/E Recommendation ITU-T X.121 (10/00)		* http://www.itu.int/rec/T-REC-X.121-200010-I/E Recommendation ITU-T X.121 (10/00)
	* [http://web.archive.org/web/*/http://www.rats.org/ RATS website] on [http://www.archive.org archive.org]]		* [http://web.archive.org/web/*/http://www.rats.org/ RATS website] on [http://www.archive.org archive.org]

← Older revision		Revision as of 23:59, 15 April 2006
Line 6:		Line 6:

	== See also ==		== See also ==
	* [[Wikipedia:X.25\|X.25]] ~~X.25~~ on Wikipedia		* [[Wikipedia:X.25\|X.25]] on Wikipedia
	* [[Wikipedia:X.121\|X.121]] ~~X.121~~ on Wikipedia		* [[Wikipedia:X.121\|X.121]] on Wikipedia
	* http://www.itu.int/rec/T-REC-X.25-199610-I/E Recommendation ITU-T X.25 (10/96)		* http://www.itu.int/rec/T-REC-X.25-199610-I/E Recommendation ITU-T X.25 (10/96)
	* http://www.itu.int/rec/T-REC-X.25-199809-I!Cor1/E Recommendation ITU-T X.25 (10/96) Corrigendum 1		* http://www.itu.int/rec/T-REC-X.25-199809-I!Cor1/E Recommendation ITU-T X.25 (10/96) Corrigendum 1
	* http://www.itu.int/rec/T-REC-X.121-200010-I/E Recommendation ITU-T X.121 (10/00)		* http://www.itu.int/rec/T-REC-X.121-200010-I/E Recommendation ITU-T X.121 (10/00)
	* [http://web.archive.org/web/*/http://www.rats.org/ RATS website] on [http://www.archive.org archive.org]]		* [http://web.archive.org/web/*/http://www.rats.org/ RATS website] on [http://www.archive.org archive.org]]