*** From dhcp-server -- To unsubscribe, see the end of this message. ***
This is EXACTLY the same problem that I had with dhcrelay.
I believe that your "fix", which has the same effect the one that I used,
is fine. As I analyze things, the relays get involved ONLY when the
client broadcasts. (If the client unicasts to the server, the relay code
is not involved). As you note, MS clients fail unless you broadcast the
reply.
On Wed, 17 Mar 1999 [EMAIL PROTECTED] wrote:
> Interesting problem I ran into when I went from pl6 to pl18.
> Many of my clients out on subnets (mostly microsoft) stopped
> receiving lease renewals. They could request a lease, but
> the renew failed (worked fine under pl6). After digging around,
> I tracked it down to the common/socket.c lib which
> always returns a 0 from the can_unicast_without_arp()
> function, which is called from dhcp.c when sending out
> a DHCPACK. With the function returning false, the packet
> was sent via broadcast, instead of unicast, so the subnet
> router dropped it. My "fix", cough, was to change the return status
> from can_unicast_without_arp to 1 and now everything
> seems to work ok. My fear is that false was set for a reason,
> what did I just break? The comments discuss the process
> of clients doing unicast renewal, which should turn to a
> broadcast DISCOVER when the renewal fails...looks like this
> is broke with MS clients? Yes, the routers are setup to
> propagate DHCP requests from clients to server, which is
> how the initial DISCOVER is serviced.
------------------------------------------------------------------------------
To unsubscribe from this list, please visit http://www.fugue.com/dhcp/lists
If you are without web access, or if you are having trouble with the web page,
please send mail to [EMAIL PROTECTED] Please try to use the web
page first - it will take a long time for your request to be processed by hand.
------------------------------------------------------------------------------
