Date: Tue, 1 Jun 1999 06:57:26 +0200 From: Andrzej Szydlo <andrzej@gv.edu.pl> To: rick hamell <hamellr@dsinw.com> Cc: freebsd-questions@freebsd.org Subject: Re: Strange DNS/Routing (buggy 3.2?) Message-ID: <19990601065726.A13241@gv.edu.pl> In-Reply-To: <Pine.BSF.3.91.990531163427.2645A-400000@dsinw.com>; from rick hamell on Mon, May 31, 1999 at 04:35:22PM -0700 References: <19990531140026.B4876@gv.edu.pl> <Pine.BSF.3.91.990531163427.2645A-400000@dsinw.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, May 31, 1999 at 04:35:22PM -0700, rick hamell wrote: > > > > Here's my problem, I upgraded my 3.1 workstation to 3.2. Now no > > > DNS services seem to work from the workstation. In addition, the only ip > > > number I can even connect to is my dial-up server. From the server itself > > > everything runs fine. traceroute eventually finds other IP numbers but > > > there is at least a 30 second wait time between each hop. > > > I thought this at first may have been a duplex problem with the de > > > driver that other people have experienced, but ifconfig shows that my > > > server running the same card is running in full duplex also. > > > The only other thing I can think that may be causing problems is > > > the name of the workstation. I changed it from the generic name.my.domain > > > to name.domainname, but changing it back makes no differance. > > > > Hi, > > > > We need more details. > > Could you please sned the output of > > netstat -rn > > ifconfig -a > > and the file /etc/resolv.conf ? > > Attached, thanks in advance for your help. > > Rick > de0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > inet 192.168.1.2 netmask 0xffffff00 broadcast 192.168.1.255 > ether 00:c0:f0:37:9b:3b > media: autoselect (10baseT/UTP) status: active > supported media: autoselect 10base5/AUI 10base2/BNC 10baseT/UTP <full-duplex> 10baseT/UTP > lp0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500 > tun0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500 > sl0: flags=c010<POINTOPOINT,LINK2,MULTICAST> mtu 552 > ppp0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500 > lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 > inet 127.0.0.1 netmask 0xff000000 > > Routing tables > > Internet: > Destination Gateway Flags Refs Use Netif Expire > default 192.168.1.1 UGSc 2 48 de0 > 127.0.0.1 127.0.0.1 UH 0 3 lo0 > 192.168.1 link#1 UC 0 0 de0 > 192.168.1.1 0:c0:f0:37:b9:56 UHLW 4 4607 de0 687 > > domain hamell.hpc1.com > nameserver 192.145.92.34 If the _only_ change you did is upgrade 3.1->3.2, this would mean the 3.2 is buggy, I guess. I the meantime I've found there are problems with dual homed hosts when the only change was upgrade 3.1 -> 3.2. I'd suggest youy to downgrade back to 3.1 and report the problem :( Andrzej To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990601065726.A13241>