CONFIG_FILTER error on arm

Mukund Deshpande sai.mukund.sagar at gmail.com
Wed Nov 30 06:48:50 UTC 2011


Hi Bjørn


I added extra message for each of the cases where this error was occuring.
It has failed at bind call..
Any suggestions how to find if there is any problem in ifindex detection?


Internet Systems Consortium DHCP Server 4.2.2
Copyright 2004-2011 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Wrote 0 leases to leases file.
socket: Error_2 (Bind to the interface name) Invalid argument - make sure
CONFIG_PACKET (Packet socket) and CONFIG_FILTER
(Socket Filtering) are enabled in your kernel
configuration!

If you did not get this software from ftp.isc.org, please
get the latest from ftp.isc.org and install that before
requesting help.

If you did get this software from ftp.isc.org and have not
yet read the README, please read it before requesting help.
If you intend to request help from the dhcp-server at isc.org
mailing list, please read the section on the README about
submitting bug reports and requests for help.

Please do not under any circumstances send requests for
help directly to the authors of this software - please
send them to the appropriate mailing list as described in
the README file.

exiting.

Regards,
Mukund

On Fri, Nov 25, 2011 at 6:44 PM, Bjørn Mork <bjorn at mork.no> wrote:

> Mukund Deshpande <sai.mukund.sagar at gmail.com> writes:
>
> > Can no one help me with this error? :(
> > I have been stuck with this error since last 4 days...Have enabled all
> > netfilter options..
> >
> > Still dhcp daemon gives same error. CONFIG_PACKET or CONFIG_FILTER
> > should be enabled in kernel configuration :|
>
> The error message is very misleading.  CONFIG_FILTER hasn't existed in
> ages. It doesn't have anything to do with NETFILTER. The functionality
> which previously required CONFIG_FILTER is unconditionally enabled in
> Linux 2.6.
>
> And if you look through common/lpf.c you'll notice that the exact same
> message is printed for not less than three(!) non-related errors.
> Unless you have Token Ring enabled, which adds a fourth...  They even
> all use "socket" as prefix.  This makes it much harder to tell exactly
> which call failed.  But at least the print the returned error code:
> "Invalid argument".  So we can look at the three calls and see which one
> is likely to cause that:
>
> 1) socket(PF_PACKET, SOCK_PACKET, htons((short)ETH_P_ALL)
>
>  Yup, could be it if you didn't enable CONFIG_PACKET
>
> *2) bind (sock, &sa, sizeof sa)
>
> * *  Yup, could be it if there is an bug in the ifindex detection?*
>
> 3) setsockopt (info -> rfdesc, SOL_SOCKET, SO_ATTACH_FILTER, &p, sizeof p)
>
>  Yup, could be a bug in the filter.  You say you cross compiled
>  this. I'm wondering if that might cause endianness problems when
>  building the filter?  Don't know - just guessing possible causes....
>
> The first thing I would do, was verifying that I actually had
> CONFIG_PACKET enabled in the running kernel.  Then I would locate these
> three calls in common/lpf.c and add enough debug output to them to find
> out exactly which one failed.  The path from there depends on the result
> of that.
>
>
>
> Bjørn
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users




-- 
Regards,
Mukund
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20111130/cebf65d7/attachment.html>


More information about the dhcp-users mailing list