From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-0.0 required=5.0 tests=T_SCC_BODY_TEXT_LINE
	autolearn=ham autolearn_force=no version=3.4.4
Received: (qmail 15960 invoked from network); 10 Jun 2022 15:17:03 -0000
Received: from 9front.inri.net (168.235.81.73)
  by inbox.vuxu.org with ESMTPUTF8; 10 Jun 2022 15:17:03 -0000
Received: from odoacer.turtle-trading.net ([93.241.193.16]) by 9front; Fri Jun 10 11:14:57 -0400 2022
Received: from zenobia.turtle-trading.net ([192.168.2.111])
	by odoacer.turtle-trading.net with esmtp (Exim 4.80)
	(envelope-from <benny@turtle-trading.net>)
	id 1nzgLX-0007hM-85; Fri, 10 Jun 2022 17:14:47 +0200
Received: from benny by zenobia.turtle-trading.net with local (Exim 4.94.2)
	(envelope-from <benny@turtle-trading.net>)
	id 1nzgLX-000dv4-04; Fri, 10 Jun 2022 17:14:47 +0200
From: Benjamin Riefenstahl <b.riefenstahl@turtle-trading.net>
To: ori@eigenstate.org
Cc: 9front@9front.org
References: <4E8DA25EACF13E3FFE406FE6B5FB9375@eigenstate.org>
	<87bkwvydi2.fsf@turtle-trading.net>
Date: Fri, 10 Jun 2022 17:14:46 +0200
In-Reply-To: <87bkwvydi2.fsf@turtle-trading.net> (Benjamin Riefenstahl's
	message of "Wed, 20 Apr 2022 17:35:01 +0200")
Message-ID: <87bkv01rfd.fsf@turtle-trading.net>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.1.50 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: optimized secure template realtime grid 
Subject: Re: [9front] ape/bsd: Enable setting the local address with bind
Reply-To: 9front@9front.org
Precedence: bulk

Hi Ori,

Benjamin Riefenstahl writes:
> I often take my time myself ;-)

Again this has taken some time, sorry. 

> I will have to create some test cases to see what works and what
> doesn't.

That's what I have done now, see
<https://git.sr.ht/~cc_benny/test-socket/tree>.

I append the results, a log from Linux as a reference, one with the
current 9front (9front-front.log) and one with my patch
(9front-patch.log).

Next for me is refining the patch.  

> Ori writes:
>> And I see no specification that describes what should be done with
>> negative ports in the sockets world, so I can only assume that this is
>> a bug.
>
> I/we should probably just make negative ports an error. 

Turns out negative ports do not occur with BSD sockets because the
numbers get filtered through 'htons' which returns 'unsigned short',
naturally.

I will drop considerations of negative ports in my patch.

Benjamin Riefenstahl writes:
>>> The documentation in the man page ip(3) for the control commands
>>> "bind" and "announce" does not mention the local address, should that
>>> be fixed, too?

I will include that in my next version. 

Thanks, benny