iptables

I also have brakeage of iptables. Kernel support seems to be missing.

linode:/etc/mail# iptables -L -n -v

iptables v1.2.11: can't initialize iptables table `filter': iptables who? (do you need to insmod?)

Perhaps iptables or your kernel needs to be upgraded.

9 Replies

Whoops. That was meant to be a reply. Not a new thread.

New threads are actually what I prefer.

Go ahead and reboot your Linode. 2.6.16-domU-linode1 build #2 has all the filtering rules enabled. Let me know if that fixes it.

-Chris

@caker:

New threads are actually what I prefer.

Go ahead and reboot your Linode. 2.6.16-domU-linode1 build #2 has all the filtering rules enabled. Let me know if that fixes it.

-Chris

Iptables works, but now I'm missing some block devices:

linode:~# mount /var

mount: /dev/hda4 is not a valid block device

This is odd because some of them work. Does the new kernel have ext2 and ext3 support?

See

http://www.linode.com/forums/viewtopic.php?t=2180

Keep rebooting until everything shows up in /proc/partitions.

-Chris

@sednet:

@caker:

New threads are actually what I prefer.

Go ahead and reboot your Linode. 2.6.16-domU-linode1 build #2 has all the filtering rules enabled. Let me know if that fixes it.

-Chris

Iptables works, but now I'm missing some block devices:

linode:~# mount /var

mount: /dev/hda4 is not a valid block device

This is odd because some of them work. Does the new kernel have ext2 and ext3 support?

From a systrace:

open("/dev/hda4", ORDONLY|OLARGEFILE) = -1 ENXIO (No such device or address)

Read the gotchas post :)

-Chris

Iptables seems to be working perfectly now.

The debian iptables job isn't applying my iptables setup but that doesn't look like xens fault.

I've bound everything that should not go over the internet to 127.0.0.1 anyway.

This has been much more fun than going to work. Grr.. SOx audits.

@sednet:

Iptables seems to be working perfectly now.

.

I think I was wrong there, I don't think all of iptables is in the kernel.

I know the following line worked, I pulled it off the linode and off my backup:

iptables -A INPUT -m state –state RELATED,ESTABLISHED -j ACCEPT

iptables: No chain/target/match by that name

The simple stuff certainly works:

linode:/var/lib/iptables# iptables -L -n -v

Chain INPUT (policy ACCEPT 1790 packets, 147K bytes)

pkts bytes target prot opt in out source destination

0 0 ACCEPT all -- lo * 0.0.0.0/0 0.0.0.0/0

Anyway I really need to go to work now. Thanks for xen Chris! It does seem to be quite a lot faster.

@sednet:

iptables -A INPUT -m state –state RELATED,ESTABLISHED -j ACCEPT

iptables: No chain/target/match by that name
Yup. Missed a few options…

# uname -a
Linux li3-242 2.6.16-domU-linode1 #3 SMP Tue Mar 28 03:10:40 EST 2006 i686 GNU/Linux
li3-242:~# iptables -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
li3-242:~#

-Chris

Reply

Please enter an answer
Tips:

You can mention users to notify them: @username

You can use Markdown to format your question. For more examples see the Markdown Cheatsheet.

> I’m a blockquote.

I’m a blockquote.

[I'm a link] (https://www.google.com)

I'm a link

**I am bold** I am bold

*I am italicized* I am italicized

Community Code of Conduct