structure sockaddr

[zio_mangrovia]

What is reason to put data (ip, port) into structure of sockaddr to use connect primitive or bind ?
It could to be easier to pass as single parameters (ip or ports) instead to pass the structure ?
Why It's implemented in this way ?

[salem_c]

https://www.man7.org/linux/man-pages/man2/bind.2.html
There are many different kinds of sockets. sockaddr is just the base type (think C++ base class).

sockaddr_in https://www.man7.org/linux/man-pages/man7/ip.7.html
sockaddr_in6 https://www.man7.org/linux/man-pages/man7/ipv6.7.html
sockaddr_un https://www.man7.org/linux/man-pages/man7/unix.7.html
and so on.

So changing from ipv4 to ipv6 say just involves changing/initialising instances of sockaddr_in to be sockaddr_in6.

[zio_mangrovia]

https://www.man7.org/linux/man-pages/man2/bind.2.html
There are many different kinds of sockets. sockaddr is just the base type (think C++ base class).

sockaddr_in

I'm referencing to this one sockaddr_in

Why it has been implemented a structure to contain af_family, port and ip address ?

[salem_c]

> Why it has been implemented a structure to contain af_family, port and ip address ?
Because those are things you need to know to create an IP socket.