Re: iptables question: no chain/target/match by that name...

2004-04-06 Thread David
On Mon, Apr 05, 2004 at 12:09:31PM -0500, hugo vanwoerkom wrote: > + iptables -A RH-Lokkit-0-50-INPUT -p tcp -m tcp --dport 80 --syn -j ACCEPT [ ... ] > + iptables -A RH-Lokkit-0-50-INPUT -p tcp -m tcp --dport 0:1023 --syn -j > REJECT > > Now I know nothing of iptables, but why can he do d

Re: iptables question: no chain/target/match by that name...

2004-04-06 Thread Laurence J. Lane
On Mon, Apr 05, 2004 at 02:08:35PM -0500, hugo vanwoerkom wrote: > I'm trying it now with multiport + eject enabled in netfilter. Check REJECT in /proc/net/ip_tables_targets and check for multiport in /proc/net/ip_tables_matches. Using either loaded netfilter modules or built in netfilter support

Re: iptables question: no chain/target/match by that name...

2004-04-05 Thread hugo vanwoerkom
hugo vanwoerkom wrote: Hi World! The lokkit question yesterday by Faheem Mitha prompted me to install lokkit on Sarge. As Dircha pointed out: it don't work. All lokkit does is create a little iptables script that sits in /etc/default/lokkit. Then upon boot lokkit in /etc/init.d executes that

iptables question: no chain/target/match by that name...

2004-04-05 Thread hugo vanwoerkom
Hi World! The lokkit question yesterday by Faheem Mitha prompted me to install lokkit on Sarge. As Dircha pointed out: it don't work. All lokkit does is create a little iptables script that sits in /etc/default/lokkit. Then upon boot lokkit in /etc/init.d executes that script. As Dircha also