similar to: Shorewall support forums

Hey all, I am using the two interface setup with Shorewall but cannot get it to work. Shorewall starts fine and runs fine. Here first is a small diagram of my setup: Inet DSL modem -> eth0 -> eth1 -> dlink DI-624 wireless/wired router -> Wireless and wired lan. The problem arises in the router, The setup config calls to set the gateway of the other computers to shorewalls internal

This is becoming a FAQ and should probably be added to the docs. Thanks, -Tom -- Tom Eastep \ Shorewall - iptables made easy AIM: tmeastep \ http://www.shorewall.net ICQ: #60745924 \ teastep@shorewall.net ---------- Forwarded message ---------- Date: Sun, 28 Apr 2002 16:09:01 -0700 (Pacific Daylight Time) From: Tom Eastep <teastep@shorewall.net> To: Carl Spelkens

Hey all, A while ago today I posted about not being able to get my two interface setup working with a router (di 652 wireless/wired). I recieved help from Tom and got everything in the router turned off and set it up as a switch rather then a rouiter, this still never corrected my problems. Use tcpdump I see there is alot of traffic, but as soon as I dhcpcd eth1 (local) I loose all outside access

Are there any plans to have a web configuration interface for shorewall ? Carl Raeside, CD, CCP Network/Telecom Administrator Elytra Enterprises 613-746-0762 Ext 232 carl.raeside@elytra.com <mailto:carl.raeside@elytra.com> www.elytra.com

Carl Raeside wrote: > Tom, > > How is it going? Quick questions. > > 1. the link to the Mandrake rpms seems to not have the shorewall rpm in > it. http://www.monkeynoodle.org/comp/net/shorewall/ > > 2. this link seems to be dead any other sources ? Iproute ? > > Iproute ("ip" utility). The iproute package is included with most > distributions

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

---------- Forwarded Message ---------- Date: Tuesday, February 25, 2003 06:58:27 PM -0600 From: Aaron Axelsen <axelseaa@amadmax.com> To: shorewall-users@lists.shorewall.net Cc: Subject: [Shorewall-users] Offical Shorewall Support Forum -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 DeveloperCube is a new project started by veterans of the web development industry. We are proud to announce

Hi, I like shorewall and I''ve been using it for a long time. I now have a requirement to block worms / trojans in a public free wifi network I''m running. fwsnort ( http://www.cipherdyne.org/fwsnort/) translates Snort rules to iptables rules and it seems to fit my requirements. What is the best way to integrate shorewall and fwsnort? I tried googling for information about this

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 DeveloperCube is a new project started by veterans of the web development industry. We are proud to announce that we are now the Official Shorewall Support Forum. We are an online community offering discussion geared towards web developers, designers, and administrators of all skill levels. There are topics ranging from how to market your website,

Is the Shorewall.net down ? Regardless of page I get a "connection refused" - Bill

On Monday 24 April 2006 04:50 am, Tom Spear (Dustin Booker, Dustin Navea) wrote: > n0dalus wrote: > > In a way this holds for mailing lists as well, but I think > > the difference is that forums usually have: > > - Large sections containing non-technical discussion > > - 'Post counts', often used as a measure of status > > - Signup date, also used as

I apologize before hand for my newbie question, but I have done the research and I still cant find a solution. Shoreline 1.4.8 Problem: Firewall isent allowing me to port forward to server Port Open = 3389 (RDP) Line added for Port Forwarding:DNAT net loc:192.168.42.5 tcp 3389 Error Produced: Mar 11 06:37:40 net2allROP:IN=ppp0 OUT=eth1 SRC=64.x.x.xxx DST=192.168.42.2 LEN=48 TOS=0x00

All, I have been using Shorewall successfully for years on many different machines and configurations. However, I just built a new box and wanted to setup shorewall on it. I''m running SuSE Linux Enterprise Server 11 and Shorewall 4.4.8 (latest version as of this e-mail) using the RPM download. I am able to install Shorewall just fine and I''m able to setup everything except

We are trying to configure shorewall as follows: 1. We have shorewall running at gateway (172.16.1.1) with NAT. 2. We have a number of web servers (172.16.1.x/24). These web servers are accessed through port forwarding at the gateway (172.16.1.1) and websites are visible through virtual hosting through a web re-director. 3. Presently the proxy server runs in a transparent mode, i.e., all web

Hello, I have forwarded this to the shorewall-users list. You will find better support for this obscure problem there. Regards, Alex Martin http://www.rettc.com Cristian Valentin Barean wrote: > Hello ! > My name is Barean Cristian, and I have a network of 35 users, on a > Linux Mandrake 9.2 server. > As I was adding more users in my network, I found a problem with

Tom, I''m setting up a new firewall using shorewall-2.0.3a. The box was installed with the minimum, almost only the kernel. before installing shorewall, I installed iptables 1.2.9 and iproute2. Then I did a manual ./install.sh from the directory extracted from the tarball. When I issued a shorewall start, I received hundreds of errors like: /usr/share/shorewall/firewall: line 5520:

http://shorewall.net/pub/shorewall/2.2-Beta/shorewall-2.2.0-Beta7 ftp://shorewall.net/pub/shorewall/2.2-Beta/shorewall-2.2.0-Beta7 Problems Corrected: 1. The "shorewall add" and "shorewall delete" commands now work in a bridged environment. The syntax is: shorewall add <interface>[:<port>]:<address> <zone>

Shorewall 2.2.2 is now available. http://shorewall.net/pub/shorewall/2.2/shorewall-2.2.2 ftp://shorewall.net/pub/shorewall/2.2/shorewall-2.2.2 Problems Corrected: 1. The SOURCE column in the /etc/shorewall/tcrules file now correctly allows IP ranges (assuming that your iptables and kernel support ranges). 2. If A is a user-defined action and you have file /etc/shorewall/A

This update will be of interest to you if you use dynamic zones or if you have an /etc/shorewall/start file and use the ''save'' command. http://shorewall.net/pub/shorewall/2.0/shorewall-2.0.12 ftp://shorewall.net/pub/shorewall/2.0/shorewall-2.0.12 Problems Corrected: 1. A typo in shorewall.conf (NETNOTSYN) has been corrected. 2. The "shorewall add" and

Plus I would like to let you know that it works like a charm. Snort can now see those packets. -----Original Message----- From: shorewall-users-bounces@lists.shorewall.net [mailto:shorewall-users-bounces@lists.shorewall.net] On Behalf Of Thibodeau, Jamie L. Sent: Wednesday, March 30, 2005 9:25 AM To: Mailing List for Shorewall Users Subject: RE: [Shorewall-users] Shorewall and an inline