Re: [Sheflug] debian network problem

[damian.b [at] xxxxxxxxxxxxxx]

hi, 
thanks for your reply...

>  from:    Alex Hudson <home [at] alexhudson.com>
>  date:    Thu, 06 Mar 2003 13:19:40
>  to:      shef-lug [at] list.sheflug.org.uk
>  subject: Re: [Sheflug] debian network problem
> 
> On Thu, Mar 06, 2003 at 01:10:33PM  0000, damian.b [at] btinternet.com wrote:
> > i gave it an address manually (192.168.64.20 - the server address is 
> > 192.168.64.1). 
> 
> How did you do this? With ifconfig? If so, your card is probably fine.
> 
i installed it as part of the install package. it was one of the options that came up as it was installing. it first said something about installing ppp, but i canceled that as I want it to connect through my lan (the ppp install thingy was asking for isp details) .
> Trying pinging 192.168.64.20, see if it works.
> 
yes, that works fine, as also does pinging the loopback address.

> > When debian was trying to locate ftp servers in the uk so the rest of 
> > debian would install, i got the report "something wicked happened".
> 
> That means your name server stuff isn't setup. 
> echo nameserver 192.168.64.20 >> /etc/resolv.conf
> 
i tried this. I also tried:
echo nameserver 192.168.64.20 >> /etc/resolve.conf in case you might have made a spelling mistake. nothing happened at all. well, not that I could see. nothing came on the screen.

to be honest, I dont have any idea what a nameserver is... well, i do in general. it is the server that holds all the names of ip addresses against web addresses. the server where domain names are registered. i guess i must be overloking something... what an earth would a nameserver be doing in my little network? why would i need it? my windows boxes work fine. i dont remember setting anything to do with a nameserver on them. i just tell them to use dhcp, and they use the ipcop box and... well... they just work. I dont really know how. 

i think i will have to do some more reading.

> 'host ftp.uk.debian.org' should then return something sensible. Also, you
> may need to tell apt about your web proxy (if you are using one), like:
> 
> http_proxy=http://192.168.64.20:3128/ apt-get update
> 
> ... or something.
> 
i tried this. I got the messages:
Reading Package Lists... Done
Building Dependency Tree... Done

I am not entirely sure what a web proxy is either.

I think i will have to do a lot more reading.

> Is this any use?
> 
thanks again. it hasnt got my network working, but it has highlighted further huge gaps in my knowledge. I think a lot of the problem with linux is knowing what to learn, so thanks for pointing me in the right direction.

regards,
Damian.
___________________________________________________________________

Sheffield Linux User's Group -
http://www.sheflug.co.uk/mailfaq.html

  GNU the choice of a complete generation.