From nobody Fri Jun 16 21:22:42 2023 X-Original-To: freebsd-net@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 4QjXFC17Mjz4fRk1 for ; Fri, 16 Jun 2023 21:22:55 +0000 (UTC) (envelope-from benoitc@enki-multimedia.eu) Received: from mail-4317.proton.ch (mail-4317.proton.ch [185.70.43.17]) (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-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "protonmail.com", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QjXF84H3sz3HJ0 for ; Fri, 16 Jun 2023 21:22:52 +0000 (UTC) (envelope-from benoitc@enki-multimedia.eu) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=enki-multimedia.eu header.s=protonmail3 header.b=aE1eMOtB; spf=pass (mx1.freebsd.org: domain of benoitc@enki-multimedia.eu designates 185.70.43.17 as permitted sender) smtp.mailfrom=benoitc@enki-multimedia.eu; dmarc=pass (policy=none) header.from=enki-multimedia.eu Date: Fri, 16 Jun 2023 21:22:42 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enki-multimedia.eu; s=protonmail3; t=1686950568; x=1687209768; bh=HRYR/2VnBguBkDG209k22Ive/CQ0/dPiylVQ+xUza/I=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=aE1eMOtBBrRO2neB9dhhACRShcSSSwCghOY/4Cna0tuHimqxNxvvl6kdqnkE7vZ24 91+YQyilchtnyXnpQp6lpD9D2/tvsfT/MWtkxtn0uOpJDtwqA8JmzCtnosrB8vF/m9 Qf68YGN+eypKYHsFBhfwIM2pwbP6dynwEGO9rvmT7DFuiTA29Xz0dn1VN/M2IhLGps xLjUiyUZuprzVr6YjZ+qLnwdtDA0YROoB2yKI9hvTiD+iLBK6fkrzV1/lxohWmlRMW gzsoSuUg7Gn/02lyRUKonFrUbocVb0BCS712Lb/Ju/kTcu54YYuBnN+8WQO75mQESB BmQWqlDgz8C4A== To: Stephane Rochoy From: Benoit Chesneau Cc: "freebsd-net@FreeBSD.org" Subject: Re: issue with bird next hop Message-ID: <5smmRN_p_A2v9n2oEBq2SFgHA31jZBnuXifkT6TIF9_jJTw1UGdHJhp0pKjKz7rOlnEY-dUGq-yV79nFK8gYFsYBmwt7z0AiZ1yyCkFGYF8=@enki-multimedia.eu> In-Reply-To: References: <86wn05hs9v.fsf@cthulhu.stephaner.labo.int> <1sE_u2MbHLU_bqWuLFwC5a0K8HeACVoCjWVPEDRZJ5KmD_Y-eG5OIVsWN9vBFV0Q6isWtc3-Z410kCBMRZhsFQUBNLoBYsIWGQ3kz0VaXXs=@enki-multimedia.eu> <86v8foj3rn.fsf@cthulhu.stephaner.labo.int> Feedback-ID: 9066678:user:proton List-Id: Networking and TCP/IP with FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-net List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spamd-Result: default: False [-3.99 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; NEURAL_HAM_SHORT(-0.99)[-0.992]; DMARC_POLICY_ALLOW(-0.50)[enki-multimedia.eu,none]; R_DKIM_ALLOW(-0.20)[enki-multimedia.eu:s=protonmail3]; R_SPF_ALLOW(-0.20)[+ip4:185.70.43.0/24]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-net@freebsd.org]; RCVD_COUNT_ZERO(0.00)[0]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; TO_DN_EQ_ADDR_SOME(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[enki-multimedia.eu:+]; ARC_NA(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; ASN(0.00)[asn:62371, ipnet:185.70.43.0/24, country:CH]; TO_DN_SOME(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4QjXF84H3sz3HJ0 X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N Is this behaviour expected? Can we replace the next hop to remove the need = of a nat? ------- Original Message ------- On Friday, June 16th, 2023 at 12:24, Benoit Chesneau wrote: > After doing more testing onf Freebsd 13.2 , bird 2.13: >=20 > When 1.1.1.1/31 and 1.1.1.2/31 are set on the vlan interface, bird correc= tly announce them as the next hop. >=20 > However when 1.1.1.1/32 and 1.1.1.2/32 are set on the loopback interface = of each instances then the local ip address of the vlan is used. >=20 > However when 1.1.1.1/31 and 1.1.1.2/31 are set on the loopback interface = of each instances then nothing happen. On each nodes 1.1.1.1/31 and 1.1.1.2= /31 resolve to the loopback interface instead of the remote node. >=20 >=20 > Is the behaviour expected ? >=20 >=20 >=20 > Beno=C3=AEt >=20 > ------- Original Message ------- > On Thursday, June 15th, 2023 at 14:48, Benoit Chesneau benoitc@enki-multi= media.eu wrote: >=20 >=20 >=20 > > I see. This may indeed be related... > >=20 > > The current route is learnt using OSPF. This is weird to not have it us= ing the source address configured in bird though:/ > >=20 > > Beno=C3=AEt Chesneau, Enki Multimedia > > =E2=80=94 > > t. +33608655490 > >=20 > > Sent with Proton Mail secure email. > >=20 > > ------- Original Message ------- > > On Thursday, June 15th, 2023 at 14:42, Stephane Rochoy stephane.rochoy@= stormshield.eu wrote: > >=20 > > > Benoit Chesneau benoitc@enki-multimedia.eu writes: > > >=20 > > > > Thanks for the hint. Unfortunately when I am setting it to /30 > > > > the machine stop to be advertised :/ Most probably because /30 > > > > will be routed locally? > > > >=20 > > > > Why would setting it to /30 fix the issue ? What does it solves > > > > when we do it? > > >=20 > > > I just reacted to the fact that, IMHO, `route get` is correct when > > > responding that 1.1.1.2 is not reachable via lo1. > > >=20 > > > Regards, > > > -- > > > St=C3=A9phane Rochoy > > > O: Stormshield