Enhancement #3341
no address range available for DHCP request via eth
| Status: | CLOSED | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 100% | |
| Category: | nethserver-firewall-base | |||
| Target version: | ~FUTURE | |||
| Resolution: | REJECTED | NEEDINFO: | No |
Description
The messages log file reports a lot of lines like:
Dec 22 14:27:53 ns dnsmasq-dhcp[15431]: no address range available for DHCP request via eth1
Scenario:
eth1 is a blue interface, dhcp is disabled on blue but enabled on green, devices connected to blue network request an ip address via dhcp: the above lines gets logged.
Workaround: enable dhcp on blue.
Possible fix: drop dhcp requests on blue
History
#1
Updated by Filippo Carletti over 5 years ago
- Status changed from NEW to TRIAGED
- % Done changed from 0 to 20
To drop dhcp requests on interfaces where dhcp is not enabled we need to remove the dhcp option from shorewall interfaces.
In /etc/e-smith/templates/etc/shorewall/interfaces/20nics the dhcp option should be subject to service status.
#2
Updated by Filippo Carletti over 5 years ago
- Target version set to ~FUTURE
#3
Updated by Giacomo Sanchietti almost 5 years ago
- Status changed from TRIAGED to CLOSED
- % Done changed from 20 to 100
- Resolution set to REJECTED
This feature will not be implemented in NS 6. If needed, please reopen it for NS 7.