From nobody Sat Sep 24 20:51:21 2022 X-Original-To: bugs@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 4MZh561ml8z4dVwL for ; Sat, 24 Sep 2022 20:51:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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 "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4MZh556jfzz3fyT for ; Sat, 24 Sep 2022 20:51:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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 mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4MZh555nwvz1BZK for ; Sat, 24 Sep 2022 20:51:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 28OKpLZH015818 for ; Sat, 24 Sep 2022 20:51:21 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 28OKpL1R015817 for bugs@FreeBSD.org; Sat, 24 Sep 2022 20:51:21 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 266586] vnet bridge with IP address is not working after reboot Date: Sat, 24 Sep 2022 20:51:21 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 13.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: sharky@schaack.io X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bugs@freebsd.org MIME-Version: 1.0 ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1664052681; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=EyMF1y9DeQLBnxLPkWUlh/FTZ5U0D9KqZHw27z9DdgA=; b=r0BlemhtEkGxvZhmfJ1wUuYx9oQAKlPRG498NwgKOaU9/q4FBO3ZjZDwL3ngZhv9VB4PTz fC5TTQyrOMc++V6TAp3o/gdVLXlpuJpy4BvhgKDvBB9RMRYV7Ob0bD01ZYeTQ9RrhK7xTS DUel/yDr0eLyN81L+R9IB+LmUDyEhcbicliKA+8tlr5D2s+ZF0FkiervWs6ODdJxMQrVzp L9ajdtKIf2sgB1rGSfdsfXRxWpsf7Yvj5+Yrf5PYpzJCwr9r5fCalLcUvG+Cfx+aY/zflJ sEfJAr7f99uYXJcZOlZb7pCBoHjI89qAdGgxL98NEY8knP2WGCM1v1WSDjnbrQ== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1664052681; a=rsa-sha256; cv=none; b=pC7ANeMuybVNtz0MSpjNaUDsyO2t4hAKB4pVBF3veDacW/t3jTVn/+8jaHvqs/7JjeIq6I bmmOImyjf5SFdWdYgPYFHGfXaXNwVUlFespSxWzoEEK156M/VIl6/uzb1NSgtL0uktsM5b pbki/8jRapKezUdaxlMMlr7GIiC6pr+o8DwlIcln+NKN6EYkrSsCM8lH7YSrf5gTv6u8ZN aKuTjW0HHrRdyAvF28ixhdJXaDAmTU29Et4QXR06jem2l1HQCn2n6sm9O4KkRa05HOZq6l ROE3QlqfN2dlvRk6M8NY10VpPjghLNCREkCwcB05sI/NuhlGA0unGtQ3ORXxNg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D266586 Bug ID: 266586 Summary: vnet bridge with IP address is not working after reboot Product: Base System Version: 13.1-STABLE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: sharky@schaack.io Actually there is not documentation on how to implement vnet jails in the handbook . I did it my self years ago , but it would be handy to have a reference. I can provide it after we have discussed this problem.=20 My setup looks like the picture attached to the bug. This setup works excep= t , that the host can't use a service which are hosted inside a vnet jail.=20 People recommend me to move the ip from the "physical" lan interface to the bridge . I followed the advise and it works ! I can successfully use the service like dns or any other protocol which is hosted in the jail , until I reboot the machine and the rc.conf will takeover and create the setup for m= e . Instead it creates a mess , ip addresses are not set or the member is attac= hed to the bridge , but the ip address is not configured...=20 When the rc.conf create the setup for me the host is no able communicate anymore , because the IP addresses are not attached to the interfaces or the main lan interface is attached to the bridge but then the IP address is mis= sing . If I do the setup manually , it works.=20 Manually steps.=20 # vtnet0 does not have an IP address .=20 ifconfig bridge1 addm vtnet0 ifconfig bridge1 inet 192.168.10.100 netmask 255.255.255.0 ifconfig bridge1 addm vtnet0 ifconfig vnet0 up # Jails behind the bridge can be reached. The host system is able to ssh in= to the jail . To make it reboot stable I tried the following rc.conf cloned_interfaces=3D"bridge1"=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20 ifconfig_bridge1=3D"inet 192.168.10.100 netmask 255.255.255.0"=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 ifconfig_bridge1=3D"addm vtnet0" # after the reboot , the brigde1 does not have an IP address , but why ? I don't get it. # this fixes the issue ifconfig bridge1 inet 192.168.10.100 netmask 255.255.255.0 --=20 You are receiving this mail because: You are the assignee for the bug.=