From nobody Tue Jun 04 07:36:38 2024 X-Original-To: freebsd-current@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 4Vtj9Y1Pgkz5MkDR for ; Tue, 04 Jun 2024 07:37:37 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Received: from mailgate.Leidinger.net (bastille.leidinger.net [89.238.82.207]) (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 ECDSA (P-256) client-digest SHA256) (Client CN "mailgate.leidinger.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Vtj9X5Mxyz4tkD for ; Tue, 4 Jun 2024 07:37:36 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Authentication-Results: mx1.freebsd.org; none List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leidinger.net; s=outgoing-alex; t=1717486651; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=/PHWuzOShPhwS6pfMn9tKKh4MBWTNYcQTYi0f710YzI=; b=LW7sJwdof3XeuOpWHTPms0ExbHakAgcctFn2Sfi3hSvqKloaM13TnPq2oY++giJcFWB3Os vJjAHBL71ivw735m1wOYMYdHaGiL3OmZjbo69qAWxDnnhDxIkKz/NfcigsodPavd3d1W3V LB2iF/g0d949t5fQhPO3ITG6ZtD6JdWpv7CRdfkTiEyKs/S9QR3fBpaTvkzLAF1YonGtI+ TVCiQcOqXYMl7pfxjIf1T9DJ+SNiltY6iXkodjvfxzMBQ9qSPzJU3G4UJ/2N7/Z7R1eyR0 IC7TkFP/OMgGUMc0RCQKbld7qr2DypxwA0pl6aHHcgi+O0LCWtdaQObuhIKSsw== Date: Tue, 04 Jun 2024 09:36:38 +0200 From: Alexander Leidinger To: FreeBSD User Cc: FreeBSD CURRENT Subject: Re: bridge: no traffic with vnet (epair) beyond bridge device In-Reply-To: <20240603210231.64889de0@thor.intern.walstatt.dynvpn.de> References: <20240603210231.64889de0@thor.intern.walstatt.dynvpn.de> Message-ID: <2433e25ebf6eae827bcd7912bbe27fbc@Leidinger.net> Organization: No organization, this is a private message. Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="=_2fd468e28f2a3da942f7a63a9ca99663"; micalg=pgp-sha256 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:34240, ipnet:89.238.64.0/18, country:DE] X-Rspamd-Queue-Id: 4Vtj9X5Mxyz4tkD This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --=_2fd468e28f2a3da942f7a63a9ca99663 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed Am 2024-06-03 21:02, schrieb FreeBSD User: > Hello, > > I'm running a dual socket NUMA CURRENT host (Fujitsu RX host) running > several jails. Jails are > attached to a bridge device (bridge1), the physical device on that > bridge is igb1 (i350 based > NIC). The bridge is created via host's rc scripts, adding and/or > deleting epair members of the > bridge is performed by the jail.conf script. > > I do not know how long the setup worked, but out of the blue, last week > after a longish > poudriere run after updating the host to most recent CURRENT (as of > today, latest update > kernel and world) and performing "etcupdate" on both the host and all > jails, traffic beyond > the bridge is not seen on the network! All jails can communicate with > each other. Traffic from > the host itself is routed via igb0 to network and back via igb1 onto > the bridge. > > I check all setups for net.link.bridge: > > net.link.bridge.ipfw: 0 > net.link.bridge.log_mac_flap: 1 > net.link.bridge.allow_llz_overlap: 0 > net.link.bridge.inherit_mac: 0 > net.link.bridge.log_stp: 0 > net.link.bridge.pfil_local_phys: 0 > net.link.bridge.pfil_member: 0 > net.link.bridge.ipfw_arp: 0 > net.link.bridge.pfil_bridge: 0 > net.link.bridge.pfil_onlyip: 0 > > I did not change anything (knowingly). > > I also have an oldish box running single socket processor, also driven > by the very same > CURRENT and similar, but not identical setup. The box is running very > well and the bridge is > working as expected. > > I was wondering if something in detail has changed in the handling of > jails, epair and > bridges. I followed the setup "after the book", nothing suspicious. "after the book" = the IP of the host itself is not on igb1 but on a different interface or on the bridge? Is there a firewall active on the box itself? Which one? What does wireshark / a traffic dump at the physical interface level tell compared to a traffic dump at the switch interface? Did you replace the cable / SFP / move to a different switch port as a test? I suggest to provide the output of ifconfig -a and netstat -rn (feel free to mangle the IPs, as long as the mangling is a consistent replacement and not a cut-off). Bye, Alexander. -- http://www.Leidinger.net Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_2fd468e28f2a3da942f7a63a9ca99663 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc; size=833 Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEER9UlYXp1PSd08nWXEg2wmwP42IYFAmZexBgACgkQEg2wmwP4 2IZjpg/+Nj8i23LkQ5zgkIU0tjOqIu7/D7NXY/MlVElWHWuZYPF+lJeD3oN1Gfsx uwSfxOEmnlvDG4Wny6hWEefzfrNdmtPpfZsfeavvaJEXqw78Gu4d7u5D5ymYNi8b GRNqUcFMDwVVMq5wPOOuXQifh2f6+2eOQ/rdL5HLPtPAdGyF/dWuI/ejbW7MxBRR Ad9/tTGN4hAbQqi+HbnEaqRxjgeLeWDr0bEHvTDZWm/aH68ydTUyqztyU0l5bSZ3 nnWoPp0Lrw5NivvDufEwGySxYL1T6fPkHcehjFW7BnLoCbRWryKyPF8EmcGw+D0V bVWmS4suVf2fvPoHsMAQsZekPZuTUoUg8unkrEJgN/dZFaWp+0vjckGHkpQJC845 QYk/8Rse+/OxUTUrf/BXn0Z9Pan6qnHxEoXv/YQTQhBmVeb7FjlX4aIuUpoe2U+V Nb0qb9F5hvRepiuIevDOd8l+7Nl3d7OXNjtX2GrkE0mrJm22hnJWO+fRQuAkGPNE o4s6Bjf9LGGtGS0dSqp02hwOPh94+evVzTvVyI1Es//hkXsgsdCE9nDHkBYu54fd rtr7Nto84cetwJ8I1/QE5VjuO4rSwTPMUeWn0kd0E1W1mCG3ytCCFbF+39BU9LV6 vDYxwmYLHYpE9Gp+mdzNhRkTQRshW3eC2zUcrhln7ySwfUXkVNg= =o4+t -----END PGP SIGNATURE----- --=_2fd468e28f2a3da942f7a63a9ca99663--