Bug 996968 - DHCPD should set SO_REUSEPORT on DHCPv4 socket so it doesn't conflict with dnsmasq
Summary: DHCPD should set SO_REUSEPORT on DHCPv4 socket so it doesn't conflict with dn...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: dhcp
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomáš Hozza
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-14 11:32 UTC by Tomáš Hozza
Modified: 2013-08-15 10:57 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-15 10:57:30 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Tomáš Hozza 2013-08-14 11:32:54 UTC
Description of problem:
dnsmasq binds to ANY_ADDR address to be able to serve DHCP clients without
any IP address. It sets SO_REUSEPORT on the DHCPv4 socket. If it is not available then it sets SO_REUSEADDR.

ISC DHCP sets always SO_REUSEADDR on DHCPv4 socket. This leads to dhcpd
conflicting with dnsmasq run by libvirt.

In order to solve this issue both daemons have to use the same socket option.
Currently dnsmasq in Fedora has been patched to use SO_REUSEADDR so it does
not conflicts with ISC DHCP. However it makes more sense to patch dhcpd to set
also SO_REUSEPORT (as it does for DHCPv6 socket)

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Bug #981973

Comment 1 Tomáš Hozza 2013-08-15 10:57:30 UTC
After discussion with dnsmasq upstream they agreed to set both socket options
to improve interoperability with other network daemon. Therefore there is no
need to fix ISC DHCP.

Closing this bug as WONTFIX.


Note You need to log in before you can comment on or make changes to this bug.