Samstag, 25. Oktober 2003 01:34, [PUG] dhcp client, Denny Schierz <[EMAIL PROTECTED]>, [EMAIL PROTECTED] > hi, hi
CONFIG_FILTER CONFIG_PACKET ---snip dhcp-client readme --- 5.1.2 PROTOCOL NOT CONFIGURED One additional Linux 2.1/2.2 issue: if you get the following message, it's because your kernel doesn't have the linux packetfilter or raw packet socket configured: Make sure CONFIG_PACKET (Packet socket) and CONFIG_FILTER (Socket Filtering) are enabled in your kernel configuration If this happens, you need to configure your Linux kernel to support Socket Filtering and the Packet socket. You can do this by typing ``make config'', ``make menuconfig'' or ``make xconfig'', and then enabling the Packet socket and Socket Filtering options that you'll see displayed on the menu or in the questionnaire. You can also edit your linux kernel .config file directly: set CONFIG_FILTER=y and CONFIG_PACKET=y. If you do this, make sure you run ``make oldconfig'' afterwards, so that the changes you've made are propogated to the kernel header files. After you've reconfigured, you need to type ``make'' to build a new Linux kernel, and then install it in the appropriate place (probably /linux). Make sure to save a copy of your old /linux. If the preceding paragraph made no sense to you, ask your Linux vendor/guru for help - please don't ask us. If you set CONFIG_PACKET=m or CONFIG_FILTER=m, then you must tell the kernel module loader to load the appropriate modules. If this doesn't make sense to you, don't use CONFIG_whatever=m - use CONFIG_whatever=y. Don't ask for help with this on the DHCP mailing list - it's a Linux kernel issue. This is probably not a problem with the most recent Linux 2.2.x kernels. --- snap dhcp-client readme --- -gk -- G�nther K�nzel +49 160 91586447 [EMAIL PROTECTED] http://www.jawz.de ---------------------------------------------------------------------------- PUG - Penguin User Group Wiesbaden - http://www.pug.org
