From nobody Sun Feb 13 10:51:38 2022 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 67A291949670 for ; Sun, 13 Feb 2022 10:51:51 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: from mail.evolve.de (mail.evolve.de [213.239.217.29]) (using TLSv1.3 with cipher TLS_CHACHA20_POLY1305_SHA256 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA512 client-signature ECDSA (P-384) client-digest SHA384) (Client CN "mail.evolve.de", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4JxPLG0rjBz4lS2; Sun, 13 Feb 2022 10:51:50 +0000 (UTC) (envelope-from grembo@freebsd.org) Received: by mail.evolve.de (OpenSMTPD) with ESMTP id 9a97604a; Sun, 13 Feb 2022 10:51:42 +0000 (UTC) Received: by mail.evolve.de (OpenSMTPD) with ESMTPSA id fb0d25b0 (TLSv1.3:AEAD-CHACHA20-POLY1305-SHA256:256:NO); Sun, 13 Feb 2022 10:51:39 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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 (1.0) Subject: Re: Some strangeness with CARP From: Michael Gmelin In-Reply-To: <2d5c3b3c-1ebd-3fd1-f36b-00b09cc6b87e@netfence.it> Date: Sun, 13 Feb 2022 11:51:38 +0100 Cc: freebsd-net@freebsd.org Message-Id: <5FC5E885-EE5D-4186-949E-F19F270CBE2E@freebsd.org> References: <2d5c3b3c-1ebd-3fd1-f36b-00b09cc6b87e@netfence.it> To: Andrea Venturoli X-Mailer: iPhone Mail (19D52) X-Rspamd-Queue-Id: 4JxPLG0rjBz4lS2 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=softfail (mx1.freebsd.org: 213.239.217.29 is neither permitted nor denied by domain of grembo@freebsd.org) smtp.mailfrom=grembo@freebsd.org X-Spamd-Result: default: False [-0.44 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FREEFALL_USER(0.00)[grembo]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; MV_CASE(0.50)[]; NEURAL_HAM_LONG(-0.76)[-0.760]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[freebsd.org]; R_SPF_SOFTFAIL(0.00)[~all:c]; NEURAL_SPAM_MEDIUM(0.81)[0.812]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.89)[-0.894]; RCPT_COUNT_TWO(0.00)[2]; MLMMJ_DEST(0.00)[freebsd-net]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:24940, ipnet:213.239.192.0/18, country:DE]; RCVD_TLS_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-ThisMailContainsUnwantedMimeParts: N > On 13. Feb 2022, at 11:45, Andrea Venturoli wrote: >=20 > =EF=BB=BF >> On 2/12/22 13:38, Michael Gmelin wrote: >> Maybe the switch or something it=E2=80=99s connected to uses vrrp? >=20 > The switch has no options about VRRP, AFAICT (unless it can be called by a= different name) and I don't think any other device could use VRRP. >=20 According to their web site, some of their switches have support (don=E2=80=99= t know your model) under IP Application > VRRP > Configuration. Good luck getting to the bottom of this! Cheers Michael >=20 >=20 >=20 >=20 >> When using vhid 1, can you see any vrrp traffic using tcpdump >=20 > You mean "tcpdump vrrp"? > In that case I see CARP advertisements, as CARP is using the same protocol= number as VRRP. >=20 >=20 > bye & Thanks > av.