DHCP option 60

Does anyone know how I can configure Solaris DHCP server such that it will send option 60 and string "PXEClient" to DHCP clients that use PXE ? Thanks in advance for any help in this matter.
Edmund Gean

You should understand that DHCP 43 and DHCP 60 are both needed and ofcourse they combine together to send the controller IP address to a registering LAP. The DHCP server is configured for DHCP option 60 to know the Access points VCI string value. The DHCP option 43 is used to return the controller IP address in response to receiving a DHCP request from LAP specified in Option 60. Here is the CLI configuratione example:
http://www.cisco.com/en/US/docs/wireless/access_point/1500/installation/guide/1500_axg.html

Similar Messages

  • Multiple domains via DHCP (option 15)

    It seems Mac OS X (I use 10.4.10 but I suspect it affects many versions) is incompatible with receiving multiple domain names in a single string over DHCP Option 15.
    If DHCP returns Option 15 with "exampledomain.com eng.exampledomain.com", then any lookup (using dig, ping, Microsoft Entourage, etc.) of a non-fully qualified domain name will fail.
    You can see this in the /etc/resolv.conf file, which contains:
    domain exampledomain.com eng.exampledomain.com
    nameserver 10.X.X.1
    nameserver 10.X.X.2
    I know that putting multiple domains within the same "domain" option in DHCP is a proprietary hack but some networks still use this. Has anybody run into this and have they found a good resolution to make Mac OS X work with multiple domains?

    While a single mailbox can be configured to receive on multiple addresses (called "proxy addresses" or "aliases"), the mailbox is configured with only one primary SMTP address (outbound address).  So if your requirement is to send
    as the received address, you would not be able to do that with a single mailbox through normal means.
    Some people have developed a workaround to the above limitation by configuring Outlook to use multiple POP3 accounts for a single mailbox.  See this link for additional details: 
    http://blogs.technet.com/b/hot/archive/2012/04/26/how-to-add-an-alias-to-an-office-365-account-and-how-to-set-up-outlook-to-send-email-messages-as-this-alias.aspx
    I would also be sure to look at the client requirements for Exchange Online.  The supported version of Outlook is going to be Outlook 2010 SP2.  Older versions may work but would not be supported.  Outlook 2003 would at best possibly
    connect via POP3.
    Joseph Palarchio http://www.itworkedinthelab.com

  • Implement DHCP Option 60 in SPA100 series

    Hello,
    Is there any plan to implement DHCP Option 60(vendor class id) in SPA100 series devices in future FWs? CISCO SPA5xx series already has this option implemented.
    Regards,
    Josep.

    I'm not sure what exact device you mean saying "SPA100 series devices" but in SPA112 and SPA122 it is implemented already. I'm using it for long time. See catched packet:
        0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request
                Hostname Option 12, length 6: "SPA112"
                Vendor-Class Option 60, length 12: "CISCO SPA112"
    Don't forget to mark thread as answered if it answers your question ...

  • SPA122 - How to turn off "DHCP Option To Use" in the Provisioning tab using the XML configuration file?

    As default, SPA122 and SPA112 have DHCP Options 66, 160, 159 and 150 turned on.
    Our pre-provisioning process includes adding our default profile rule to our provisioning server for the device to pull its configuration files once the device has been added to an account.
    However, it seems like some customers have had problems with the device downloading the definite configuration file and manually turning off option Option 66 in the provisioning tab in the device solves this issue.
    Is there any option we could add to our pre-provisioning file so that it removes 66 from the "DHCP Option to Use" field in the provisioning tab?
    Please advise...

    Thanks Dan,
    I didn't know the dhcp server could serve different options to different classes of clients, I'll have to look that up!
    Moises
    so if your provisioning file has this line below (this is from a spa5xx config I had in my temp folder, so use the line from your provisioning file, or use the SPC tool to create a new default config for that device type)
    <DH<DHCP_Option_To_Use group="Provisioning/Configuration_Profile">66,160,159,150,60,43,125</DHCP_Option_To_Use>
    change it to
    <DH<DHCP_Option_To_Use group="Provisioning/Configuration_Profile">160,159,150,60,43,125</DHCP_Option_To_Use>
    Hope it helps,
    Provisioning guide is here
    Cisco IP Telephony Devices Provisioning Guide - Cisco Support Community
    Dan

  • DHCP Option Tags are not being applied...

    Hi,
    About to loose my mind... basically we are working towards a small WYSE Thin Client deployment in our environment.  The WYSE clients require to receive certain DHCP Option Tags to find the WCM server of which they receive their configuration from.  Same
    applies to the WDM Server as well.  The problem is no matter what we do, our test client is not receiving the custom option tags we've defined in our DHCP server.  
    DHCP Servers:
    vlan41
    10.40.1.206
    10.40.1.207
    Test Client:
    vlan46 - ip helpers defined on the switch
    Set to receive the same ip address from the DHCP server through the reservation route.
    Option Tags:
    186 - WDM Server - 10.40.1.184
    195 - WCM Server - 10.40.1.185
    196 - WCM Path - / 
    I've installed Wire Shark on the test client to monitor the DHCP activity.  The above custom options tags are not being pushed on to the client.  
    The Router, DNS Server and Domain Tags are being pushed.  So it's working but also not working????!!!
    Anybody with some insight to this problem?

    Hi hpaul_p
    In all fairness I'm about to give up... the vendor is not coming up with a solution and constantly blaming Microsoft.  To further test and confirm this wasn't a network issue, I've setup a secondary test environment using a 4 port switch, a client and
    a DHCP server.  Same results!!!  I'm really running out of time, so my work around is this:  I've setup a SRV records pointing to the WCM server... in your case this would be SRV record for the WDM server.  I've disabled the auto
    discovery functionality of the WDM Agent, for some reason it seems to be clashing with the WCM agent.  Since you will be using WDM only, don't disable auto discovery, tick the DNS SRV record from the Discovery Settings under the client agent. 
    I'm going to add the clients to the WDM server manually through their ip addresses so don't need auto discovery. From what I gather from the manuals the WCM searches for the repository or conifg servers in this order:  1. SRV 2.DNS (A record)
    3.DHCP (Options), I bet it's the same with WDM.  Though SRV and DNS methods has their limitations, if you will be using the default paths and credentials it shouldn't be a problem.  This is all I have have.  Steven Song I've forwarded you the
    DHCP database, if you find any problems with it please let me know.

  • Dnsmasq sends out its own ip as dns-server dhcp option

    Hi,
    i have a gateway / dns server on 192.168.1.1
    I have a dhcp server on 192.168.1.2 (dnsmasq)
    I configured dnsmasq to look into /etc/resolv.conf (well, that's actually default behavior) and use that to specify dns server when replying to client dhcp requests.
    However, it sends out its own ip instead, which is *not cool*.
    # cat /etc/resolv.conf
    nameserver 192.168.1.1
    #nameserver 127.0.0.1
    #nameserver 212.71.0.33
    # edpnet
    nameserver 212.71.0.33
    # grep -v ^# /etc/dnsmasq.conf | grep -v '^$'
    domain-needed
    bogus-priv
    dhcp-range=192.168.1.5,192.168.1.255,12h
    dhcp-host=q700
    dhcp-host=dieter-ws
    dhcp-host=dieter-dellD620-arch
    dhcp-host=gibran
    dhcp-host=hilde-compaq-arch
    dhcp-host=hilde-vbox-win
    dhcp-host=BRN_0441B3
    dhcp-option=option:router,192.168.1.1
    log-dhcp
    # cat /etc/hosts
    # /etc/hosts: static lookup table for host names
    #<ip-address> <hostname.domain.org> <hostname>
    127.0.0.1 localhost.localdomain localhost
    192.168.1.2 dieter-p4sci-arch server
    192.168.1.3 q700
    192.168.1.5 dieter-ws
    192.168.1.6 dieter-dellD620-arch
    192.168.1.7 dieter-delle5410-arch gibran
    192.168.1.8 hilde-compaq-arch
    192.168.1.9 hilde-vbox-win
    192.168.1.10 BRN_0441B3 hl5250
    178.79.146.162 dieter-linode1
    # End of file
    here's what I see in /var/log/daemon.log, when I start dnsmasq and do a dhcp request.
    Note the discrepancy between what it says as "using nameserver" and what it actually tells clients.
    Feb 12 18:10:50 dieter-p4sci-arch dnsmasq[2168]: started, version 2.55 cachesize 150
    Feb 12 18:10:50 dieter-p4sci-arch dnsmasq[2168]: compile time options: IPv6 GNU-getopt no-DBus no-I18N DHCP TFTP
    Feb 12 18:10:50 dieter-p4sci-arch dnsmasq-dhcp[2168]: DHCP, IP range 192.168.1.5 -- 192.168.1.255, lease time 12h
    Feb 12 18:10:50 dieter-p4sci-arch dnsmasq[2168]: reading /etc/resolv.conf
    Feb 12 18:10:50 dieter-p4sci-arch dnsmasq[2168]: using nameserver 212.71.0.33#53
    Feb 12 18:10:50 dieter-p4sci-arch dnsmasq[2168]: using nameserver 192.168.1.1#53
    Feb 12 18:10:50 dieter-p4sci-arch dnsmasq[2168]: read /etc/hosts - 10 addresses
    Feb 12 18:10:56 dieter-p4sci-arch dnsmasq-dhcp[2168]: 2764941049 available DHCP range: 192.168.1.5 -- 192.168.1.255
    Feb 12 18:10:56 dieter-p4sci-arch dnsmasq-dhcp[2168]: 2764941049 DHCPRELEASE(eth0) 192.168.1.5 80:ee:73:09:fa:94
    Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 available DHCP range: 192.168.1.5 -- 192.168.1.255
    Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 client provides name: dieter-ws
    Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 vendor class: dhcpcd-5.2.10:Linux-2.6.37-ARCH:i686:GenuineIntel
    Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 DHCPDISCOVER(eth0) 80:ee:73:09:fa:94
    Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 DHCPOFFER(eth0) 192.168.1.5 80:ee:73:09:fa:94
    Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 requested options: 1:netmask, 121:classless-static-route, 33:static-route,
    Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 requested options: 3:router, 6:dns-server, 12:hostname, 15:domain-name,
    Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 requested options: 26:mtu, 28:broadcast, 42:ntp-server, 51:lease-time,
    Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 requested options: 54:server-identifier, 58:T1, 59:T2, 119:domain-search
    Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 tags: known, eth0
    Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 next server: 192.168.1.2
    Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 1 option: 53:message-type 02
    Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 54:server-identifier 192.168.1.2
    Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 51:lease-time 00:00:a8:c0
    Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 58:T1 00:00:54:60
    Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 59:T2 00:00:93:a8
    Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 1:netmask 255.255.255.0
    Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 28:broadcast 192.168.1.255
    Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 6:dns-server 192.168.1.2
    Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 3:router 192.168.1.1
    Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 available DHCP range: 192.168.1.5 -- 192.168.1.255
    Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 client provides name: dieter-ws
    Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 vendor class: dhcpcd-5.2.10:Linux-2.6.37-ARCH:i686:GenuineIntel
    Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 DHCPREQUEST(eth0) 192.168.1.5 80:ee:73:09:fa:94
    Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 DHCPACK(eth0) 192.168.1.5 80:ee:73:09:fa:94 dieter-ws
    Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 requested options: 1:netmask, 121:classless-static-route, 33:static-route,
    Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 requested options: 3:router, 6:dns-server, 12:hostname, 15:domain-name,
    Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 requested options: 26:mtu, 28:broadcast, 42:ntp-server, 51:lease-time,
    Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 requested options: 54:server-identifier, 58:T1, 59:T2, 119:domain-search
    Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 tags: known, eth0
    Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 next server: 192.168.1.2
    Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 1 option: 53:message-type 05
    Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 54:server-identifier 192.168.1.2
    Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 51:lease-time 00:00:a8:c0
    Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 58:T1 00:00:54:60
    Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 59:T2 00:00:93:a8
    Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 1:netmask 255.255.255.0
    Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 28:broadcast 192.168.1.255
    Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 6:dns-server 192.168.1.2
    Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 9 option: 12:hostname dieter-ws
    Feb 12 18:11:00 dieter-p4sci-arch dnsmasq-dhcp[2168]: 3497735943 sent size: 4 option: 3:router 192.168.1.1

    1 yes, the dhcp server who's scope is full will not do a dhcp
    'offer'
    2 dhcp that answers fastest with a 'offer' will win. A delay is configurable (but changes nothing
    about the root scenario were the fastest will win)
    Note that if the scopes overlap on the servers, they might not lease out all the addresses in the scope.
    I would enlarge the scope as you will want to fence against unavailability of one of the servers (or a network connection for that matter). you currently have more addresses leased out than any set of two of your servers can offer.
    MCP/MCSA/MCTS/MCITP

  • DHCP Option 100 corrupt

    The DHCP option 100 "Middle Tier server" is configured and
    added on the scope under "Other DHCP Options".
    The values set for option 100 are two operable IP-addresses, reflecting
    two running Middle Tier servers
    Problem:
    When a client gets it's DHCP-address, the registry values for
    the Middle Tier server is corrupted.
    The registry keys hosting the values are (reference TID 10092121 for
    details):
    HKLM\Software\Novell\ZENworks\<dword> MiddleTierDHCPOptionNumber
    (we use decimal value 100 as Option number)
    HKLM\Software\Novell\ZENworks\<string> MiddleTierAddress
    (we use 192.168.1.4 and 192.168.1.5 in the DHCP-scope)
    But the Middle Tier login fails after DHCP delivery.
    Looking at the registry on the client, the string values for the
    MiddleTierAddressis corrupted. Instead of showing the two correct
    IP-addresses, it shows just messed up characters like squares,
    bars and other cryptical signs at the end of the enrty.
    Without a DHCP delivery, things works ok, if the ZfD Agent is configured
    with the Middle Tier DNS name.
    The registry key holding the DHCP-distributed Middle Tier address is:
    HKLM\Software\Novell\ZENworks\<string> MiddleTierAddress
    After DHCP-distribution, in the Middle Tier login dialog, the squares
    appears like bold vertical bars. Middle Tier login then fails.
    Also found a related TID # 10089967.

    See:
    "Workstation receives corrupted middle tier address when middle tier address
    is"
    http://support.novell.com/cgi-bin/se...i?10099553.htm
    I'm sure Shaun or one of the SysOps could tell you the status of this issue.
    Regards
    Rolf Lidvall
    Swedish Radio (Ltd)

  • DHCP Option 82 on Solaris 8

    If DHCP option 82 is supported, how can I add it to my server?

    Thanks, I upgraded software to newest 1.3.0.59, then rebooted. After configuring ( only option 82 - no relay agent ) there is still no 82 option in dhcp discover packets.
    Wireshark with captured dhcp discover broadcast packet. Dhcp part:
    As You can see - there is no 82 option.
    All interfaces are trusted (dhcp snooping).
    Should I configure anything else to make it work ?
    regards,

  • MDT/WDS PXE Deployment - DHCP Options for both x64 and x86

    Alright, I've found out the option 66 & 67 information, as what to set for each. The problem I'm trying to figure out is what to use for the boot file for option 67. So far all the info I've found says this:
    Configure DHCP option 67 with the right boot image file.
    For 32-bits systems \boot\x86\wdsnbp.com
    For 64-bits systems \boot\x64\wdsnbp.com
    I want to be able to use this for both 32 and 64 bit Windows clients, but cannot find anywhere that specifies how I would be able to do both.

    DHCP Options (specifically 067) can have a significant impact on which NBP your client can access.  If you specify \Boot\x86\Wdsnbp.com you are forcing the client to the 32bit NBP.
    If you specify \Boot\x64\Wdsnbp.com you are forcing the client to the 64bit NBP.
    Niether option is an ideal solution, especially if you have a varied environment.
    I would take a look at the following article and see if it sheds some light on your question:
    PXE booting with WDS – DHCP Scope vs IP Helpers

  • DHCP option 66

    I would love to just post in this thread:
    http://discussions.apple.com/thread.jspa?threadID=2347065
    But Apple likes to lock old threads and force you to start over...
    The indication in that thread is people did get this to work, but there is no final note of exactly how. So far we are finding it does not function properly. We're trying to set up a Fog server, but using the Mac server for DHCP. Unfortunately it fails to actually forward the client to the Fog server as needed. Here is what we have done:
    on the Mac server (10.6.4) edit the /etc/bootpd.plist
    below the array for dhcpdomainsearch and above the dhcp_router key, we insert the following:
    <key>dhcpoption66</key>
    <data>
    krp+CQ==
    </data>
    <key>dhcpoption67</key>
    <data>
    cHhlbGludXguMA==
    </data>
    These values are obtained using the DHCP Option Code Utility posted in the above thread with these inputs:
    Option Code Number: 66
    Option Code Type: IP
    Option Code Value: 146.186.126.9
    Option Code Number: 67
    Option Code Type: String
    Option Code Value: pxelinux.0
    When those didn't work, because the info in the noted thread was not clear, we also tried:
    Option Code Number: 66
    Option Code Type: String
    Option Code Value: 146.186.126.9
    Which gave us:
    <key>dhcpoption66</key>
    <data>
    MTQ2LjE4Ni4xMjYuOQ==
    </data>
    This also did not work. In every case the TFTP times out indicating option 66 is not defined or is not being followed correctly. It's a shame that unlike Microsoft, Apple has not included these common option controls in their server interface. We're hoping someone who has actually gotten this to work will see this and be able to clear up what Apple needs for input to make it actually work right.
    Thanks for any help!

    Hi, I am the author of the DHCP Option Code Utility and therefore the unofficial worldwide expert on Apple's DHCP Server
    If you go to http://www.sustworks.com/site/prodipmxoverview.html you can download a copy of IPNetMonitorX which includes a feature to test DHCP option codes. For example, you could test option 66 on a different make of DHCP Server (one that works) to see what exactly it returns, and then do the same test against Apple's DHCP Server and see if it is returning exactly the same result. Obviously if it returns a different result there is a problem.
    Note: IPNetmonitorX shows all DHCP option code results as decimal numbers (you need verbose logging turned on), you may therefore need to translate these to hex or ASCII values. One decimal number equals one hex number or one ASCII character.
    I can tell you that using DHCP Option Code Utility to generate the values, Apple's DHCP server works fine for many users needing to do this to support VoIP phone systems which also need to advertise a TFTP server.
    I have looked at your message and as far as I can see, your entry for Option67 is what I would believe to be correct. Obviously this field is not an Integer, nor is it an IP address, so using the String option is the only logical choice. For Option66, like your post, two choices spring to mind, the first being to use the IP address choice and the second the string choice. Again your examples are what I would use with my first choice being the IP address one.
    However there is one thing I can mention that may (or may not) help. An IP address for humans is written as 146.186.126.9 that is four decimal integers between 0 and 255 each separated by a full stop, if we break this down we have the following decimal integers
    146
    186
    126
    9
    in hexadecimal the above translates to
    92
    BA
    7E
    9
    Now the way Apple's DHCP Server actually stores IP addresses (ignoring the encoding you see) is actually as four hexadecimal bytes so if you use my utility to encode
    92 BA 7E 09
    as hexadecimal, you will find it results in the identical krp+CQ== result. Now apart from giving you some background which may help if/when you use IPNetMonitorX to test DHCP server option codes, what this also allows you to consider is that it maybe that some systems want these bytes in a different order. This relates to 'little endian' vs. 'big endian' see http://www.cs.umass.edu/~verts/cs32/endian.html
    I am somewhat doubtful of this, as all the VoIP systems I have dealt with use the same order equivalent to 146 186 126 9
    If your able to use IPNetMonitorX to query FOG's own DHCP server and give me the result, I can see what difference it is doing.
    Note: You should only have one DHCP server on a network at a time, so you should do this test on a standalone network or when you will not interfere with your live network.
    Note: You need to stop and start the Apple DHCP server in Server Admin to get it to re-read /etc/bootpd.plist and use your new settings. You should therefore stop the DHCP server while editing the file.
    UPDATE - NEWSFLASH
    Just retested my own Mac OS X 10.6.4 DHCP Server which has four DHCP option codes defined which were previously working. When I tried adding a copy of your option66, even with supposedly my DHCP Server 'stopped' it kept overwriting the changes I made. It maybe your server is also almost immediately overwriting and losing your option codes. Try doing it in single user mode or even booting from another disk and of course double check your bootpd.plist still lists your option codes.

  • Adding DHCP options into bootpd.plist

    Hello All,
    I'm having issues inserting DHCP options 66 and 67 into the /etc/bootpd.plist file. I'm a bit baffled by this task and it's not rocket science so I really don't understand why this is not working the way it should.
    Goal:
    I'm setting up a dual platform imaging server for the company I work for using DeployStudio. I have the mac side imaging 100% perfectly with no issues. Now, the PC side is a different story. I can get the PC machines to PXE boot just fine, DHCP IP address received, then continues to load the imaging applications console and then hangs with a tftp error.
    We are running Mountain Lion 10.8.4 and using OS X Server 2.2.1
    the options I added are 66 and 67.
    Option 66:
    10.10.10.2 is the IP address I want to use.
    Option 67:
    pxelinux.0
    I've added my bootpd.plist file below and bolded the data I entered into the file. I don't even know if I entered the data into the right place or it needs to go somewhere else. I really don't know if i'm inserting the correct data I need into options 66 and 67. I've sat there and read the man page for bootpd and it provided very little to no information on the topic.
    Thanks in advance!!
    ================================================================================ =======
    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
    <plist version="1.0">
    <dict>
            <key>NetBoot</key>
            <dict/>
            <key>Subnets</key>
            <array>
                    <dict>
                            <key>allocate</key>
                            <true/>
                            <key>dhcp_domain_name</key>
                            <string>no-dns-available.example.com</string>
                            <key>dhcp_domain_name_server</key>
                            <array>
                                    <string>0.0.0.0</string>
                            </array>
                            <key>dhcp_option_66</key>
                            <data>
                            CgoKAg==
                            </data>
                            <key>dhcp_option_67</key>
                            <data>
                            cHhlbGludXguMA==
                            </data>
                            <key>lease_max</key>
                            <integer>3600</integer>
                            <key>name</key>
                            <string>10.10.10 USB Ethernet</string>
                            <key>net_address</key>
                            <string>10.10.10.0</string>
                            <key>net_mask</key>
                            <string>255.255.255.0</string>
                            <key>net_range</key>
                            <array>
                                    <string>10.10.10.2</string>
                                    <string>10.10.10.253</string>
                            </array>
                            <key>selected_port_name</key>
                            <string>en1</string>
                            <key>uuid</key>
                            <string>EE34E237-9C59-42A9-BB26-9B54CEE66447</string>
                            <key>dhcp_option_66</key>
                            <data>
                            CgoKAg==
                            </data>
                            <key>dhcp_option_67</key>
                            <data>
                            cHhlbGludXguMA==
                            </data>
                    </dict>
            </array>
            <key>allow</key>
            <array/>
            <key>bootp_enabled</key>
            <false/>
            <key>deny</key>
            <array/>
            <key>detect_other_dhcp_server</key>
            <false/>
            <key>dhcp_enabled</key>
            <array>
                    <string>en1</string>
            </array>
            <key>old_netboot_enabled</key>
            <false/>
            <key>relay_enabled</key>
            <false/>
            <key>relay_ip_list</key>
            <array/>
            <key>timeServiceStarted</key>
            <string>2013-07-31 22:32:12 +0000</string>
    </dict>
    </plist>

    Hey John,
    Been reading many of your posts and they all seem quite helpful, but I'm also stuck trying to configure options 66 & 67.
    I'm running Server 3.1.2 on Mavericks, your utility to generate the options seems to work, but I'm not sure where to place them in the file, tried a few different locations without success.  Here is my current bootpd.plist:
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
    <plist version="1.0">
    <dict>
            <key>NetBoot</key>
            <dict>
                    <key>startTime</key>
                    <string>2014-06-30 18:29:49 +0000</string>
            </dict>
            <key>Subnets</key>
            <array>
                    <dict>
                            <key>allocate</key>
                            <true/>
                            <key>dhcp_domain_name</key>
                            <string>domain.ad</string>
                            <key>dhcp_domain_name_server</key>
                            <array>
                                    <string>172.16.10.10</string>
                                    <string>172.16.10.7</string>
                                    <string>8.8.8.8</string>
                            </array>
                             <key>dhcp_option_66</key>
                             <data>
                             rBAKEw==
                             </data>
                             <key>dhcp_option_67</key>
                             <data>
                             cHhlbGludXguMAA=
                             </data>
                            <key>dhcp_domain_search</key>
                            <array>
                                    <string>domain.ad</string>
                            </array>
                            <key>dhcp_router</key>
                            <string>172.16.8.1</string>
                            <key>lease_max</key>
                            <integer>3600</integer>
                            <key>name</key>
                            <string>172.16.8/22 Ethernet</string>
                            <key>net_address</key>
                            <string>172.16.8.0</string>
                            <key>net_mask</key>
                            <string>255.255.252.0</string>
                            <key>net_range</key>
                            <array>
                                    <string>172.16.8.10</string>
                                    <string>172.16.11.253</string>
                            </array>
                            <key>selected_port_name</key>
                            <string>bond0</string>
                            <key>uuid</key>
                            <string>0F3374EB-FDDA-4DCD-A8F8-E5CDFC661A99</string>
                    </dict>
            </array>
            <key>allow</key>
            <array/>
            <key>bootp_enabled</key>
            <false/>
            <key>deny</key>
            <array/>
            <key>detect_other_dhcp_server</key>
            <false/>
            <key>dhcp_enabled</key>
            <array>
                    <string>bond0</string>
            </array>
            <key>netboot_enabled</key>
            <array>
                    <string>bond0</string>
            </array>
            <key>old_netboot_enabled</key>
            <false/>
            <key>relay_enabled</key>
            <false/>
            <key>relay_ip_list</key>
            <array/>
            <key>timeServiceStarted</key>
            <string>2014-07-02 15:16:23 +0000</string>
    </dict>
    </plist>
    I have a Fog server handling my Windows imaging on 172.16.10.19, using pxelinux.0 (all tested through a TFTP client), but when I boot a Dell into PXE, it finds an IP address but the output for the TFTP server looks like this:
    TFTP.
    Then it just exits, before it should show the IP address of the TFTP server.
    I do have the option of using DHCP on a Windows Server VM, but I'd rather have my Mac Mini do it.

  • WLC "DHCP Option 82 Remote Id field format"

    On WLC, does "DHCP Option 82 Remote Id field format" show client hostname on wlc monitor

    Hi Jonathan with sub option 2, from your example D is the node identifier.
    When seeing the variable per connection type, I would give a safe assumption it is verbose padding the sub type 1.
    The verbose pad formatting for the packet should contain
    sub option
    length
    node identifier
    port type
    interface number
    vlan id
    For normal pad format it should contain
    sub option
    length
    circuit
    length
    vlan id
    interface number
    -Tom
    Please mark answered for helpful posts

  • How to query a DHCP option field?

    I am able to successfully define various DHCP Option codes for use with Apple's DHCP server and indeed I am the person who wrote a GUI utility to make it much easier to generate the data values needed to do this. The following is a typical example of what you need to (manually) add to /etc/bootpd.plist
    <key>dhcpoption66</key>
    <data>
    CgBklg==
    </data>
    I am also able to query specific DHCP option codes (as provided by Apple's DHCP server as above) using IPNetMonitorX from Sustainable Softworks. However it should I believe be possible to do the same tests via the command line in Terminal using the ipconfig getoption command, please see the "man ipconfig" page.
    While as an example "ipconfig getoption en0 router" works fine, I cannot seem to get the right syntax for querying a specific DHCP option code, despite the man page suggesting this should be possible. Unfortunately like nearly all man pages, the information is very skimpy and the examples practically non-existant.
    Could anyone reply with the correct syntax to query as an example DHCP option code 66?
    I suppose (gasp!) Apple could have a bug in ipconfig preventing the ability to query option codes. (Shock, horror!)

    MrHoffman wrote:
    When in doubt, use the source.
    The DHCP [client.c source code|http://www.opensource.apple.com/source/bootp/bootp-198.2/ipconfig.tproj/client.c] might be interesting here.
    The core of the option-related code looks to be over in the [dhcp_options.c source code|http://www.opensource.apple.com/source/bootp/bootp-198.2/bootplib/dhcp_options.c ?txt] and what looks to be the option tag table mapping is over in the [gendhcp_parsetable.h source code|http://www.opensource.apple.com/source/bootp/bootp-198.2/bootplib/gendhcp_parsetable.h].
    A quick read of the source files and particularly the routines command_info and Sgetoption and the tag table implies that the +ipconfig getoption en0 66+ command might work. Or maybe +ipconfig getoption en0 tftpservername+ will work.
    When I test this syntax, I get +ipconfiggetoption failed, (os/kern) failure+ and which obviously doesn't bode well for this syntax, but then I likely don't have any of the related stuff enabled on this test network. (And I'm only very quickly reading the C code here...)
    I have not found and viewed the source but I had tried that exact syntax (as per your example) and got the exact same error hence my comment that maybe (gasp!) there is a bug here.
    I have submitted a bugreporter entry and will have to wait and see if Apple reply.
    Thanks for the apparent confirmation.

  • SF302-08 - CLI configuration of dhcp option 66

    Hi,
    i'm trying to use cli to configure dhcp option 66 but i'm getting this error below.
    thanks
    switch702df6(config-dhcp)#ip dhcp pool network Voice
    switch702df6(config-dhcp)#option 66 ascii-string "http://provisioning.domain.tld/$MA.xml"
    % Wrong number of parameters or invalid range, size or characters entered

    Hi Luis, I do not believe option 66 is supported.
    1, 3, 4, 6, 12, 15, 44, 46, 50, 51, 53, 54 55, 56, 58, 59, and 61.
    If you remove the name of your file, you will notice the switch declares it is an unsupported option
    switchb28f36(config-dhcp)#option 66 ascii test
    Not supported option.
    -Tom
    Please mark answered for helpful posts

  • RV320: DHCP Option 82 + DHCP relay at Ethernet switch

    We purchased a RV320 router and want to use the DHCP Option 82 IP Assignment in combination with a ZyXEL GS1910-24 Smart Managed Switch.
    The switch is able to insert Option 82 Circuit-IDs into DHCP requests, if they are relayed to a specific DHCP server. So there must be configured exactly one IP address of the DHCP server in the switch configuration (eg 192.168.1.1). The problem is, that the RV320 creates different IP subnets for different Circuit-IDs. So the RV320-router has multiple IPs, one unique IP per subnet (192.168.1.1, 192.168.2.1, 192.168.3.1, ...).
    How can I use the Option 82 IP assignment with this configuration?
    Is a routing/firewall rule at the RV320 a solution (to forward DHCP requests from subnet specific IP - eg 192.168.3.1 - to exactly one IP, eg 192.168.1.1)?

    mpyhala,
    seems not to work as the RV320 is restricted to 6 custom VLANs (+ 1 Management VLAN with ID 1).
    Maybe I should describe the whole scenario, which should be implemented:
    The configuration is like for a small hotel: each room should be logically seperated from each other (no inter-room traffic for security) and each rooms bandwidth should be managed.
    Bandwidth management at the RV320 relies on IP addresses. So I need to achieve somehow, that a room (= port number on switch) is always assigned a specific IP address.
    14 rooms should be covered in that way.
    The problem is currently the link IP<->Switch Port. I thought DHCP option 82 is the way to go, but VLANs (one VLAN for each room) may be also a solution. Unfortunately none of the two ways work.
    What can be a solution? Was the RV320 the wrong decision (not enough flexibility)?
    Thanks.

Maybe you are looking for