RE: Question about getpeername() response

That should be the port. Looks like 55857.

struct sockaddr_in {
short sin_family; // e.g. AF_INET, AF_INET6
unsigned short sin_port; // e.g. htons(3490)
struct in_addr sin_addr; // see struct in_addr, below
char sin_zero[8]; // zero this if you want to
};

Kevin Bucknum
Senior Programmer Analyst
MEDDATA/MEDTRON
Tel: 985-893-2550

-----Original Message-----

From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf
Of James H. H. Lampert
Sent: Thursday, April 19, 2018 8:11 PM
To: Midrange Systems Technical Discussion
Subject: Question about getpeername() response

I'm working on adding some new troubleshooting code to a product, and
discovered the "getpeername()" call in the socket section of the

"unix-type

API" manual.

I've called it successfully, but I'm not entirely sure what I'm

getting

The first two bytes are 00 02; that seems to fit with the first two

bytes being

the "address family," and family 2 being Internet.

Then I get DA 31 C0 A8 01 0F. Now the internal IP address of the Mac I
connected from in the test is 192.168.1.15, which accounts for the C0

A8

01 0F,
but where is the DA 31 coming from? All of the docs talk about IPv6
addresses, but a complete 128-bit IPv6 address would take up more

bytes

than the sockaddr structure provides.

Does anybody here know enough about what's going on to shed any light

on

this?

--
JHHL
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD