DHCP server is not able to set SO_BINDTODEVICE if not running under root

[Marcin Siodelski]

----- Original Message -----
> From: "Tomas Hozza" <thozza at redhat.com>
> To: bind10-dhcp at lists.isc.org
> Sent: Tuesday, 8 October, 2013 4:33:11 PM
> Subject: DHCP server is not able to set SO_BINDTODEVICE if not running under	root
> 
> Hi.
> 
> I already filed ticket (http://bind10.isc.org/ticket/3176), but
> nobody responded yet.
> 
> It seems that if running b10-init with "-u" option and having
> DHCP server configured to run, the server fails because it is
> no able to set SO_BINDTODEVICE socket option.
> 
> I'm wondering if there is any workaround other than running
> bind10 as a root.
> 
> Thanks in advance.

Tomas,

Many thanks for your efforts and submitting the ticket. I responded in the ticket: http://bind10.isc.org/ticket/3176.

Unfortunately, we are unlikely to implement the use of b10-sockcreator in DHCP components in the short term. What we definitely have to think about is an update to the bind10-guide to mention that -u option should not be used, when DHCP modules are started and explain why. In the long term, the proper solution will be implemented as a part of the ticket that I mentioned: http://bind10.isc.org/ticket/2780. Please note that this is not trivial change because it requires changes in DHCP, in b10-sockcreator and possibly other components such as b10-init to support raw sockets creation and setting appropriate options.

For now, the working workaround is to run as root.

Regards,
Marcin