XPost: comp.mobile.android, alt.os.linux, alt.comp.os.windows-10
From: this@ddress.is.invalid
nospam wrote:
> In article , Frank Slootweg
> wrote:
>
> > > > He wasnts to be able toaddress his phone so he can ftp
> > > > to it, and transfer files to and from the phone using his Win computer.
> > > > As such not having to figure out what the IP address of the phone is
> > > > each time he does so is a convenience and he wants that convenience.
> > >
> > > if he was interested in convenience, he wouldn't be asking about static
> > > ips. he'd be asking about dns so he doesn't need to remember any ips.
> >
> > Nice straw man! NOT!
>
> no straw man.
In your - as usual misguided - opinion.
> > He didn't say he's interested in "static IPs" (plural), he's talking
> > about a *single* static IP.
>
> word games.
In your - as usual misguided - opinion.
> > Setting up a DNS server [1] for your local
> > network is an overkill if you need only one (or a few) static IP and can
> > configure that in your router.
>
> it's not overkill. dns makes using all devices, not just one or two,
Red herring. He needs only one.
> much easier. it's also trivial to set up, if it isn't already, which it
> probably is.
Tell us - oh wise one - exactly *where* and *how* it "probably is
already set up"? In the real world these things don't happen
automagically.
When spouting your next response: The context is an Android device, a
Windows computer and a simple consumer-type (NAT) router.
> > [1] Not to mention that most users wouldn't know what the fsck that
> > *is*, let alone install and configure one.
>
> and yet they'll know how to configure a static ip?
Yes, because the IP in question is reported by the FTP server when you
start it and it can be configured in the router.
OTOH, your imaginary DNS server is blissfully absent in the described
set up, so it *can* not even be set up.
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
