In message <199810192103.XAA00497@nethotel.dk>,
     Ib-Michael Martinsen wrote:

> 
> Mark Brinicombe writes:
>  > Hi,
>  >   Quick question. What does your /etc/resolv.conf look like ? The long
>  > delays are probably due to nameserve lookup attempts.
> 
> It looks like:
> 
> /etc/resolv.conf
> domain	dk

Shouldn't this line read "domain nethotel.dk"? Is nethotel.dk the domain
of your provider or is it your own domain?

> lookup	file bind
> nameserver	193.162.146.9
> nameserver	193.162.153.131
> 
> and btw, I haven't got my nameserver running yet, does it mean that
> I should avoid 'lookup bind'?

No. /etc/resolv.conf is just the config file for the client part (e.g. the
gethostbyname() system call) of the name lookup service. The machines
193.162.146.9 and 193.162.153.131 are running the server part (named).

> 
> I have tried removing the bind option, but then I can not resolve any
> addresses not specified in /etc/hosts. According to the resolv.conf
> man-pages the order for name searching is specified with the lookup
> statement, but it does not appear to work as intended. It seems to
> me that my 'netstat -r' first makes a DNS-lookup, and when timed out
> it looks for the names in the /etc/hosts file. Shouldn't it have been
> the other way around?
> 

This might be caused by the domain entry in your /etc/resolv.conf. The
resolver routines append the domain to each name that is not fully
qualified. 

> 
> 
> I tried to remove /etc/resolv.conf and then the 'netstat -r' worked
> without any delay, but I still can not ping the gateway :-(
> 
> A tcpdump command shows lot of output like:
> 
> 13:29:58.253800 arp who-has 192.168.80.120 tell (0xcc02e) 192.168.80.254
> 13:29:58.404383 arp who-has gateway tell (0xcc02e) nethotel.dk
> 13:30:00.069319 arp who-has 192.168.88.80 tell (0xcc06a) 192.168.80.254
> 13:30:00.069320 arp who-has 192.168.80.213 tell (0xcc0ba) 192.168.80.254
> 13:30:00.075303 arp who-has 192.168.88.62 tell (0xcc10a) 192.168.80.254
> 13:30:00.283939 arp who-has 192.168.89.24 tell (0xcc15a) 192.168.80.254
> 13:30:01.831142 arp who-has 192.168.93.63 tell (0xcc1aa) 192.168.80.254
> 13:30:03.409312 arp who-has gateway tell (0xcc1fa) nethotel.dk
> 13:30:04.286115 arp who-has 192.168.89.48 tell (0xcc236) 192.168.80.254
> 13:30:05.289745 arp who-has 192.168.89.24 tell (0xcc286) 192.168.80.254
> 
> so obviously there is connection to the (outside world) cable-network.
> (I guess the lines not mentioning gateway are from other users on the
> cable-network). But what does the above lines really tell me?
> (Obviously nothing :-)

You are right. The above arp lines clearly show that you are connected to
the world. Two routers (192.168.80.254 and nethotel.dk) are asking for mac
addresses of attached machines. 192.160.80.254 is asking for mac addresses
for a bunch of machines and your machine (nethotel.dk) is asking for the
mac address of your gateway.

However there's something missing: There are no answers to the arp
requests. There should be lines saying "tt:vv:ww:xx:yy:zz is gateway". Can
you ping the address 192.168.80.254? If you can just use that address as
your gateway.

You could also try a different netmask. There are arp requests from
networks other than 192.168.89.0. The address part they have in common is
192.168 so they might use a netmask 255.255.0.0 instead of 255.255.255.0.
Configure you ethernet card with netmask 255.255.0.0 and see if it makes
any difference. 

> 
> Don't bother to answer, I read the tcpdump man-pages and got wiser!
> 
> 
> Another question:
> I do not have any apropos-help ready. I know there is a database
> I have to build (because I have done it before in v1.2 I think), but
> I can not remember the name of the db or how to build it. And I
> can not find anything in the man-pages as the apropos is not working
> properly :-(

Apropos-help? Are you talking about makewhatis?

> 

Regards,
   Stefan
   

-- 
Stefan Voss
(voss@yoda.in-berlin.de)