Re: How do nonroot Android & nonjailbroken iOS run SMB servers to connect to each other & Windows?

On Thu, 17 Apr 2025 05:58:07 -0000 (UTC), Chris wrote :

No you don't. You look for anything that you try and squirm away from the
facts when they don't match your anti-Apple bias.

Chris,

I'm digging for the answer - like an intelligent person should.

Yet I'm well aware of how Apple trolls think, which is that only Apple can
(magically) do the impossible. It's a defining feature of all Apple trolls.

Another defining feature of all Apple trolls is they have no idea how
anything works. That's also what makes Apple trolls what they are.

So you insist - repeatedly - that iOS is binding to ports below 1024.
When it's not. As far as I know, it's impossible. So it's just not.

But what is it doing then?
I do not know (yet).

That's why I asked the question.
This is a defining feature of intelligent people, Chris.

When you "see" Apple doing the impossible, you believe it.
(Like Apple saying they have special battery chemistry for example.)

When I see Apple or Android doing what appears to be impossible, I try to
figure out _how_ they managed that feat. Because it's clear that they did.

I get it that you believe that only iOS has special ways to get around the
port restriction for nonjailbroken/nonrooted devices to bind to ports below
1024, but the fact is iOS isn't special any more than Android is.

Neither of them can bind to ports lower than 1024 (AFAIK).
But let's work together to figure out precisely WHAT they're dong, Chris.

Note that you're the only Apple troll who can actually do that.
Maybe Tyrone can also. But not Jolly Roger. He's incapable of a GED.
You, ahem, have a PhD in the biological sciences Chris. Remember?

Moving forward to resolve the technical question of how they do it,
it seems we have the same issue with WebDav servers & LocalSend too.

Let's take the case of Android/iOS WebDAV Servers using Port 80:

Instead of the WebDAV application directly binding to port 80,
the operating system (or a privileged system process)
likely handles incoming HTTP requests on port 80.

When a request arrives on port 80, the system then forwards
or redirects that traffic to the actual port the WebDAV server
application is listening on (which would be a port above 1024).

This redirection is transparent to the user!

They access the WebDAV server using http://<device_ip>
(which defaults to port 80), and the system takes care of
routing the connection to the correct application port.

Something like that is almost certainly happening with SMB servers.

Only you and Tyrone (of the Apple trolls) has the capacity to comprehend
this, so I'm imploring you to start putting your thinking hat on please.

I'll eventually figure it out, but I'm asking for help to figure it out.
That way we all benefit from what we've learned about how this works.