From nobody Thu Jun 03 18:01:19 2021 X-Original-To: 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 607F41369795 for ; Thu, 3 Jun 2021 18:01:19 +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 4FwtxW2Dwvz4TVD for ; Thu, 3 Jun 2021 18:01:19 +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 35A776660 for ; Thu, 3 Jun 2021 18:01:19 +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 153I1J32081802 for ; Thu, 3 Jun 2021 18:01:19 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 153I1J2R081801 for net@FreeBSD.org; Thu, 3 Jun 2021 18:01:19 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: net@FreeBSD.org Subject: [Bug 256393] Issue with recreation of ppp/tun interfaces Date: Thu, 03 Jun 2021 18:01:19 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 13.0-STABLE X-Bugzilla-Keywords: needs-qa, regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: nwhitehorn@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: net@FreeBSD.org X-Bugzilla-Flags: mfc-stable13? mfc-stable12- mfc-stable11- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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: 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 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D256393 --- Comment #3 from Nathan Whitehorn --- I at least found the proximate problem: root@conference:/home/nwhitehorn # netstat -rn -f inet Routing tables Internet: Destination Gateway Flags Netif Expire default 128.135.X.X UGS vtnet0 127.0.0.1 link#2 UH lo0 128.135.X.X/25 link#1 U vtnet0 128.135.X.X link#1 UHS lo0 169.254.169.254 128.135.X.X UGHS vtnet0 192.168.42.1 127.0.0.1 UH lo0 <- this is the IP th= at the tunnel will use once established, and it didn't go away when the tunnel interface did If I delete the route to the tunnel endpoint on the loopback interface that appeared: root@conference:/home/nwhitehorn # route delete 192.168.42.1 delete host 192.168.42.1 Then the connection re-establishes itself without issue. The route in question seems to have been added by routed(8), replacing the link-level default route, though I am not sure why it is not going away when routed(8) exits and the interface disappears or why routed(8) is re-writing= it: root@conference:/home/nwhitehorn # netstat -rn -f inet Routing tables Internet: Destination Gateway Flags Netif Expire default 128.135.X.X UGS vtnet0 127.0.0.1 link#2 UH lo0 128.135.X.X/25 link#1 U vtnet0 128.135.X.X link#1 UHS lo0 169.254.X.X 128.135.X.X UGHS vtnet0 192.168.42.0/24 192.168.42.2 UGS tun0 192.168.42.1 link#3 UHS lo0 <- Original loopback route 192.168.42.2 link#3 UH tun0 root@conference:/home/nwhitehorn # service routed start Starting routed. root@conference:/home/nwhitehorn # netstat -rn -f inet Routing tables Internet: Destination Gateway Flags Netif Expire default 128.135.X.X UGS vtnet0 10.7.114.0/24 192.168.42.2 UG tun0 127.0.0.1 link#2 UH lo0 128.135.X.X/25 link#1 U vtnet0 128.135.X.X link#1 UHS lo0 157.132.6.8/29 192.168.42.2 UG tun0 169.254.X.X 128.135.158.134 UGHS vtnet0 192.168.1.0/24 192.168.42.2 UG tun0 192.168.2.0/24 192.168.42.2 UG tun0 192.168.3.0/24 192.168.42.2 UG tun0 192.168.5.0/24 192.168.42.2 UG tun0 192.168.42.0/24 192.168.42.2 UGS tun0 192.168.42.1 127.0.0.1 UH lo0 <- Rewritten by route= d(8) 192.168.42.2 link#3 UH tun0 192.168.176.0/24 192.168.42.2 UG tun0 On the 12.2 system on the other end of this link, the same loopback host ro= ute is present, but it doesn't seem to prevent re-IP'ing the link: $ netstat -rn -f inet Routing tables Internet: Destination Gateway Flags Netif Expire 192.168.42.1 link#5 UHS tun0 192.168.42.2 127.0.0.1 UH lo0 My suspicion is that the actual problem is that some of the routing-table verification code that went in recently is preventing adding an IP address = with an address to which there is already a route on another interface. --=20 You are receiving this mail because: You are the assignee for the bug.=