[wellylug] repository timed out issues

[Steve Macdonald]

On Saturday 24 June 2006 09:29, Jethro Carr wrote:
> On Sat, 2006-06-24 at 02:05 +1200, Harrold Potter wrote:
> > 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.
>
> Great! Pleased to help. :-)
>
> These routers do seem to have quite a buggy interface... but they run
> Linux, which means that if someone hacked it a bit, you could have a
> bloody cool router with real good firewalling and even vlan support.
> It's been something I've been meaning to look doing sometime...
>
> > 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
>
> ah, yes - the ping command will keep running.
>
> Usually, once you have 5 entries like the below, you just kill it with
> CTL+C. This rule applies to many command line Linux programs. CTL+C
> basicly says "I want you to close". Like clicking X.
>
> With ping, you can also use "-c #" to tell it how many times to bing,
> and then it will close itself.
>
> > 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
>
> cool, so the DNS fix works.
>
> > So I am guessing the problem is with the DNS settings
> >
> > Any help with setting this up would be greatfully
> > appreciated.
>
> Okay, here is the fix I used with my router.
>
>
> 1) Your PC is set to get it's IP via DHCP
>
> 2) Login to the router web interface. Select the DNS tab.
>
> change "DNS Relay Selection" to "Disable DNS Relay".
> add the following DNS servers:
> 	"preferred" = "203.109.252.42"
> 	"alternate" = "203.109.252.43".
> click "apply" - the router will prompt you to save & reboot.
>
>
> 3) Once your router reboots - if you can navigate it's web interface,
> it's rebooted. Make sure the ADSL light has connected (should be lit,
> flickering, not slow blinking).
>
> 4) Run these commands:
> 	---
> 	sudo ifdown eth0
> 	sudo ifup eth0
> 	---
> these commands just restart your network interface, so that it requests
> a new DHCP address from the router.
>
> 4) Run:
> 	----
> 	cat /etc/resolv.conf
> 	----
>
> and you should get output containing "nameserver 203.109.252.42".
>
>
> 5) Run these commands:
> 	----
> 	ping -c5 nz.archive.ubuntu.com
> 	----
> and you should get the same output as the last email's ping. However,
> the -c5 will cause it to only ping 5 times, and then quit. :-)
>
> Now run:
> 	----
> 	sudo apt-get update
> 	----
>
> And it should "just work(tm)". :-)
>
>
> Again, if something doesn't work, just cut & paste all the content into
> an email.
>
>
> cheers,

You are a legend thank you so much for that it works perfectly. Also thanks 
for explaining what each command means. I was up until 5 am this morning 
adding software with the commands you gave me last night allowed me to access 
the repositories for a brief time so made the most of it. 

Such a simple fix yet so many different forums were telling me to buy a new 
router.

A couple of other quick questions if I may. every so often the display comes 
up say display on in a grey box, how do I get rid of that happening? and also 
I had to create a folder in usr/shared but without root rights I cant. I dont 
know how to get root rights to do simple things like that.

Anyway thanks for your help you rock

Steve