dhcp issueshttps://gitlab.isc.org/isc-projects/dhcp/-/issues2019-12-09T13:20:38Zhttps://gitlab.isc.org/isc-projects/dhcp/-/issues/51ldap.c won't compile under ubuntu 182019-12-09T13:20:38ZGhost Userldap.c won't compile under ubuntu 18There's an error in ldap.c which Ubuntu 18 catches. srvaddr[0] is a pointer. You can't validly compare it to '\0'. Here's my fix, but it really depends upon what the author actually intended the code to do.
Here's how srvaddr is iniitia...There's an error in ldap.c which Ubuntu 18 catches. srvaddr[0] is a pointer. You can't validly compare it to '\0'. Here's my fix, but it really depends upon what the author actually intended the code to do.
Here's how srvaddr is iniitialized:
```
char srvaddr[2][64] = {"\0", "\0"};
```
I'm pretty sure this means we don't need to test for the srvaddr[0] being null, but rather for them pointing to a string containing two bytes of 0.
```
@@ -925,7 +926,7 @@ ldap_parse_failover (struct ldap_config_stack *item, struct parse *cfile)
ldap_value_free_len (tempbv);
- if (primary == -1 || srvaddr[0] == '\0' || srvaddr[1] == '\0')
+ if (primary == -1 || srvaddr[0][0] == '\0' || srvaddr[1][0] == '\0')
{
log_error("Could not decide if the server type is primary"
" or secondary for failover peering '%s'.", peername[0]->bv_val);
```Thomas MarkwalderThomas Markwalderhttps://gitlab.isc.org/isc-projects/dhcp/-/issues/53dhclient v4.4.1 - REQUIRE(ctx->running) assertion triggered on SIGTERM/SIGINT2019-11-18T16:52:56ZGhost Userdhclient v4.4.1 - REQUIRE(ctx->running) assertion triggered on SIGTERM/SIGINT---
name: REQUIRE(ctx->running) assertion triggered on SIGTERM/SIGINT
about: dhclient v4.4.1
---
**Describe the bug**
We noticed that sometimes, under heavy load, when SIGTERM/SIGINT is sent to dhclient, the following ASSERT is trig...---
name: REQUIRE(ctx->running) assertion triggered on SIGTERM/SIGINT
about: dhclient v4.4.1
---
**Describe the bug**
We noticed that sometimes, under heavy load, when SIGTERM/SIGINT is sent to dhclient, the following ASSERT is triggered:
```
...lib/isc/unix/app.c:574: REQUIRE(ctx->running) failed, back trace
#0 0x59355e in ??
#1 0x5936ea in ??
#2 0x5b4492 in ??
#3 0x7f20d70f0560 in ??
#4 0x7f20d71758f0 in ??
#5 0x7f20d71757a4 in ??
#6 0x42486c in ??
#7 0x40a39a in ??
#8 0x7f20d70dd6b0 in ??
#9 0x40ae39 in ??
Aborted
```
If the SIGTERM/SIGINT signal is sent during startup, in the small window interval between signal handler registration and the moment when ctx->running is set to 1, the REQUIRE(ctx->running) assertion is triggered.
Please let us know if any additional info is required.4.4.2Thomas MarkwalderThomas Markwalderhttps://gitlab.isc.org/isc-projects/dhcp/-/issues/54One NIC with a subnet for known clients and another one for unknown clients2019-09-25T11:02:26ZGhost UserOne NIC with a subnet for known clients and another one for unknown clientsI'd like on one network card to manage two subnets:
- One dedicated to known clients
- One dedicated to unknown clients
Then, I'd be able to build on my router some iptable rules to limit unknown client’s access to the other subnet.
In...I'd like on one network card to manage two subnets:
- One dedicated to known clients
- One dedicated to unknown clients
Then, I'd be able to build on my router some iptable rules to limit unknown client’s access to the other subnet.
In the current implementation of ISC DHCPD, I can only isolate guests on a pool in a subnet:
Known clients in a range, 192.168.0.1 -> 192.168.0.10
Unknown clients in another range of the same subnet, 192.168.0.11 -> 192.168.0.20
My router can’t filter packets since there is only one subnet
Expected configuration:
```
shared-network xxx {
subnet xxx ... {
...
deny unknown-clients;
}
subnet yyy ... {
allow unknown-clients;
}
}
```https://gitlab.isc.org/isc-projects/dhcp/-/issues/55ISC-DHCP-server service failed to start after the installation of NetSUS2019-10-24T14:46:09ZGhost UserISC-DHCP-server service failed to start after the installation of NetSUSDear, sir / madam
I installed NetSUS last night. The next day when I woke up, I found that my clients are not able to get IP address from my ISC-DHCP service. I check the status of the ISC-DHCP service and it is failed. I noticed that a...Dear, sir / madam
I installed NetSUS last night. The next day when I woke up, I found that my clients are not able to get IP address from my ISC-DHCP service. I check the status of the ISC-DHCP service and it is failed. I noticed that after the installation of NetSUS, there is a new dhcpd.conf file created (`/etc/dhcpd.conf`).
Here is the installation brief log of NetSUS.
```
sudo ./NetSUSLPInstaller_5.0.1.run
Verifying archive integrity... All good.
Uncompressing NetSUSLP Installer..............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
Starting the NetSUS Installation
Checking installation requirements...
Checking for a 64-bit OS...OK
Checking for a supported OS...Ubuntu 18.04.2 LTS found
Warning: Ubuntu 18.04 support is currently experimental, proceed with caution.
Checking for required Ubuntu binaries...OK
Passed all requirements
The following will be installed
* Appliance Web Interface
* File Sharing
* Software Update Server
* NetBoot Server
* LDAP Proxy
Proceed? (y/n): y
Installing...
Starting Web Application Installation
Restarting apache...
OK
Finished deploying the appliance web application
Starting NetBoot Installation
OK
Finished deploying NetBoot
Starting SUS Installation
OK
Finished deploying SUS
Starting LDAP Proxy Installation
OK
Finished deploying the LDAP Proxy
The NetSUSLP has been installed.
Verify that port 443 and 80 are not blocked by a firewall.
Note: IP Helpers are required if using NetBoot across subnets.
The NetBoot folder name can not contain any spaces
To complete the installation, open a web browser and navigate to https://server:443/.
If you are installing NetSUSLP for the first time, please follow the documentation for setup instructions.
```
Here is the status of my ISC-DHCP-Server
```
sudo systemctl status isc-dhcp-server
● isc-dhcp-server.service - ISC DHCP IPv4 server
Loaded: loaded (/lib/systemd/system/isc-dhcp-server.service; enabled; vendor
Active: failed (Result: exit-code) since Fri 2019-10-04 05:09:22 UTC; 17s ago
Docs: man:dhcpd(8)
Process: 10255 ExecStart=/bin/sh -ec CONFIG_FILE=/etc/dhcp/dhcpd.conf;
Main PID: 10255 (code=exited, status=1/FAILURE)
Oct 04 05:09:22 server dhcpd[10255]: If you intend to request help from the dhcp
Oct 04 05:09:22 server dhcpd[10255]: mailing list, please read the section on th
Oct 04 05:09:22 server dhcpd[10255]: submitting bug reports and requests for hel
Oct 04 05:09:22 server dhcpd[10255]:
Oct 04 05:09:22 server dhcpd[10255]: Please do not under any circumstances send
Oct 04 05:09:22 server dhcpd[10255]: help directly to the authors of this softwa
Oct 04 05:09:22 server dhcpd[10255]: send them to the appropriate mailing list a
Oct 04 05:09:22 server dhcpd[10255]: the README file.
Oct 04 05:09:22 server dhcpd[10255]:
Oct 04 05:09:22 server dhcpd[10255]: exiting.
```
It must have been caused by NetSUS. Seems the ISC-DHCP service has never failed before. I want to use both NetSUS and ISC-DHCP. Thank you.
Tomhttps://gitlab.isc.org/isc-projects/dhcp/-/issues/57Fix reference count leaks2020-01-14T08:15:10ZThomas MarkwalderFix reference count leaksFix leaks reported in #44.Fix leaks reported in #44.4.4.2Thomas MarkwalderThomas Markwalderhttps://gitlab.isc.org/isc-projects/dhcp/-/issues/58undocumented "option routers false;" usefull - should be documented2019-10-16T16:45:32ZGhost Userundocumented "option routers false;" usefull - should be documented* isc-dhcpd-4.3.5
* dhcpd.conf
Dear ISC-Maintainers,
in my network there is one single host named "gw" that itself is a gateway. I could give it a static ip - but i want it to be a normal DHCP-Client. But sending a standard-route to "...* isc-dhcpd-4.3.5
* dhcpd.conf
Dear ISC-Maintainers,
in my network there is one single host named "gw" that itself is a gateway. I could give it a static ip - but i want it to be a normal DHCP-Client. But sending a standard-route to "gw" makes no sense, more than this, it confuses this gateway routing ip-traffic back to the default-router used in the dhcpd-network. So i searched for a possibility to supress isc-dhcpd from sending a router-ip to this special host. This worked:
option routers 192.168.1.1;
[... hundred hosts ...]
host gw {
option host-name "gw";
hardware ethernet b8:27:eb:dd:fa:77;
fixed-address gw;
**option routers false;**
}
This is very usefull -- but undocumented, please document this in man dhcpd.conf.
Andreashttps://gitlab.isc.org/isc-projects/dhcp/-/issues/59Add support for DDNS updates to non-standard port2020-02-13T13:44:39ZhlmtreAdd support for DDNS updates to non-standard port---
name: DDNS update to non-standard port
about: Add support for sending to non-standard DNS port (not 53) for DDNS updates
---
**Some initial questions**
- Are you sure your feature is not already implemented in the latest ISC DHCP v...---
name: DDNS update to non-standard port
about: Add support for sending to non-standard DNS port (not 53) for DDNS updates
---
**Some initial questions**
- Are you sure your feature is not already implemented in the latest ISC DHCP version?
- Are you sure your feature is not already implemented in the latest Kea version? Perhaps it's a
good time to consider migration?
- Are you sure what you would like to do is not possible using some other mechanisms?
- Have you discussed your idea on dhcp-users or dhcp-workers mailing lists?
**Is your feature request related to a problem? Please describe.**
Currently it is impossible to specify the port to send DNS updates to in the `dhcpd.conf` file for a zone.
**Describe the solution you'd like**
Add the ability to specify the port to send the DDNS update notice to. `nsupdate` can currently do this.
**Describe alternatives you've considered**
I ended up setting up the primary DNS server on a secondary address on the standard port so DDNS updates could be performed. I also considered using `iptables` to remap the outgoing request.
**Additional context**
Example of what relevant `dhcpd.conf` might look like:
```
zone lan.my.example.com {
primary 192.168.6.4;
port 5300;
key dnsupdate;
}
```
**Funding its development**
ISC DHCP is run by ISC, which is a small non-profit organization without any government funding or
any permanent sponsorship organizations. Are you able and willing to participate financially in the
development costs? Can't contribute financially at the moment.
**Participating in development**
Are you willing to participate in the feature development? ISC team always tries to make a feature
as generic as possible, so it can be used in wide variety of situations. That means the proposed
solution may be a bit different that you initially thought. Are you willing to take part in the
design discussions? Are you willing to test an unreleased engineering code?
**Yes, absolutely.**
**Contacting you**
How can ISC reach you to discuss this matter further? If you do not specify any means such as
e-mail, jabber id or a telephone, we may send you a message on github with questions when we have
them.
hellmitre@gmail.comOutstandinghttps://gitlab.isc.org/isc-projects/dhcp/-/issues/60DHCP IP addresses conflicting2019-10-29T19:30:37ZGhost UserDHCP IP addresses conflictingMy Mac continuously get this error:
> Another device on the network is using your computer’s IP address (10.0.0.21).
It happens before I added a MAC-IP address reflection rule. There is no another device applying for the IP address of...My Mac continuously get this error:
> Another device on the network is using your computer’s IP address (10.0.0.21).
It happens before I added a MAC-IP address reflection rule. There is no another device applying for the IP address of 10.0.0.21, but my Mac cannot get IP from my ISC-DHCP server.
It also happens after I combine my Mac's MAC to the IP address of 10.0.0.21.
To restart the ISC-DHCP-server service is of no use. The only way to solve this issue is to restart the whole server.
Tom
Update on Oct 24
![Screen_Shot_2019-10-24_at_10.38.56_PM](/uploads/2d4d4bc74b117d7fc11d23a62274d7f7/Screen_Shot_2019-10-24_at_10.38.56_PM.png)
The Mac's system log says the dhcpd server takes the IP address for which the Mac is trying to get.https://gitlab.isc.org/isc-projects/dhcp/-/issues/61dhcp-4.4.1 build fails with "make -j16"2019-12-09T14:51:02ZGhost Userdhcp-4.4.1 build fails with "make -j16"---
name: dhcp-4.4.1 build fails with "make -j16"
about: dhcp failed build
---
**Describe the bug**
The build fails with "make -j16".
**To Reproduce**
Steps to reproduce the behavior:
1. wget https://downloads.isc.org/isc/dhcp/4.4.1/d...---
name: dhcp-4.4.1 build fails with "make -j16"
about: dhcp failed build
---
**Describe the bug**
The build fails with "make -j16".
**To Reproduce**
Steps to reproduce the behavior:
1. wget https://downloads.isc.org/isc/dhcp/4.4.1/dhcp-4.4.1.tar.gz
2. tar -xzf dhcp-4.4.1.tar.gz
3. cd dhcp-4.4.1/
4. ./configure
5. make -j16
Making all in ./bind
make[1]: Entering directory '/home/andrei/dhcp-4.4.1/bind'
Building BIND libraries - this takes some time.
/bin/sh: 6: cd: can't cd to /home/andrei/dhcp-4.4.1/bind/bind-9.11.2-P1/lib/isc
Building isc library in /home/andrei/dhcp-4.4.1/bind
/bin/sh: 6: cd: can't cd to /home/andrei/dhcp-4.4.1/bind/bind-9.11.2-P1/lib/isc
/bin/sh: 6: cd: can't cd to /home/andrei/dhcp-4.4.1/bind/bind-9.11.2-P1/lib/isc
/bin/sh: 6: cd: can't cd to /home/andrei/dhcp-4.4.1/bind/bind-9.11.2-P1/lib/isc
/bin/sh: 6: cd: can't cd to /home/andrei/dhcp-4.4.1/bind/bind-9.11.2-P1/lib/isc
/bin/sh: 6: cd: can't cd to /home/andrei/dhcp-4.4.1/bind/bind-9.11.2-P1/lib/isc
/bin/sh: 7: ./configure: Text file busy
make[6]: *** [Makefile:42: bind1] Error 2
make[6]: *** Waiting for unfinished jobs....
/bin/sh: 6: cd: can't cd to /home/andrei/dhcp-4.4.1/bind/bind-9.11.2-P1/lib/isc
/bin/sh: 7: ./configure: Text file busy
make[7]: *** [Makefile:42: bind1] Error 2
make[7]: *** Waiting for unfinished jobs....
tar: bind-9.11.2-P1/configure: Cannot open: File exists
/bin/sh: 6: cd: can't cd to /home/andrei/dhcp-4.4.1/bind/bind-9.11.2-P1/lib/isc
tar: bind-9.11.2-P1/isc-config.sh.in: Cannot open: File exists
/bin/sh: 6: cd: can't cd to /home/andrei/dhcp-4.4.1/bind/bind-9.11.2-P1/lib/isc
/bin/sh: 6: cd: can't cd to /home/andrei/dhcp-4.4.1/bind/bind-9.11.2-P1/lib/isc
tar: bind-9.11.2-P1/util/mksymtbl.pl: Cannot open: File exists
tar: bind-9.11.2-P1/unit/Makefile.in: Cannot open: File exists
tar: bind-9.11.2-P1/unit/unittest.sh.in: Cannot open: File exists
/bin/sh: 6: cd: can't cd to /home/andrei/dhcp-4.4.1/bind/bind-9.11.2-P1/lib/isc
/bin/sh: 6: cd: can't cd to /home/andrei/dhcp-4.4.1/bind/bind-9.11.2-P1/lib/isc
/bin/sh: 6: cd: can't cd to /home/andrei/dhcp-4.4.1/bind/bind-9.11.2-P1/lib/isc
tar: bind-9.11.2-P1/unit/atf-src/doc/atf-formats.5: Cannot open: File exists
tar: bind-9.11.2-P1/unit/atf-src/doc/atf.7.in: Cannot open: File exists
/bin/sh: 6: cd: can't cd to /home/andrei/dhcp-4.4.1/bind/bind-9.11.2-P1/lib/isc
/bin/sh: 6: cd: can't cd to /home/andrei/dhcp-4.4.1/bind/bind-9.11.2-P1/lib/isc
make[17]: *** No rule to make target 'all'. Stop.
make[17]: *** No rule to make target 'all'. Stop.
make[17]: *** No rule to make target 'all'. Stop.
make[17]: *** No rule to make target 'all'. Stop.
make[17]: *** No rule to make target 'install'. Stop.
make[17]: *** No rule to make target 'install'. Stop.
make[17]: *** No rule to make target 'install'. Stop.
make[17]: *** No rule to make target 'install'. Stop.
make[16]: *** [Makefile:76: bind2] Error 2
make[16]: *** Waiting for unfinished jobs....
tar: bind-9.11.2-P1/lib/dns/rdata/generic/proforma.h: Cannot open: File exists
tar: bind-9.11.2-P1/bin/tests/system/rsabigexponent/Makefile.in: Cannot open: File exists
tar: bind-9.11.2-P1/bin/tests/system/masterfile/ns1/named.conf: Cannot open: File exists
cat: conftest.er1: No such file or directory
tar: Exiting with failure status due to previous errors
make[3]: *** [Makefile:41: bind1] Error 2
make[3]: *** Waiting for unfinished jobs....
tar: Exiting with failure status due to previous errors
make[5]: *** [Makefile:41: bind1] Error 2
make[5]: *** Waiting for unfinished jobs....
tar: Exiting with failure status due to previous errors
make[2]: *** [Makefile:41: bind1] Error 2
make[2]: *** Waiting for unfinished jobs....
configure: error: in `/home/andrei/dhcp-4.4.1/bind/bind-9.11.2-P1':
configure: error: C compiler cannot create executables
See `config.log' for more details
tar: Exiting with failure status due to previous errors
make[1]: *** [Makefile:41: bind1] Error 2
make[1]: *** Waiting for unfinished jobs....
configure: error: in `/home/andrei/dhcp-4.4.1/bind/bind-9.11.2-P1':
configure: error: C compiler cannot create executables
See `config.log' for more details
configure: error: in `/home/andrei/dhcp-4.4.1/bind/bind-9.11.2-P1':
configure: error: C compiler cannot create executables
See `config.log' for more details
sed: can't read conftest.c: No such file or directory
configure: error: in `/home/andrei/dhcp-4.4.1/bind/bind-9.11.2-P1':
configure: error: C compiler cannot create executables
See `config.log' for more details
make[11]: *** [Makefile:42: bind1] Error 77
make[11]: *** Waiting for unfinished jobs....
cat: confdefs.h: No such file or directory
make[9]: *** [Makefile:42: bind1] Error 77
make[9]: *** Waiting for unfinished jobs....
make[16]: *** [Makefile:42: bind1] Error 77
cat: confdefs.h: No such file or directory
make[16]: *** No rule to make target 'all'. Stop.
make[16]: *** No rule to make target 'all'. Stop.
cat: confdefs.h: No such file or directory
make[16]: *** No rule to make target 'all'. Stop.
configure: error: in `/home/andrei/dhcp-4.4.1/bind/bind-9.11.2-P1':
configure: error: cannot compute suffix of executables: cannot compile and link
See `config.log' for more details
make[16]: *** No rule to make target 'install'. Stop.
make[16]: *** No rule to make target 'install'. Stop.
make[16]: *** No rule to make target 'install'. Stop.
make[16]: *** No rule to make target 'install'. Stop.
make[15]: *** [Makefile:76: bind2] Error 2
make[15]: *** Waiting for unfinished jobs....
configure: error: in `/home/andrei/dhcp-4.4.1/bind/bind-9.11.2-P1':
configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details
make[15]: *** [Makefile:42: bind1] Error 77
configure: error: in `/home/andrei/dhcp-4.4.1/bind/bind-9.11.2-P1':
configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details
make[15]: *** No rule to make target 'all'. Stop.
make[15]: *** No rule to make target 'all'. Stop.
make[15]: *** No rule to make target 'all'. Stop.
make[15]: *** No rule to make target 'install'. Stop.
make[15]: *** No rule to make target 'install'. Stop.
make[15]: *** No rule to make target 'install'. Stop.
make[15]: *** No rule to make target 'install'. Stop.
make[14]: *** [Makefile:76: bind2] Error 2
make[14]: *** Waiting for unfinished jobs....
configure: error: in `/home/andrei/dhcp-4.4.1/bind/bind-9.11.2-P1':
configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details
make[12]: *** [Makefile:42: bind1] Error 1
make[12]: *** Waiting for unfinished jobs....
configure: error: in `/home/andrei/dhcp-4.4.1/bind/bind-9.11.2-P1':
configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details
cat: confdefs.h: No such file or directory
make[8]: *** [Makefile:42: bind1] Error 1
make[8]: *** Waiting for unfinished jobs....
make[14]: *** [Makefile:42: bind1] Error 1
make[14]: *** No rule to make target 'all'. Stop.
make[14]: *** No rule to make target 'all'. Stop.
make[14]: *** No rule to make target 'all'. Stop.
make[14]: *** No rule to make target 'install'. Stop.
make[14]: *** No rule to make target 'install'. Stop.
make[14]: *** No rule to make target 'install'. Stop.
make[14]: *** No rule to make target 'install'. Stop.
make[13]: *** [Makefile:76: bind2] Error 2
make[13]: *** Waiting for unfinished jobs....
make[10]: *** [Makefile:42: bind1] Error 1
make[10]: *** Waiting for unfinished jobs....
make[13]: *** [Makefile:42: bind1] Error 1
make[13]: *** No rule to make target 'all'. Stop.
make[13]: *** No rule to make target 'all'. Stop.
make[13]: *** No rule to make target 'all'. Stop.
make[13]: *** No rule to make target 'install'. Stop.
make[13]: *** No rule to make target 'install'. Stop.
make[13]: *** No rule to make target 'install'. Stop.
make[13]: *** No rule to make target 'install'. Stop.
make[12]: *** [Makefile:76: bind2] Error 2
make[12]: *** No rule to make target 'all'. Stop.
make[12]: *** No rule to make target 'all'. Stop.
make[12]: *** No rule to make target 'all'. Stop.
make[12]: *** No rule to make target 'install'. Stop.
make[12]: *** No rule to make target 'install'. Stop.
make[12]: *** No rule to make target 'install'. Stop.
make[12]: *** No rule to make target 'install'. Stop.
make[11]: *** [Makefile:76: bind2] Error 2
make[11]: *** No rule to make target 'all'. Stop.
make[11]: *** No rule to make target 'all'. Stop.
make[11]: *** No rule to make target 'all'. Stop.
make[11]: *** No rule to make target 'install'. Stop.
make[11]: *** No rule to make target 'install'. Stop.
make[11]: *** No rule to make target 'install'. Stop.
make[11]: *** No rule to make target 'install'. Stop.
make[10]: *** [Makefile:76: bind2] Error 2
make[10]: *** No rule to make target 'all'. Stop.
make[10]: *** No rule to make target 'all'. Stop.
make[10]: *** No rule to make target 'all'. Stop.
make[10]: *** No rule to make target 'install'. Stop.
make[10]: *** No rule to make target 'install'. Stop.
make[10]: *** No rule to make target 'install'. Stop.
make[10]: *** No rule to make target 'install'. Stop.
make[9]: *** [Makefile:76: bind2] Error 2
make[9]: *** No rule to make target 'all'. Stop.
make[9]: *** No rule to make target 'all'. Stop.
make[9]: *** No rule to make target 'all'. Stop.
make[9]: *** No rule to make target 'install'. Stop.
make[9]: *** No rule to make target 'install'. Stop.
make[9]: *** No rule to make target 'install'. Stop.
make[9]: *** No rule to make target 'install'. Stop.
make[8]: *** [Makefile:76: bind2] Error 2
make[8]: *** No rule to make target 'all'. Stop.
make[8]: *** No rule to make target 'all'. Stop.
make[8]: *** No rule to make target 'all'. Stop.
make[8]: *** No rule to make target 'install'. Stop.
make[8]: *** No rule to make target 'install'. Stop.
make[8]: *** No rule to make target 'install'. Stop.
make[8]: *** No rule to make target 'install'. Stop.
make[7]: *** [Makefile:76: bind2] Error 2
make[7]: *** No rule to make target 'all'. Stop.
make[7]: *** No rule to make target 'all'. Stop.
make[7]: *** No rule to make target 'all'. Stop.
make[7]: *** No rule to make target 'install'. Stop.
make[7]: *** No rule to make target 'install'. Stop.
make[7]: *** No rule to make target 'install'. Stop.
make[7]: *** No rule to make target 'install'. Stop.
make[6]: *** [Makefile:76: bind2] Error 2
make[6]: *** No rule to make target 'all'. Stop.
make[6]: *** No rule to make target 'all'. Stop.
cat: confdefs.h: No such file or directory
make[6]: *** No rule to make target 'all'. Stop.
make[6]: *** No rule to make target 'install'. Stop.
make[6]: *** No rule to make target 'install'. Stop.
make[6]: *** No rule to make target 'install'. Stop.
make[6]: *** No rule to make target 'install'. Stop.
make[5]: *** [Makefile:76: bind2] Error 2
make[5]: *** No rule to make target 'all'. Stop.
make[5]: *** No rule to make target 'all'. Stop.
make[5]: *** No rule to make target 'all'. Stop.
make[5]: *** No rule to make target 'install'. Stop.
make[5]: *** No rule to make target 'install'. Stop.
make[5]: *** No rule to make target 'install'. Stop.
make[5]: *** No rule to make target 'install'. Stop.
make[4]: *** [Makefile:76: bind2] Error 2
make[4]: *** Waiting for unfinished jobs....
cat: confdefs.h: No such file or directory
cat: confdefs.h: No such file or directory
cat: confdefs.h: No such file or directory
cat: confdefs.h: No such file or directory
cat: confdefs.h: No such file or directory
cat: confdefs.h: No such file or directory
cat: confdefs.h: No such file or directory
cat: confdefs.h: No such file or directory
cat: confdefs.h: No such file or directory
cat: confdefs.h: No such file or directory
cat: confdefs.h: No such file or directory
cat: confdefs.h: No such file or directory
cat: confdefs.h: No such file or directory
cat: confdefs.h: No such file or directory
^Cmake[4]: *** [Makefile:42: bind1] Interrupt
make[3]: *** [Makefile:76: bind2] Interrupt
make[2]: *** [Makefile:76: bind2] Interrupt
make[1]: *** [Makefile:76: bind2] Interrupt
make: *** [Makefile:462: all-recursive] Interrupt
**Expected behavior**
Build works ok if build with "make" or "make -j4"
**Environment:**
- ISC DHCP version: 4.4.1
- OS: Ubuntu 19.04https://gitlab.isc.org/isc-projects/dhcp/-/issues/66Cannot unpack the tar file2019-12-11T11:39:33ZGhost UserCannot unpack the tar fileHello,
I am trying to install the dhcp relay agent on the console server Opengear/IM72xx which is built on uCLinux. After I scp'd the file to the server, I am not able to untar it and I am getting the following error. I checked the md5 o...Hello,
I am trying to install the dhcp relay agent on the console server Opengear/IM72xx which is built on uCLinux. After I scp'd the file to the server, I am not able to untar it and I am getting the following error. I checked the md5 of the file on the server against my computer and it matches. Also I am able to untar it on my local mac laptop.
tar: corrupted octal value in tar header
Can someone please help in resolving this issue?https://gitlab.isc.org/isc-projects/dhcp/-/issues/67DHCP client does not perform IPv4 duplicate address detection2019-12-11T12:13:13ZGhost UserDHCP client does not perform IPv4 duplicate address detection---
name: Bug report
about: Create a report to help us improve
---
**Describe the bug**
DHCP client not sending GARP to resolve the IP address offered from server to identify the same IP already there in the same network or not.
**To ...---
name: Bug report
about: Create a report to help us improve
---
**Describe the bug**
DHCP client not sending GARP to resolve the IP address offered from server to identify the same IP already there in the same network or not.
**To Reproduce**
Steps to reproduce the behavior:
1. Configure DHCP server(dhcpd) on Device-1 and Wan-0 interface.
2. Assign the lease range as 10.0.1.11 to 10.0.1.12.
3. In the same L2 network configure Device-2 with static IP address as 10.0.1.11.
4. Start the DHCP client(dhclient) on Device-3 which is also part of same L2 network where Device-1 and Device-2 reside.
5. Device-1 may offer 10.0.1.11 address for Device-3. This is redundant IP in the same L2 network.
**Expected behavior**
The Device-3 should send GARP packet to know whether the same IP address already there in network or not.
If it is present send the DHCP decline message to DHCP server.
**Environment:**
- ISC DHCP version: 4.4.1
- OS: GNU/Linu
- features: dhclient and dhcpd
**Some initial questions**
- Are you sure your feature is not already implemented in the latest ISC DHCP version? Yes
- Are you sure your requrested feature is not already impemented in Kea? Perhaps it's a good time
to consider migration? Yes
- Are you sure what you would like to do is not possible using some other mechanisms? Yes
- Have you discussed your idea on dhcp-users and/or dhcp-workers mailing lists? Nohttps://gitlab.isc.org/isc-projects/dhcp/-/issues/68Changing 'd' content type to RFC 1035 name broke omapi-key parsing2023-05-17T11:22:29ZThomas MarkwalderChanging 'd' content type to RFC 1035 name broke omapi-key parsingWe overlooked three server options with 'd' format: omapi-key, ldap-port, ldap-init-retry. Changing 'd' under #2 from being handled as text, breaks the ability to match omapi-key to any parsed keys. When server config file defines a TS...We overlooked three server options with 'd' format: omapi-key, ldap-port, ldap-init-retry. Changing 'd' under #2 from being handled as text, breaks the ability to match omapi-key to any parsed keys. When server config file defines a TSIG key to use with omapi such as shown below:
```
# define a key
key toms-key {
algorithm hmac-md5;
secret <some key here>;
}
# tell the server to use the key for omapi
omapi-key toms-key;
```
With a "d" option format for omapi-key, during configuration parsing the server will emit the error "OMAPI key : not found" and then exit. This is because the value for omapi-key option when evaluated by the server is in RFC 1035 format "\007toms-key" rather than plain text "toms-key". Changing the format to "t" will solve the problem. This should work for all three as prior #2, "d" format content equivalent to plain text.
This will need to go to v4_1_esv too.4.4.2Thomas MarkwalderThomas Markwalderhttps://gitlab.isc.org/isc-projects/dhcp/-/issues/69Add new option type 'k' to keama parser2023-05-17T11:22:25ZThomas MarkwalderAdd new option type 'k' to keama parser#68 added a new option format type, this needs to be added to Keama.#68 added a new option format type, this needs to be added to Keama.4.5.0-betahttps://gitlab.isc.org/isc-projects/dhcp/-/issues/71Correct buffer pointer logic in dhcrelay agent option functions2020-01-28T15:02:10ZThomas MarkwalderCorrect buffer pointer logic in dhcrelay agent option functionsTwo functions in dhcrelay.c, strip_relay_agent_options() and add_relay_agent_options() incorrectly advance pointers when removing existing agent options. See #63 for details.
This will need to be fixed in v4_1_esv as well.Two functions in dhcrelay.c, strip_relay_agent_options() and add_relay_agent_options() incorrectly advance pointers when removing existing agent options. See #63 for details.
This will need to be fixed in v4_1_esv as well.4.4.2Thomas MarkwalderThomas Markwalderhttps://gitlab.isc.org/isc-projects/dhcp/-/issues/72(From ISC Bugs 47555) dhcpd: failover.c...:scrubbing lease for ... emitted un...2020-01-14T12:29:40ZCathy Almond(From ISC Bugs 47555) dhcpd: failover.c...:scrubbing lease for ... emitted unexpectedlyFrom [BUG ticket #47555](https://bugs.isc.org/Ticket/Display.html?id=47555) - I understand the intent was to fix this in 4.4.2 but it seems not to have had a GL issue opened for it.
Originally from Customer Support ticket [#12731](https...From [BUG ticket #47555](https://bugs.isc.org/Ticket/Display.html?id=47555) - I understand the intent was to fix this in 4.4.2 but it seems not to have had a GL issue opened for it.
Originally from Customer Support ticket [#12731](https://support.isc.org/Ticket/Display.html?id=12731)
This message is logged by scrub_lease() in server/failover.c:
void scrub_lease(struct lease* lease, const char *file, int line) {
log_debug ("%s(%d):scrubbing lease for %s, hostname: %s", file,
line,
--
It seems to be the only log_debug statement in the failover code that is not surrounded by a "#if defined (DEBUG_FAILOVER_MESSAGES)" statement, which seems to be an oversight.
The code that introduced this logging stanza was added to ISC DHCP with this change:
- Leases are now scrubbed of certain prior use information when pool
re-balancing reassigns them from one FO peer to the other. This
corrects an issue where leases that were offered but not used
by the client retained the client hostname from the original
client. Thanks to Pavel Polacek, Jan Evangelista Purkyne University
for reporting the issue.
[ISC-Bugs #42008]4.4.2Thomas MarkwalderThomas Markwalderhttps://gitlab.isc.org/isc-projects/dhcp/-/issues/75Add interface name to socket setup fatal error logs2020-01-14T19:31:54ZThomas MarkwalderAdd interface name to socket setup fatal error logsThere mulitple calls to setsockopt (and the ilk) in common/socket.c that do not emit the interface name for which the operation is being invoked. It's helpful data to have when these calls fail and while it can typically be inferred, it...There mulitple calls to setsockopt (and the ilk) in common/socket.c that do not emit the interface name for which the operation is being invoked. It's helpful data to have when these calls fail and while it can typically be inferred, it's easy enough to simply emit it.4.4.2Thomas MarkwalderThomas Markwalderhttps://gitlab.isc.org/isc-projects/dhcp/-/issues/76Add a version of dhcpctl_wait_completion() that accepts a timeout2022-01-25T19:06:54ZThomas MarkwalderAdd a version of dhcpctl_wait_completion() that accepts a timeoutPer support ticket:
https://support.isc.org/Ticket/Display.html?id=15842
Calling dhcpctl_wait_completion() has two shortcomings:
1. First, it does not provide a timeout parameter and thus may effectively hang
2. Underneath the covers ...Per support ticket:
https://support.isc.org/Ticket/Display.html?id=15842
Calling dhcpctl_wait_completion() has two shortcomings:
1. First, it does not provide a timeout parameter and thus may effectively hang
2. Underneath the covers the way the logic is structured in omapi/dispatch.c, we end up effectively using the select() calls to poll in a tight loop eating CPU.
The first issue is simply address. The latter is a bit more sticky. The select calls are with omapi_dispatch_one(). They monitor the read and write sides of OMAPI connections. However, once the basic socket connection is made, the write side virtually ALWAYS tests as ready to write, thus even
passing in a timeout value as shown in the second call below:
```
isc_result_t omapi_one_dispatch (omapi_object_t *wo,
struct timeval *t)
{
:
/* poll once */
count = select(max + 1, &r, &w, &x, &now);
if (!count) {
/* We are dry now */
trigger_event(&rw_queue_empty);
/* Wait for a packet or a timeout... XXX */
r = rr;
w = ww;
x = xx;
count = select(max + 1, &r, &w, &x, t ? &to : NULL);
}
:
```
results in an immediate return from select. Thus we should only test the write side of the socket for readiness to write if we are connected AND we have data to write.4.4.3-beta1Thomas MarkwalderThomas Markwalderhttps://gitlab.isc.org/isc-projects/dhcp/-/issues/77replace deprecated ifconfig with ip2022-01-12T16:49:43ZChristian Hessereplace deprecated ifconfig with ipFor linux scripts the deprected ifconfig has been replaced with ip.
However there is one leftover, replace that as well.
(I can not fork with error "Namespace is not valid", thus attaching a patch.)
[0001-replace-deprecated-ifconfig-wi...For linux scripts the deprected ifconfig has been replaced with ip.
However there is one leftover, replace that as well.
(I can not fork with error "Namespace is not valid", thus attaching a patch.)
[0001-replace-deprecated-ifconfig-with-ip.patch](/uploads/faf0d556ef8a9ac08427fbd861699347/0001-replace-deprecated-ifconfig-with-ip.patch)https://gitlab.isc.org/isc-projects/dhcp/-/issues/78dhclient -1 breaks connections?2020-01-22T16:23:13ZGhost Userdhclient -1 breaks connections?
**Describe the bug**
dhclient -1 breaks existing connections
**To Reproduce**
Steps to reproduce the behavior:
I am using Fedora 31.
When updating from
dhcp-client.x86_64 12:4.4.1-15.fc31 @fedora
to
dhcp-client.x86_64 12:4.4.1-19.fc...
**Describe the bug**
dhclient -1 breaks existing connections
**To Reproduce**
Steps to reproduce the behavior:
I am using Fedora 31.
When updating from
dhcp-client.x86_64 12:4.4.1-15.fc31 @fedora
to
dhcp-client.x86_64 12:4.4.1-19.fc31 @updates
I had the following issue:
I was hammering my ISP (comcast xfinity) with lease renewals every 5 minutes with the crontab entry:
*/5 * * * * /usr/sbin/dhclient -1
I had this configured because my ISP had unusually long leases (>3000 minutes) and someone had cloned my wifi MAC address and was occasionally colliding me off my ISP's wifi network, causing my incoming packets to route to them instead and all my IP connections to timeout.
This worked reasonably well to keep my ISP routing to me while I was AFK.
Anyway, after updating to 4.4.1-19, every time there did a dhclient -1, my existing connections would stop receiving packets and eventually timeout.
Downgrading back to 4.4.1-15 fixed the problem.
**Expected behavior**
Lease renewal on connected interface should not break existing IP connections
**Environment:**
- isc-dhclient-4.4.1 from fedora 31 package dhcp-client.x86_64 12:4.4.1-19.fc31 @updates
- OS: Fedora 31https://gitlab.isc.org/isc-projects/dhcp/-/issues/79networking.service doesn't work2020-01-13T11:54:56ZGhost Usernetworking.service doesn't workI can't raise my network interface, I'm using debian 10, I only can connect to the internet by my ethernet cable.
Here's what happen when I try to start networking.service:
`systemctl status networking.service
● networking.service...I can't raise my network interface, I'm using debian 10, I only can connect to the internet by my ethernet cable.
Here's what happen when I try to start networking.service:
`systemctl status networking.service
● networking.service - Raise network interfaces
Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2020-01-12 19:59:07 -03; 46min ago
Docs: man:interfaces(5)
Process: 629 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
Main PID: 629 (code=exited, status=1/FAILURE)
jan 12 19:59:07 L0stH0st dhclient[704]: than a configuration issue please read the section on submitting
jan 12 19:59:07 L0stH0st dhclient[704]: bugs on either our web page at www.isc.org or in the README file
jan 12 19:59:07 L0stH0st dhclient[704]: before submitting a bug. These pages explain the proper
jan 12 19:59:07 L0stH0st dhclient[704]: process and the information we find helpful for debugging.
jan 12 19:59:07 L0stH0st dhclient[704]:
jan 12 19:59:07 L0stH0st dhclient[704]: exiting.
jan 12 19:59:07 L0stH0st ifup[629]: ifup: failed to bring up eth0
jan 12 19:59:07 L0stH0st systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
jan 12 19:59:07 L0stH0st systemd[1]: networking.service: Failed with result 'exit-code'.
jan 12 19:59:07 L0stH0st systemd[1]: Failed to start Raise network interfaces.
`
What should I do?