Salut,
<BR>Pour l´ip fixe, deja essaye ca n´a rien change.
<BR>Voici les contenus des fichiers
<BR>
<BR>SHOREWALL n´existe pas mais il y a un SHOREWALL.conf
<BR>
<BR>RULES:
<BR>#
<BR># Shorewall version 1.4 - Rules File
<BR>#
<BR># /etc/shorewall/rules
<BR>#
<BR># Rules in this file govern connection establishment. Requests and
<BR># responses are automatically allowed using connection tracking.
<BR>#
<BR># In most places where an IP address or subnet is allowed, you
<BR># can preceed the address/subnet with "!" (e.g., !192.168.1.0/24) to
<BR># indicate that the rule matches all addresses except the address/subnet
<BR># given. Notice that no white space is permitted between "!" and the
<BR># address/subnet.
<BR>#
<BR># Columns are:
<BR>#
<BR>#
<BR># ACTION ACCEPT, DROP, REJECT, DNAT, DNAT-, REDIRECT, CONTINUE
<BR># or LOG.
<BR>#
<BR># ACCEPT -- allow the connection request
<BR># DROP -- ignore the request
<BR># REJECT -- disallow the request and return an
<BR># icmp-unreachable or an RST packet.
<BR># DNAT -- Forward the request to another
<BR># system (and optionally another
<BR># port).
<BR># DNAT- -- Advanced users only.
<BR># Like DNAT but only generates the
<BR># DNAT iptables rule and not
<BR># the companion ACCEPT rule.
<BR># REDIRECT -- Redirect the request to a local
<BR># port on the firewall.
<BR># REDIRECT-
<BR># -- Advanced users only.
<BR># Like REDIRET but only generates the
<BR># REDIRECT iptables rule and not
<BR># the companion ACCEPT rule.
<BR># CONTINUE -- (For experts only). Do not process
<BR># any of the following rules for this
<BR># (source zone,destination zone). If
<BR># The source and/or destination IP
<BR># address falls into a zone defined
<BR># later in /etc/shorewall/zones, this
<BR># connection request will be passed
<BR># to the rules defined for that
<BR># (those) zone(s).
<BR># LOG -- Simply log the packet and continue.
<BR>#
<BR># May optionally be followed by ":" and a syslog log
<BR># level (e.g, REJECT:info). This causes the packet to be
<BR># logged at the specified level.
<BR>#
<BR># You may also specify ULOG (must be in upper case) as a
<BR># log level.This will log to the ULOG target for routing
<BR># to a separate log through use of ulogd
<BR># (
http://www.gnumonks.org/projects/ulogd).
<BR>#
<BR># SOURCE Source hosts to which the rule applies. May be a zone
<BR># defined in /etc/shorewall/zones, $FW to indicate the
<BR># firewall itself, or "all" If the ACTION is DNAT or
<BR># REDIRECT, sub-zones of the specified zone may be
<BR># excluded from the rule by following the zone name with
<BR># "!' and a comma-separated list of sub-zone names.
<BR>#
<BR># Except when "all" is specified, clients may be further
<BR># restricted to a list of subnets and/or hosts by
<BR># appending ":" and a comma-separated list of subnets
<BR># and/or hosts. Hosts may be specified by IP or MAC
<BR># address; mac addresses must begin with "~" and must use
<BR># "-" as a separator.
<BR>#
<BR># dmz:192.168.2.2 Host 192.168.2.2 in the DMZ
<BR>#
<BR># net:155.186.235.0/24 Subnet 155.186.235.0/24 on the
<BR># Internet
<BR>#
<BR># loc:192.168.1.1,192.168.1.2
<BR># Hosts 192.168.1.1 and
<BR># 192.168.1.2 in the local zone.
<BR># loc:~00-A0-C9-15-39-78 Host in the local zone with
<BR># MAC address 00:A0:C9:15:39:78.
<BR>#
<BR># Alternatively, clients may be specified by interface
<BR># by appending ":" to the zone name followed by the
<BR># interface name. For example, loc:eth1 specifies a
<BR># client that communicates with the firewall system
<BR># through eth1. This may be optionally followed by
<BR># another colon (":") and an IP/MAC/subnet address
<BR># as described above (e.g., loc:eth1:192.168.1.5).
<BR>#
<BR># DEST Location of Server. May be a zone defined in
<BR># /etc/shorewall/zones, $FW to indicate the firewall
<BR># itself or "all"
<BR>#
<BR># Except when "all" is specified, the server may be
<BR># further restricted to a particular subnet, host or
<BR># interface by appending ":" and the subnet, host or
<BR># interface. See above.
<BR>#
<BR># Restrictions:
<BR>#
<BR># 1. MAC addresses are not allowed.
<BR># 2. In DNAT rules, only IP addresses are
<BR># allowed; no FQDNs or subnet addresses
<BR># are permitted.
<BR># 3. You may not specify both an interface and
<BR># an address.
<BR>#
<BR># Unlike in the SOURCE column, you may specify a range of
<BR># up to 256 IP addresses using the syntax
<BR># <first ip>-<last ip>. When the ACTION is DNAT or DNAT-,
<BR># the connections will be assigned to addresses in the
<BR># range in a round-robin fashion.
<BR>#
<BR># The port that the server is listening on may be
<BR># included and separated from the server's IP address by
<BR># ":". If omitted, the firewall will not modifiy the
<BR># destination port. A destination port may only be
<BR># included if the ACTION is DNAT or REDIRECT.
<BR>#
<BR># Example: loc:192.168.1.3:3128 specifies a local
<BR># server at IP address 192.168.1.3 and listening on port
<BR># 3128. The port number MUST be specified as an integer
<BR># and not as a name from /etc/services.
<BR>#
<BR># if the ACTION is REDIRECT, this column needs only to
<BR># contain the port number on the firewall that the
<BR># request should be redirected to.
<BR>#
<BR># PROTO Protocol - Must be "tcp", "udp", "icmp", a number, or
<BR># "all".
<BR>#
<BR># DEST PORT(S) Destination Ports. A comma-separated list of Port
<BR># names (from /etc/services), port numbers or port
<BR># ranges; if the protocol is "icmp", this column is
<BR># interpreted as the destination icmp-type(s).
<BR>#
<BR># A port range is expressed as <low port>:<high port>.
<BR>#
<BR># This column is ignored if PROTOCOL = all but must be
<BR># entered if any of the following ields are supplied.
<BR># In that case, it is suggested that this field contain
<BR># "-"
<BR>#
<BR># If your kernel contains multi-port match support, then
<BR># only a single Netfilter rule will be generated if in
<BR># this list and the CLIENT PORT(S) list below:
<BR># 1. There are 15 or less ports listed.
<BR># 2. No port ranges are included.
<BR># Otherwise, a separate rule will be generated for each
<BR># port.
<BR>#
<BR># CLIENT PORT(S) (Optional) Port(s) used by the client. If omitted,
<BR># any source port is acceptable. Specified as a comma-
<BR># separated list of port names, port numbers or port
<BR># ranges.
<BR>#
<BR># If you don't want to restrict client ports but need to
<BR># specify an ADDRESS in the next column, then place "-"
<BR># in this column.
<BR>#
<BR># If your kernel contains multi-port match support, then
<BR># only a single Netfilter rule will be generated if in
<BR># this list and the DEST PORT(S) list above:
<BR># 1. There are 15 or less ports listed.
<BR># 2. No port ranges are included.
<BR># Otherwise, a separate rule will be generated for each
<BR># port.
<BR>#
<BR># ORIGINAL DEST (0ptional -- only allowed if ACTION is DNAT[-] or
<BR># REDIRECT[-]) If included and different from the IP
<BR># address given in the SERVER column, this is an address
<BR># on some interface on the firewall and connections to
<BR># that address will be forwarded to the IP and port
<BR># specified in the DEST column.
<BR>#
<BR># A comma-separated list of addresses may also be used.
<BR># This is usually most useful with the REDIRECT target
<BR># where you want to redirect traffic destined for
<BR># particular set of hosts.
<BR>#
<BR># Finally, if the list of addresses begins with "!" then
<BR># the rule will be followed only if the original
<BR># destination address in the connection request does not
<BR># match any of the addresses listed.
<BR>#
<BR># The address (list) may optionally be followed by
<BR># a colon (":") and a second IP address. This causes
<BR># Shorewall to use the second IP address as the source
<BR># address in forwarded packets. See the Shorewall
<BR># documentation for restrictions concerning this feature.
<BR># If no source IP address is given, the original source
<BR># address is not altered.
<BR>#
<BR># Example: Accept SMTP requests from the DMZ to the internet
<BR>#
<BR># #ACTION SOURCE DEST PROTO DEST SOURCE ORIGINAL
<BR># # PORT PORT(S) DEST
<BR># ACCEPT dmz net tcp smtp
<BR>#
<BR># Example: Forward all ssh and http connection requests from the internet
<BR># to local system 192.168.1.3
<BR>#
<BR># #ACTION SOURCE DEST PROTO DEST SOURCE ORIGINAL
<BR># # PORT PORT(S) DEST
<BR># DNAT net loc:192.168.1.3 tcp ssh,http
<BR>#
<BR># Example: Redirect all locally-originating www connection requests to
<BR># port 3128 on the firewall (Squid running on the firewall
<BR># system) except when the destination address is 192.168.2.2
<BR>#
<BR># #ACTION SOURCE DEST PROTO DEST SOURCE ORIGINAL
<BR># # PORT PORT(S) DEST
<BR># REDIRECT loc 3128 tcp www - !192.168.2.2
<BR>#
<BR># Example: All http requests from the internet to address
<BR># 130.252.100.69 are to be forwarded to 192.168.1.3
<BR>#
<BR># #ACTION SOURCE DEST PROTO DEST SOURCE ORIGINAL
<BR># # PORT PORT(S) DEST
<BR># DNAT net loc:192.168.1.3 tcp 80 - 130.252.100.69
<BR>#
<BR># Example: You want to accept SSH connections to your firewall only
<BR># from internet IP addresses 130.252.100.69 and 130.252.100.70
<BR>#
<BR># #ACTION SOURCE DEST PROTO DEST SOURCE ORIGINAL
<BR># # PORT PORT(S) DEST
<BR># ACCEPT net:130.252.100.69,130.252.100.70
<BR># tcp 22
<BR>##############################################################################
<BR>#ACTION SOURCE DEST PROTO DEST SOURCE ORIGINAL
<BR># PORT PORT(S) DEST
<BR>ACCEPT masq fw tcp domain,bootps,http,https,631,imap,pop3,smtp,nntp,ntp -
<BR>ACCEPT masq fw udp domain,bootps,http,https,631,imap,pop3,smtp,nntp,ntp -
<BR>ACCEPT fw masq tcp 631,515,137,138,139 -
<BR>ACCEPT fw masq udp 631,515,137,138,139 -
<BR>#LAST LINE -- ADD YOUR ENTRIES BEFORE THIS ONE -- DO NOT REMOVE
<BR>
<BR>RFC1918:
<BR>
<BR>#
<BR># Shorewall 1.4 -- RFC1918 File
<BR>#
<BR># /etc/shorewall/rfc1918
<BR>#
<BR># Lists the subnetworks that are blocked by the 'norfc1918' interface option.
<BR>#
<BR># The default list includes those IP addresses listed in RFC 1918, those listed
<BR># as 'reserved' by the IANA, the DHCP Autoconfig class B, and the class C
<BR># reserved for use in documentation and examples.
<BR>#
<BR># Columns are:
<BR>#
<BR># SUBNET The subnet (host addresses also allowed)
<BR># TARGET Where to send packets to/from this subnet
<BR># RETURN - let the packet be processed normally
<BR># DROP - silently drop the packet
<BR># logdrop - log then drop
<BR>#
<BR>###############################################################################
<BR>#SUBNET TARGET
<BR>255.255.255.255 RETURN # We need to allow limited broadcast
<BR>169.254.0.0/16 DROP # DHCP autoconfig
<BR>172.16.0.0/12 logdrop # RFC 1918
<BR>192.0.2.0/24 logdrop # Example addresses
<BR>192.168.0.0/16 logdrop # RFC 1918
<BR>#
<BR># The following are generated with the help of the Python program found at:
<BR>#
<BR>#
http://www.shorewall.net/pub/shorewall/ ... _reserved/
<BR>#
<BR># The program was contributed by Andy Wiggin
<BR>#
<BR>0.0.0.0/7 logdrop # Reserved
<BR>2.0.0.0/8 logdrop # Reserved
<BR>5.0.0.0/8 logdrop # Reserved
<BR>7.0.0.0/8 logdrop # Reserved
<BR>10.0.0.0/8 logdrop # Reserved
<BR>23.0.0.0/8 logdrop # Reserved
<BR>27.0.0.0/8 logdrop # Reserved
<BR>31.0.0.0/8 logdrop # Reserved
<BR>36.0.0.0/7 logdrop # Reserved
<BR>39.0.0.0/8 logdrop # Reserved
<BR>41.0.0.0/8 logdrop # Reserved
<BR>42.0.0.0/8 logdrop # Reserved
<BR>49.0.0.0/8 logdrop # JTC - Returned to IANA Mar 98
<BR>50.0.0.0/8 logdrop # JTC - Returned to IANA Mar 98
<BR>58.0.0.0/7 logdrop # Reserved
<BR>60.0.0.0/8 logdrop # Reserved
<BR>70.0.0.0/7 logdrop # Reserved
<BR>72.0.0.0/5 logdrop # Reserved
<BR>83.0.0.0/8 logdrop # Reserved
<BR>84.0.0.0/6 logdrop # Reserved
<BR>88.0.0.0/5 logdrop # Reserved
<BR>96.0.0.0/3 logdrop # Reserved
<BR>127.0.0.0/8 logdrop # Loopback
<BR>197.0.0.0/8 logdrop # Reserved
<BR>198.18.0.0/15 logdrop # Reserved
<BR>201.0.0.0/8 logdrop # Reserved - Central & South America
<BR>240.0.0.0/4 logdrop # Reserved
<BR>#
<BR># End of generated entries
<BR>#
<BR>#LAST LINE -- ADD YOUR ENTRIES BEFORE THIS ONE -- DO NOT REMOVE
<BR>
<BR>