[wellylug] repository timed out issues

[Harrold Potter]

--- Jethro Carr <jethro.carr at jethrocarr.com> wrote:

> On Fri, 2006-06-23 at 22:38 +1200, Steve wrote:
> > Ok after a lot of looking around it seems that my
> adsl router does not like
> > IPV6 so it is a case of buying a new one
> > 
> > Can anyone recommend a wireless adsl router that
> does support this.
> > 
> > And if possible one that they sell at dick smiths
> > 
> > Now to try and get rid of my two D-Link wireless
> adsl routers
> 
> hi Steve,
> 
> Firstly, IPV6 should not be a problem here. I don't
> even think there are
> sites using it in NZ yet... at least none of the
> ones I use. There is no
> need to go and replace all your routers. :-)
> 
> I have the exact same router. I have no problems
> getting ubuntu updates,
> but I have found some DNS problems with this model
> router:
> 
> 
> The DNS relay server on these routers is best
> described as "retarded".
> It does weird resolution problems - for example, I
> might be downloading
> some files. And randomly, after it completes one
> file, it will try
> resolving the remote address as 1.0.0.0. Yet just 2
> seconds ago, it was
> being resolved corrected.
> 
> So, let's try setting your machine to avoid using
> it. This is a
> temporary fix (it will get wiped next time your
> machine updates it's
> DHCP address - usually next reboot.). However, it
> will show us if the
> fault is with the router's DNS.
> 
> Run the following commands in the terminal (just cut
> n' paste):
> -------
> sudo bash
> cat > /etc/resolv.conf << "EOF"
> nameserver 203.109.252.42
> nameserver 203.109.252.43
> EOF
> exit
> ---------
> 
> This switches you to the super user (root), and then
> recreates
> the /etc/resolv.conf file with the settings for
> ihug's DNS.
> 
> Now run:
> ------
> ping nz.archive.ubuntu.com
> ------
> 
> and you should get something like this:
> ------
> [jethro at jessie ~]$ ping nz.archive.ubuntu.com
> PING ftp.citylink.co.nz (202.7.6.9) 56(84) bytes of
> data.
> 64 bytes from ftp.citylink.co.nz (202.7.6.9):
> icmp_seq=0 ttl=60 time=57.9 ms
> 64 bytes from ftp.citylink.co.nz (202.7.6.9):
> icmp_seq=1 ttl=60 time=58.7 ms
> 64 bytes from ftp.citylink.co.nz (202.7.6.9):
> icmp_seq=2 ttl=60 time=57.4 ms
> 64 bytes from ftp.citylink.co.nz (202.7.6.9):
> icmp_seq=3 ttl=60 time=59.2 ms
> 64 bytes from ftp.citylink.co.nz (202.7.6.9):
> icmp_seq=4 ttl=60 time=58.7 ms
> -----
> 
> If the above works, it shows that the problem is
> with the router's relay
> DNS, and we can give you instructions on how to
> correctly set your DNS.
> 
> If it doesn't please just cut and paste all the
> output you do get into
> an email, so I have some idea of what might have
> gone wrong. :-)
> 
> 
> cheers,
> 
> -- 
> Jethro

Hi Jethro that has been the first bit of advice that
has actually made sense, on other forums I have been
told it is a problem with D-link routers etc.

I ran those commands and got the same results as you
but a load of them so shall only cut n paste the first
so many

PING ftp.citylink.co.nz (202.7.6.9) 56(84) bytes of
data.
64 bytes from ftp.citylink.co.nz (202.7.6.9):
icmp_seq=1 ttl=59 time=43.0 ms
64 bytes from ftp.citylink.co.nz (202.7.6.9):
icmp_seq=2 ttl=59 time=47.5 ms
64 bytes from ftp.citylink.co.nz (202.7.6.9):
icmp_seq=3 ttl=59 time=46.3 ms
64 bytes from ftp.citylink.co.nz (202.7.6.9):
icmp_seq=4 ttl=59 time=43.5 ms
64 bytes from ftp.citylink.co.nz (202.7.6.9):
icmp_seq=5 ttl=59 time=42.3 ms
64 bytes from ftp.citylink.co.nz (202.7.6.9):
icmp_seq=6 ttl=59 time=44.4 ms
64 bytes from ftp.citylink.co.nz (202.7.6.9):
icmp_seq=7 ttl=59 time=46.4 ms
64 bytes from ftp.citylink.co.nz (202.7.6.9):
icmp_seq=8 ttl=59 time=43.4 ms
64 bytes from ftp.citylink.co.nz (202.7.6.9):
icmp_seq=9 ttl=59 time=43.7 ms

So I am guessing the problem is with the DNS settings

Any help with setting this up would be greatfully
appreciated.

Cheers'

Steve


Send instant messages to your online friends http://au.messenger.yahoo.com