Skip to content
GitLab
Menu
Projects
Groups
Snippets
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Menu
Open sidebar
ISC Open Source Projects
dhcp
Commits
164f9c7e
Commit
164f9c7e
authored
Mar 07, 2000
by
Ted Lemon
Browse files
Fix corner case where REBIND would be ignored rather than NAKed.
parent
cb9cf4bd
Changes
1
Hide whitespace changes
Inline
Side-by-side
server/dhcp.c
View file @
164f9c7e
...
...
@@ -22,7 +22,7 @@
#ifndef lint
static
char
copyright
[]
=
"$Id: dhcp.c,v 1.14
0
2000/03/0
6 23:33:52
mellon Exp $ Copyright (c) 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium. All rights reserved.
\n
"
;
"$Id: dhcp.c,v 1.14
1
2000/03/0
7 02:50:45
mellon Exp $ Copyright (c) 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium. All rights reserved.
\n
"
;
#endif
/* not lint */
#include "dhcpd.h"
...
...
@@ -215,7 +215,10 @@ void dhcprequest (packet, ms_nulltp)
If ciaddr was specified and Requested Address was not, then
we really only know for sure what network a packet came from
if it came through a BOOTP gateway - if it came through an
IP router, we'll just have to assume that it's cool.
IP router, we can't respond. However, a client in REBINDING
state with the wrong IP address will also look like this, and
this is more likely, so we NAK these packets - if the packet
came through a router, the NAK won't reach the client anyway.
If we don't think we know where the packet came from, it
came through a gateway from an unknown network, so it's not
...
...
@@ -251,6 +254,7 @@ void dhcprequest (packet, ms_nulltp)
if
(
!
packet
->
shared_network
||
(
packet
->
raw
->
ciaddr
.
s_addr
&&
packet
->
raw
->
giaddr
.
s_addr
)
||
(
!
oc
&&
packet
->
raw
->
ciaddr
.
s_addr
)
||
(
oc
&&
!
packet
->
raw
->
ciaddr
.
s_addr
))
{
/* If we don't know where it came from but we do know
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment