From nobody Thu Nov 28 19:02:40 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 4Xzm0Y1F82z5f76d for ; Thu, 28 Nov 2024 19:02:53 +0000 (UTC) (envelope-from briansho@gmail.com) Received: from mail-ot1-x330.google.com (mail-ot1-x330.google.com [IPv6:2607:f8b0:4864:20::330]) (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 "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Xzm0X6ccZz4kBv for ; Thu, 28 Nov 2024 19:02:52 +0000 (UTC) (envelope-from briansho@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ot1-x330.google.com with SMTP id 46e09a7af769-71d47201b3fso464796a34.2 for ; Thu, 28 Nov 2024 11:02:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1732820571; x=1733425371; 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=ila+ww7OR/JGDy+MhD+549psgN4kBC7OX0gNXCFiSS4=; b=khpemeSI8+VD41skksqMume34QPE7+01veP2d4XpI8IkvDMdUsCmVo1UBBWFpq+dzs V9g8I9bpzJA8rREcmzTKs9MNzDAAPf4gXhpVLczbuzsdREK4xDaoptVMW2bhmBrci+4v tKHXF/8K/yKb8X7o8pewl2/MNjRSVuBqlB94g5FSEnstcZR4bDR9jLO7ux6sRXZ35+fm lVyjvCAr0Awu7pE/dTIw1hOhVP6gaUqGcny2f+Epy5kdX63EiSy2lr+I5JaWXw4L7EQj gDb7mH7eRD7rurjegmFIrI6hQLYwH7ZcK5ujf6EwZjVeXZZC85PZWZ1y2VGIketIjCZC YC/g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1732820571; x=1733425371; 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=ila+ww7OR/JGDy+MhD+549psgN4kBC7OX0gNXCFiSS4=; b=gOpCuQa3xuzr0y2yOfSgkFkoJhScQdzDkF+bz6PlvMHUEciMGCpiAH51S4OPPYObP9 n146KVcfrB4csuY4Ymvx8Xyh7FhV/hVETYj/xHeCGt7ZcimTjAWB0sPR5OfIIi8tBkxf nmxYeNr1Pj64WRiTMqDx3+/g97jS9Ujs7g+eTCpp/eVTcn8WL3mVIkYwVpi+B3yNThxS Pk14WJqQl85orPDgErwZlNYmEw1TW8KFZyg6SS6YLdipdrkr096oSX4a2MxcGmwhnGqc cV+mZfAtfC91DPeAvpMuo7sgCUtZAnfYC0OGdDWYqxjUT4+UAzuDwKbgUUZCPmtkJqma ollQ== X-Gm-Message-State: AOJu0Yw0nCljJaYttPz+91FffjDby32n6HRFZ9LcSvS/gK29AD3t77hc oDMIyzMIbalO2N0qzz45CWMVj7k/v4SxN6ULy90JWk9kRv4AakAgrOZgTEPiTL5+E0Nf6Rl9h+A Fpo/ZKu9OinwgL+qcM3zPtVl5VKnNFQ/Qzw== X-Gm-Gg: ASbGncs66KbqanzJ62HuK9N/SkA9ogl4Ett38DoTCriT81zC5ZL3NI3D2eeDsld1h7Q 5XEqq7vKaLezMDp7O9IBiyI5cppBTf2K2XQ+O2oRE8Wfs5EaTb0JSViu6SdGyhLVG X-Google-Smtp-Source: AGHT+IGsNwN9mr3xJENS6q+XuxDt8VbCkkUF14qz463qFZDsfuWX8kR7KLaBa4B6gdLirSaM6mVi7+leUUkcKk8aANg= X-Received: by 2002:a05:6808:448f:b0:3e5:f7c0:b8f1 with SMTP id 5614622812f47-3ea6dd4974dmr9509714b6e.32.1732820571521; Thu, 28 Nov 2024 11:02:51 -0800 (PST) List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.org MIME-Version: 1.0 References: <86jzcn5lac.fsf@beasty.markusgraf.net> In-Reply-To: <86jzcn5lac.fsf@beasty.markusgraf.net> From: Brian S Date: Thu, 28 Nov 2024 20:02:40 +0100 Message-ID: Subject: Re: sockstat local address *:* To: Markus Graf Cc: FreeBSD questions Content-Type: multipart/alternative; boundary="000000000000a009f50627fdba3d" 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:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4Xzm0X6ccZz4kBv X-Spamd-Bar: ---- --000000000000a009f50627fdba3d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I believe it refers to ANY IPv6 addres. The distinction between an unknown/unspecified address is vague in IPv4, so we use 0.0.0.0/0 to represent any host on the network, but in IPv6 there is a subtle difference. For the most part however, people use :: to represent a contiguous string of 0's. In an IPv6 address, any sequence of contiguous zeros can be replaced with := : so: - 0.0.0.0/0 =3D> 0000:0000:0000:0000:0000:0000:0000:0000 =3D> :: =3D> *:= * - fe80:0000:0000:0000:2000:0aff:fea7:0f7c =3D> fe80::2000:0aff:fea7:0f7c The representation using wildcards however allows a finer control of address patterns. For instance, :: would not match fe80::2000:0aff:fea7:0f7= c, but *:* will. This difference isn't really meaningful to any device that isn't performing routing, but when it comes time to select optimal routes to aggregated address spaces, the wildcard notation allows more flexible selection of destination networks. From https://superuser.com/questions/1095793/do-0-0-0-00-and-represent-the-same-= thing?noredirect=3D1&lq=3D1 On Thu, Nov 28, 2024 at 6:19=E2=80=AFPM Markus Graf wrote: > > Hi, > > what does the *:* in the LOCAL ADDRESS column stand for? > > sockstat -4l > > USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN > ADDRESS > markus soffice.bi 84571 9 tcp4 *:* *:* > root wpa_suppli 49000 3 udp4 *:* *:* > other lines deleted > > This can't mean listening on all ports on all interfaces, can it? > > The system runs just fine. > > The question is a bit hard to goole with the two asterisks :( > > Best regards > > Markus > > --000000000000a009f50627fdba3d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I believe it refers to ANY IPv6 addres.=C2=A0

The distinction between an unknown/unspecified address is vague in=20 IPv4, so we use 0.0.0.0/0 to represent any= host on the network, but in=20 IPv6 there is a subtle difference.

For the most part however, people use :: to represent a con= tiguous string of 0's.

In an IPv6 address, any sequence of contiguous zeros can be replaced wit= h :: so:

  • 0.0.0.0/0 =3D> 000= 0:0000:0000:0000:0000:0000:0000:0000 =3D> :: =3D> = *:*
  • fe80:0000:0000:0000:2000:0aff:fea7:0f7c =3D= > fe80::2000:0aff:fea7:0f7c

The representation using wildcards however allows a finer control of add= ress patterns. For instance, :: would not match fe80::20= 00:0aff:fea7:0f7c, but *:* will.

This difference isn't really meaningful to any device that isn't= =20 performing routing, but when it comes time to select optimal routes to=20 aggregated address spaces, the wildcard notation allows more flexible=20 selection of destination networks.


= On Thu, Nov 28, 2024 at 6:19=E2=80=AFPM Markus Graf <markus.graf@markusgraf.net> wrote:

Hi,

what does the *:* in the LOCAL ADDRESS column stand for?

sockstat -4l

USER=C2=A0 =C2=A0 =C2=A0COMMAND=C2=A0 =C2=A0 PID=C2=A0 =C2=A0FD=C2=A0 PROTO= =C2=A0 LOCAL ADDRESS=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0FOREIGN
ADDRESS
markus=C2=A0 =C2=A0soffice.bi 84571 9=C2=A0 =C2=A0tcp4=C2=A0 =C2=A0*:*=C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0*:*
root=C2=A0 =C2=A0 =C2=A0wpa_suppli 49000 3=C2=A0 =C2=A0udp4=C2=A0 =C2=A0*:*= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0*:* other lines deleted

This can't mean listening on all ports on all interfaces, can it?

The system runs just fine.

The question is a bit hard to goole with the two asterisks :(

Best regards

Markus

--000000000000a009f50627fdba3d--