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!
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!
FS#5769 - iptables protocol display is wrong
Attached to Project:
Arch Linux
Opened by Jason Carr (jason2) - Monday, 06 November 2006, 16:50 GMT
Last edited by Tobias Powalowski (tpowa) - Monday, 06 November 2006, 20:06 GMT
Opened by Jason Carr (jason2) - Monday, 06 November 2006, 16:50 GMT
Last edited by Tobias Powalowski (tpowa) - Monday, 06 November 2006, 20:06 GMT
|
Detailsiptables seems to say '0' for the protocol when all or any should be correct display. The four 0's in INPUT are supposed to be any. The rules work fine, but just display incorrectly.
# iptables -V iptables v1.3.6 # iptables -L -v Chain INPUT (policy DROP 236K packets, 34M bytes) pkts bytes target prot opt in out source destination 323K 205M ACCEPT 0 -- any any anywhere anywhere state RELATED,ESTABLISHED 13448 772K ACCEPT tcp -- any any anywhere anywhere tcp dpt:ssh 725 25820 ACCEPT icmp -- any any anywhere anywhere icmp echo-request 10 565 ACCEPT 0 -- lo any anywhere anywhere 236K 34M LOG 0 -- any any anywhere anywhere LOG level warning tcp-sequence tcp-options ip-options Chain FORWARD (policy DROP 0 packets, 0 bytes) pkts bytes target prot opt in out source destination Chain OUTPUT (policy ACCEPT 303K packets, 39M bytes) pkts bytes target prot opt in out source destination 37 2839 ACCEPT 0 -- any lo anywhere anywhere |
This task depends upon
Closed by Thomas Bächler (brain0)
Saturday, 10 February 2007, 10:12 GMT
Reason for closing: Won't fix
Additional comments about closing: This is a minor glitch that's not worth the effort to fix.
Report that upstream to the netfilter team.
Saturday, 10 February 2007, 10:12 GMT
Reason for closing: Won't fix
Additional comments about closing: This is a minor glitch that's not worth the effort to fix.
Report that upstream to the netfilter team.