iptables -A POSTROUTING -t nat -o eth1 -j MASQUERADE doesn't seem to work. If I go back to net-firewall/iptables-1.2.7a-r3 then it works ok. No reboots or anything just reinstall the pervious stable iptables. Internal interface is eth0 Reproducible: Always Steps to Reproduce: 1.emerge iptables 2. set up normal firewall rules and load modules for masq 3.iptables -A POSTROUTING -t nat -o eth1 -j MASQUERADE Actual Results: media root # iptables -A POSTROUTING -t nat -o eth1 -j MASQUERADE iptables: Invalid argument Expected Results: media root # iptables -A POSTROUTING -t nat -o eth1 -j MASQUERADE media root # media root # emerge info Portage 2.0.47-r10 (default-x86-1.4, gcc-3.2.2, glibc-2.3.1-r4) ================================================================= System uname: 2.4.20 i686 AMD Athlon(tm) XP 2400+ GENTOO_MIRRORS="http://gentoo.linux.no/pub/gentoo/" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share/config /var/bind /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" PORTDIR="/usr/portage" DISTDIR="/pub/portage/distfiles" PKGDIR="/pub/portage/packages/athlon-xp" PORTAGE_TMPDIR="/pub/tmp" PORTDIR_OVERLAY="/pub/portage_local" USE="x86 oss 3dnow apm avi crypt gif jpeg libg++ libwww mikmod mmx mpeg ncurses nls pdflib png quicktime spell xml2 zlib gtkhtml gdbm berkdb slang readline bonobo svga java guile sdl gpm tcpd pam perl python imlib oggvorbis qt opengl X gtk -gnome -alsa kde mozilla mysql ssl xmms xv dvd motif acpi cdr -pcmcia -arts -cups -esd truetype encode lirc" COMPILER="gcc3" CHOST="i686-pc-linux-gnu" CFLAGS="-march=athlon-xp -O3 -pipe" CXXFLAGS="-march=athlon-xp -O3 -pipe" ACCEPT_KEYWORDS="x86" MAKEOPTS="-j2" AUTOCLEAN="yes" SYNC="rsync://rsync.gentoo.org/gentoo-portage" FEATURES="sandbox ccache"
Do you still have this problem with the latest stable version?
Seems ok nowdays. thanks
Ok, setting this to WONTFIX then?
yep, it's turned out to be me playing with different kernels and I had /usr/src/linux symlinked to a kernel that wasn't the current running one. Under that condition iptables failed to build the masq stuff correctly. Once it is built it is happy to work with any 2.4 flavour kernel it seems.
So, reopening...
... and setting to INVALID. Thanks for investigating further though it worked for you :-)