From owner-freebsd-stable@freebsd.org Sun Apr 25 15:04:50 2021 Return-Path: Delivered-To: freebsd-stable@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 3785F6257A8 for ; Sun, 25 Apr 2021 15:04:50 +0000 (UTC) (envelope-from lwhsu@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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 "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FSrst10gkz3jfS for ; Sun, 25 Apr 2021 15:04:50 +0000 (UTC) (envelope-from lwhsu@freebsd.org) Received: from mail-yb1-f182.google.com (mail-yb1-f182.google.com [209.85.219.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: lwhsu/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 1107C5C2F for ; Sun, 25 Apr 2021 15:04:50 +0000 (UTC) (envelope-from lwhsu@freebsd.org) Received: by mail-yb1-f182.google.com with SMTP id e8so1681713ybq.11 for ; Sun, 25 Apr 2021 08:04:50 -0700 (PDT) X-Gm-Message-State: AOAM531A3da2Il/tLdBef//wlTb5BzEiBbsWMkjlg38/QSYAEl2oInLx knKQ5jKafAIW0sPQVChrfsbU+CZmGzeGmeUhwg4= X-Google-Smtp-Source: ABdhPJwJAfdevrThWBWmbQpWjOpV4K5Snup4BDhqndJTUqSkPjFFg4inBiWJjY5J52ziIYGStx9xk+lx+iMzmI+oG1w= X-Received: by 2002:a25:4dd7:: with SMTP id a206mr18297887ybb.451.1619363089481; Sun, 25 Apr 2021 08:04:49 -0700 (PDT) MIME-Version: 1.0 References: <0367FE4C-B573-424B-9768-A532FB72E95C@icloud.com> In-Reply-To: <0367FE4C-B573-424B-9768-A532FB72E95C@icloud.com> From: Li-Wen Hsu Date: Sun, 25 Apr 2021 23:04:37 +0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: iPhone tethering not working To: =?UTF-8?B?5a6L56uL5p2w?= Cc: freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Apr 2021 15:04:50 -0000 On Sun, Apr 25, 2021 at 9:55 PM =E5=AE=8B=E7=AB=8B=E6=9D=B0 wrote: > > > > =E5=9C=A8 2021=E5=B9=B44=E6=9C=8825=E6=97=A5=EF=BC=8C19:08=EF=BC=8CLi-W= en Hsu =E5=86=99=E9=81=93=EF=BC=9A > > > > =EF=BB=BF > > > > I didn't see behavior before, previously if there is no ue0 found, > > other than usbconfig set_config, I use `/usr/local/sbin/usbmuxd -U > > root -f` from usbmuxd pkg. > > > > For iOS 14, this patch is needed > > https://cgit.freebsd.org/src/commit/?id=3D2076350d801b81f570850cea7e701= 388d8709cfb > > but from the report it still compatiable for iOS 13. I'm not sure if > > reverting it helps or not. > > > > Does it work with previous versions (12.2-RELEASE, 13.0-RELEASE, or > > older 12.2-STABLE), or other OS? > > > > Best, > > Li-Wen > > Yes, there is no ue0. And I made a mistake, it is 12.2-RELEASE other than= STABLE. Sorry for that. Do I need to install STABLE to keep up with the ne= west development? > > This time usbmuxd works, but why it has to run in foreground? And what=E2= =80=99s the difference to usb_config? > And running in background, I can get DHCP offer this time, but I still ca= n=E2=80=99t ping to any website, =E2=80=9CThe network is down=E2=80=9D. Why= ? > > Best wishes, > A BSD newbie Please don't forget CC the list unless there is sensitive information, the discussion may also help others. For iOS 14, that patch is needed so if Apple did the same change in the newer iOS 13 branch, upgrading to 12.2-STABLE is necessary. You can also upgrade to 13.0-RELEASE if you want to keep tracking -RELEASE. You can exit usbmuxd when you see ue0 is available. TBH I don't check the details in those tools. If you can get an IP from DHCP, but cannot do any transmission, that's exactly the same behavior on iOS 14 without that patch so upgrading to a newer version might help. Best, Li-Wen