BSDSocket SocketBaseTagList()

[flype]

Hello Tony,

About this part here :
https://github.com/tonioni/WinUAE/bl...cket.cpp#L1460

Do you think it would be possible to implement some of the AmiTCP standard tags such as :

SBTM_GETREF(SBTC_GET_BYTES_SENT)
SBTM_GETREF(SBTC_GET_BYTES_RECEIVED)

So that such monitor tool could work also on UAE :
https://github.com/flype44/DockBot/b...Net/net.c#L215

[Toni Wilen]

Can be done but what does bytes sent and bytes received mean? Total count of bytes transferred using TCP and UDP sockets?

EDIT: and it would be nice to have some header file that tells value of those two defines.

[flype]

Yes, it's the total bytes sent/recv, copied in a 64bits quad, by reference, since last init of the stack.

It's, as far as i understand, a AmiTCP v4 specification.

It's described in the public RoadShow API by Olaf Barthel (bsdsocket.doc, and bsdsocket.h), freely downloadable, or here https://wiki.amigaos.net/amiga/autod...socket.doc.txt

Remark:
There are also other ways, by network 'interface' (if/when a system would have more than one NIC), or SANA methods.
Advantage of that one is it's global (sum of) to all interfaces, which probably fits good the concept of the UAE auto-embedded bsdsocket / Single-interface.

	SBTC_GET_BYTES_RECEIVED
	    Obtain the number of bytes received by the TCP/IP stack.
	    The parameter must be of type 'SBQUAD_T'. Note that the
	    data must be passed by reference.

	    Older version of "bsdsocket.library" may return a failure
	    code when querying this option.

	SBTC_GET_BYTES_SENT
	    Obtain the number of bytes sent by the TCP/IP stack.
	    The parameter must be of type 'SBQUAD_T'. Note that the
	    data must be passed by reference.

	    Older version of "bsdsocket.library" may return a failure
	    code when querying this option.

/* Query the number of bytes received so far. */
#define SBTC_GET_BYTES_RECEIVED 64

/* Query the number of bytes sent so far. */
#define SBTC_GET_BYTES_SENT 65

typedef struct
{
	ULONG sbq_High;
	ULONG sbq_Low;
} SBQUAD_T;

[Toni Wilen]

Done. Untested. winuae.7z updated.

Spec does not say what would happen if SBTM_GETVAL is attempted (UAE will ignore it).

[flype]

Ok just did some searchs since it's was not very clear to me from which Amiga TCP standard they belongs. Olaf could tell better.

Looking at those packages :
http://aminet.net/package/comm/tcp/MiamiSDK211
http://aminet.net/package/comm/tcp/AmiTCP-SDK-4.3
https://www.amigafuture.de/app.php/d...ils?df_id=3658 => Roadshow-SDK-1.5.lha

When browsing in the Miami and AmiTCP ones,
SocketBaseTagList() is there, but not those SENT/RECV BYTES tags (and others).

So actually it seems they _could_ be new from RoadShow.

That said, those are quite de facto a standard.

Well, given those facts, i dont know, you are free to decide if it makes sense to have some up-to-date similarities between the last bsdsocket.h specifications and the UAE one. Maybe this can be debated.

[flype]

Originally Posted by Toni Wilen

Done. Untested. winuae.7z updated.

Spec does not say what would happen if SBTM_GETVAL is attempted (UAE will ignore it).

Oh, you were fast

Need i test asap now.

[Toni Wilen]

It was too trivial (note that it does not mean it is correct!)

Any other missing bsdsocket features?

[flype]

Spec does not say what would happen if SBTM_GETVAL is attempted (UAE will ignore it).

Which is correct behaviour imho, since it's about 64bits, it would not fit.

Any other missing bsdsocket features?

Ouch Probably a lot since Olaf pushed a huge number of new specs/features in his stack.

If i had myself to choose, i would focus on the 'monitoring' and 'hooks' ones, which may brings new debugging levels for developers (which the strong force of UAE over hw when it comes to help people in development), and monitor tools for end users.

/* Whether or not the monitoring API is supported. */
#define SBTC_HAVE_MONITORING_API 50

	SBTC_HAVE_MONITORING_API
	    This tag is an extension to the AmiTCP V4 API and must be
	    used prior to calling any of the interface API functions,
	    such as AddNetMonitorHookTagList() and RemoveNetMonitorHook().
	    Since older "bsdsocket.library" implementations do not
	    process this tag you should be prepared to handle failure of
	    the query operation.

	    This tag will return TRUE if the monitoring API is supported,
	    and FALSE or failure otherwise.

Those ones would be too much pastings here, though.
Best is have a look at the API from Roadshow-SDK-1.5.lha

However, i'd probably better ask Olaf if he just agree / happy that this standard specs can be shared by others stacks.

[Toni Wilen]

Most importantly: it MUST be used in some existing software. I don't support features that can't be tested and no one uses.

[flype]

Yeah, you're right.

SampleNetSpeed for example, use them, and is a useful one.

And that DockBot module i'm working on.

Let's ask Olaf.
https://eab.abime.net/showpost.php?p...9&postcount=44

[flype]

Olaf is ok.

https://eab.abime.net/showpost.php?p...2&postcount=50

Will tell you how behave the beta.