Displaying 20 results from an estimated 4000 matches similar to: "Shorewall 1.3.14a"
2003 Mar 03
3
losing connection
Tom, or whomever reads this, when I say disconnect I mean close out IE6,
sorry for so unclear on this point. My IP address never changes unless I
unplug the modem. I have had the same IP address for ... well since I
had to reset it to hook it up to my Linux box.which was 2 weeks ago. If
I set DHCP on my eth1 interface that will contradict the static address
I have assigned to it,
2003 Oct 06
2
Shorewall 1.4.7
Shorewall 1.4.7 is now available at:
http://shorewall.net/pub/shorewall/shorewall-1.4.7
ftp://shorewall.net/pub/shorewall/shorewall-1.4.7
It will be available at your favorite mirror shortly.
The release notes are attached.
As always, many thanks go to Francesca Smith for updating the sample
configurations for this release.
-Tom
--
Tom Eastep \ Nothing is foolproof to a sufficiently
2003 Aug 25
5
Shorewall 1.4.7 Beta 1
http://shorewall.net/pub/shorewall/Beta
ftp://shorewall.net/pub/shorewall/Beta
Problems Corrected since version 1.4.6:
1) Corrected problem in 1.4.6 where the MANGLE_ENABLED variable was
being tested before it was set.
2) Corrected handling of MAC addresses in the SOURCE column of the
tcrules file. Previously, these addresses resulted in an invalid
iptables command.
3) The
2003 Feb 21
0
Shorewall 1.4.0 Beta 1
The first 1.4.0 Beta is now available at:
http://www.shorewall.net/pub/shorewall/Beta
ftp://ftp.shorewall.net/pub/shorewall/Beta
Function from 1.3 that has been omitted from this version includes:
1) The MERGE_HOSTS variable in shorewall.conf is no longer
supported. Shorewall 1.4 behavior is the same as 1.3 with
MERGE_HOSTS=Yes.
2. Interface names of the form
2003 Feb 19
0
Proposed Shorewall 1.4.0 Content
Here is the proposed content -- I''m looking for a Beta to start in the
next week or so with release around the middle of next month. The main
focus of 1.4 will be to provide external behavior similar to the
upcoming 2.0 release.
Function from 1.3 that has been omitted from this version includes:
1) The MERGE_HOSTS variable in shorewall.conf is no longer
supported. Shorewall 1.4
2005 Apr 07
4
Shorewall 2.2.3
http://shorewall.net/pub/shorewall/2.2/shorewall-2.2.3
ftp://shorewall.net/pub/shorewall/2.2/shorewall-2.2.3
Problems Corrected:
1) If a zone is defined in /etc/shorewall/hosts using
<interface>:!<network> in the HOSTS column then startup errors occur
on "shorewall [re]start".
2) Previously, if "shorewall status" was run on a system whose kernel
lacked
2003 Aug 12
1
Shorewall Keeps sending false IP Address Conflict
Dear All,
After installing Shorewall, on a router with 4 NIC, seems running ok.
Next day, when connecting from clients, (MS) we keep getting ip conflict for non-conflicting ip addresses.
Any help is appreciated.
Detals of Startup:
+ shift
+ nolock=
+ ''['' 1 -gt 1 '']''
+ trap ''my_mutex_off; exit 2'' 1 2 3 4 5 6 9
+ command=start
+
2002 Jun 17
0
Another 1.3.x Bug
Another bug with similar symptoms to the last one has been found by Renato
Tirol.
The bug fixed by the earlier errata update affects the following options:
dhcp
dropunclean
logunclean
norfc1918
routefilter
multi
filterping
noping
The bug reported by Renato and fixed in the current errata update affects:
routestopped
The new update is available at:
2003 Mar 05
3
Shorewall 1.4.0 RC1
The first release candidate is now available at:
http://www.shorewall.net/pub/shorewall/Beta
ftp://ftp.shorewall.net/pub/shorewall/Beta
The only change between Beta 1 and RC1 is that the ''check'' command is back
in RC1.
Function from 1.3 that has been omitted from this version includes:
1) The MERGE_HOSTS variable in shorewall.conf is no longer
supported. Shorewall 1.4
2003 Aug 23
2
Warning of upcoming removal of ''logunclean'' and ''dropunclean'' interface options.
Harald Welte just announced that the 2.6 Kernels will not support the
''unclean'' match extension except via Patch-O-Matic.
Since I have a polciy of not supporting Netfilter features that are only
available in P-O-M, I will be removing the ''logunclean'' and ''dropunclean''
interface options from Shorewall.
In 1.4.7, a warning will be issued if
2004 Feb 10
1
Preparing for Shorewall 2.0
Shorewall 2.0.0 is now in Beta so this is a good time to begin thinking about
preparing to migrate to the 2.0 Shorewall series.
Shorewall 2.0 makes a number of incompatible changes in the configuration
files. Luckily, you will be able to make changes ahead of time to your 1.4
configuration that will ease the migration when the time comes.
a) Shorewall 2.0 doesn''t allow you to specify
2004 Nov 04
0
Preparing for Shorewall 2.2
Shorewall 2.2.0 is expected to be released in the February/March
timeframe so it is now time to begin thinking about preparing to
upgrade. This is particularly important for those of you still running
Shorewall 1.4 since support for that version will end with the release
of 2.2.
For those of you still running Shorewall 1.4, here are some things that
you can do ahead of time to ease the upgrade to
2002 Dec 22
2
maclist option -> sorry good ver.
Setting up MAC Verification on eth0...
Error: Interface eth0 must be up before Shorewall can start
my :
/etc/shorewall/shorewall.conf:
MACLIST_DISPOSITION=REJECT
MACLIST_LOG_LEVEL=info
interfaces:
#ZONE INTERFACE BROADCAST OPTIONS
net ppp0 217.96.90.242 noping
loc eth0 255.255.255.0 routestopped,maclistmaclist:
maclist:
#INTERFACE MAC IP
2003 Feb 27
6
Shorewall 1.4.0 Beta 2
The second Beta is now available at:
http://www.shorewall.net/pub/shorewall/Beta
ftp://ftp.shorewall.net/pub/shorewall/Beta
Function from 1.3 that has been omitted from this version includes:
1) The ''check'' command is no longer supported.
2) The MERGE_HOSTS variable in shorewall.conf is no longer
supported. Shorewall 1.4 behavior is the same as 1.3 with
MERGE_HOSTS=Yes.
2003 Feb 25
2
Unclean packets
Hello,
If I set my network interface to have "logunclean" along with
"dhcp,norfc1918,routefilter,noping,tcpflags", then when I connect to
http://welcome.hp.com/country/us/eng/support.htm and choose any of the
product I get this.
logpkt:LOG:IN=eth0 OUT= MAC=00:a0:cc:5b:09:5f:00:08:e2:32:34:70:08:00
SRC=192.151.11.205 DST=24.24.243.178 LEN=80 TOS=0x00 PREC=0x00 TTL=239
ID=14025
2004 Dec 26
1
Preparing for Shorewall 2.2 -- End of Support for Shorewall 1.4 is near!
Shorewall 2.2.0 is expected to be released in the February/March
timeframe so it is now time to begin thinking about preparing to
upgrade. This is particularly important for those of you still running
Shorewall 1.4 since support for that version will end with the release
of 2.2.
For those of you still running Shorewall 1.4, here are some things that
you can do ahead of time to ease the upgrade to
2007 Nov 10
2
Access Point with Ethernet.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi:
I have a small infrastructure of network of local area, that are based on a
computer, with computer and with a Point Access, with Debian Etch 4.0r1.
With Shorewall 3.2.6-2.
Well. Since I have two cards of network, which of which, I have left like that:
Internet --> Router (217.126.221.65) --> eth1 (217.126.221.117) --> eth0
(LAN
2002 May 14
3
[Shorewall-users] Redirect loc::80 to fw::3128 not work (fwd)
I''m beginning to believe that the use of the last column in the rules file
to designate redirection/forwarding is too subtle for many users. For 1.3,
I think I''ll do something like the following:
Current rule:
ACCEPT net loc:192.168.1.3 tcp 80 - all
New rule:
FORWARD net loc:192.168.1.3 tcp 80
Current rule:
ACCEPT net fw::3128 tcp 80 - all
New rule:
REDIRECT net
2002 Dec 22
0
with maclist option can''t start
Setting up MAC Verification on eth0...
Error: Interface eth0 must be up before Shorewall can start
my :
/etc/shorewall/shorewall.conf:
MACLIST_DISPOSITION=REJECT MACLIST_LOG_LEVEL=infointerfaces:#ZONE
INTERFACE BROADCAST OPTIONSnet ppp0 217.96.90.242
nopingloc eth0 255.255.255.0
routestopped,maclistmaclist:#INTERFACE MAC
IP ADDRESSES (Optional)eth0
2008 Nov 13
4
ERROR: Unknown Host (All hosts) : /usr/share/shorewall/macro.Any macro or rule
Hi. I set, for example, a rule with a host server:
Macro.http accept fw net:www.google.es
I restart shorewall and it works, but when i stop the firewall for
disabling Internet (for any reason), and i want start the firewall it
says:
Failed to start firewall :
Compiling...
Compiling /etc/shorewall/zones...
Compiling /etc/shorewall/interfaces...
WARNING: Support for the detectnets interface