I have commented out that line, to test the behaviour of the server without the bindtodevice option.
Now, when I run it, I have: ./busybox udhcpd -f udhcpd (v1.14.1) started and that's it, the daemon stops and nothing else happens. Is it possible to check some log, or set some debug parameter? Thanks! 2009/10/14 Ruben Lagar <[email protected]> > Well, I have checked it, and it was set to Y. > > So the problem has to be somewhere else... > > The line where the problem is, is > > setsockopt(fd, SOL_SOCKET, SO_BINDTODEVICE, &ifr, sizeof(ifr)); > > used to bind the server to a network interface. In my case there is only > one interface, so maybe I could change it to bind the server to any > interface... But, ¿why is it throwing that strange error? > > > 2009/10/13 Denys Vlasenko <[email protected]> > > On Tue, Oct 13, 2009 at 4:21 PM, Ruben Lagar <[email protected]> >> wrote: >> > I run it as root >> > >> > I added that line in the right place >> > >> > It still doesn't work. When you ask if af_packet is built in my kernel, >> do >> > you mean the option "Packet socket" under "Networking options"? I am not >> > sure what I should check... >> >> Yes. Let me know whether setting it to Y solves the problem. >> -- >> vda >> > >
_______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
