From nobody Thu Feb 16 22:56:17 2023 X-Original-To: freebsd-questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4PHr0V36QYz3qTN4 for ; Thu, 16 Feb 2023 22:56:26 +0000 (UTC) (envelope-from possessor.assizer305@aceecat.org) Received: from beesty.loosely.org (beesty.loosely.org [IPv6:2600:3c01:e000:4c0::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4PHr0T5Ws3z4Jn8 for ; Thu, 16 Feb 2023 22:56:25 +0000 (UTC) (envelope-from possessor.assizer305@aceecat.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=aceecat.org header.s=rsa header.b=jInlWni5; spf=pass (mx1.freebsd.org: domain of possessor.assizer305@aceecat.org designates 2600:3c01:e000:4c0::2 as permitted sender) smtp.mailfrom=possessor.assizer305@aceecat.org; dmarc=none DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=aceecat.org ; s=rsa; h=Sender:In-Reply-To:Content-Type:MIME-Version:References:Message-ID :Subject:To:From:Date:Reply-To:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=W5IZTbcAqprtyTyVSa1u0AwxFzGdNUHp9qq0tVqAwAM=; b=jInlWni5y6kOpMd+mZUg/MvSPN YrMmz7kiXCnvjo1DLdWw7r/gt4wzZDXhoirRAA39ItXDtjNqlZkvtOaaShhsQYklH+7JIrC4IAjW9 FgXWtnzcL2jXzA4OUKSsim4MxNnnWFjQuIrgzHbZhElT4D3IQ7a+ZgUIs51IBD2z/9w70WVXxWRfz D9mZg/YI99KML9rFLP90FL24fJsygJ5HXZ3nJgFQOYQ44KdtH73UewmcJ0hjWM3ywcN45AxTo9F7Y /4JZ4DMZlNFIb7irY792R5rk6oEDf1zDsLRSdWNPMVG5hM2weXPEEfIsHRYaYlbjUYDcntLXIguDZ Uclg+v3Q==; Received: from [::1] (helo=beesty) by beesty.loosely.org with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.96-20-303f59ccb) (envelope-from ) id 1pSnAn-000KL9-0y for freebsd-questions@freebsd.org; Thu, 16 Feb 2023 14:56:17 -0800 Date: Thu, 16 Feb 2023 14:56:17 -0800 From: Ian Zimmerman To: freebsd-questions@freebsd.org Subject: Re: Source IP selection Message-ID: <20230216225617.mjleld4gaopwj32w@beesty.loosely.org> Mail-Followup-To: freebsd-questions@freebsd.org References: <20230216221234.7C6999986157@ary.qy> List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230216221234.7C6999986157@ary.qy> Sender: itz@aceecat.org X-Spamd-Result: default: False [-3.49 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_LONG(-0.99)[-0.994]; R_SPF_ALLOW(-0.20)[+mx]; R_DKIM_ALLOW(-0.20)[aceecat.org:s=rsa]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-questions@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; DKIM_TRACE(0.00)[aceecat.org:+]; ASN(0.00)[asn:63949, ipnet:2600:3c01::/32, country:SG]; RCVD_VIA_SMTP_AUTH(0.00)[]; DMARC_NA(0.00)[aceecat.org]; RCVD_COUNT_TWO(0.00)[2]; ARC_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; FROM_HAS_DN(0.00)[]; TO_DN_NONE(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4PHr0T5Ws3z4Jn8 X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N On Thu, Feb 16, 2023 at 05:12:34PM -0500, John Levine wrote: > It appears that Paul Mather said: > >> My VPS provider (Linode) gave me a secondary address so my two nodes > >> can talk to each other without accruing charges. Note that: > >> > >> - it really is an alias on the same interface, *not* a VLAN > >> > >> - it is not a publicly routable address (192.168.) > > While the advice about setting addresses in unbound was good, my > advice would be "don't do that." Depending on IPs on the same > interface to be routed differently will just cause endless pain. > > Linode says you can set up a VLAN for free. Why not do that, > and put the shortcut on a separate interface? Then everything > should work without any funny configuration. That was exactly my first reaction too. Then I read a little bit further, learning that VLAN is not (yet?) available in Fremont, where I'm hosted. Thanks for the replies, everyone, I have a picture now. (Btw Linode gets away with this because on Linux, which is the only kernel they officially support, routes have an associated source address - so no endless pain LOL.) -- Ian