On 7/15/19 12:45 PM, Claudio Jeker wrote:
On Mon, Jul 15, 2019 at 11:08:53AM +0300, Vadim Penzin wrote:
On 7/15/19 10:28 AM, Claudio Jeker wrote:
On Sun, Jul 14, 2019 at 01:15:40PM +0300, Vadim Penzin wrote:
Since `sa_len' describes the size of a `sockaddr' (or one of its
derivatives) /in
On Mon, Jul 15, 2019 at 11:08:53AM +0300, Vadim Penzin wrote:
>
>
> On 7/15/19 10:28 AM, Claudio Jeker wrote:
> > On Sun, Jul 14, 2019 at 01:15:40PM +0300, Vadim Penzin wrote:
> > > > > Since `sa_len' describes the size of a `sockaddr' (or one of its
> > > > > derivatives) /including/ `sa_len' (m
On 7/15/19 10:28 AM, Claudio Jeker wrote:
On Sun, Jul 14, 2019 at 01:15:40PM +0300, Vadim Penzin wrote:
Since `sa_len' describes the size of a `sockaddr' (or one of its
derivatives) /including/ `sa_len' (maybe I am wrong, but this is my
interpretation of the comment `total length' that appear
On Sun, Jul 14, 2019 at 01:15:40PM +0300, Vadim Penzin wrote:
> > > Since `sa_len' describes the size of a `sockaddr' (or one of its
> > > derivatives) /including/ `sa_len' (maybe I am wrong, but this is my
> > > interpretation of the comment `total length' that appears near the
> > > definition of
Since `sa_len' describes the size of a `sockaddr' (or one of its
derivatives) /including/ `sa_len' (maybe I am wrong, but this is my
interpretation of the comment `total length' that appears near the
definition of `struct sockaddr' in ), `sa_len' just
cannot be zero.
Yes, it can not be zero.
Well, the manual shall tell the truth, whatever it is:
Messages are formed by a header followed by a small number of
sockaddr structures of variable length. The size of every
sockaddr structure can be computed by rounding the value of the
`sa_len' field of the current structure up
On Fri, Apr 26, 2019 at 01:55:52PM +0300, Vadim Penzin wrote:
> Greetings,
>
>
> 1. The manual of route(4) explains the structure of its messages thus:
>
> `Messages are formed by a header followed by a small number of
> sockaddr structures (which are variable length), interpreted by
>
Greetings,
1. The manual of route(4) explains the structure of its messages thus:
`Messages are formed by a header followed by a small number of
sockaddr structures (which are variable length), interpreted by
position, and delimited by the length entry in the sockaddr.'
(That phras
