From owner-freebsd-questions@FreeBSD.ORG Sun Sep 2 01:13:52 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 10A5816A417 for ; Sun, 2 Sep 2007 01:13:52 +0000 (UTC) (envelope-from josepha48@yahoo.com) Received: from web34607.mail.mud.yahoo.com (web34607.mail.mud.yahoo.com [209.191.68.141]) by mx1.freebsd.org (Postfix) with SMTP id C7C7A13C457 for ; Sun, 2 Sep 2007 01:13:51 +0000 (UTC) (envelope-from josepha48@yahoo.com) Received: (qmail 80206 invoked by uid 60001); 2 Sep 2007 01:13:21 -0000 Message-ID: <20070902011321.80204.qmail@web34607.mail.mud.yahoo.com> Cc: recipient list not shown: ; DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=OOkvOOUM3zSZRP8+4mWZAMexZAhA4Tb2wXLg43Xc+7etBw878acCsUySUtD7++w3k0S21IDz6Wfxzf9850qt+2uTfDVrwxbWP/rbNuzhZuH4YGjL2/J+rbYKrxVV/J4W0+Djbd5Y5AmapgR82cJfvnXvXgGjT/uspsfXw0yvUK0=; X-YMail-OSG: HXsIAOkVM1nPvFD9c.cNGgMKoGGzpuSUQ2V1eSnbsGi0oRj9XaXDhQrfOwxX62mkx66hQmsCHdiOhZCCSvteTf37FrOzKqbWRjSJVVO6EnBvlLQm.WwHvw3JZpgHhzeZGqYFn22uQ9lLSxyqZayrjsL6wT3vlu7xyDXpDRIH2WL1MueBQPgDsJxDYeo_K7YG0oUb5EeKL6Lt7L9V Received: from [67.101.218.14] by web34607.mail.mud.yahoo.com via HTTP; Sat, 01 Sep 2007 18:13:21 PDT Date: Sat, 1 Sep 2007 18:13:21 -0700 (PDT) From: Joe X-Mailman-Approved-At: Sun, 02 Sep 2007 01:48:54 +0000 Subject: Re: how to change isc-dhcp3-server replies? (was: X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Sep 2007 01:13:52 -0000 isc-dhcp3-server issues with windows 2000 client) To: freebsd-questions@freebsd.org In-Reply-To: <20070902000628.BD4AC16A4D5@hub.freebsd.org> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1649509927-1188695601=:80192" Content-Transfer-Encoding: 8bit Message-ID: <513147.80192.qm@web34607.mail.mud.yahoo.com> --0-1649509927-1188695601=:80192 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Ok, no so true. I am watching tcpdump output from the two binaries. The old binary sends its reply to 255.255.255.255, while the new one sends its reply to 192.168.0.15. Same config file and I tried the always-broadcast flag, and it only sets the bit for the client, but the server still broadcasts its reply to the client on the subnet mask. Old client reply (ml.. is server af is client): 1188694380.961642 ml:ml:ml:ml:ml:ml > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: (tos 0x10, ttl 16, id 0, offset 0, flags [none], proto: UDP (17), length: 328) 192.168.0.15.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length: 300, xid:0x77915dc3, flags: [Broadcast] (0x8000) Your IP: 192.168.0.13 Client Ethernet Address: af:af:af:af:af:af [|bootp] new client does not do this and clients do not get their ip address. I read somewhere that linux had a problem doing this in 2.2 kernels and it has something to do with the routing table in linux. Not sure what is going on here, but the routing table looks fine. Joe freebsd-questions-request@freebsd.org wrote: > > It seems that the dhcpd server is replying to the subnet and not the > > broadcast net. So the reply that should be sent to 255.255.255.255:68 is > > sent to 192.168.0.255:68. Then, because the client has no IP address or > > has defaulted it to a 169.x.x.x(MS defaults) it does not seem to be > > getting the reply and thus never gets an address assigned. > It is for DHCPDISCOVER, since there is no subnet yet: # dhclient -d fxp0 DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 4 As for the option you're looking for, man dhcpd.conf showed me this: always-broadcast flag; --------------------------------- Moody friends. Drama queens. Your life? Nope! - their life, your story. Play Sims Stories at Yahoo! Games. --0-1649509927-1188695601=:80192 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Ok, no so true.  I am watching tcpdump output from the two binaries. The old binary sends its reply to 255.255.255.255, while the new one sends its reply to 192.168.0.15.  Same config file and I tried the always-broadcast flag, and it only sets the bit for the client, but the server still broadcasts its reply to the client on the subnet mask. 

Old client reply (ml.. is server af is client): 

1188694380.961642 ml:ml:ml:ml:ml:ml > ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: (tos 0x10, ttl  16, id 0, offset 0, flags [none], proto: UDP (17), length: 328) 192.168.0.15.67 > 255.255.255.255.68: BOOTP/DHCP, Reply, length: 300, xid:0x77915dc3, flags: [Broadcast] (0x8000)
          Your IP: 192.168.0.13
          Client Ethernet Address: af:af:af:af:af:af [|bootp]

new client does not do this and clients do not get their ip address. I read somewhere that linux had a problem doing this in 2.2 kernels and it has something to do with the routing table in linux.  Not sure what is going on here, but the routing table looks fine. 

Joe

freebsd-questions-request@freebsd.org wrote:
> > It seems that the dhcpd server is replying to the subnet and not the
> > broadcast net. So the reply that should be sent to 255.255.255.255:68 is
> > sent to 192.168.0.255:68. Then, because the client has no IP address or
> > has defaulted it to a 169.x.x.x(MS defaults) it does not seem to be
> > getting the reply and thus never gets an address assigned.
>
It is for DHCPDISCOVER, since there is no subnet yet:
# dhclient -d fxp0
DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 4

As for the option you're looking for, man dhcpd.conf showed me this:
always-broadcast flag;

Moody friends. Drama queens. Your life? Nope! - their life, your story.
Play Sims Stories at Yahoo! Games. --0-1649509927-1188695601=:80192--