From nobody Mon Feb 12 08:30:37 2024 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 4TYHjM3Chzz59Jv6 for ; Mon, 12 Feb 2024 08:31:03 +0000 (UTC) (envelope-from benoitc@enki-multimedia.eu) Received: from mail-4317.proton.ch (mail-4317.proton.ch [185.70.43.17]) (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 RSA-PSS (4096 bits) client-digest SHA256) (Client CN "protonmail.com", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4TYHjK0PsMz49sC for ; Mon, 12 Feb 2024 08:31:00 +0000 (UTC) (envelope-from benoitc@enki-multimedia.eu) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=enki-multimedia.eu header.s=protonmail2 header.b=CWFryUe4; dmarc=pass (policy=none) header.from=enki-multimedia.eu; spf=pass (mx1.freebsd.org: domain of benoitc@enki-multimedia.eu designates 185.70.43.17 as permitted sender) smtp.mailfrom=benoitc@enki-multimedia.eu DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enki-multimedia.eu; s=protonmail2; t=1707726656; x=1707985856; bh=wqQeeSEFOwW+4JzYc3Z00cX/qB3WESsOL7BhbduIDF8=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=CWFryUe4bW1TVnuGnMwaZ5R2kPReonkCRTSiQ6Ey4fl+PqvFo27lv3deUCUuu80Ln BKtRgDRvO6Dw/jvT9oWL+lOzWpcM4Bul3cejXd++UitELFR0bjUqUM8m8ZhTfAFhnK JfdJ27+A0ftnhUcUhKk6uS1jqQ+6d0y7DnONAlBGO7S5kN4jvGVHCYc2V7j4065mp3 xmIbn46JtGI/vaecmCGMjXbMKjW5pesVa0w/xzw3JAVST2opyRNnI1/ZgImd1YR0xn IKhdkT9j1z4e3TgEEDjD3twE7/WmQy3/a9405veRRQs+FC8w3+aTFiGXuZug1tviQF 0k8dMPQ8qwqiw== Date: Mon, 12 Feb 2024 08:30:37 +0000 To: Konstantin Belousov From: Benoit Chesneau Cc: "freebsd-net@FreeBSD.org" Subject: Re: mlx5en issue with SR-IOV when using in the bridge Message-ID: In-Reply-To: References: <7L4ctsvv8st_6uOSAw8Li1SvAPsNYXPWjv3rRepGpwcRdl900YajxFSLe3frQl4hUE28PKU5lf98gRpN7WlZG7u2FWgOf3BImZu4spzI3Sg=@enki-multimedia.eu> Feedback-ID: 9066678:user:proton 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: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.39 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.991]; DMARC_POLICY_ALLOW(-0.50)[enki-multimedia.eu,none]; RWL_MAILSPIKE_EXCELLENT(-0.40)[185.70.43.17:from]; R_DKIM_ALLOW(-0.20)[enki-multimedia.eu:s=protonmail2]; R_SPF_ALLOW(-0.20)[+ip4:185.70.43.0/24]; MIME_GOOD(-0.10)[text/plain]; TO_DN_EQ_ADDR_SOME(0.00)[]; ASN(0.00)[asn:62371, ipnet:185.70.43.0/24, country:CH]; MISSING_XM_UA(0.00)[]; MIME_TRACE(0.00)[0:+]; TO_DN_SOME(0.00)[]; FREEMAIL_TO(0.00)[gmail.com]; ARC_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_COUNT_ZERO(0.00)[0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; MLMMJ_DEST(0.00)[freebsd-net@freebsd.org]; MID_RHS_MATCH_FROM(0.00)[]; DKIM_TRACE(0.00)[enki-multimedia.eu:+] X-Rspamd-Queue-Id: 4TYHjK0PsMz49sC Hi Konstantin, indeed the port is plugged to a switch. The port is enabled. So yes that pr= obably is. Is this a firmware issue or can it be solved in the driver? Beno=C3=AEt On Sunday, February 11th, 2024 at 04:50, Konstantin Belousov wrote: > On Sat, Feb 10, 2024 at 09:23:36AM +0000, Benoit Chesneau wrote: >=20 > > I have tested the following scenario: > >=20 > > Setup the mellanox driver with SRIOV: > >=20 > > ``` > > $ sudo more /etc/iov/mce0.conf > > PF { > > device: "mlx5_core0"; > > num_vfs: 8; > > } > >=20 > > DEFAULT { > > passthrough: true; > > } > >=20 > > VF-0 { > > mac-addr: "02:01:02:02:01:00"; > > } > >=20 > > VF-1 { > > mac-addr: "02:01:02:02:01:01"; > > } > >=20 > > VF-2 { > > passthrough: false;} > >=20 > > ``` > >=20 > > With one VF in the vm answering to a specific vlan, and one jail on the= host using vnet with the PF in a bridge and a epair interface added to thi= s bridge. > >=20 > > When I am pinging from the jail to the VF in the vm , the vm receive th= e ping or arp requests. But the jail doesn't receive the response. In a sam= e manner , when I ping from the VM to the jail, the host is not found. brid= ge arp doesn't return the vm mac address. > >=20 > > All the hosts has the PF interface set in promiscuous mode but this doe= sn't seem to be enough to allows the bridge to learn other mac ids. When I = directly add the IP to PF, Ping works from the vm to the PF, the reverse is= also true. > >=20 > > Do I miss a setting? Is this expected with mellanox cards? What shoudl = I look for? >=20 >=20 > Do you have the port plugged into a switch and the port enabled? > I suspect VFs do not have enough hairpin code to do proper loopback > communications, and I certain that multicast loopback does not work.