SUMMARY: A DHCP server on a DHCP Client (Sun never tested this)

I got one recommendation to use a third party DHCP server.  An option, but I
was hoping to get Sun's Software to work (The problem of adding more
variables, etc.)

Other than that, I haven't gotten any other suggestions or advice.

==================================================

On Fri, May 04, 2001 at 06:17:27PM -0400, Brett Thorson wrote:
> So I finally have Solaris x86 running on an Intel 810, with 2 Intel
network
> cards, with DHCP running.  Wow, I never thought I would get this far.
> (Thanks for everyone's help to get me here).
>
> Now for a little bug I found?
>
> I have 2 nic's in the same box.  iprb0 is a dhcp client, thus getting a
> different IP address everytime (well you get the idea, not everytime, but
> often enough to be an issue).  iprb1 is the nic that is connected to an
> internal network that only exists and is apparent to the machine.  (No
> routing from one to another).
>
> iprb0 (The card that is connected to the rest of the world) got assigned
the
> dhcp address 10.1.1.156
> iprb1 is a static 192.168.1.1 address.
>
> So I went ahead and used the dhcp setup utility to make a dhcp config for
my
> system.
> It made the /var/dhcp/192_168_1_0 entries as appropriate with the utility
> dhcpconfig
> In the file mentioned above I found a bunch of these:
> 00      00      192.168.1.11    10.1.1.155      0       unknown
>
> Notice the 10.1.1.155?
>
> I left it alone hoping it wouldn't be that big a deal..... Wrong.
>
> So the machine rebooted, and it got 10.1.1.156.  Everything started up
just
> fine, but then the DHCP server started spewing out
>  Datagram received on network device: iprb1
>  Client: 006035005F3E is requesting verification of address owned by
> 10.1.1.156
>  Datagram received on network device: iprb1
>  Client: 006035005F3E is RELEASEing: 0.0.0.0 not owned by this server.
>  Datagram received on network device: iprb1
>  Client: 006035005F3E has a configuration owned by server: 10.1.1.156.
>
> Whoops, doesn't look likes it appreciates a moving target.
>
> Ok, no problem.  So what happens if we swap 10.1.1.155 for 10.1.1.156
> Works just fine!
>
> Ok, so then I thought, well I do have one static IP address that I know
will
> always exist.  And what this thing needs to know about 10.1.1.15X is
beyond
> me, so why not change this entry to 192.168.1.1.
> I mean that is a valid IP address for this machine.
>
>  Datagram received on network device: iprb1
>  Client: 006035005F3E is RELEASEing: 0.0.0.0 not owned by this server.
>  Datagram received on network device: iprb1
>  Client: 006035005F3E has a configuration owned by server: 192.168.1.1.
>
> Gee, I wonder who 192.168.1.1 is.  Oh wait, that's ME!
>
> Any thoughts?
>
> Brett M. Thorson
> Eko Systems Inc.