Re: shorewall II

2003-01-16 Par sujet Didier Chalm
On Wednesday 15 January 2003 20:05, [EMAIL PROTECTED] wrote:

 La zone fw est définie par défautut et correspond au firewall.

D'ailleurs, ne vaut-il pas mieux utiliser $FW ?

-- 
Didier



shorewall II

2003-01-15 Par sujet claude parisot

Bon, j'ai modifié les fichiers de conf comme conseillé et ça donne :

claude:~# shorewall start
Processing /etc/shorewall/shorewall.conf ...
Processing /etc/shorewall/params ...
Starting Shorewall...
Loading Modules...
Initializing...
Determining Zones...
Zones: net
Validating interfaces file...
Validating hosts file...
Determining Hosts in Zones...
Net Zone: ppp0:0.0.0.0/0
Deleting user chains...
Configuring Proxy ARP and NAT
Adding Common Rules
Enabling RFC1918 Filtering
Setting up Kernel Route Filtering...
IP Forwarding Disabled!
Processing /etc/shorewall/tunnels...
Processing /etc/shorewall/rules...
Error: Undefined Client Zone in rule ACCEPT loc fw tcp ssh
Complété

Je vais regarder de mon coté , mais si vous avez une idée

PS :je l'ai provisoirement désinstallé, je ne pouvais plus accéder au 
net  voir plus haut.



   Merci

#
# Shorewall 1.3 /etc/shorewall/zones
#
# This file determines your network zones. Columns are:
#
#   ZONEShort name of the zone
#   DISPLAY Display name of the zone
#   COMMENTSComments about the zone
#
#ZONE   DISPLAY COMMENTS
net Net Internet
#LAST LINE - ADD YOUR ENTRIES ABOVE THIS ONE - DO NOT REMOVE

##
#  /etc/shorewall/shorewall.conf V1.3 - Change the following variables to
#  match your setup
#
#  This program is under GPL [http://www.gnu.org/copyleft/gpl.htm] 
#
#  This file should be placed in /etc/shorewall
#
#  (c) 1999,2000,2001,2002 - Tom Eastep ([EMAIL PROTECTED])
##
#
# PATH - Change this if you want to change the order in which Shorewall
#searches directories for executable files. 
#
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin:/usr/local/sbin

#
# NAME OF THE FIREWALL ZONE
#
# Name of the firewall zone -- if not set or if set to an empty string, fw
# is assumed.
#
FW=fw

#
# SUBSYSTEM LOCK FILE
#
# Set this to the name of the lock file expected by your init scripts. For
# RedHat, this should be /var/lock/subsys/shorewall. On Debian, it
# should be /var/state/shorewall. If your init scripts don't use lock files,
# set this to .
#

SUBSYSLOCK=/var/lock/subsys/shorewall

#
# SHOREWALL TEMPORARY STATE DIRECTORY
#
# This is the directory where the firewall maintains state information while
# it is running
#

STATEDIR=/var/lib/shorewall

#
# ALLOW RELATED CONNECTIONS
#
# Set this to yes or Yes if you want to accept all connection requests
# that are related to already established connections. For example, you want
# to accept FTP data connections. If you say no here, then to accept
# these connections between particular zones or hosts, you must include
# explicit related rules in /etc/shorewall/rules.
#

ALLOWRELATED=yes

#
# KERNEL MODULE DIRECTORY
#
# If your netfilter kernel modules are in a directory other than
# /lib/modules/`uname -r`/kernel/net/ipv4/netfilter then specify that
# directory in this variable. Example: MODULESDIR=/etc/modules.

MODULESDIR=

#
# LOG RATE LIMITING
#
# The next two variables can be used to control the amount of log output
# generated. LOGRATE is expressed as a number followed by an optional
# `/second',  `/minute', `/hour', or `/day' suffix and specifies the maximum
# rate at which a particular message will occur. LOGBURST determines the
# maximum initial burst size that will be logged. If set empty, the default
# value of 5 will be used.
#
# Example:
#
#   LOGRATE=10/minute
#   LOGBURST=5
#
# If BOTH variables are set empty then logging will not be rate-limited.
#

LOGRATE=
LOGBURST=

#
# LEVEL AT WHICH TO LOG 'UNCLEAN' PACKETS
#
# This variable determines the level at which Mangled/Invalid packets are logged
# under the 'dropunclean' interface option. If you set this variable to an
# empty value (e.g., LOGUNCLEAN= ), Mangled/Invalid packets will be dropped
# silently.
#
# The value of this variable also determines the level at which Mangled/Invalid
# packets are logged under the 'logunclean' interface option. If the variable
# is empty, these packets will still be logged at the 'info' level.
#

LOGUNCLEAN=info

#
# LOG FILE LOCATION
#
# This variable tells the /sbin/shorewall program where to look for Shorewall
# log messages. If not set or set to an empty string (e.g., LOGFILE=) then
# /var/log/messages is assumed.
#
# WARNING: The LOGFILE variable simply tells the 'shorewall' program where to
#  look for Shorewall messages.It does NOT control the destination for
#  these messages. For information about how to do that, see
#
#  http://www.shorewall.net/FAQ.htm#faq6

LOGFILE=/var/log/messages

#
# ENABLE NAT SUPPORT
#
# You probally want yes here. Only gateways not doing NAT in any form, like
# SNAT,DNAT masquerading, port forwading etc. should say no here.
#
NAT_ENABLED=Yes

#
# ENABLE MANGLE SUPPORT
#
# If you 

Re: shorewall II

2003-01-15 Par sujet Dominique Arpin

 Bon, j'ai modifié les fichiers de conf comme conseillé et ça donne :

 claude:~# shorewall start
 Processing /etc/shorewall/shorewall.conf ...
 Processing /etc/shorewall/params ...
 Starting Shorewall...
 Loading Modules...
 Initializing...
 Determining Zones...
 Zones: net
 Validating interfaces file...
 Validating hosts file...
 Determining Hosts in Zones...
 Net Zone: ppp0:0.0.0.0/0
 Deleting user chains...
 Configuring Proxy ARP and NAT
 Adding Common Rules
 Enabling RFC1918 Filtering
 Setting up Kernel Route Filtering...
 IP Forwarding Disabled!
 Processing /etc/shorewall/tunnels...
 Processing /etc/shorewall/rules...
 Error: Undefined Client Zone in rule ACCEPT loc fw tcp ssh
 Complété

C'est normal, ta zone fw n'est pas definie dans ton fichier de zone


 Je vais regarder de mon coté , mais si vous avez une idée

 PS :je l'ai provisoirement désinstallé, je ne pouvais plus accéder au
 net  voir plus haut.


Merci


-- 
Dominique Arpin___[   espace
gestionnaire réseau courbe]

  http://www.espacecourbe.com/
  téléphone514.933.9861
  télécopieur  514.933.9546





Re: shorewall II

2003-01-15 Par sujet pgbob
 
  Bon, j'ai modifié les fichiers de conf comme conseillé et ça donne :

Il faut bien regarder *tous* les fichiers de conf ;)

[...]
  Processing /etc/shorewall/rules...
  Error: Undefined Client Zone in rule ACCEPT loc fw tcp ssh
  Complété
 
 C'est normal, ta zone fw n'est pas definie dans ton fichier de zone

Si les fichiers de conf sont conformes à ce qui est indiqué sur 
http://www.shorewall.net/standalone.htm, j'aurais plutôt tendance 
à pencher pour la non-définition de la zone loc. Ce qui est 
normal, puisque cette zone correspond normalement au LAN. Cette 
règle autorise les stations du LAN à communiquer avec le FW par 
ssh.

La zone fw est définie par défautut et correspond au firewall.

Revois ton fichier rules pour ne garder que le strict nécessaire.

Cordialement,

--
Philippe Gaudron