Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#25497 - iptables couldn't work on linux 3.0

Attached to Project: Arch Linux
Opened by Athurg Gooth (athurg) - Wednesday, 10 August 2011, 14:41 GMT
Last edited by Gaetan Bisson (vesath) - Thursday, 11 August 2011, 05:20 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
After upgrade kernel26 to linux3.0, iptables looks not work. when i run 'iptables -L', it notice me:

iptables v1.4.12: can't initialize iptables table `filter': Permission denied (you must be root)
Perhaps iptables or your kernel needs to be upgraded.

Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:
This task depends upon

Closed by  Gaetan Bisson (vesath)
Thursday, 11 August 2011, 05:20 GMT
Reason for closing:  Not a bug
Comment by Gaetan Bisson (vesath) - Wednesday, 10 August 2011, 16:27 GMT
It works fine as root. That's what the "Permission denied (you must be root)" part of the error message is about...
Comment by Athurg Gooth (athurg) - Thursday, 11 August 2011, 00:56 GMT
If i run as root, it notice me:
iptables v1.4.12: can't initialize iptables table `filter': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.

if there's some module of kernel i didn't load?
Comment by Gaetan Bisson (vesath) - Thursday, 11 August 2011, 01:42 GMT
`iptables -L` automatically loads the modules iptable_filter, ip_tables, and x_tables. Did you reboot your computer since you upgraded to linux-3.0.1?
Comment by Athurg Gooth (athurg) - Thursday, 11 August 2011, 05:06 GMT
It's OK now on 3.0.1 after reboot.

Please close this bugs. TKS!

Loading...