ntp/network: CONFIG_SECURITY_CAPABILITIES [solved]

[eastux]

I followed this wiki to setup ntp on my box:

http://gentoo-wiki.com/HOWTO_NTP

In it, it suggests compiling the kernel with CONFIG_SECURITY_CAPABILITIES=y because of "root dropping". However, I recompiled and now my network starts but I can't ping anything. I'm running madwifi wireless driver.

Would there be any reason that this CONFIG_SECURITY_CAPABILITIES setting would cause security issues?

Here's my emerge --info:

Gentoo Base System version 1.4.16
Portage 2.0.51.19 (default-linux/amd64/2005.0, gcc-3.4.3, glibc-2.3.4.20041102-r0, 2.6.11-gentoo-r1 x86_64)
=================================================================
System uname: 2.6.11-gentoo-r1 x86_64 AMD Opteron(tm) Processor 242
Python: dev-lang/python-2.3.4-r1 [2.3.4 (#1, Mar 4 2005, 20:56:19)]
dev-lang/python: 2.3.4-r1
sys-devel/autoconf: 2.59-r6, 2.13
sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.4
sys-devel/binutils: 2.15.92.0.2-r1
sys-devel/libtool: 1.5.10-r4
virtual/os-headers: 2.6.8.1-r4
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CFLAGS="-march=k8 -pipe -O2"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-march=k8 -pipe -O2"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distlocks sandbox"
GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="amd64 X acpi alsa berkdb bitmap-fonts crypt f77 fortran gif gpm ipv6 jp2 jpeg kde lzw lzw-tiff ncurses nls opengl oss pam perl png python qt readline ssl tcpd tiff truetype truetype-fonts type1-fonts usb userlocales xml2 xpm xrandr xv zlib"
Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, PORTDIR_OVERLAY

[eastux]

I'm embarassed, but I just needed to stop and start my wireless router. problem solved.