Displaying 4 results from an estimated 4 matches for "dhcpnack".
Did you mean:
dhcpack
2008 Jun 14
5
PATCH: ipconfig may accept DHCPOFFER as DHCPACK
.../
---
> case 1: /* ACK received */
211c211
< case DHCPNAK: /* NAK received */
---
> case 2: /* NAK received */
diff dhcp_proto.c ../ipconfig.old/dhcp_proto.c:
74,78d73
< * Returns:
< * 0 = Not handled
< * 2 = DHCPOFFER (from dhcp_proto.h)
< * 5 = DHCPACK
< * 6 = DHCPNACK
109,110c104,105
< ret = bootp_parse(dev, hdr, exts, extlen) ? DHCPOFFER : 0;
< if (ret == DHCPOFFER && serverid != INADDR_NONE)
---
> ret = bootp_parse(dev, hdr, exts, extlen);
> if (ret == 1 && serverid != INADDR_NONE)
116c111
< ret = bootp_parse(dev, hdr,...
2008 Jun 14
2
PATCH: ipconfig may discard useful packets
...sr/kinit/ipconfig/dhcp_proto.c
+++ b/usr/kinit/ipconfig/dhcp_proto.c
@@ -72,7 +72,7 @@ static struct iovec dhcp_request_iov[] = {
/*
* Parse a DHCP response packet
* Returns:
- * 0 = Not handled
+ * 0 = Unexpected packet, not parsed
* 2 = DHCPOFFER (from dhcp_proto.h)
* 5 = DHCPACK
* 6 = DHCPNACK
@@ -128,8 +128,8 @@ static int dhcp_parse(struct netdev *dev, struct
bootp_hdr *hdr,
/*
* Receive and parse a DHCP packet
* Returns:
- *-1 = Error in packet_recv
- * 0 = Not handled
+ *-1 = Error in packet_recv, try again later
+ * 0 = Unexpected packet, discarded
* 2 = DHCPOFFER (from dhcp_...
2004 Jul 21
4
Bug#260743: logcheck-database: dhcp rule updates for failover support
...(\([._[:alnum:]-]+\) )?via [[:alnum:]]+$
# if you are paranoid, you'll want to skip these rules:
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dhcpd: DHCPREQUEST for [.0-9]+ (\([.0-9]+\) )?from [:[:alnum:]]+ (\([._[:alnum:]-]+\) )?via [[:alnum:]]+: wrong network.$
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dhcpd: DHCPNACK on [0-9.]+ to [[:alnum:]]+ via [[:alnum:]]+$
Thanks for your good work.
I'm expecting to get more rule updates soon. Should i submit them here or to
some mailing list?
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (1, &...
2011 Jul 08
4
[PATCH 0/4] usr/kinit checkpatch
Various coding style fixes checkpatch warns about.
The goal is not to be 100% checkpatch compliant,
but to have more consistent coding style.
As this is a trivial patch serie, will land in 24 hours in klibc git,
unless of course ml review hits a bugger.
Checked with size(3) that the generated kinit, fstype, ipconfig and
nfsmount are the same.
maximilian attems (4):
[klibc] ipconfig: reduce