From nobody Sat Mar 09 03:17:56 2024 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 4Ts7XK3KjVz5ChXy for ; Sat, 9 Mar 2024 03:18:09 +0000 (UTC) (envelope-from pprocacci@gmail.com) Received: from mail-lj1-x22b.google.com (mail-lj1-x22b.google.com [IPv6:2a00:1450:4864:20::22b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Ts7XK2Zvzz4gBM for ; Sat, 9 Mar 2024 03:18:09 +0000 (UTC) (envelope-from pprocacci@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-lj1-x22b.google.com with SMTP id 38308e7fff4ca-2d2fad80eacso16713841fa.2 for ; Fri, 08 Mar 2024 19:18:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1709954287; x=1710559087; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=sM/Fdm6d8ca/Dn5i94C7n0Ae8LJhjD5RKF3a0l7+rBk=; b=Npxs38JZbXaUEBGdRcr4dJMsObVz+Y2DUPYguDJu9uM+nEV4vTfrkL+R9lwQwAcXpo KRtPQ7L5jFvYuFAC5IX+ZoxmTcauc1Zhn5FceqVpp0jBRTgPqaBdbKSpftu4TVWL/9Tp X7NRr5AanyO9iKEV7mfrXEp9k8Tbd9DKfZiS/CXEiurHHPktgPBHgh/5uvqNXaB6Oyf4 yDOzP1+yBdsRuWJX0oaim8uZbLZmB7GwyLIR7lj3Er3Z6jLhRDI1Iipt1grGOneoORK4 SNWz5jvBq6VDgKmeJb+XOLnAcTmKPEjpOPpbITzb7FOIsAnr/9Eq4ZHrHRhXPx7kgLD6 ZZjQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709954287; x=1710559087; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=sM/Fdm6d8ca/Dn5i94C7n0Ae8LJhjD5RKF3a0l7+rBk=; b=hWz/JgFae7NGM30ox6aEo7wUa+wni9oH5jb8QjsZohtPDQEwayWpyuHA2aMxHVOhGy jctu0hecWX1iB/XCPf1KAZEGVhEuZcQSHsSJalRcsEumW+OvmKv8PdvgxCjlqcMFK8m2 TfQSuHN0G0irmN0kE1r9DyP3y6OuSLS/Y+URUBxfq4UJLpulNI+V04s/wTX2aWnn1HJI 11aqmYhe7L1xiP6uyLARQ0/u6rtIWi7/94QnoDn5JhxdKcD7HNb6QHv9HS7xeNLvLK0H QYhqiBaYWAbdz9+9GM1A7gM1AaBPEP7bDTgKI8FriRogjp/aLTfnJAQMnteYuuq8OvqK NDAw== X-Gm-Message-State: AOJu0YwlB/tvS/619+LwfDoVmiEJ0cnSFjNkGDwzu3KmwWvcVdrRi8K9 QN8jnj7LulHTYGr0flY0Z5FwgZx0b1eoHjBdRZH/IcD0za89cLZBdbty/tBBMHZu5sg+MgJHwc/ /4Bg+rvlJwr/nXE5IUK5kUdIiZg== X-Google-Smtp-Source: AGHT+IFy4Pe1G2quHVBR5rtagelK126hhnX9/hvRVRuJ4TXYQRN/WO89i5AmqMkLvkr1HrvCAU45wpNzl+QRqs/DLak= X-Received: by 2002:a2e:b907:0:b0:2d4:2250:1da with SMTP id b7-20020a2eb907000000b002d4225001damr481569ljb.30.1709954287086; Fri, 08 Mar 2024 19:18:07 -0800 (PST) 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 References: In-Reply-To: From: Paul Procacci Date: Fri, 8 Mar 2024 22:17:56 -0500 Message-ID: Subject: Re: ping acting strangely on 13.3 To: Andrea Venturoli Cc: freebsd-questions@freebsd.org Content-Type: multipart/alternative; boundary="000000000000dd3583061331c1f8" X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Queue-Id: 4Ts7XK2Zvzz4gBM --000000000000dd3583061331c1f8 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Mar 8, 2024 at 9:54=E2=80=AFPM Andrea Venturoli wr= ote: > Hello. > > On some machines I completely removed IPv6 by commenting "options INET6" > in the kernel. > I've recently upgraded one of these from 13.2 to 13.3 and now ping is > behaving differently from before. > > > % host www.google.it > > www.google.it has address 216.58.204.227 > > www.google.it has IPv6 address 2a00:1450:4002:415::2003 > > % ping www.google.it > > ping: socket ssend: Address family not supported by protocol family > > % ping -4 www.google.it > > PING www.google.it (216.58.204.227): 56 data bytes > > 64 bytes from 216.58.204.227: icmp_seq=3D0 ttl=3D117 time=3D13.422 ms > > 64 bytes from 216.58.204.227: icmp_seq=3D1 ttl=3D117 time=3D15.746 ms > > ^C > > On 13.2 and 14.0 (and every previous version I ever used), the first > ping ("ping www.google.it") behaves exactly as if "-4" was given. > > I din't read anything about this change in release notes (unless I'm > failing to understand something) and the ping man pages are identical. > > Is this some regression? Do I need to set something? > Are others seeing this? > Shall I report this as a bug? > > bye & Thanks > av. > > This is less likely a change to `ping` and more likely a change to the resolver. From ping(8): "When invoked with a hostname, the version to which the target is resolved first is used." If you haven't already, set ipv6_activate_all_interfaces=3D"NO" I'm not entirely sure whether or not this affects it, but it makes sense that if there's no transport for ipv6 available, it shouldn't provide you with an answer that requires ipv6. ~Paul --=20 __________________ :(){ :|:& };: --000000000000dd3583061331c1f8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Fri, Mar = 8, 2024 at 9:54=E2=80=AFPM Andrea Venturoli <ml@netfence.it> wrote:
Hello.

On some machines I completely removed IPv6 by commenting "options INET= 6"
in the kernel.
I've recently upgraded one of these from 13.2 to 13.3 and now ping is <= br> behaving differently from before.

> % host www.google.it
> = www.google.it has address 216.58.204.227
> = www.google.it has IPv6 address 2a00:1450:4002:415::2003
> % ping www.google.it
> ping: socket ssend: Address family not supported by protocol family > % ping -4 www.google.it
> PING www.google.it (216.58.204.227): 56 data bytes
> 64 bytes from 216.58.204.227: icmp_seq=3D0 ttl=3D117 time=3D13.422 ms<= br> > 64 bytes from 216.58.204.227: icmp_seq=3D1 ttl=3D117 time=3D15.746 ms<= br> > ^C

On 13.2 and 14.0 (and every previous version I ever used), the first
ping ("ping www.google.it") behaves exactly as if "-4" w= as given.

I din't read anything about this change in release notes (unless I'= m
failing to understand something) and the ping man pages are identical.

Is this some regression? Do I need to set something?
Are others seeing this?
Shall I report this as a bug?

=C2=A0 bye & Thanks
=C2=A0 =C2=A0 =C2=A0 =C2=A0 av.


This is less likely a change to = `ping` and more likely a change to the resolver.
From ping(8):
=
"When invoked with a hostname, the version to which the target is = resolved
=C2=A0 =C2=A0 =C2=A0first is used."

If you ha= ven't already, set ipv6_activate_all_interfaces=3D"NO"
I'm not entirely sure whether or not this affects it, but it mak= es sense that if there's no transport for ipv6 available, it shouldn= 9;t provide you with an answer that requires ipv6.

~Paul<= /div>

--
__________________

:(){ :|:& };:
<= /div>
--000000000000dd3583061331c1f8--