mirror of
https://gitlab.com/shorewall/code.git
synced 2024-12-02 20:44:11 +01:00
3666482643
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@343 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
147 lines
5.7 KiB
Plaintext
Executable File
147 lines
5.7 KiB
Plaintext
Executable File
#
|
|
# Shorewall 1.3 -- Interfaces File
|
|
#
|
|
# /etc/shorewall/interfaces
|
|
#
|
|
# You must add an entry in this file for each network interface on your
|
|
# firewall system.
|
|
#
|
|
# Columns are:
|
|
#
|
|
# ZONE Zone for this interface. Must match the short name
|
|
# of a zone defined in /etc/shorewall/zones.
|
|
#
|
|
# If the interface serves multiple zones that will be
|
|
# defined in the /etc/shorewall/hosts file, you should
|
|
# place "-" in this column.
|
|
#
|
|
# INTERFACE Name of interface. Each interface may be listed only
|
|
# once in this file. You may NOT specify the name of
|
|
# an alias (e.g., eth0:0) here; see
|
|
# http://www.shorewall.net/FAQ.htm#faq18
|
|
#
|
|
# DO NOT DEFINE THE LOOPBACK INTERFACE (lo) IN THIS FILE.
|
|
#
|
|
# BROADCAST The broadcast address for the subnetwork to which the
|
|
# interface belongs. For P-T-P interfaces, this
|
|
# column is left black.If the interface has multiple
|
|
# addresses on multiple subnets then list the broadcast
|
|
# addresses as a comma-separated list.
|
|
#
|
|
# If you use the special value "detect", the firewall
|
|
# will detect the broadcast address for you. If you
|
|
# select this option, the interface must be up before
|
|
# the firewall is started, you must have iproute
|
|
# installed and the interface must only be associated
|
|
# with a single subnet.
|
|
#
|
|
# If you don't want to give a value for this column but
|
|
# you want to enter a value in the OPTIONS column, enter
|
|
# "-" in this column.
|
|
#
|
|
# OPTIONS A comma-separated list of options including the
|
|
# following:
|
|
#
|
|
# dhcp - interface is managed by DHCP or used by
|
|
# a DHCP server running on the firewall or
|
|
# you have a static IP but are on a LAN
|
|
# segment with lots of Laptop DHCP clients.
|
|
# noping - icmp echo-request (ping) packets
|
|
# addressed to the firewall should
|
|
# be ignored on this interface
|
|
# filterping - icmp echo-request (ping) packets
|
|
# addressed to the firewall should
|
|
# be controlled by the rules file and
|
|
# applicable policy. If neither 'noping'
|
|
# nor 'filterping' are specified then
|
|
# the firewall will respond to 'ping'
|
|
# requests. 'filterping' takes
|
|
# precedence over 'noping' if both are
|
|
# given.
|
|
# routestopped - (Deprecated -- use
|
|
# /etc/shorewall/routestopped)
|
|
# When the firewall is stopped, allow
|
|
# and route traffic to and from this
|
|
# interface.
|
|
# norfc1918 - This interface should not receive
|
|
# any packets whose source is in one
|
|
# of the ranges reserved by RFC 1918
|
|
# (i.e., private or "non-routable"
|
|
# addresses. If packet mangling is
|
|
# enabled in shorewall.conf, packets
|
|
# whose destination addresses are
|
|
# reserved by RFC 1918 are also rejected.
|
|
# multi - This interface has multiple IP
|
|
# addresses and you want to be able to
|
|
# route between them.
|
|
# routefilter - turn on kernel route filtering for this
|
|
# interface (anti-spoofing measure). This
|
|
# option can also be enabled globally in
|
|
# the /etc/shorewall/shorewall.conf file.
|
|
# dropunclean - Logs and drops mangled/invalid packets
|
|
#
|
|
# logunclean - Logs mangled/invalid packets but does
|
|
# not drop them.
|
|
# . . blacklist - Check packets arriving on this interface
|
|
# against the /etc/shorewall/blacklist
|
|
# file.
|
|
# maclist - Connection requests from this interface
|
|
# are compared against the contents of
|
|
# /etc/shorewall/maclist. If this option
|
|
# is specified, the interface must be
|
|
# an ethernet NIC and must be up before
|
|
# Shorewall is started.
|
|
# tcpflags - Packets arriving on this interface are
|
|
# checked for certain illegal combinations
|
|
# of TCP flags. Packets found to have
|
|
# such a combination of flags are handled
|
|
# according to the setting of
|
|
# TCP_FLAGS_DISPOSITION after having been
|
|
# logged according to the setting of
|
|
# TCP_FLAGS_LOG_LEVEL.
|
|
# proxyarp -
|
|
# Sets
|
|
# /proc/sys/net/ipv4/conf/<interface>/proxy_arp.
|
|
# Do NOT use this option if you are
|
|
# employing Proxy ARP through entries in
|
|
# /etc/shorewall/proxyarp. This option is
|
|
# intended soley for use with Proxy ARP
|
|
# sub-networking as described at:
|
|
# http://www.tldp.org/HOWTO/mini/Proxy-ARP-Subnet
|
|
#
|
|
# The order in which you list the options is not
|
|
# significant but the list should have no embedded white
|
|
# space.
|
|
#
|
|
# Example 1: Suppose you have eth0 connected to a DSL modem and
|
|
# eth1 connected to your local network and that your
|
|
# local subnet is 192.168.1.0/24. The interface gets
|
|
# it's IP address via DHCP from subnet
|
|
# 206.191.149.192/27 and you want pings from the internet
|
|
# to be ignored. You interface a DMZ with subnet
|
|
# 192.168.2.0/24 using eth2. You want to be able to
|
|
# access the firewall from the local network when the
|
|
# firewall is stopped.
|
|
#
|
|
# Your entries for this setup would look like:
|
|
#
|
|
# net eth0 206.191.149.223 noping,dhcp
|
|
# local eth1 192.168.1.255 routestopped
|
|
# dmz eth2 192.168.2.255
|
|
#
|
|
# Example 2: The same configuration without specifying broadcast
|
|
# addresses is:
|
|
#
|
|
# net eth0 detect noping,dhcp
|
|
# loc eth1 detect routestopped
|
|
# dmz eth2 detect
|
|
#
|
|
# Example 3: You have a simple dial-in system with no ethernet
|
|
# connections and you want to ignore ping requests.
|
|
#
|
|
# net ppp0 - noping
|
|
##############################################################################
|
|
#ZONE INTERFACE BROADCAST OPTIONS
|
|
net eth0 detect norfc1918,routefilter,dhcp
|
|
#LAST LINE -- ADD YOUR ENTRIES BEFORE THIS ONE -- DO NOT REMOVE
|