From owner-freebsd-stable Fri May 31 14:21:46 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail.27in.tv (roc-24-169-198-248.rochester.rr.com [24.169.198.248]) by hub.freebsd.org (Postfix) with ESMTP id A89D637B40B for ; Fri, 31 May 2002 14:21:10 -0700 (PDT) Received: (from root@localhost) by mail.27in.tv (8.12.3/8.11.6) id g4VLLAiE035053; Fri, 31 May 2002 17:21:10 -0400 (EDT) (envelope-from cjm2@earthling.net) Received: from 27in.tv (localhost [127.0.0.1]) by mail.27in.tv (8.12.3/8.11.6av) with SMTP id g4VLL2TI035029; Fri, 31 May 2002 17:21:07 -0400 (EDT) (envelope-from cjm2@earthling.net) Received: from 216.153.201.118 (SquirrelMail authenticated user cjm2) by www.27in.tv with HTTP; Fri, 31 May 2002 17:21:08 -0400 (EDT) Message-ID: <2618.216.153.201.118.1022880068.squirrel@www.27in.tv> Date: Fri, 31 May 2002 17:21:08 -0400 (EDT) Subject: RE: new dhcp client causing problems From: "C J Michaels" To: In-Reply-To: <07f401c208e4$a7a8f9f0$0d00a8c0@celery> References: <2453.216.153.201.118.1022876310.squirrel@www.27in.tv> <07f401c208e4$a7a8f9f0$0d00a8c0@celery> X-Priority: 3 Importance: Normal X-MSMail-Priority: Normal Cc: X-Mailer: SquirrelMail (version 1.3.0 [CVS-DEVEL]) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: by AMaViS perl-11 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG tony said: > Since updating to 4.6R I seem to be having the same problem Same in that your connections are being reset? Because nothing looks bogus in your output either. Can you take a look in /var/db/dhclient.leases and see what "renew", "rebind", "expire", "option dhcp-lease-time" are set to for the most current lease. > > May 31 03:21:42 tntpro dhclient: New Network Number: 192.168.0.0 > May 31 03:21:42 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 31 08:14:03 tntpro dhclient: New Network Number: 192.168.0.0 > May 31 08:14:03 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 31 13:46:04 tntpro dhclient: New Network Number: 192.168.0.0 > May 31 13:46:04 tntpro dhclient: New Broadcast Address: 192.168.0.255 > root:~# ifconfig -a > xl0: flags=8843 mtu 1500 > options=3 > inet 192.168.0.100 netmask 0xffffff00 broadcast 192.168.0.255 > ether 00:50:da:c2:a1:48 > media: Ethernet autoselect (100baseTX ) > status: active > lo0: flags=8049 mtu 16384 > inet 127.0.0.1 netmask 0xff000000 > > Here is a grep just for fun notice it gets a new addy every 5 minutes > most of the time > > root:~# grep dhclient /var/log/messages > May 27 01:02:12 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 01:02:12 tntpro dhclient: New Broadcast Address: 192.168.0.255 [Was it necessary to paste the WHOLE log?] > > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG] On Behalf Of C J Michaels > Sent: Friday, May 31, 2002 4:19 PM > To: sean@mcneil.com > Cc: freebsd-stable@FreeBSD.ORG > Subject: Re: new dhcp client causing problems > > > Sean McNeil said: >> Hi, >> >> I've noticed that I occasionally lose connections through my computer >> to the internet. This has been happening because the dhcp client is >> trying to change my ip to something bogus and resetting the ethernet: > > Can you give an example of the 'bogus' ip address it's trying to set? > What you have listed below (without any additional information) appears > to be valid. (Note: no ip address is actually listed.) > >> >> May 30 23:44:17 blue dhclient: New Network Number: 66.75.176.0 May 30 >> 23:44:17 blue dhclient: New Broadcast Address: 255.255.255.255 > > Yes, I did note the broadcast address, my dhclient is pulling the same > broadcast addr (RoadRunner) and I have no problems. I believe this may > actually be an issue w/ a mis-configured dhcpd not dhclient. > >> May 31 02:38:07 blue su: sean to root on /dev/ttyp0 >> >> The previous dhcp client in 4.5 did not do this. It is only happening >> with the 4.6-RC. >> >> Cheers, >> Sean > > -- > Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message