Re: SO_BINDTODEVICE and dhcpd - howto?

David Woodhouse (dwmw2@cam.ac.uk)
Thu, 30 Oct 1997 00:35:56 +0000

edge@dux.raex.com said:
> However, when I run dhcpd it gives me an error trying to set this
> option and exits. Is there anything special that I need to do to
> allow SO_BINDTODEVICE to work?

Which kernel, which version of dhcpd, etc....

Myself and a friend of mine spent some time over the summer vacation working
on DHCPD and SO_BINDTODEVICE (it was me who ported it to 2.1.5x-vger), but
have found it to work fine. I did the kernel code, Robert (rjf22@cam.ac.uk)
did the DHCPD modifications. Show us exactly what you tried (and a strace of
it, preferably), and the details of the kernel you tried it on, and we'll have
a go at working out what went wrong.

Naturally, if you try it on a 2.1.5x kernel, I'll be more useful, as the
SO_BINDTODEVICE code is fairly different between 2.1 and 2.0 - the routing
code has changed a lot in between.

AFAIK, SO_BINDTODEVICE is only in 2.1.59-vger, not the real 2.1.60 - Linus and
the CVS tree seem to be ignoring each other ATM.

The latest CVS snapshot can be obtained from ftp://ftp.kernel.org/pub/linux/ker
nel/davem/
It's supposedly a "daily snapshot", but the latest one is
linux-2.1.59-VGER-CVS971020.tar.gz