Posted: Mon Nov 09, 2020 19:09 Post subject: Re: 14.2 is not a solution
blkt wrote:
Did you test it? Edit: Never mind, the Apple thread now has another reply 14.2 is no solution.
Don't know why anyone would put up with two months of this, or any length of time, then all is forgiven.
This isn't the first time Apple broke tethering either, so why reward bad behavior with a new phone?
msoengineer is right about 2013, as designs became complacent and further cost reduced.
Then S6 set the standard, then S7, again with Note 8, Pixel 3 and so on. Time to look at the alternatives.
I have tested 14.2 on an iPhone XS Max and it still does not work. It does the same thing as before. It gets the ip and says it's connected. The phone shows that it has a client, but no access to the outside world on the router.
Posted: Tue Nov 10, 2020 5:48 Post subject: Took a shot with USB over IP
I tried enabling dd-wrt setting "USB over IP" with no success. Seemed worth a shot.
Wish I could find an associated router system error message to start troubleshooting this tethering problem.
Posted: Tue Nov 10, 2020 12:11 Post subject: Re: 14.2 is not a solution
neruve wrote:
blkt wrote:
Did you test it? Edit: Never mind, the Apple thread now has another reply 14.2 is no solution.
Don't know why anyone would put up with two months of this, or any length of time, then all is forgiven.
This isn't the first time Apple broke tethering either, so why reward bad behavior with a new phone?
msoengineer is right about 2013, as designs became complacent and further cost reduced.
Then S6 set the standard, then S7, again with Note 8, Pixel 3 and so on. Time to look at the alternatives.
I have tested 14.2 on an iPhone XS Max and it still does not work. It does the same thing as before. It gets the ip and says it's connected. The phone shows that it has a client, but no access to the outside world on the router.
My router is a TM-1900AC (converted to ASUS RT-68U) with the newest BS beta firmware on it.
"Looks like the issue is indeed in the path from the iPhone back to the host. Somehow the receiving URB seems to stall and always completes only after a significant delay. Using a slightly smaller length (1516 -> 1514) for the receiving URB seems to fix the issue, though. The extra control messages observed in Windows/macOS dumps don't seem to make any difference.
Why exactly reducing the length works is a bit unclear, considering Windows and macOS seem to be issuing even bigger transfers (assuming the lengths are comparable between dumps from different OSs). One thing I noticed is that the Windows and macOS drivers seem to issue multiple simultaneous receiving URBs, whereas the Linux driver issues only one at a time and waits for it to complete before receiving again. So perhaps the same stall happens on Windows and macOS as well, but only on one of the transfers."
"Hi, I'm not sure where you got that idea, but it does look to fix the problem for me too. I tried to very simple following patch:
-#define IPHETH_BUF_SIZE 1516
+#define IPHETH_BUF_SIZE 1514
#define IPHETH_IP_ALIGN 2 /* padding at front of URB */
#define IPHETH_TX_TIMEOUT (5 * HZ)
and it does restore the previous behavior. Before submitting that to the upstream kernel, could someone with older iOS version try that it doesn't break their usage?"
"It would be nice to have a better fix and to understand precisely what to do but without having a clear protocol description it's kind of hard. I don't have enough knowledge about USB to know if we can setup multiple URBs queues inside the ipheth driver (and maybe achieve more performance?) but for now I think just fixing the issue would be nice."
Posted: Mon Nov 30, 2020 18:49 Post subject: imputting ios 14 usb tethering patch into router
I'm new to imputing a patch into my dir868l router. I've inputted the patch into the administration code startup section, but I still get no internet throughput. My win10 laptop showed I have a internet connection, but does not say secure as it always does. So I must be doing something wrong or missed something? Any help would be appreciated.
dir868l A1 with V3.0-r39800
Win10 laptop
iphone 7plus 14.2
Joined: 18 Mar 2014 Posts: 12917 Location: Netherlands
Posted: Tue Dec 01, 2020 7:31 Post subject:
you have to compile your own build with the patch,it is not something many regular users can do
I have mailed the patch to our main developer, but as it is unclear why it should work and what else breaks it is quite possible he will wait till it is incorporated upstream in the kernel or until apple gives us more details.
Joined: 18 Mar 2014 Posts: 12917 Location: Netherlands
Posted: Tue Dec 01, 2020 11:08 Post subject:
egc wrote:
you have to compile your own build with the patch,it is not something many regular users can do
I have mailed the patch to our main developer, but as it is unclear why it should work and what else breaks it is quite possible he will wait till it is incorporated upstream in the kernel or until apple gives us more details.
Thank You for the information. I may look at the wiki and see if I can follow the instructions on how to compile a build, but most likely will wait for a new build to arrive.
As a temporary solution I use the 2.4Ghz radio as wireless repeater bridge (see https://wiki.dd-wrt.com/wiki/index.php/Repeater_Bridge), WiFi connected to my iPhone's hotspot. The 5Ghz radio still acts as AP.
Just make sure to reboot the router during the short window the hotspot SSID is advertised after enabling it on the iPhone, otherwise it won't connect.
