Revision 4 - Revision history

Costel Mincea: Text replacement - "" to ""

2025-01-26T19:27:39Z

Text replacement - "<syntaxhighlight>" to "<syntaxhighlight lang="C" line>"

← Older revision		Revision as of 19:27, 26 January 2025
Line 117:		Line 117:
	There already exists a SANA-II command for querying global device statistics (<tt>S2_GETGLOBALSTATS</tt>) which should be common to all kinds of networking devices. Statistics that are particular to a certain device type are intended to be returned through the <tt>S2_GETSPECIALSTATS</tt> command. I feel that these mechanisms both fail to cater well enough for dial-up or session-oriented networking applications such as PPP or PPPoE. Since the data structure used by <tt>S2_GETGLOBALSTATS</tt> is of a fixed size and not intended to accomodate for new fields, I propose to introduce a new command which uses a different data structure, as follows:		There already exists a SANA-II command for querying global device statistics (<tt>S2_GETGLOBALSTATS</tt>) which should be common to all kinds of networking devices. Statistics that are particular to a certain device type are intended to be returned through the <tt>S2_GETSPECIALSTATS</tt> command. I feel that these mechanisms both fail to cater well enough for dial-up or session-oriented networking applications such as PPP or PPPoE. Since the data structure used by <tt>S2_GETGLOBALSTATS</tt> is of a fixed size and not intended to accomodate for new fields, I propose to introduce a new command which uses a different data structure, as follows:

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	struct Sana2ExtDeviceStats		struct Sana2ExtDeviceStats
	{		{
Line 251:		Line 251:
	To bridge this gap, I propose a new command which will make a driver connect to its link layer and go online, which uses the following data structure:		To bridge this gap, I propose a new command which will make a driver connect to its link layer and go online, which uses the following data structure:

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	struct Sana2Connection		struct Sana2Connection
	{		{
Line 274:		Line 274:
	This list contains options, to be used during the connection process. Each node has the following format:		This list contains options, to be used during the connection process. Each node has the following format:

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	struct Sana2ConnectionOption		struct Sana2ConnectionOption
	{		{
Line 310:		Line 310:
	The <tt>reserved</tt> parameter '''must''' be <tt>NULL</tt>. The <tt>s2cm</tt> parameter points to a data structure, as follows:		The <tt>reserved</tt> parameter '''must''' be <tt>NULL</tt>. The <tt>s2cm</tt> parameter points to a data structure, as follows:

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	struct Sana2ConnectionMessage		struct Sana2ConnectionMessage
	{		{
Line 781:		Line 781:
	The SANA-II standard already allows for statistics to be returned on the amount of data that has passed through a driver. Unfortunately, that information is not very accurate in that no information is provided on the time span in which the data was accumulated. Such information would be helpful in trying to determine as accurately as possible how large the data throughput actually is. I therefore propose a new command which can be used to obtain that information, which uses the following data structure:		The SANA-II standard already allows for statistics to be returned on the amount of data that has passed through a driver. Unfortunately, that information is not very accurate in that no information is provided on the time span in which the data was accumulated. Such information would be helpful in trying to determine as accurately as possible how large the data throughput actually is. I therefore propose a new command which can be used to obtain that information, which uses the following data structure:

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	struct Sana2ThroughputStats		struct Sana2ThroughputStats
	{		{
Line 909:		Line 909:
	I propose that the <tt>S2_DEVICEQUERY</tt> command and the associated <tt>Sana2DeviceQuery</tt> structure are extended to allow for the raw MTU to be queried. The new <tt>Sana2DeviceQuery</tt> structure would look like this:		I propose that the <tt>S2_DEVICEQUERY</tt> command and the associated <tt>Sana2DeviceQuery</tt> structure are extended to allow for the raw MTU to be queried. The new <tt>Sana2DeviceQuery</tt> structure would look like this:

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	struct Sana2DeviceQuery		struct Sana2DeviceQuery
	{		{
Line 1,060:		Line 1,060:
	The <tt>reserved</tt> parameter '''must''' be set to <tt>NULL</tt>. The <tt>S2LogMessage</tt> structure passed as the third parameter looks like this:		The <tt>reserved</tt> parameter '''must''' be set to <tt>NULL</tt>. The <tt>S2LogMessage</tt> structure passed as the third parameter looks like this:

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	struct S2LogMessage		struct S2LogMessage
	{		{

Steven Solie: /* Introduction */

2012-05-10T20:54:23Z

Introduction

← Older revision		Revision as of 20:54, 10 May 2012
Line 14:		Line 14:
	The following text tries to tie all issues together and will conclude by listing problems which I think still need attention (or in other words, I didn't find a solution myself). Wherever possible, I have tried to provide a rationale for the changes I propose.		The following text tries to tie all issues together and will conclude by listing problems which I think still need attention (or in other words, I didn't find a solution myself). Wherever possible, I have tried to provide a rationale for the changes I propose.

	Please feel free to comment; you can contact me through the [~~mailto~~:~~olsen@amiga~~.~~com?subject=SANA-IIR4%20proposal~~ ~~e-mail~~ ~~address~~] ~~given in the headline of this document~~. Note that the issues discussed in this document are just a list of proposed changes. No such features are part of any SANA-II specifications, although I'd like to claim that I have tried to implement the majority of the changes listed below in my own software.		Please feel free to comment; you can contact me through the [http://www.amigaos.net/contact AmigaOS contact form]. Note that the issues discussed in this document are just a list of proposed changes. No such features are part of any SANA-II specifications, although I'd like to claim that I have tried to implement the majority of the changes listed below in my own software.

	This is a revised version of the original document I put together around October 14, 2001. For a list of changes that have been made since, please see [[#10_changes\|section 10]] ('Changes'). This document has been updated and enhanced several times, in response to discussions with Heinz Wrobel.		This is a revised version of the original document I put together around October 14, 2001. For a list of changes that have been made since, please see [[#10_changes\|section 10]] ('Changes'). This document has been updated and enhanced several times, in response to discussions with Heinz Wrobel.

Steven Solie: /* SANA-II Revision 4 */

2012-05-10T20:52:51Z

SANA-II Revision 4

← Older revision		Revision as of 20:52, 10 May 2012
Line 2:		Line 2:

	Extending the SANA-II network driver specification<br />		Extending the SANA-II network driver specification<br />
	by ~~[mailto:olsen@amiga.com?subject=SANA-IIR4%20proposal~~ Olaf Barthel]		by Olaf Barthel

	(Last updated 02-Mar-2003)		(Last updated 02-Mar-2003)

Steven Solie at 15:40, 2 May 2012

2012-05-02T15:40:51Z

Show changes

Steven Solie: /* 2.3 S2_GETEXTENDEDGLOBALSTATS */

2012-05-02T15:28:30Z

2.3 S2_GETEXTENDEDGLOBALSTATS

← Older revision		Revision as of 15:28, 2 May 2012
Line 117:		Line 117:


	=== ~~2.3 <tt>~~S2_GETEXTENDEDGLOBALSTATS~~</tt>~~ ===		=== S2_GETEXTENDEDGLOBALSTATS ===

	There already exists a SANA-II command for querying global device statistics (<tt>S2_GETGLOBALSTATS</tt>) which should be common to all kinds of networking devices. Statistics that are particular to a certain device type are intended to be returned through the <tt>S2_GETSPECIALSTATS</tt> command. I feel that these mechanisms both fail to cater well enough for dial-up or session-oriented networking applications such as PPP or PPPoE. Since the data structure used by <tt>S2_GETGLOBALSTATS</tt> is of a fixed size and not intended to accomodate for new fields, I propose to introduce a new command which uses a different data structure, as follows:		There already exists a SANA-II command for querying global device statistics (<tt>S2_GETGLOBALSTATS</tt>) which should be common to all kinds of networking devices. Statistics that are particular to a certain device type are intended to be returned through the <tt>S2_GETSPECIALSTATS</tt> command. I feel that these mechanisms both fail to cater well enough for dial-up or session-oriented networking applications such as PPP or PPPoE. Since the data structure used by <tt>S2_GETGLOBALSTATS</tt> is of a fixed size and not intended to accomodate for new fields, I propose to introduce a new command which uses a different data structure, as follows:

			<syntaxhighlight>
	~~<pre>~~struct Sana2ExtDeviceStats		struct Sana2ExtDeviceStats
	{		{
	ULONG s2xds_Length;		ULONG s2xds_Length;
Line 137:		Line 138:
	struct timeval s2xds_LastDisconnected;		struct timeval s2xds_LastDisconnected;
	struct timeval s2xds_TimeConnected;		struct timeval s2xds_TimeConnected;
	};~~</pre>~~		};
			</syntaxhighlight>

	Before I proceed to explain what purposes the individual members serve, a few words on the <tt>S2QUAD</tt> type, which is defined as follows:		Before I proceed to explain what purposes the individual members serve, a few words on the <tt>S2QUAD</tt> type, which is defined as follows:

Line 246:		Line 249:

	<tt>#define S2_GETEXTENDEDGLOBALSTATS 0xC004</tt>		<tt>#define S2_GETEXTENDEDGLOBALSTATS 0xC004</tt>



	=== 2.4 <tt>S2_CONNECT</tt> ===		=== 2.4 <tt>S2_CONNECT</tt> ===

Steven Solie at 05:00, 1 April 2012

2012-04-01T05:00:36Z

← Older revision		Revision as of 05:00, 1 April 2012
Line 1:		Line 1:
	== SANA-II Revision 4 ==		= SANA-II Revision 4 =

	Extending the SANA-II network driver specification<br />		Extending the SANA-II network driver specification<br />

Steven Solie at 04:59, 1 April 2012

2012-04-01T04:59:48Z

← Older revision		Revision as of 04:59, 1 April 2012
Line 1:		Line 1:
			== SANA-II Revision 4 ==
	= =

	Extending the SANA-II network driver specification<br />		Extending the SANA-II network driver specification<br />
	by [mailto:olsen@amiga.com?subject=SANA-IIR4%20proposal Olaf Barthel]		by [mailto:olsen@amiga.com?subject=SANA-IIR4%20proposal Olaf Barthel]

	=== ===

	(Last updated 02-Mar-2003)		(Last updated 02-Mar-2003)

Steven Solie: Created page with "= = Extending the SANA-II network driver specification
by [mailto:olsen@amiga.com?subject=SANA-IIR4%20proposal Olaf Barthel] === === (Last updated 02-Mar-2003) ==..."

2012-03-28T03:28:09Z

Created page with "= = Extending the SANA-II network driver specification<br /> by [mailto:olsen@amiga.com?subject=SANA-IIR4%20proposal Olaf Barthel] === === (Last updated 02-Mar-2003) ==..."