Date: Tue, 2 Jul 2024 10:40:20 +0200 (CEST) From: Ronald Klop <ronald-lists@klop.ws> To: Craig Leres <leres@freebsd.org> Cc: freebsd-stable@freebsd.org, Michael Proto <mike@jellydonut.org> Subject: Re: FreeBSD 14.x localhost source address Message-ID: <1298289263.3566.1719909620825@localhost> In-Reply-To: <7005d0ed-70ea-4c70-ac61-2a12e023cdd7@freebsd.org> References: <086405e2-8fc2-4463-b8bb-d6c652745ae1@freebsd.org> <CAGAnWo2LbT6mGdgo7u5CA6d%2BQE8bX9nJagaHMn5p=3DBsC0fOg@mail.gmail.com> <7005d0ed-70ea-4c70-ac61-2a12e023cdd7@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
------=_Part_3565_798228293.1719909620800 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Van: Craig Leres <leres@freebsd.org> Datum: dinsdag, 2 juli 2024 01:04 Aan: Michael Proto <mike@jellydonut.org> CC: freebsd-stable@freebsd.org Onderwerp: Re: FreeBSD 14.x localhost source address > > 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 > > > > Hi, Could it be that this mail thread also applies to your situation? https://lists.freebsd.org/archives/freebsd-current/2024-June/006047.html It has a follow-up about a fix in https://lists.freebsd.org/archives/freebsd-current/2024-June/006075.html. Regards, Ronald. ------=_Part_3565_798228293.1719909620800 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit <html><head></head><body><br> <p><strong>Van:</strong> Craig Leres <leres@freebsd.org><br> <strong>Datum:</strong> dinsdag, 2 juli 2024 01:04<br> <strong>Aan:</strong> Michael Proto <mike@jellydonut.org><br> <strong>CC:</strong> freebsd-stable@freebsd.org<br> <strong>Onderwerp:</strong> Re: FreeBSD 14.x localhost source address</p> <blockquote style="padding-right: 0px; padding-left: 5px; margin-left: 5px; border-left: #000000 2px solid; margin-right: 0px"> <div class="MessageRFC822Viewer" id="P"> <div class="TextPlainViewer" id="P.P">On 7/1/24 15:53, Michael Proto wrote:<br> > What netmask are you using for 127.0.0.2? I'd treat it as I would an<br> > IP alias (only on localhost) with a /32 netmask, should keep it<br> > isolated. Just tried it myself on a test box and iperf works as<br> > expected, using 127.0.0.1 as the source when connecting.<br> <br> 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.<br> <br> 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.<br> <br> I guess the overlap between 127.0.0.0/8 and 127.0.0.0/24 was problematic.<br> <br> Craig<br> </div> <hr></div> </blockquote> <br> <br> Hi,<br> <br> Could it be that this mail thread also applies to your situation?<br> <a href="https://lists.freebsd.org/archives/freebsd-current/2024-June/006047.html">https://lists.freebsd.org/archives/freebsd-current/2024-June/006047.html</a><br>; <br> It has a follow-up about a fix in <a href="https://lists.freebsd.org/archives/freebsd-current/2024-June/006075.html">https://lists.freebsd.org/archives/freebsd-current/2024-June/006075.html</a>.<br>; <br> Regards,<br> Ronald.<br> </body></html> ------=_Part_3565_798228293.1719909620800--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1298289263.3566.1719909620825>