Date: Fri, 31 May 2002 17:28:11 -0400 From: "tony" <tony@tntpro.com> To: "'C J Michaels'" <cjm2@earthling.net> Cc: <freebsd-stable@FreeBSD.ORG> Subject: RE: new dhcp client causing problems Message-ID: <07f501c208ea$11139260$0d00a8c0@celery> In-Reply-To: <2618.216.153.201.118.1022880068.squirrel@www.27in.tv>
next in thread | previous in thread | raw e-mail | index | archive | help
lease {
interface "xl0";
fixed-address 192.168.0.100;
option subnet-mask 255.255.255.0;
option routers 192.168.0.1;
option dhcp-lease-time 43200;
option dhcp-message-type 5;
option domain-name-servers 192.168.0.1;
option dhcp-server-identifier 192.168.0.1;
option domain-name "tntpro.com";
renew 5 2002/5/31 23:21:04;
rebind 6 2002/6/1 04:16:04;
expire 6 2002/6/1 05:46:04;
}
-----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 5:21 PM
To: tony@tntpro.com
Cc: freebsd-stable@FreeBSD.ORG
Subject: RE: new dhcp client causing problems
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<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> options=3<rxcsum,txcsum>
> inet 192.168.0.100 netmask 0xffffff00 broadcast 192.168.0.255
> ether 00:50:da:c2:a1:48
> media: Ethernet autoselect (100baseTX <full-duplex>)
> status: active
> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> 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
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?07f501c208ea$11139260$0d00a8c0>