isc-dhcp3-server issues with windows 2000 client) To: freebsd-questions@freebsd.org In-Reply-To: <[EMAIL PROTECTED]> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1649509927-1188695601=:80192" Content-Transfer-Encoding: 8bit Message-ID: <[EMAIL PROTECTED]>
--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 [EMAIL PROTECTED] 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. <br><br>Old client reply (ml.. is server af is client): <br><br>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)<br> Your IP: 192.168.0.13<br> Client Ethernet Address: af:af:af:af:af:af [|bootp]<br><br>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. <br><br>Joe<br><br><b><i>[EMAIL PROTECTED]</i></b> wrote:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><[EMAIL PROTECTED]><[EMAIL PROTECTED]><freebsd-questions@freebsd.org><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><freebsd-questions@freebsd.org><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED] org><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><freebsd-questions@freebsd.org><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><[EMAIL PROTECTED]><freebsd-questions@freebsd.org><[EMAIL PROTECTED]>> > It seems that the dhcpd server is replying to the subnet and not the<br>> > broadcast net. So the reply that should be sent to 255.255.255.255:68 is<br>> > sent to 192.168.0.255:68. Then, because the client has no IP address or<br>> > has defaulted it to a 169.x.x.x(MS defaults) it does not seem to be<br>> > getting the reply and thus never gets an address assigned.<br>><br>It is for DHCPDISCOVER, since there is no subnet yet:<br># dhclient -d fxp0<br>DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 4<br><br>As for the option you're looking for, man dhcpd.conf showed me this:<br> always-broadcast flag;<br></[EMAIL PROTECTED]></freebsd-questions@freebsd.org></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></freebsd-questions@freebsd.org></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></kr [EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></freebsd-questions@freebsd.org></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></[EMAIL PROTECTED]></freebsd-questions@freebsd.org></[EMAIL PROTECTED] om></[EMAIL PROTECTED]></blockquote><br><p>  <hr size=1>Moody friends. Drama queens. Your life? Nope! - their life, your story.<br> <a href="http://us.rd.yahoo.com/evt=48224/*http://sims.yahoo.com/">Play Sims Stories at Yahoo! Games. </a> --0-1649509927-1188695601=:80192-- _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"