From owner-freebsd-questions Mon Sep 24 5:26: 3 2001 Delivered-To: freebsd-questions@freebsd.org Received: from funnel.cisco.com (funnel.cisco.com [161.44.168.79]) by hub.freebsd.org (Postfix) with ESMTP id E73E737B40C for ; Mon, 24 Sep 2001 05:25:57 -0700 (PDT) Received: from bmcgover-pc.cisco.com (bmcgover-pc.cisco.com [161.44.149.69]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id IAA26082; Mon, 24 Sep 2001 08:25:57 -0400 (EDT) Received: from bmcgover-pc.cisco.com (localhost.cisco.com [127.0.0.1]) by bmcgover-pc.cisco.com (8.11.6/8.11.6) with ESMTP id f8OCLak22081; Mon, 24 Sep 2001 08:21:36 -0400 (EDT) (envelope-from bmcgover@bmcgover-pc.cisco.com) Message-Id: <200109241221.f8OCLak22081@bmcgover-pc.cisco.com> To: David Strait Cc: freebsd-questions@freebsd.org Subject: Re: DHCP going nuts? Date: Mon, 24 Sep 2001 08:21:36 -0400 From: "Brian J. McGovern" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >I'm having a problem with my dhclient, or, for the most part, setting up my >internet numbers. The problem follows an unusual pattern. [...] >My number is xxx.yyy.zzz.173 >On FreeBSD, my dhclient gets this address: >xxx.yyy.zzz.172 [...] >I didn't have this problem last year so I suspect someone in networking was >messing around with the equipment. [...] >Other than keep yelling at my networking dept., does anyone have any solid > advice about what I can do? Even if you don't have any advice, a > hypothesis of what is wrong is valued. Thanks. I'm assuming what you're describing is one machine, two operating systems, different addresses for each. What you describe above is a perfectly valid thing for a DHCP server to do. MAC address is not the only criteria usually used for assigning IP addresses by DHCP. There is the client-id field, as well as a few others (I can pull out the spec if need be), that must/should/can (depending on the working in the spec) be used to identify the client, and even different forms of the client. I expect the one that is biting you is the client-id field, as I'm sure FreeBSD and Windows are not setting the fields identically. If you are absolutely determined to get the same IP, then you need to make sure that the request packets have all the same client information. I doubt yelling at the network department will have little affect, as they probably can't change the server. Matter of fact, your problem probably 'started' when they upgraded the server to a version that does the _correct_ thing. Anyhow, you have both my opinion, and the solution. You may have to research dhclient.conf(5) to make my solution a reality, but it shouldn't be too difficult to do. You'll probably want a packet sniffer, and a copy of the RFC that defines DHCP, so you have all the option numbers handy. -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message