<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=iso-8859-1" http-equiv="Content-Type">
<style>
pre {
white-space: pre-wrap; /* css-3 */
white-space: -moz-pre-wrap; /* Mozilla, since 1999 */
white-space: -pre-wrap; /* Opera 4-6 */
white-space: -o-pre-wrap; /* Opera 7 */
word-wrap: break-word; /* Internet Explorer 5.5+ */
}
</style>
</head>
<body bgcolor="#ffffff" text="#000000">
<div>
<br /><br />"Corley, Kenneth L \\(Kenny\\)" <corley@alcatel-lucent.com> wrote:<br /><blockquote class="webmail-quote" style="padding-right: 0px; padding-left: 5px; margin-left: 5px; border-left: #000000 2px solid; margin-right: 0px">We are not currently using option 82. <br /></blockquote><div><br />How do you distinguis between the different networks on the "client" side ? Are they in different VLANs routed by the Extreeme ? If so then you might considder enabling opt. 82 <br /><br />Cut from Extreeme man:<br />Configuring the DHCP Relay Agent Option (Option 82)<br />After configuring and enabling the DHCP/BOOTP relay feature, you can enable the DHCP relay agent option feature. This feature inserts a piece of information, called option 82, into any DHCP request packet that is to be relayed by the switch. Similarly, if a DHCP reply received by the switch contains a valid relay agent option, the option will be stripped from the packet before it is relayed to the client.<br />The DHCP relay agent option consists of two pieces of data, called sub-options. The first is the agent circuit ID sub-option, and the second is the agent remote ID sub-option. When the DHCP relay agent option is enabled on switches running ExtremeWare, the value of these sub-options is set as follows:<br />•Agent circuit ID sub-option: Contains the ID of the port on which the original DHCP request packet was received. This ID is encoded as ((slot_number * 1000) + port_number). For example, if the DHCP request were received on port 3:12, the agent circuit ID value would be 3012. On non-slot-based switches, the agent circuit ID value is simply the port number.<br />•Agent remote ID sub-option: Always contains the Ethernet MAC address of the relaying switch. You can display the Ethernet MAC address of the switch by issuing the show switch command.<br />To enable the DHCP relay agent option, use the following command after configuring the DHCP/BOOTP relay function:<br />configure bootprelay dhcp-agent information option<br />To disable the DHCP relay agent option, use the following command:<br />unconfigure bootprelay dhcp-agent information option<br />In some instances, a DHCP server may not properly handle a DHCP request packet containing a relay agent option. To prevent DHCP reply packets with invalid or missing relay agent options from being forwarded to the client, use the following command:<br />configure bootprelay dhcp-agent information check<br />To disable checking of DHCP replies, use this command:<br />unconfigure bootprelay dhcp-agent information check<br />A DHCP relay agent may receive a client DHCP packet that has been forwarded from another relay agent. If this relayed packet already contains a relay agent option, then the switch will handle this packet according to the configured DHCP relay agent option policy. To configure this policy, use the following command:<br />configure bootprelay dhcp-agent information policy <policy><br />where <policy> must be one of the following values: replace, keep, or drop. The default relay policy is replace. To configure the policy to the default, use this command: <br />unconfigure bootprelay dhcp-agent information policy<br />For more general information about the DHCP relay agent information option, refer to RFC 3046.<br />Verifying the DHCP/BOOTP Relay Configuration<br />To verify the DHCP/BOOTP relay configuration, use the following command:<br />show ipconfig<br />This command displays the configuration of the BOOTP relay service, and the addresses that are currently configured.<br />UnCut from Extreeme man.<br /><br />Again if several networks are comming into the DHCP server in the same network (interface) then you should use "shared network"<br /><br />Try search the list on opt. 82 and you might find some inspiration on matching with use of classes etc.<br /><br /></div><blockquote class="webmail-quote" style="padding-right: 0px; padding-left: 5px; margin-left: 5px; border-left: #000000 2px solid; margin-right: 0px">The giaddr is always 10.6.0.1 in DHCP Discover for both STB traffic and<br />data/internet traffic so the DHCP server is allocating from 10.6.0.x<br />always. I need it to allocate 10.5.0.x for STBs and 10.6.0.x for<br />data/internet (ie. PCs). <br /><br />Do you think using MAC OUI for STB address allocation would work...then<br />put the scopes for data/internet and voip below in the DHCPd config file<br />since it is processed from top to bottom?<br /><br />class "ADB" {<br />match if substring(hardware,1,3) = 00:03:91; *** ADB is the STB<br /><br />}<br />pool {<br />range 10.5.0.2 10.5.0.200;<br />allow members of "ADB";<br /></blockquote><div><br />This should work, but if a STB is put on the network anywhere else (a different VLAN) it will still match the class and can be alocated an adress form this scope.<br /> </div><blockquote class="webmail-quote" style="padding-right: 0px; padding-left: 5px; margin-left: 5px; border-left: #000000 2px solid; margin-right: 0px"># subnet 10.6.0.0/24 Test Data<br />subnet 10.6.0.0 netmask 255.255.255.0<br />{<br />authoritative;<br />option routers 10.6.0.1;<br />option broadcast-address 10.6.0.255;<br />pool {<br />deny members of "adb3800W-bootloader";<br />deny members of "adb3800W-hlcode";<br />deny members of "adb5810WX-bootloader";<br />deny members of "adb5810WX-hlcode";<br />range 10.6.0.201 10.6.0.225;<br />}<br />}<br />#<br /># subnet 10.7.0.0/24 Test Phone<br />subnet 10.7.0.0 netmask 255.255.255.0<br />{<br />authoritative;<br />option routers 10.7.0.1;<br />option broadcast-address 10.7.0.255;<br />range dynamic-bootp 10.7.0.201 10.7.0.225;<br />option tftp-server-name "192.168.22.254";<br />}<br /><br />So I basically removed the following from the config:<br /><br /># subnet 10.5.0.0/24 Test Video<br />subnet 10.5.0.0 netmask 255.255.255.0<br />{<br />authoritative;<br />option routers 10.5.0.1;<br />option broadcast-address 10.5.0.255;<br />pool {<br />range dynamic-bootp 10.5.0.201 10.5.0.225;<br />allow members of "adb3800W-bootloader";<br />allow members of "adb3800W-hlcode";<br />allow members of "adb5810WX-bootloader";<br />allow members of "adb5810WX-hlcode";<br />}<br />}<br /><br />Appreciate your thoughts.<br /><br />Kenny<br /><br />-----Original Message-----<br />From: dhcp-users-bounce@isc.org [mailto:dhcp-users-bounce@isc.org] On<br />Behalf Of Eric Helm<br />Sent: Tuesday, May 06, 2008 8:23 PM<br />To: dhcp-users@isc.org<br />Subject: Re: Address allocation not working correctly<br /><br /><br /><br />Corley, Kenneth L (Kenny) wrote:<br />> Eric,<br />> <br />> The Extreme has the following DHCP relay config:<br />> <br />> enable bootprelay<br />> configure bootprelay add 10.100.0.2 (10.100.0.2 is the DHCP server) <br />> configure ip-down-vlan-action forward<br />> <br />> I did notice when looking at the DHCP DISCOVER from Set Top Box going <br />> from the Extreme to the DHCP server that the bootp flag - relay agent <br />> IP address - is set to 10.6.0.1. I assume this is why the DHCP server<br /><br />> is allocating from the 10.6.0.x subnet? But I have deny statements <br />> for the Set Top box class in the data or 10.6.0.x scope.<br />> <br />> Would you happen to know how to configure the Extreme to send 10.5.0.1<br /><br />> in relay agent field of DISCOVER for STBs and send 10.6.0.1 in relay <br />> agent field of DISCOVER for anything other than STBs (ie.<br />PCs/laptops)?<br />> <br /><br />As far as I know, it cannot be done, but it shouldn't matter with the<br />dhcp shared-network because it will service both networks regardless if<br />the giaddr is 10.6.0.1 or 10.5.0.1.<br /><br />You'll need to make sure your Option 82 classes are accurate and<br />matching in the dhcpd.conf and that the Extreme is not stripping that<br />information out of the DHCP packets. By the looks of the Extreme config,<br />you'll need to add that line:<br /><br />configure bootprelay dhcp-agent information policy keep<br /><br />/Eric<br /></blockquote><div><br />Regards<br />Lars </div>
</div>
</body>
</html>