similar to: iptables: No chain/target/match by that name

Hi, I have a problem installing Shorewall 2.0.7 on a box, when I launch it I have: Initializing... Shorewall has detected the following iptables/netfilter capabilities: NAT: Available Packet Mangling: Available Multi-port Match: Available Connection Tracking Match: Available Determining Zones... Zones: net loc Validating interfaces file... Validating hosts file... Validating Policy

I''m trying to setup Shorewall 2.0.8 with the one-interface settings on my LFS (kernel 2.6.5) system. I''ve read the troubleshooting guide, recompiled my kernel with just about every netfilter/iptables module I could find, but I''m still getting this error: # tail /tmp/trace + prefix=Shorewall:smurfs:DROP: + ''['' 22 -gt 29 '']'' +

Hi, I am using Shorewall 2.0.6 on Debian with iptables 1.29. Before I was using Shorewall 2.0.3 and If work correctly, I am not sure that my problems begin after upgrade to 2.0.6, but my problem is that I can''t see some websites on the pc clients ( such as www.microsoft.com ), but some websites yes ( they are not in the pc cache ). My config is Shorewall as gateway/router of

I have installed latest Shorewall 1.46b on my Debian Woody ( debian-kernel 2.4.21 + iptables 1.28 ) I have an Ethernet ADSL Modem that connect using " PPTP " My ADSL line has dynamic IP. The modem is on eth0 The modem ip is: 192.168.1.1 eth0 ip is: 192.168.1.2 I''d like to make that pc as gateway for my local network of 7 pc too. The second NIC card eth1 has

Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://lists.shorewall.net/pipermail/shorewall-devel/attachments/20041014/45aef157/attachment-0001.bin

Hi all, I''ve shorewall 3.2.6-2, kernel 2.4.27, iptables 1.3.6.0debian1-5 on a debian sarge machine. >From yesterday shorewall can''t start anymore and in the shorewall-init.log I''ve this: ERROR: Rule "REDIRECT lan 8081 tcp 80 " requires NAT which is disabled /sbin/shorewall: line 527: 17071 Terminated $SHOREWALL_SHELL ${SHAREDIR}/compiler

http://bugzilla.netfilter.org/show_bug.cgi?id=633 Summary: No chain/target/match by that name Product: iptables Version: 1.3.5 Platform: i386 OS/Version: RedHat Linux Status: NEW Severity: blocker Priority: P1 Component: iptables AssignedTo: netfilter-buglog at lists.netfilter.org

good day to you i have compiled evertything related to ip tables as modules, but still i get this error when trying to use /etc/shorewall/routes can someone tell me the spicific module i need to have? here are my info intranet linux # shorewall version 2.4.2 intranet linux # uname -a Linux intranet 2.6.12-gentoo-r10 #10 SMP Sun Sep 11 15:01:49 SAST 2005 i686 AMD Athlon(tm) XP 2400+

Hi, I''m running RH9 Linux and I''m having a slight problem with shorewall, i originally set it up as a two card configuration, but i have now bridged the connections in an attempt to get my WiFi network communicating with the wired network (eth0 and wlan0). I have followed the instructions for bridging from http://www.shorewall.net/bridge.html but when I activate shorewall i get

After starting to shape local traffic now i am getting a lot of kernel panics in tcp_retransmit, so i decided to update my kernel from 2.6.17.14 to 2.6.21.1 , the problem is that after that i get: # iptables -t mangle -A POSTROUTING -o eth0 -j IMQ --todev 0 iptables: No chain/target/match by that name so i can not redirect ttraffic to IMQ device. and modules are loaded. - # lsmod Module

Hi, I have 2 Debian testing boxes running a very similar setup (both running the latest aptosid kernel); on one of them, since the iptables/libxtables10 packages have been upgraded from 1.4.19.1-1 to 1.4.20-2, shorewall-init can''t start shorewall anymore and for this reason ifupdown also fails triggering firewall up. Shorewall can be successfully started later on, and ifupdown starts

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 claas@rootdir.de wrote: > Hello, > > > I am trying to get ipsec with kernel 2.6.8.1 and shorewall 2.1.9 running, > but I still have a problem: > > Validating hosts file... > Error: Your kernel and/or iptables does not not support policy match: ipsec > > I had a look for netfilter patch-o-matic, but I did not find the

Hello, I''ve been using shorewall ever since Mandrake started shipping it, and am passably familiar with the config files and the simple setups. Recently I''ve discovered the "recent" module (no pun intended!) and want to setup a few rules that use this module. I searched all through the shorewall site (including

Hey all- Trying to run sh 1.2.8 and iptables 1.2.5 on my linux 2.4.17 box. I build the kernel from kernel.org sources, and then patched it with iptables 1.2.5 by doing %make pending-patches KERNEL_DIR=/usr/src/linux I let it run and patched these: Welcome to Rusty''s Patch-o-matic! Each patch is a new feature: many have minimal impact, some do not. Almost every one has bugs, so I

I''m doing more releases of 1.4.* to try to work around the absurd way in which the 2.6 kernel supports ipsec. 1.4.10 will provide a means for excluding multiple destination hosts/subnets from masquerade/SNAT. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net

Hi, as per the shorewall MultiISP documentation ( http://www1.shorewall.net/MultiISP.html ), it says "Use of this feature requires that your kernel and iptables include CONNMARK target and connmark match support (Warning: Standard Debian™ and Ubuntu™ kernels are lacking that support!)." it means MultiISP wont work properly if i am using Ubuntu server. if yes whats the

Hi, i have a problem concerning my previous shorewall installation. I tried to use shorewall to configure my firewall, but i couldn''t get NAT to work. So i decided to remove shorewall and tried it with plain iptables. This is now working for me but everytime when i start my network connection it seems that my handmade iptable rules are overwritten. I have to manually run my

https://bugzilla.netfilter.org/show_bug.cgi?id=944 Summary: Improvement of feedback of missing chain/target/match name Product: iptables Version: 1.4.x Platform: x86_64 OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: iptables AssignedTo:

I have a 3 nic setup with shorewall 1.4.8-1 running on redhat 9. My eth2 (dmz zone)has 7 secondary address attached to it. I can ping a machine in each subnet, dmz to net rules seem to be working fine on all machines.. I have my policy set as dmz to dmz accept. If I try to ping between subnets I get Nov 21 12:18:45 kbeewall kernel: Shorewall:FORWARD:REJECT:IN=eth2 OUT=eth2 SRC=172.17.0.2