Re: Unable to compile DHCP server on Solaris
- From: mike3 <mike4ty4@xxxxxxxxx>
- Date: Sat, 23 Feb 2008 15:29:12 -0800 (PST)
On Feb 23, 3:10 pm, Jeff Wieland <wiel...@xxxxxxxxxxxxxxxx> wrote:
In article <627d5790-c37e-40e2-beb4-4063dcbcf...@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> mike3 <mike4...@xxxxxxxxx> writes:
On Feb 23, 12:17 am, Dave Uhring <daveuhr...@xxxxxxxxx> wrote:
On Fri, 22 Feb 2008 22:50:59 -0800, mike3 wrote:
Forgot to mention it: the version I was using was the latest, 4.1.0a1. I
tried
4.0.0 before that, same problem.
Try dhcp-3.0.6.
Alright, I'll try it. Why don't the newer versions work though?
We're using dhcp 3.1.0 under Solaris 8 & 10 on SPARC -- they work
well and they are supported by other tools that generate the
config files. If you don't need IPv6 support, 3.1.0 should be
fine. You probably don't want to use the "USE_SOCKETS" option.
For one thing, it limits you to one interface on Solaris. The
site.h file says:
/* Define this to use the standard BSD socket API.
On many systems, the BSD socket API does not provide the ability to
send packets to the 255.255.255.255 broadcast address, which can
prevent some clients (e.g., Win95) from seeing replies. This is
not a problem on Solaris.
In addition, the BSD socket API will not work when more than one
network interface is configured on the server.
However, the BSD socket API is about as efficient as you can get, so if
the aforementioned problems do not matter to you, or if no other
API is supported for your system, you may want to go with it. */
/* #define USE_SOCKETS */
We sure don't use it.
I use it because of what is said in the README:
---
SOLARIS
One problem which has been observed and is not fixed in this
patchlevel has to do with using DLPI on Solaris machines. The symptom
of this problem is that the DHCP server never receives any requests.
This has been observed with Solaris 2.6 and Solaris 7 on Intel x86
systems, although it may occur with other systems as well. If you
encounter this symptom, and you are running the DHCP server on a
machine with a single broadcast network interface, you may wish to
edit the includes/site.h file and uncomment the #define USE_SOCKETS
line. Then type ``make clean; make''. As an alternative workaround,
it has been reported that running 'snoop' will cause the dhcp server
to start receiving packets. So the practice reported to us is to run
snoop at dhcpd startup time, with arguments to cause it to receive one
packet and exit.
snoop -c 1 udp port 67 > /dev/null &
The DHCP client on Solaris will only work with DLPI. If you run it
and it just keeps saying it's sending DHCPREQUEST packets, but never
gets a response, you may be having DLPI trouble as described above.
If so, we have no solution to offer at this time, aside from the above
workaround which should also work here.
---
See, it says to enable USE_SOCKETS if the DHCP server
does not recieve any requests, which seems like the trouble I was
having with it. (I'm using Solaris 10 on x86-64.). When I try to use
another machine on my net to call up the DHCP server, it doesn't
give anything out, the requests all go unanswered.
I tried the "snoop" thing and that didn't work, so I figured the next
option was to try USE_SOCKETS, and BOOM, I got the compile
failure.
.
- Follow-Ups:
- Re: Unable to compile DHCP server on Solaris
- From: Jeff Wieland
- Re: Unable to compile DHCP server on Solaris
- References:
- Re: Unable to compile DHCP server on Solaris
- From: mike3
- Re: Unable to compile DHCP server on Solaris
- From: Dave Uhring
- Re: Unable to compile DHCP server on Solaris
- From: mike3
- Re: Unable to compile DHCP server on Solaris
- From: Jeff Wieland
- Re: Unable to compile DHCP server on Solaris
- Prev by Date: Re: Preventing serial break (OBP)
- Next by Date: Re: Is there any way given a a.out
- Previous by thread: Re: Unable to compile DHCP server on Solaris
- Next by thread: Re: Unable to compile DHCP server on Solaris
- Index(es):
Relevant Pages
|