On Sat, 30 Oct 2004 13:29:43 +0300, Marius Andreiana wrote: > > > Using FC3t2. The command line > > > iptables -A OUTPUT -j LOG > > > works. iptables-save gives > > > > > > > > > > > > *filter > > > :INPUT ACCEPT [0:0] > > > :FORWARD ACCEPT [0:0] > > > :OUTPUT ACCEPT [0:0] > > > -A OUTPUT -j log > > > > > > COMMIT > > > > > > Putting just this in /etc/sysconfig/iptables gives the same error on > > > restart. > > > > When did you add "-j log" and not "-j LOG"? You found that "-j LOG" > > works, so don't use "-j log". > I used LOG initially and on command line. iptables-save returned it with > "log". Can't reproduce with Test2 (iptables-1.2.11-2) and neither with Test3 (iptables-1.2.11-3.1), and no package changelog entry refers to any such symptoms. I still believe you edited /etc/sysconfig/iptables manually and added "-j log" there. The empty line in front of COMMIT backs up that theory. -- Fedora Core release 2.92 (FC3 Test 3) - Linux 2.6.9-1.640 loadavg: 0.56 0.62 0.27