I'm installing debian 3.1 on a P3 500 with 128M RAM via ADSL, booting
from floppys. When I get to Install base system step, it retrieves and
installs all the core packages, but fails when it gets to "Updating list
of available packages". The log screen has the message:

Err http://<mirror> sarge/main Packages
Could not connect to <mirror> (1.0.0.0), connection timed out.

I have tried 3 mirrors now, 2 local (Australia) and 1 US, all get the
same result. I have no idea where to look for the problem. Why does the
connection time out when it's just spent 20 mins downloading all the
core packages from that same server? And what does the (1.0.0.0) mean?

Thanks for any help,

ROSCO

On Thu, 24 Nov 2005 15:03:32 +1100, Ross Crawford wrote:

> I'm installing debian 3.1 on a P3 500 with 128M RAM via ADSL, booting from
> floppys. When I get to Install base system step, it retrieves and installs
> all the core packages, but fails when it gets to "Updating list of
> available packages". The log screen has the message:
>
> Err http://<mirror> sarge/main Packages
> Could not connect to <mirror> (1.0.0.0), connection timed out.
>
> I have tried 3 mirrors now, 2 local (Australia) and 1 US, all get the same
> result. I have no idea where to look for the problem. Why does the
> connection time out when it's just spent 20 mins downloading all the core
> packages from that same server? And what does the (1.0.0.0) mean?
>
> Thanks for any help,
>
> ROSCO

Looks Like, an Misconfiguration in your network, check your DNS Settings.

--
MFG
Christian Fuß, replica-solutions.de
( Linux, Poetry, Community 4 everyone, International German/English )

Ross Crawford wrote:
> I'm installing debian 3.1 on a P3 500 with 128M RAM via ADSL, booting
> from floppys. When I get to Install base system step, it retrieves and
> installs all the core packages, but fails when it gets to "Updating list
> of available packages". The log screen has the message:
>
> Err http://<mirror> sarge/main Packages
> Could not connect to <mirror> (1.0.0.0), connection timed out.
>
> I have tried 3 mirrors now, 2 local (Australia) and 1 US, all get the
> same result. I have no idea where to look for the problem. Why does the
> connection time out when it's just spent 20 mins downloading all the
> core packages from that same server? And what does the (1.0.0.0) mean?

Well I found the problem, the DHCP client doesn't grab the correct
nameserver(s) from my ADSL router.

It may be a problem with the router, I will investigate further, but in
/etc/resolve.conf, it put:

nameserver 192.168.1.254

instead of grabbing the nameservers from my router (my subnet is
192.168.1.*). So I added my ISPs nameservers manually to resolv.conf,
and it worked. I'm guessing it will get overridden each time I reboot,
maybe even each time the lease is renewed, so I still need to work out
what's not working and fix it, but at least I got the install to complete.

ROSCO

In message <4386428c_1@news.iprimus.com.au>
Ross Crawford <ross.crawford@gmail.com> wrote:

> Ross Crawford wrote:
> > I'm installing debian 3.1 on a P3 500 with 128M RAM via ADSL, booting
> > from floppys. When I get to Install base system step, it retrieves and
> > installs all the core packages, but fails when it gets to "Updating list
> > of available packages". The log screen has the message:
> >
> > Err http://<mirror> sarge/main Packages
> > Could not connect to <mirror> (1.0.0.0), connection timed out.
> >
> > I have tried 3 mirrors now, 2 local (Australia) and 1 US, all get the
> > same result. I have no idea where to look for the problem. Why does the
> > connection time out when it's just spent 20 mins downloading all the
> > core packages from that same server? And what does the (1.0.0.0) mean?
>
> Well I found the problem, the DHCP client doesn't grab the correct
> nameserver(s) from my ADSL router.
>
> It may be a problem with the router, I will investigate further, but in
> /etc/resolve.conf, it put:
>
> nameserver 192.168.1.254

That's normal behaviour with many routers, if the router is the DHCP server.
Your network machines see the router as nameserver, and the router relays
the requests to a real nameserver. I'm not sure why it isn't working for you
though.

For it to work, your ROUTER needs to have the correct nameservers set up in
its config, so it knows wherre to relay the requests to. It might (should?)
get these from the ISP in turn, rather than having them statically set, but
there might be a router setting that's interfering.

>
> instead of grabbing the nameservers from my router (my subnet is
> 192.168.1.*). So I added my ISPs nameservers manually to resolv.conf,
> and it worked. I'm guessing it will get overridden each time I reboot,
> maybe even each time the lease is renewed, so I still need to work out
> what's not working and fix it, but at least I got the install to complete.
>
> ROSCO

--
Alan Adams
alan.adams@orchard-way.freeserve.co.uk
http://www.nckc.org.uk/

In message <4386428c_1@news.iprimus.com.au
Ross Crawford <ross.crawford@gmail.com> wrote

> Ross Crawford wrote
> I'm installing debian 3.1 on a P3 500 with 128M RAM via ADSL
bootin
> from floppys. When I get to Install base system step, it retrieve
an
> installs all the core packages, but fails when it gets to "Updatin
lis
> of available packages". The log screen has the message
>
> Err http://<mirror> sarge/main Package
> Could not connect to <mirror> (1.0.0.0), connection timed out
>
> I have tried 3 mirrors now, 2 local (Australia) and 1 US, all ge
th
> same result. I have no idea where to look for the problem. Why doe
th
> connection time out when it's just spent 20 mins downloading all th
> core packages from that same server? And what does the (1.0.0.0
mean
>
> Well I found the problem, the DHCP client doesn't grab the correc
> nameserver(s) from my ADSL router
>
> It may be a problem with the router, I will investigate further, bu
i
> /etc/resolve.conf, it put
>
> nameserver 192.168.1.25
>
That's normal behaviour with many routers, if the router is the DHC
server
Your network machines see the router as nameserver, and the route
relay
the requests to a real nameserver. I'm not sure why it isn't workin
for yo
though

For it to work, your ROUTER needs to have the correct nameservers se
up i
its config, so it knows wherre to relay the requests to. It migh
(should?
get these from the ISP in turn, rather than having them staticall
set, bu
there might be a router setting that's interfering

>
> instead of grabbing the nameservers from my router (my subnet i
> 192.168.1.*). So I added my ISPs nameservers manually t
resolv.conf
> and it worked. I'm guessing it will get overridden each time
reboot
> maybe even each time the lease is renewed, so I still need to wor
ou
> what's not working and fix it, but at least I got the install t
complete
>
> ROSC
>
--
Alan Adam
alan.adams@orchard-way.freeserve.co.u
http://www.nckc.org.uk