Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: DHCP Site Specific Options?!?

> Jason,
>
> Thank you for the quick reply, but you completely lost me. I am far
> from unix savvy. I am just about GUI only. Would you know how to do
> what you described? Is it possible with the OSXS GUI? I could handle
> altering a few lines of a config file if I needed to, or is this way
> over my head?
>
> Mitchell

Your best bet would be to first talk with the manufacturer and confirm that
the extensions they are using conform to RFC2132. Assuming they do, they
should probably be able to help you out with the necessary directives to add
to your bootpd configuration. You'll most likely have to edit the
configuration files by hand (I'm not sure where OS X's bootpd stores its
configs off the top of my head). If the manufacturer isn't particularly Unix
savvy, it's a wonder they're in business ;) They should /at least/ be able
to confirm which RFC the extensions they are implementing fall under.

Really configuring this probably can't be done through the GUI. If OS X's
bootpd isn't sufficient, you can use the ISC DHCP daemon, which I've found
to be a bit more robust. Installing it is much like installing any other
Unix daemon, usually involves something like:

1) download the tarball (tar.gz file)
2) expand the tarball with the command "tar zxvf isc-dhcp-x.xx.tar.gz"
3) "cd isc-dhcp-x.xx" into the resulting folder
4) run the configure script, this is usually something like "./configure
PREFIX=/usr/local/isc-dhcp"
5) run make to build the program "make"
6) install the program using "sudo make install"
7) create a SystemStarter bundle to launch the daemon at
startup:(http://www.opensource.apple.com/projects/documentation/howto/html/S
ystemStarter_HOWTO.html)
8) Configure the daemon as necessary and then launch it.

If you're not Unix-savvy, there is a strong chance you'll encounter
difficulty in installing the ISC DHCP package. Configuring bootpd from the
command line shouldn't be too difficult even for someone who is not very
Unix-savvy.

--
JD


> On Wednesday, January 29, 2003, at 12:21 PM, Jason Deraleau wrote:
>
> >> I don't have clue....
> >>
> >> We are installing an Avaya IP Phone system. I have a G4 Tower running
> >> MacOSX Server 10.2.3. as a DHCP server. It won't serve addresses to
> >> our
> >> IP Phones. The Avaya Tech people say I need to set "Site Specific
> >> Option 176" on my DHCP server in order for it to serve the addresses
> >> to
> >> the phones. Can anyone explain this to me and share how in the world
> >> to
> >> do this on my G4.
> >
> > I found a document on Avaya's site at the link below, here's a quote:
> >
> > Option 176 includes:
> > - Gatekeeper Address (CLAN) and alternates
> > - TFTP Server
> > - QoS Parameters
> >
> > http://www1.avaya.com/enterprise/inaau/2002/annual/docs/724.pdf
> >
> > A man on bootpd (the daemon shipping with Mac OS X Server 10.2) shows
> > that
> > it supports RFC951, RFC1542, and RFC2132. Judging by the content of the
> > Avaya site, I think the Option 176 they're talking about is a part of
> > BOOTP
> > Extensions/DHCP Options, which are defined in RFC2132. If that's the
> > case,
> > you should be good with the bootpd shipping with OS X Server.
> >
> > If the extensions aren't encompassed in one of the RFCs mentioned
> > above, you
> > might have luck with the ISC DHCP daemon, which you can build and
> > install
> > manually on OS X Server if you are Unix savvy.
_______________________________________________
macos-x-server mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/macos-x-server
Do not post admin requests to the list. They will be ignored.


Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.