Re: how to change isc-dhcp3-server replies?
I found out where my dhcp offers are going. It seems my dhcp offers are being sent out my external port instead of my internal port. Anyone ever have a problem where the internal port is setup as a server and for some reason natd kicked in and sent the data out using the external ip? Thanks, Joe 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. - Choose the right car based on your needs. Check out Yahoo! Autos new Car Finder tool. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: how to change isc-dhcp3-server replies? (was:
On Sunday 02 September 2007 03:13:21 Joe wrote: Gosh, I suddenly remember why I dropped yahoo webmail 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. slash mangled quotes So what does the tcpdump exchange look like with the new binary and the always-broadcast flag? And we're talking server binaries, right? -- Mel People using reply to all on lists, must think I need 2 copies. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: how to change isc-dhcp3-server replies?
For some reason they are no longer showing up in tcpdump? I can see the DHCP discover and the DHCP offers, but can't get tcpdump to output them? DHCPDISCOVER from AA:AA:AA:AA:AA:AA via xl0 DHCPOFFER on 192.168.0.13 to AA:AA:AA:AA:AA:AA (w2k-box) via xl0 This happens 4 times, but I can get tcpdump to output the offer. Using tcpdump -netvvvi xl0 -t udp port 67 or udp port 68 Not sure what is going on now. Joe 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. So what does the tcpdump exchange look like with the new binary and the always-broadcast flag? And we're talking server binaries, right? - Looking for a deal? Find great prices on flights and hotels with Yahoo! FareChase. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
how to change isc-dhcp3-server replies? (was: isc-dhcp3-server issues with windows 2000 client)
Hello, after running tcpdump for a while I discoverd what is going on with my dhcpd server and why some clients are not able to get an IP address from it, in particular windows clients. It turns out it is not just win2k but any windows. 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. Anyone know how to force dhcpd to send its broadcast replies to the 'correct' broadcast address? Thanks, Joe - Choose the right car based on your needs. Check out Yahoo! Autos new Car Finder tool. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: how to change isc-dhcp3-server replies? (was: isc-dhcp3-server issues with windows 2000 client)
Joe wrote: Hello, after running tcpdump for a while I discoverd what is going on with my dhcpd server and why some clients are not able to get an IP address from it, in particular windows clients. It turns out it is not just win2k but any windows. 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. I have no problems running dhcp3 with windows clients at all... As far as I can tell the broadcast address of a subnet *never* is 255.255.255.255. Peter -- http://www.boosten.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: how to change isc-dhcp3-server replies? (was: isc-dhcp3-server issues with windows 2000 client)
On Saturday 01 September 2007 23:30:27 Peter Boosten wrote: Joe wrote: Hello, after running tcpdump for a while I discoverd what is going on with my dhcpd server and why some clients are not able to get an IP address from it, in particular windows clients. It turns out it is not just win2k but any windows. 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. I have no problems running dhcp3 with windows clients at all... As far as I can tell the broadcast address of a subnet *never* is 255.255.255.255. 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; The DHCP and BOOTP protocols both require DHCP and BOOTP clients to set the broadcast bit in the flags field of the BOOTP message header. Unfortunately, some DHCP and BOOTP clients do not do this, and there- fore may not receive responses from the DHCP server.The DHCP server can be made to always broadcast its responses to clients by setting this flag to 'on' for the relevant scope; relevant scopes would be inside a conditional statement, as a parameter for a class, or as a parameter for a host declaration. To avoid creating excess broadcast traffic on your network, we recommend that you restrict the use of this option to as few clients as possible. For example, the Microsoft DHCP client is known not to have this problem, as are the OpenTransport and ISC DHCP clients. Worth a shot :) -- Mel People using reply to all on lists, must think I need 2 copies. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: how to change isc-dhcp3-server replies? (was: isc-dhcp3-server issues with windows 2000 client)
I'd say thanks for the help, but telling someone that 'it works for me' is not helpful. I upgraded to 6.2p7 from 6.2p6 and this problem started happening, but only with dhcpd. In fact I can run the old dhcpd fine, but the new binary deos not run fine. The old binary does a dhcp reply from [dhcpd ip address] to 255.255.255.255. The new binary does a dhcp reply from [dhcpd ip address] to 192.168.0.255. Windows is not getting the reply from the new binary. This is not the correct behavior. In fact there is a bug in OLD 2.2 linux kernels that says that the kernel routing is messed up (see isc-dhcp3 web site docs). Joe Peter Boosten [EMAIL PROTECTED] wrote: Joe wrote: Hello, after running tcpdump for a while I discoverd what is going on with my dhcpd server and why some clients are not able to get an IP address from it, in particular windows clients. It turns out it is not just win2k but any windows. 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. I have no problems running dhcp3 with windows clients at all... As far as I can tell the broadcast address of a subnet *never* is 255.255.255.255. Peter -- http://www.boosten.org - Building a website is a piece of cake. Yahoo! Small Business gives you all the tools to get online. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: how to change isc-dhcp3-server replies? (was:
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.nbsp; 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.nbsp; 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.nbsp; brbrOld client reply (ml.. is server af is client):nbsp; brbr1188694380.961642 ml:ml:ml:ml:ml:ml gt; ff:ff:ff:ff:ff:ff, ethertype IPv4 (0x0800), length 342: (tos 0x10, ttlnbsp; 16, id 0, offset 0, flags [none], proto: UDP (17), length: 328) 192.168.0.15.67 gt; 255.255.255.255.68: BOOTP/DHCP, Reply, length: 300, xid:0x77915dc3, flags: [Broadcast] (0x8000)brnbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Your IP: 192.168.0.13brnbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; Client Ethernet Address: af:af:af:af:af:af [|bootp]brbrnew 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.nbsp; Not sure what is going on here, but the routing table looks fine.nbsp; brbrJoebrbrbi[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]gt; gt; It seems that the dhcpd server is replying to the subnet and not thebrgt; gt; broadcast net. So the reply that should be sent to
