From nobody Wed Dec 20 20:55:30 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 4SwQnX3G8tz55KmF for ; Wed, 20 Dec 2023 20:55:44 +0000 (UTC) (envelope-from DtxdF@disroot.org) Received: from layka.disroot.org (layka.disroot.org [178.21.23.139]) (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 4SwQnX0FhQz3RWM for ; Wed, 20 Dec 2023 20:55:43 +0000 (UTC) (envelope-from DtxdF@disroot.org) Authentication-Results: mx1.freebsd.org; none Received: from localhost (localhost [127.0.0.1]) by disroot.org (Postfix) with ESMTP id 39CC741929; Wed, 20 Dec 2023 21:55:36 +0100 (CET) X-Virus-Scanned: SPAM Filter at disroot.org Received: from layka.disroot.org ([127.0.0.1]) by localhost (disroot.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aU7tjYgNwy0B; Wed, 20 Dec 2023 21:55:34 +0100 (CET) Date: Wed, 20 Dec 2023 20:55:30 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=disroot.org; s=mail; t=1703105734; bh=1KmQn4u+zbCB33zfA1rLQJFtRalNSELi2592t+el1M8=; h=Date:From:To:Subject:In-Reply-To:References; b=ihPdKGLNKzoJRUpjO3mpRHzG1mZCP/sRoSBhCbgLJ/4zJk7TKX2ohZzneM1AWra5W qaPjtzI1UOEDEPFv3ESnO54kt1/L3iLYm4vnUZtRT8Xdz393G4Kz1S+FqP2VxUBN7U rQrLjQm1vOUIpgG4S1Yt7UkVxjMrrnKRbV2IRmbuzS4o97sn9l/G50k5fdPZftoysO +a1Ml8fmLsdjGKRoCwc9Xf2LFihcCTM3QT9AcDr8di1pws/fVtFni6D6BJeDuo2228 Onq+5yTLW+Ryah1gDxyUSEBHSDW3r1T+G3H6v/TRsnNr3RKJQBH5jyRM6OtT4FX6wo FA4yMoRE2U0aQ== From: DtxdF To: freebsd-net@freebsd.org, "Patrick M. Hausen" , FreeBSD Net Subject: Re: Display of bridge member interfaces cut short - bug or intention? In-Reply-To: References: Message-ID: <30AEAEFC-F46F-452F-BFE6-760A21811793@disroot.org> 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: multipart/alternative; boundary=----BH82CI3GV8E16QOSXQ5BCOFHPL9J36 Content-Transfer-Encoding: 7bit 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:50673, ipnet:178.21.23.0/24, country:NL] X-Spamd-Bar: ---- X-Rspamd-Queue-Id: 4SwQnX0FhQz3RWM ------BH82CI3GV8E16QOSXQ5BCOFHPL9J36 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Patrick, I have opened a bug in BugZilla [1] some time ago, it seems to be related= =2E Truncating the output can be a problem with automation tools that rely on = the output of ifconfig(8) to perform some tasks=2E [1] https://bugs=2Efreebsd=2Eorg/bugzilla/show_bug=2Ecgi?id=3D275491 El 20 de diciembre de 2023 5:04:36 p=2E m=2E UTC, "Patrick M=2E Hausen" escribi=C3=B3: >Hi all, > >as some probably know we provide web hosting services and we use jails fo= r that=2E > >On some particular host we have 255 vnet jails all of which are connected= to the >external interface of the host - renamed to "inet0" in our environment - = via >if_bridge(4) and all managed with iocage=2E > >root@ph003:~ # grep inet0 /iocage/jails/vpro*/config=2Ejson|wc -l > 255 > >Of these 251 also have a second epair interface connected to a private br= idge >named "priv1"=2E These are used for connections to the central database s= erver >which should not be exposed to the Internet=2E > >root@ph003:~ # grep priv1 /iocage/jails/vpro*/config=2Ejson | wc -l > 251 > >While looking for a different problem to my great suprise I found today t= hat >ifconfig truncates the list of member interfaces for both bridge instance= s=2E >And both to the same value of 102, although the member numbers are (albei= t slightly) >different: > >root@ph003:~ # ifconfig inet0|grep member:|wc -l > 102 >root@ph003:~ # ifconfig priv1 | grep member: | wc -l > 102 > >All 255 jails are connected to the external network and perfectly reachab= le from >the Internet=2E That's why I conclude that the display is wrong, not the = bridge >configuration=2E > >What's happening here? Is this intentional or shall I file a bug report? > >More importantly: either way is this only cosmetic or will we hit another= unexpected >limit of the number of interfaces that can be members of a bridge any tim= e soon? > >Kind regards, >Patrick >--=20 >punkt=2Ede GmbH >Patrick M=2E Hausen >infrastructure > >Sophienstr=2E 187 >76185 Karlsruhe > >Tel=2E +49 721 9109500 > >https://infrastructure=2Epunkt=2Ede >info@punkt=2Ede > >AG Mannheim 108285 >Gesch=C3=A4ftsf=C3=BChrer: Daniel Lienert, Fabian Stein > > ------BH82CI3GV8E16QOSXQ5BCOFHPL9J36 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Hi Patrick,

I have opened= a bug in BugZilla [1] some time ago, it seems to be related=2E

Trun= cating the output can be a problem with automation tools that rely on the o= utput of ifconfig(8) to perform some tasks=2E

[1] https://bugs=2Ef= reebsd=2Eorg/bugzilla/show_bug=2Ecgi?id=3D275491


El 20 de diciembre de 2023 5:04:36 p=2E= m=2E UTC, "Patrick M=2E Hausen" <hausen@punkt=2Ede> escribi=C3=B3:
Hi all,

as some probably kn=
ow we provide web hosting services and we use jails for that=2E

On s=
ome particular host we have 255 vnet jails all of which are connected to th=
e
external interface of the host - renamed to "inet0" in our environment=
 - via
if_bridge(4) and all managed with iocage=2E

root@ph003:~ #=
 grep inet0 /iocage/jails/vpro*/config=2Ejson|wc -l
     255

Of t=
hese 251 also have a second epair interface connected to a private bridgenamed "priv1"=2E These are used for connections to the central database s=
erver
which should not be exposed to the Internet=2E

root@ph003:~=
 # grep priv1 /iocage/jails/vpro*/config=2Ejson | wc -l
     251

=
While looking for a different problem to my great suprise I found today tha=
t
ifconfig truncates the list of member interfaces for both bridge insta=
nces=2E
And both to the same value of 102, although the member numbers a=
re (albeit slightly)
different:

root@ph003:~ # ifconfig inet0|gre=
p member:|wc -l
     102
root@ph003:~ # ifconfig priv1 | grep member:=
 | wc -l
     102

All 255 jails are connected to the external net=
work and perfectly reachable from
the Internet=2E That's why I conclude =
that the display is wrong, not the bridge
configuration=2E

What's=
 happening here? Is this intentional or shall I file a bug report?

M=
ore importantly: either way is this only cosmetic or will we hit another un=
expected
limit of the number of interfaces that can be members of a brid=
ge any time soon?

Kind regards,
Patrick
------BH82CI3GV8E16QOSXQ5BCOFHPL9J36--