its) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: leres) by smtp.freebsd.org (Postfix) with ESMTPSA id 4WChT43bWVzYds; Mon, 1 Jul 2024 23:04:56 +0000 (UTC) (envelope-from leres@freebsd.org) Message-ID: <7005d0ed-70ea-4c70-ac61-2a12e023cdd7@freebsd.org> Date: Mon, 1 Jul 2024 16:04:55 -0700 List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: FreeBSD 14.x localhost source address To: Michael Proto Cc: freebsd-stable@freebsd.org References: <086405e2-8fc2-4463-b8bb-d6c652745ae1@freebsd.org> From: Craig Leres Content-Language: en-US In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 7/1/24 15:53, Michael Proto wrote: > What netmask are you using for 127.0.0.2? I'd treat it as I would an > IP alias (only on localhost) with a /32 netmask, should keep it > isolated. Just tried it myself on a test box and iperf works as > expected, using 127.0.0.1 as the source when connecting. I was just looking at that and I used 127.0.0.2 without an explicit mask and the system picked /24. I'm not sure why I did it that way but it's been awhile. I just got rid of lo2 and made 127.0.0.2/32 an alias on lo0 and it seems to work better all around. I guess the overlap between 127.0.0.0/8 and 127.0.0.0/24 was problematic. Craig