On Tue, 14 Nov 2006 11:43:33 +0530, arnuld <arnuld3@gmail.com> wrote:

> 
> i get:
> 
> 1.)  "var0" is my interface
> 2.) exactly same "media" & "status"
> 3.) "inet 192.168.0.1 netmask 0xff000000 broadcast 192.168.0.255"
> 
> > You are interested in the first group here - i.e. fxp0 (obviously it
> > is configured on mine). Let's assume your interface is fxp0 as well.
> > Create the file /etc/ifconfig.fxp0
> > with the contents:
> >
> > inet xx.yy.zz.tt netmask 255.255.255.0
> 
> created with contents:
> 
> ifconfig 192.168.0.1 netmask 255.255.255.0
> 
> 
> > ifconfig fxp0 xx.yy.zz.tt up
> 
> it is fine
> 
> > and then try to ping some other host on your network).
> 
> ping 192.168.0.1. (default gateway) ( i do not have any network. it is
> my home computer)
> 
> it takes tooooooooo long to ping.

That's a DNS timeout, almost certainly. 

	ping -n 192.168.0.1

should return much faster.
> 
> > If this is OK, then you should:
> >
> > A. Enter your host address and name in /etc/hosts
> > B. Put your default gateway address in /etc/mygate
> > C. Create /etc/resolv.conf to contain your DNS settings (you already
> > have this in your Linux installation, it should do).
> 
> /etc/mygate      contents:   192.168.0.1
> /etc/myname    contents:   netbsd
> /etc/defaultdomain  contents:   unix
> /etc/resolv.conf      contents:
> nameserver  218.248.255.145
> nameserver  61.1.96.69
> search netbsd
> 
> > The reboot and try
> >
> > dig www.asd.com or whatever.
> 
> ping www.google.com  gives "host name unresolvable" error
> ping 192.168.0.1 again takes tooooooo long to ping
> 
It looks like a fairly low-level connectivity problem.  What happens if
you do

	traceroute -n 61.1.96.69

(I'm using one of your nameservers).


		--Steven M. Bellovin, http://www.cs.columbia.edu/~smb