iptables

InAt!QuE · Posted: Wed Feb 04, 2004 11:39 am Post subject: iptables

Hi,

I did emerge -k iptables and i got an error during compiling:

nevynxxx · Posted: Wed Feb 04, 2004 1:57 pm Post subject:

did you try without the -k? maybe it can't find the binary packages it needs to, what does

InAt!QuE · Posted: Wed Feb 04, 2004 2:17 pm Post subject:

dreamer · Apprentice Joined: 16 Aug 2003 Posts: 236

InAt!QuE · Posted: Wed Feb 04, 2004 2:57 pm Post subject:

kaffeen · Posted: Wed Feb 04, 2004 4:48 pm Post subject: Same error with Iptables v1.2.9

I am receiving the same error when trying to 'emerge iptables'. I have attempted to do so with both the gentoo-sources-2.4.20-r6 and gentoo-dev-sources-2.6.1 kernels. My only success was in copying the tbz2 packaged from the LiveCD and doing a binary emerge 'emerge -k iptables-1.2.8-r1.tbz2'.

I was able to emerge iptables-1.2.9 on my other pc a week or so ago without any problems but shortly after that, have not been able to successfully build it on my other pc.

InAt!QuE · Posted: Wed Feb 04, 2004 5:20 pm Post subject:

could this be a kernel issue ??
_________________
...Unix, MS-DOS, and Windows NT (also known as the Good, the Bad, and the Ugly).

go2sleep · n00b Joined: 06 Sep 2003 Posts: 31 Location: Belgium

Iptables care about kernel config when iptable is compiling.

So if you are not sure about your kernel configuration you can check by reading this page : http://www.shorewall.net/kernel.htm. On it there are nice screenshot of kernel configuration.

I used that way for setting up my kernel configuration.
And it work fine.

Just one thing, if you are using lilo as boot loader, after compyling your kernel and espacialy after copying you bzImage file to the /boot directory, don't forget to run the /sbin/lilo command for refreshing the lilo loader. If you don't do that your new kernel configuration will not be loaded when you will reboot your computer.

kaffeen · Posted: Wed Feb 04, 2004 8:03 pm Post subject: Conntrack..

I am getting the same error with two different kernels (see above post).

I am using grub rather than lilo and am not aware of any changes (beyond editing the grub.conf file) that I would have to make once I've built a new kernel and copied the bzImage to /boot.

Having been a little more than frustrated by this and iptables v1.2.8 not working at all, I didn't notice this before. When iptables 1.2.9 is compiling, it is always failing when configuring Conntrack. I don't recall at this momen the exact line before I get the same error message posted in the original post of this thread. When I get home, I will try building a kernel without conntrack support and see if it can then compile iptables-1.2.9.

TheCoop · Posted: Wed Feb 04, 2004 8:14 pm Post subject:

whats in the 6 or so lines above the error msg you posted? ideally post everything below the last line starting with 'gcc'
_________________
95% of all computer errors occur between chair and keyboard (TM)

"One World, One web, One program" - Microsoft Promo ad.
"Ein Volk, Ein Reich, Ein Führer" - Adolf Hitler

Change the world - move a rock

InAt!QuE · Posted: Thu Feb 05, 2004 11:14 am Post subject:

InAt!QuE · Posted: Thu Feb 05, 2004 11:49 am Post subject:

friction · Tux's lil' helper Joined: 16 Sep 2002 Posts: 109

Having the same problem while trying to upgrade from 1.2.8-r1 on two different machines, but both using conntrack.

kaffeen · Posted: Thu Feb 05, 2004 2:34 pm Post subject: Possible solution

I was getting the same error when trying to emerge iptables 1.2.9. However, my /usr/src/linux symlink was pointing to my original kernel source, not my current. I delete the symlink and created a new one pointing to the new kernel source