Prev: Please suggest an upgrade path.
Next: Kernel+toolchain sources for x86/ia32/en only
From: Frederick Williams on 28 Mar 2010 08:05
I get an error message

Could not launch 'KWord': could not connect to 192.168.11.150:2081

and similar with everything else in place of 'KWord'. Why can't I use
andLinux without connecting to the Internet?

--
I can't go on, I'll go on.
From: The Natural Philosopher on 28 Mar 2010 08:07
Frederick Williams wrote:
> I get an error message
>
> Could not launch 'KWord': could not connect to 192.168.11.150:2081
>
> and similar with everything else in place of 'KWord'. Why can't I use
> andLinux without connecting to the Internet?
>


What makes you think that 192.168.11.150 is on the Internet?

From: Frederick Williams on 28 Mar 2010 08:29
The Natural Philosopher wrote:
>
> Frederick Williams wrote:
> > I get an error message
> >
> > Could not launch 'KWord': could not connect to 192.168.11.150:2081
> >
> > and similar with everything else in place of 'KWord'. Why can't I use
> > andLinux without connecting to the Internet?
> >
>
> What makes you think that 192.168.11.150 is on the Internet?

Wherever it is, why does andLinux need to connect to it and how do I
make it do so?

Another, presumably related, error message is:

TAP Colinux
A network cable is unplugged

I'm not aware of having any unplugged network cables.

Anyway, to answer (probably unsatisfactorily) your question:
192.168.11.150 looks to me like an IPv4 address.

--
I can't go on, I'll go on.
From: Bit Twister on 28 Mar 2010 08:51
On Sun, 28 Mar 2010 13:29:26 +0100, Frederick Williams wrote:

> Anyway, to answer (probably unsatisfactorily) your question:
> 192.168.11.150 looks to me like an IPv4 address.

True, but 192.168.x.x packets do not travel across the Internet.
They are not supposed to get past your ISP's gateway router.

From: Frederick Williams on 28 Mar 2010 09:52
Bit Twister wrote:
>
> On Sun, 28 Mar 2010 13:29:26 +0100, Frederick Williams wrote:
>
> > Anyway, to answer (probably unsatisfactorily) your question:
> > 192.168.11.150 looks to me like an IPv4 address.
>
> True, but 192.168.x.x packets do not travel across the Internet.
> They are not supposed to get past your ISP's gateway router.

Why does andLinux want to send them at all?

--
I can't go on, I'll go on.
 |  Next  |  Last
Pages: 1 2 3 4
Prev: Please suggest an upgrade path.
Next: Kernel+toolchain sources for x86/ia32/en only