Date: Fri, 31 May 2002 23:57:45 -0400 From: "tony" <tony@tntpro.com> To: "'Cy Schubert - CITS Open Systems Group'" <Cy.Schubert@uumail.gov.bc.ca>, "'Ted Sikora'" <tsikora@ntplx.net> Cc: <freebsd-stable@FreeBSD.ORG> Subject: RE: new dhcp client causing problems Message-ID: <07fe01c20920$7cf3ef80$0d00a8c0@celery> In-Reply-To: <200206010119.g511JCr1059003@cwsys.cwsent.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I'm just wondering why my /var/log/messages is filling with
May 31 19:21:04 tntpro dhclient: New Network Number: 192.168.0.0
May 31 19:21:04 tntpro dhclient: New Broadcast Address: 192.168.0.255
-----Original Message-----
From: owner-freebsd-stable@FreeBSD.ORG
[mailto:owner-freebsd-stable@FreeBSD.ORG] On Behalf Of Cy Schubert -
CITS Open Systems Group
Sent: Friday, May 31, 2002 9:19 PM
To: Ted Sikora
Cc: freebsd-stable@FreeBSD.ORG
Subject: Re: new dhcp client causing problems
In message <3CF7E836.742CD559@ntplx.net>, Ted Sikora writes:
> C J Michaels wrote:
> >
> > 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
>
> The default lease time has changed in the client. Does it on all my
> dhcp connected servers with -stable. Maybe adding a line like Cy
Schubert
> suggested
>
> send requested-lease-time 172800
>
> in dhclient.conf with unlimited lease might be a good idea or a
> commented out one explaining why. Nice to have options.
The client doesn't have a default lease time. That's determined by the
server or more specifically the server's admin person. You might be
able to request a longer lease time in your dhclient.conf, however
since this is a policy decision made by your service provider, you'll
probably have to talk to a person to request a longer lease time.
Following is a copy of my current lease from dhclient.leases:
lease {
interface "dc0";
fixed-address x.x.x.x;
option subnet-mask 255.255.252.0;
option routers x.x.x.1;
option dhcp-lease-time 172800;
option dhcp-message-type 5;
option domain-name-servers x.x.x.x,y.y.y.y;
option dhcp-server-identifier x.x.x.x;
option dhcp-renewal-time 86400;
option dhcp-rebinding-time 151200;
option host-name "hxx-xx-xx-xx";
option domain-name "xx.xxxx.net";
renew 6 2002/6/1 06:50:28;
rebind 0 2002/6/2 03:09:34;
expire 0 2002/6/2 09:09:34;
}
I have not requested a lease time of 2 days, but that's what my cable
company has given me by default. From time to time they will reduce
the lease time to 1 hour. This will last for a day or two, maybe a
week, when they do any work on their infrastructure. Usually I can
expect outages for a short time following this.
My dhclient.conf is pretty basic. It looks like this:
timeout 60;
reboot 10;
retry 60;
select-timeout 5;
initial-interval 2;
interface "dc0" {
#this next line is required for @home, a pseudo authentication #it
should be something like cx111111-a send host-name "blah-x"; request
subnet-mask, broadcast-address, routers, domain-name-servers,
domain-name, time-servers;
require domain-name-servers;
script "/usr/local/etc/dhclient-script";
}
IMO, I think that people are wasting their time by looking for DHCP
problems within FreeBSD or fiddling with parameters that more than
likely their service provider will not allow them to request or change.
More than likely the problem is with your service providers DHCP
policy and the configuration that stems from their policy. The DHCP
support in FreeBSD has been extremely solid for the years I've been
connected to the cable company. What more can I say? Just like the
Energizer rabbit, it just keeps on working.
--
Cheers, Phone: 250-387-8437
Cy Schubert Fax: 250-387-5766
Team Leader, Sun/Alpha Team Email: Cy.Schubert@osg.gov.bc.ca
Open Systems Group, CITS
Ministry of Management Services
Province of BC
FreeBSD UNIX: cy@FreeBSD.org
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?07fe01c20920$7cf3ef80$0d00a8c0>