Quote:
Originally Posted by IsaacKuo
You don't have any problems with Arch Duke? What is /etc/resolv.conf in your Arch Duke install? If the problem is long DNS resolution, then perhaps manually copying resolv.conf will fix it.
|
in both, Debia and Arch, "/etc/resolv.conf" is same.
Quote:
Originally Posted by IsaacKuo
Alternatively, the problem may be that connectivity is simply very poor from your location to Debian's security updates servers. If you do another Debian install, check out the contents of /etc/apt/sources.list. I don't know if there are local mirrors for security.debian.org...maybe not.
|
i am sure this is not the case as on Arch and BLAG i can access internet without any troubles at all.
Quote:
Originally Posted by IsaacKuo
Anyway, what happens if you try to ping or ftp connect to security.debian.org? If it's a connectivity problem, then you'll have problems downloading from security.debian.org in Arch Duke also.
|
it takes a l..o..o..o..o..n..g time to show me the 1st ping. on Arch and Debian pings takes just 7 seconds.
ping -c5 google.com
i think this has to do with both "/etc/hosts" and IPv6. check my other thread in "Debian-User" mailing list archives where i have posted enough information with different view-point of the same problem. this is one solution i have got from "Douglas Allan Tutty":
---------- WHOLE POST ----------
> i installed Debian Etch AMD64 using netinst CD. installation went fine
> except one thing. it configured and connected my network using DHCP
> but says "unable to connect to Debian security updates" then after
> installation and booting into new system, i faced the same problem.
> even "apt-get install xorg" does not work correctly. it goes like
> this:
[snip: timeout waiting to connect to security]
> it seems like i have long DNS lookup.
>
> i chose these during installation:
>
> hostname = debian
> domainname = planet
>
> every time, when i boot up, i also get this message: "internet
> superserver disabled"
Normal unless you're running services out of inetd.
>
> ----- /etc/hosts -------------
> 127.0.0.1 localhost
> 127.0.1.1 debian.planet debian
>
> --------- /etc/resolv.conf -----
> nameserver 218.248.255.145
> nameserver 61.1.96.69
>
> -------------- /etc/network/interfaces -----
> did not remember exactly what was here but it was something like this:
>
> auto lo ....
> auto eth0...
> eth0 inet dhcp ....
I've never used dhcp so I don't know how it integrates with /etc/hosts.
If eth0 was setup manually, your /etc/hosts file would look something
like mine:
127.0.0.1 localhost.localdomain localhost
192.168.1.1 debian.planet debian
If your network is planet, and this box on your network is debian, then
having that show in your /etc/hosts file as 127.* will be a source of
confusion or errors. You need them to point to your network.
Since it is your network, can you try manually configuring it and not
use dhcp to see if the problem persists?
Doug.
--------------- EOF ----------