<rc.firewall-iptables-stronger START>
#!/bin/sh # # rc.firewall-iptables-stronger # FWVER=0.88s # An example of a stronger IPTABLES firewall with IP Masquerade # support for 2.4.x kernels. # # Log: # # 0.88s - Updated the commands for dynamically addresses machines and # to point to an expanded FAQ section for more information # # 0.87s - Removed the unused drop-and-logit chain as it was only later # being deleted anyway # 0.86s - Fixed a typo that had a preceeding ; instead of a # # 0.85s - renamed from rc.firewall-2.4-stronger to rc.firewall-iptables- # stronger to reflect this script works for all IPTABLES enabled # platforms including 2.6.x kernels # - fixed an incorrect /24 netmask for the INTIP variable # - removed the unneeded SED variable # 0.84s - Changed the defaults from 192.168.1.0 to 192.168.0.x to align # with the rest of the IPMASQ howto # 0.83s - Added additional comments to make PORTFW configs more obvious # 0.82s - Added a special ICMP filter to work around a Netfilter security # issue # - renamed the drop-and-log-it rule to reject-and-log-it # 0.81s - Added an additional comment in the INPUT section for NOT # allowing all traffic in, but only select traffic # 0.80s - Added a DISABLED ip_nat_irc kernel module section, changed the # default of the ip_conntrack_irc to NOT load by default, and # added additional kernel module comments # 0.79s - ruleset now uses modprobe instead of insmod # 0.78s - REJECT is not a legal policy yet; back to DROP # 0.77s - Changed the default block behavior to REJECT not DROP # 0.76s - Added a comment about the OPTIONAL WWW ruleset and a comment # where to put optional PORTFW commands # 0.75s - Added clarification that PPPoE users need to use # "ppp0" instead of "eth0" for their external interface # 0.74s - Changed the EXTIP command to work on NON-English distros # 0.73s - Added comments in the output section that DHCPd is optional # and changed the default settings to disabled # 0.72s - Changed the filter from the INTNET to the INTIP to be # stateful; moved the command VARs to the top and made the # rest of the script to use them # 0.70s - Added a disabled examples for allowing internal DHCP # and external WWW access to the server # 0.63s - Added support for the IRC module # 0.62s - Initial version based upon the basic 2.4.x rc.firewall echo -e "\nLoading rc.firewall-iptables-STRONGER - version $FWVER..\n" # The location of various iptables and other shell programs # # If your Linux distribution came with a copy of iptables, most # likely it is located in /sbin. If you manually compiled # iptables, the default location is in /usr/local/sbin # # ** Please use the "whereis iptables" command to figure out # ** where your copy is and change the path below to reflect # ** your setup # #IPTABLES=/sbin/iptables IPTABLES=/usr/local/sbin/iptables # LSMOD=/sbin/lsmod DEPMOD=/sbin/depmod MODPROBE=/sbin/modprobe GREP=/bin/grep AWK=/bin/awk IFCONFIG=/sbin/ifconfig #Setting the EXTERNAL and INTERNAL interfaces for the network # # Each IP Masquerade network needs to have at least one # external and one internal network. The external network # is where the natting will occur and the internal network # should preferably be addressed with a RFC1918 private address # scheme. # # For this example, "eth0" is external and "eth1" is internal" # # NOTE: If this doesnt EXACTLY fit your configuration, you must # change the EXTIF or INTIF variables above. For example: # # If you are a PPPoE or analog modem user: # # EXTIF="ppp0" # EXTIF="eth0" INTIF="eth1" echo " External Interface: $EXTIF" echo " Internal Interface: $INTIF" echo " ---" # Specify your Static IP address here or let the script take care of it # for you. # # If you prefer to use STATIC addresses in your firewalls, un-# out the # static example below and # out the dynamic line. If you don't care, # just leave this section alone. # # If you have a DYNAMIC IP address, the ruleset already takes care of # this for you. Please note that the different single and double quote # characters and the script MATTER. # # # PPP and DHCP (Cablemodem and DSL ) users: # ----------------------------------------- # PPP: If you get your TCP/IP address via DHCP, **you will need ** to # enable the # #ed out command below underneath the PPP section AND # replace the word "eth0" with the name of your EXTERNAL Internet # connection (ppp0, ippp0, etc) on the lines for "ppp-ip" and "extip". # # DHCP and PPP users: The remote DHCP or PPP server can and will change # IP addresses on you over time. To deal with this, users should configure # their DHCP or PPP client to re-run the rc.firewall-* ruleset everytime # the IP address is changed. Please see the "masq-and-dyn-addr" FAQ entry # in the IPMASQ howto for full details on how to do this. # # # Determine the external IP automatically: # ---------------------------------------- # # The following line will determine your external IP address. This # line is somewhat complex and confusing but it will also work for # all NON-English Linux distributions: # EXTIP="`$IFCONFIG $EXTIF | $AWK \ /$EXTIF/'{next}//{split($0,a,":");split(a[2],a," ");print a[1];exit}'`" # For users who wish to use STATIC IP addresses: # # # out the EXTIP line above and un-# out the EXTIP line below # #EXTIP="your.static.PPP.address" echo " External IP: $EXTIP" echo " ---" # Assign the internal TCP/IP network and IP address INTNET="192.168.0.0/24" INTIP="192.168.0.1/32" echo " Internal Network: $INTNET" echo " Internal IP: $INTIP" echo " ---" # Setting a few other local variables # UNIVERSE="0.0.0.0/0" #====================================================================== #== No editing beyond this line is required for initial MASQ testing == # Need to verify that all modules have all required dependencies # echo " - Verifying that all kernel modules are ok" $DEPMOD -a echo -en " Loading kernel modules: " # With the new IPTABLES code, the core MASQ functionality is now either # modular or compiled into the kernel. This HOWTO shows ALL IPTABLES # options as MODULES. If your kernel is compiled correctly, there is # NO need to load the kernel modules manually. # # NOTE: The following items are listed ONLY for informational reasons. # There is no reason to manual load these modules unless your # kernel is either mis-configured or you intentionally disabled # the kernel module autoloader. # # Upon the commands of starting up IP Masq on the server, the # following kernel modules will be automatically loaded: # # NOTE: Only load the IP MASQ modules you need. All current IP MASQ # modules are shown below but are commented out from loading. # =============================================================== #Load the main body of the IPTABLES module - "ip_tables" # - Loaded automatically when the "iptables" command is invoked # # - Loaded manually to clean up kernel auto-loading timing issues # echo -en "ip_tables, " # #Verify the module isn't loaded. If it is, skip it # if [ -z "` $LSMOD | $GREP ip_tables | $AWK {'print $1'} `" ]; then $MODPROBE ip_tables fi #Load the IPTABLES filtering module - "iptable_filter" # # - Loaded automatically when filter policies are activated #Load the stateful connection tracking framework - "ip_conntrack" # # The conntrack module in itself does nothing without other specific # conntrack modules being loaded afterwards such as the "ip_conntrack_ftp" # module # # - This module is loaded automatically when MASQ functionality is # enabled # # - Loaded manually to clean up kernel auto-loading timing issues # echo -en "ip_conntrack, " # #Verify the module isn't loaded. If it is, skip it # if [ -z "` $LSMOD | $GREP ip_conntrack | $AWK {'print $1'} `" ]; then $MODPROBE ip_conntrack fi #Load the FTP tracking mechanism for full FTP tracking # # Enabled by default -- insert a "#" on the next line to deactivate # echo -e "ip_conntrack_ftp, " # #Verify the module isn't loaded. If it is, skip it # if [ -z "` $LSMOD | $GREP ip_conntrack_ftp | $AWK {'print $1'} `" ]; then $MODPROBE ip_conntrack_ftp fi #Load the IRC tracking mechanism for full IRC tracking # # Disabled by default -- insert a "#" on the next few lines to activate # # echo -en " ip_conntrack_irc, " # #Verify the module isn't loaded. If it is, skip it # # if [ -z "` $LSMOD | $GREP ip_conntrack_irc | $AWK {'print $1'} `" ]; then # $MODPROBE ip_conntrack_irc # fi #Load the general IPTABLES NAT code - "iptable_nat" # - Loaded automatically when MASQ functionality is turned on # # - Loaded manually to clean up kernel auto-loading timing issues # echo -en "iptable_nat, " # #Verify the module isn't loaded. If it is, skip it # if [ -z "` $LSMOD | $GREP iptable_nat | $AWK {'print $1'} `" ]; then $MODPROBE iptable_nat fi #Loads the FTP NAT functionality into the core IPTABLES code # Required to support non-PASV FTP. # # Enabled by default -- insert a "#" on the next line to deactivate # echo -e "ip_nat_ftp" # #Verify the module isn't loaded. If it is, skip it # if [ -z "` $LSMOD | $GREP ip_nat_ftp | $AWK {'print $1'} `" ]; then $MODPROBE ip_nat_ftp fi #Loads the IRC NAT functionality (for DCC) into the core IPTABLES code # # DISABLED by default -- delete the "#" on the next few lines to activate # # echo -e "ip_nat_irc" # #Verify the module isn't loaded. If it is, skip it # # if [ -z "` $LSMOD | $GREP ip_nat_irc | $AWK {'print $1'} `" ]; then # $MODPROBE ip_nat_irc # fi echo " ---" # Just to be complete, here is a partial list of some of the other # IPTABLES kernel modules and their function. Please note that most # of these modules (the ipt ones) are automatically loaded by the # master kernel module for proper operation and don't need to be # manually loaded. # -------------------------------------------------------------------- # # ip_nat_snmp_basic - this module allows for proper NATing of some # SNMP traffic # # iptable_mangle - this target allows for packets to be # manipulated for things like the TCPMSS # option, etc. # # -- # # ipt_mark - this target marks a given packet for future action. # This automatically loads the ipt_MARK module # # ipt_tcpmss - this target allows to manipulate the TCP MSS # option for braindead remote firewalls. # This automatically loads the ipt_TCPMSS module # # ipt_limit - this target allows for packets to be limited to # to many hits per sec/min/hr # # ipt_multiport - this match allows for targets within a range # of port numbers vs. listing each port individually # # ipt_state - this match allows to catch packets with various # IP and TCP flags set/unset # # ipt_unclean - this match allows to catch packets that have invalid # IP/TCP flags set # # iptable_filter - this module allows for packets to be DROPped, # REJECTed, or LOGged. This module automatically # loads the following modules: # # ipt_LOG - this target allows for packets to be # logged # # ipt_REJECT - this target DROPs the packet and returns # a configurable ICMP packet back to the # sender. #CRITICAL: Enable IP forwarding since it is disabled by default since # # Redhat Users: you may try changing the options in # /etc/sysconfig/network from: # # FORWARD_IPV4=false # to # FORWARD_IPV4=true # echo " Enabling forwarding.." echo "1" > /proc/sys/net/ipv4/ip_forward # Dynamic IP users: # # If you get your IP address dynamically from SLIP, PPP, or DHCP, # enable the following option. This enables dynamic-address hacking # which makes the life with Diald and similar programs much easier. # echo " Enabling DynamicAddr.." echo "1" > /proc/sys/net/ipv4/ip_dynaddr echo " ---" ############################################################################# # # Enable Stronger IP forwarding and Masquerading # # NOTE: In IPTABLES speak, IP Masquerading is a form of SourceNAT or SNAT. # # NOTE #2: The following is an example for an internal LAN address in the # 192.168.0.x network with a 255.255.255.0 or a "24" bit subnet # mask connecting to the Internet on external interface "eth0". # This example will MASQ internal traffic out to the Internet # but not allow non-initiated traffic into your internal network. # # # ** Please change the above network numbers, subnet mask, and your # #Clearing any previous configuration # # Unless specified, the defaults for INPUT, OUTPUT, and FORWARD to DROP # # You CANNOT change this to REJECT as it isn't a vaild policy setting. # If you want REJECT, you must explictly REJECT at the end of a giving # INPUT, OUTPUT, or FORWARD chain # echo " Clearing any existing rules and setting default policy to DROP.." $IPTABLES -P INPUT DROP $IPTABLES -F INPUT $IPTABLES -P OUTPUT DROP $IPTABLES -F OUTPUT $IPTABLES -P FORWARD DROP $IPTABLES -F FORWARD $IPTABLES -F -t nat #Not needed and it will only load the unneeded kernel module # #$IPTABLES -F -t mangle # Delete all User-specified chains $IPTABLES -X # Reset all IPTABLES counters $IPTABLES -Z #Configuring specific CHAINS for later use in the ruleset # # NOTE: Some users prefer to have their firewall silently # "DROP" packets while others prefer to use "REJECT" # to send ICMP error messages back to the remote # machine. The default is "REJECT" but feel free to # change this below. # # NOTE: Without the --log-level set to "info", every single # firewall hit will goto ALL vtys. This is a very big # pain. # echo " Creating a DROP chain.." $IPTABLES -N reject-and-log-it $IPTABLES -A reject-and-log-it -j LOG --log-level info $IPTABLES -A reject-and-log-it -j REJECT echo -e "\n - Loading INPUT rulesets" ####################################################################### # INPUT: Incoming traffic from various interfaces. All rulesets are # already flushed and set to a default policy of DROP. # # loopback interfaces are valid. # $IPTABLES -A INPUT -i lo -s $UNIVERSE -d $UNIVERSE -j ACCEPT # local interface, local machines, going anywhere is valid # $IPTABLES -A INPUT -i $INTIF -s $INTNET -d $UNIVERSE -j ACCEPT # remote interface, claiming to be local machines, IP spoofing, get lost # $IPTABLES -A INPUT -i $EXTIF -s $INTNET -d $UNIVERSE -j reject-and-log-it # external interface, from any source, for ICMP traffic is valid # # If you would like your machine to "ping" from the Internet, # enable this next line # #$IPTABLES -A INPUT -i $EXTIF -p ICMP -s $UNIVERSE -d $EXTIP -j ACCEPT # remote interface, any source, going to the MASQ servers IP address is valid # # ENABLE this line if you want ALL Internet traffic to connect to your # the various servers running on the MASQ server. This includes # web servers, ssh servers, dns servers, etc. # # I DON'T recommend you enable this rule. Instead, only enable specific # access to select server ports under the "OPTIONAL INPUT Section". # An example of enabling HTTP (WWW) has been given below: # # #$IPTABLES -A INPUT -i $EXTIF -s $UNIVERSE -d $EXTIP -j ACCEPT # Allow any related traffic coming back to the MASQ server in. # # STATEFULLY TRACKED # $IPTABLES -A INPUT -i $EXTIF -s $UNIVERSE -d $EXTIP -m state --state \ ESTABLISHED,RELATED -j ACCEPT # ----- Begin OPTIONAL INPUT Section ----- # # DHCPd - Enable the following lines if you run an INTERNAL DHCPd server # #$IPTABLES -A INPUT -i $INTIF -p tcp --sport 68 --dport 67 -j ACCEPT #$IPTABLES -A INPUT -i $INTIF -p udp --sport 68 --dport 67 -j ACCEPT # HTTPd - Enable the following lines if you run an EXTERNAL WWW server # # NOTE: This is NOT needed for simply enabling PORTFW. This is ONLY # for users that plan on running Apache on the MASQ server itself # #echo -e " - Allowing EXTERNAL access to the WWW server" #$IPTABLES -A INPUT -i $EXTIF -m state --state NEW,ESTABLISHED,RELATED \ # -p tcp -s $UNIVERSE -d $EXTIP --dport 80 -j ACCEPT # # ----- End OPTIONAL INPUT Section ----- # Catch all rule, all other incoming is denied and logged. # $IPTABLES -A INPUT -s $UNIVERSE -d $UNIVERSE -j reject-and-log-it # --------------------------------------------------------------------- echo -e " - Loading OUTPUT rulesets" ####################################################################### # OUTPUT: Outgoing traffic from various interfaces. All rulesets are # already flushed and set to a default policy of DROP. # # Workaround bug in netfilter # See http://www.netfilter.org/security/2002-04-02-icmp-dnat.html # $IPTABLES -A OUTPUT -m state -p icmp --state INVALID -j DROP # loopback interface is valid. # $IPTABLES -A OUTPUT -o lo -s $UNIVERSE -d $UNIVERSE -j ACCEPT # local interfaces, any source going to local net is valid # $IPTABLES -A OUTPUT -o $INTIF -s $EXTIP -d $INTNET -j ACCEPT # local interface, MASQ server source going to the local net is valid # $IPTABLES -A OUTPUT -o $INTIF -s $INTIP -d $INTNET -j ACCEPT # outgoing to local net on remote interface, stuffed routing, deny # $IPTABLES -A OUTPUT -o $EXTIF -s $UNIVERSE -d $INTNET -j reject-and-log-it # anything else outgoing on remote interface is valid # $IPTABLES -A OUTPUT -o $EXTIF -s $EXTIP -d $UNIVERSE -j ACCEPT # ----- Begin OPTIONAL OUTPUT Section ----- # # DHCPd - Enable the following lines if you run an INTERNAL DHCPd server # - Remove BOTH #s all the #s if you need this functionality. # #$IPTABLES -A OUTPUT -o $INTIF -p tcp -s $INTIP --sport 67 \ # -d 255.255.255.255 --dport 68 -j ACCEPT #$IPTABLES -A OUTPUT -o $INTIF -p udp -s $INTIP --sport 67 \ # -d 255.255.255.255 --dport 68 -j ACCEPT # # ----- End OPTIONAL OUTPUT Section ----- # Catch all rule, all other outgoing is denied and logged. # $IPTABLES -A OUTPUT -s $UNIVERSE -d $UNIVERSE -j reject-and-log-it echo -e " - Loading FORWARD rulesets" ####################################################################### # FORWARD: Enable Forwarding and thus IPMASQ # # ----- Begin OPTIONAL FORWARD Section ----- # # Put PORTFW commands here # # ----- End OPTIONAL FORWARD Section ----- echo " - FWD: Allow all connections OUT and only existing/related IN" $IPTABLES -A FORWARD -i $EXTIF -o $INTIF -m state --state ESTABLISHED,RELATED \ -j ACCEPT $IPTABLES -A FORWARD -i $INTIF -o $EXTIF -j ACCEPT # Catch all rule, all other forwarding is denied and logged. # $IPTABLES -A FORWARD -j reject-and-log-it echo " - NAT: Enabling SNAT (MASQUERADE) functionality on $EXTIF" # #More liberal form #$IPTABLES -t nat -A POSTROUTING -o $EXTIF -j MASQUERADE # #Stricter form $IPTABLES -t nat -A POSTROUTING -o $EXTIF -j SNAT --to $EXTIP ####################################################################### echo -e "\nrc.firewall-iptables-stronger $FWVER done.\n" |
要在此更强大的防火墙规则集在适当的时间自动启动,请参阅 第 3.4.2 节 末尾部分以获取完整详细信息。请确保您进行了正确的将 “rc.firewall-iptables” 替换为 “rc.firewall-iptables-stronger” 的操作!!
本节提供了关于使用 2.2.x 防火墙工具 IPCHAINS 的更深入指南。有关 IPFWADM 规则集,请参阅以上章节。
此示例适用于位于具有静态 PPP 地址的 PPP 链路后的防火墙/伪装系统(包含动态 PPP 说明,但已禁用)。受信任的接口是 192.168.0.1,并且 PPP 接口 IP 地址已更改以保护“有罪者” :-)。我已单独列出每个传入和传出接口,以捕获 IP 欺骗以及填充路由和/或伪装。任何未明确允许的内容都是 禁止的(实际上是拒绝的)。如果在实施此 rc.firewall-ipchains-stronger 脚本后,您的 IP MASQ 框出现故障,请务必针对您的配置对其进行编辑,并检查您的 /var/log/messages 或 /var/adm/messages SYSLOG 文件中是否有任何防火墙错误。
有关 PPP、有线调制解调器用户等强 IP 伪装 IPFWADM 规则集的更全面示例,请参阅 TrinityOS - 第 10 节 和 GreatCircle 的防火墙 WWW 页面
注意事项 #1: --- 更新您的内核 --- 低于 2.2.20 版本的 Linux 2.2.x 内核包含多个不同的 安全漏洞(有些是 MASQ 特定的)。低于 2.2.20 版本的内核有一些本地漏洞。低于 2.2.16 版本的内核有一个 TCP 根利用漏洞,低于 2.2.11 版本的内核有一个 IPCHAINS 分片错误。由于这些问题,使用强 IPCHAINS 规则集运行防火墙的用户容易受到可能的入侵。请将您的内核升级到已修复的版本。
注意事项 #2: 如果您从 ISP(PPP、DSL、有线调制解调器等)获得动态分配的 TCP/IP 地址,则您无法在启动时加载此强规则集。您要么需要在每次获得新 IP 地址时重新加载此防火墙规则集,要么使您的 /etc/rc.d/rc.firewall-ipchains-stronger 规则集更智能。要为各种类型的连接(如 PPP 或 DHCP 用户)执行此操作,请参阅 第 7.8 节 FAQ 条目以获取所有详细信息。
另请注意,还有几种 GUI 防火墙创建工具可用。有关完整详细信息,请参阅 第 7 章。
最后,如果您使用的是静态 PPP IP 地址,请更改 “EXTIF="your.static.PPP.address"” 行以反映您的地址。
----------------------------------------------------------------
<rc.firewall-ipchains-stronger START>
#!/bin/sh # # /etc/rc.d/rc.firewall-ipchains-stronger: An example of a Stronger IPCHAINS # firewall ruleset for 2.2 kernels # FWVER=0.75s # # Log: # 0.75s - Updated the commands for dynamically addresses machines and # to point to an expanded FAQ section for more information # # 0.74s - renamed from rc.firewall-2.2-stronger to # rc.firewall-ipchains-stronger to better reflect that this ruleset can # can run on different major kernel versions # - removed unused SED variable # 0.73s - Added additional comments to make PORTFW configs more obvious # 0.72s - #ed out the rule that would allow all traffic destined for the # MASQ server itself to be accepted. Use the OPTIONAL INPUT # section to only allow explicit services. # - Fixed an INTLAN rule that was allowing traffic from ANY IP address # instead of the proper INTIP IP address only. This aligns the # IPCHAINS ruleset with the IPTABLES and IPFWADM ruleset examples # 0.71s - ruleset now uses modprobe instead of insmod # 0.70s - Added missing execution variables # - fixed a missing -p tcp for the commented HTTPd section # 0.65s - Added comments HTTPd rules to the INPUT and OUTPUT section # - Added a comment where to insert IPPORTFW commands # 0.60s - Changed the EXTIP command to work on NON-English distros # - Updated the CASE of some of the script variables # echo -e "\nLoading rc.firewall-ipchains-stronger : version $FWVER..\n" # The location of various iptables and other shell programs # # If your Linux distribution came with a copy of iptables, most # likely it is located in /sbin. If you manually compiled # iptables, the default location is in /usr/local/sbin # # ** Please use the "whereis iptables" command to figure out # ** where your copy is and change the path below to reflect # ** your setup # IPCHAINS=/sbin/ipchains LSMOD=/sbin/lsmod DEPMOD=/sbin/depmod MODPROBE=/sbin/modprobe GREP=/bin/grep AWK=/bin/awk IFCONFIG=/sbin/ifconfig PATH=/sbin:/bin:/usr/sbin:/usr/bin # Global variables # ---------------- # ALL PPP and DHCP users must set this for the correct EXTERNAL and # INTERNAL interfaces names. Examples: eth0, ppp0, ippp0, etc. # See more info about this below. # EXTIF="ppp0" INTIF="eth0" # The INTERNAL IP address # INTIP="192.168.0.1/32" INTNET="192.168.0.0/24" echo " Internal IP: $INTIP" echo " Internal Network: $INTNET" # Load all required IP MASQ modules # # NOTE: Only load the IP MASQ modules you need. All current IP MASQ modules # are shown below but are commented from loading. # Needed to initially load modules # $DEPMOD -a # Supports the proper masquerading of FTP file transfers using the PORT method # $MODPROBE ip_masq_ftp # Supports the masquerading of RealAudio over UDP. Without this module, # RealAudio WILL function but in TCP mode. This can cause a reduction # in sound quality # $MODPROBE ip_masq_raudio # Supports the masquerading of IRC DCC file transfers # #$MODPROBE ip_masq_irc # Supports the masquerading of Quake and QuakeWorld by default. These modules are # for multiple users behind the Linux MASQ server. If you are going to # play Quake I, II, and III, use the second example. # # NOTE: If you get ERRORs loading the QUAKE module, you are running an old # ----- kernel that has bugs in it. Please upgrade to the newest kernel. # #Quake I / QuakeWorld (ports 26000 and 27000) #$MODPROBE ip_masq_quake # #Quake I/II/III / QuakeWorld (ports 26000, 27000, 27910, 27960) #$MODPROBE ip_masq_quake 26000,27000,27910,27960 # Supports the masquerading of the CuSeeme video conferencing software # #$MODPROBE ip_masq_cuseeme #Supports the masquerading of the VDO-live video conferencing software # #$MODPROBE ip_masq_vdolive #CRITICAL: Enable IP forwarding since it is disabled by default # # Redhat Users: you may try changing the options in # /etc/sysconfig/network from: # # FORWARD_IPV4=false # to # FORWARD_IPV4=true # echo "1" > /proc/sys/net/ipv4/ip_forward #CRITICAL: Enable automatic IP defragmentation since it is disabled by default # in 2.2.x kernels # # This used as a compile-time option but the behavior was changed # in 2.2.12. It should also be noted that some distributions have # removed this option from the /proc table. If this entry isn't # present in your /proc, don't worry about it. # echo "1" > /proc/sys/net/ipv4/ip_always_defrag # Dynamic IP users: # # If you get your IP address dynamically from SLIP, PPP, or DHCP, enable this # following option. This enables dynamic-ip address hacking in IP MASQ, # making life with Diald and similar programs much easier. # #echo "1" > /proc/sys/net/ipv4/ip_dynaddr # Enable the LooseUDP patch which some Internet-based games require # # If you are trying to get an Internet game to work through your IP MASQ box, # and you configured it to the best of your ability without it working, try # enabling this option (delete the "#" character). This option is disabled # by default due to possible internal machine UDP port scanning # vulnerabilities. # #echo "1" > /proc/sys/net/ipv4/ip_masq_udp_dloose # Specify your Static IP address here. # # If you have a DYNAMIC IP address, you need to make this ruleset recognize # your IP address everytime you get a new IP. To do this, enable the # following one-line script. (Please note that the different single and # double quote characters MATTER). # # # DHCP users (Cablemodem and DSL ) users: # --------------------------------------- # If you get your TCP/IP address via DHCP, **you will need ** to enable the # #ed out command below underneath the PPP section AND replace the word # "ppp0" with the name of your EXTERNAL Internet connection (eth0, eth1, etc) # on the lines for "ppp-ip" and "EXTIP". # # DHCP and PPP users: The remote DHCP or PPP server can and will change # IP addresses on you over time. To deal with this, users should configure # their DHCP or PPP client to re-run the rc.firewall-* ruleset everytime # the IP address is changed. Please see the "masq-and-dyn-addr" FAQ entry # in the IPMASQ howto for full details on how to do this. # # # Determine the external IP automatically: # ---------------------------------------- # # The following line will determine your external IP address. This # line is somewhat complex and confusing but it will also work for # all NON-English Linux distributions. # # Make sure the EXTIF variable above is set to reflect the name # of your Internet connection # EXTIP="`$IFCONFIG $EXTIF | $AWK \ /$EXTIF/'{next}//{split($0,a,":");split(a[2],a," ");print a[1];exit}'`" # MASQ timeouts # # 2 hrs timeout for TCP session timeouts # 10 sec timeout for traffic after the TCP/IP "FIN" packet is received # 60 sec timeout for UDP traffic (MASQ'ed ICQ users must enable a 30sec # firewall timeout in ICQ itself) # $IPCHAINS -M -S 7200 10 60 ############################################################################# # Incoming, flush and set default policy of reject. Actually the default policy # is irrelevant because there is a catch all rule with deny and log. # $IPCHAINS -F input $IPCHAINS -P input REJECT # local interface, local machines, going anywhere is valid # $IPCHAINS -A input -i $INTIF -s $INTNET -d 0.0.0.0/0 -j ACCEPT # remote interface, claiming to be local machines, IP spoofing, get lost # $IPCHAINS -A input -i $EXTIF -s $INTNET -d 0.0.0.0/0 -l -j REJECT # remote interface, any source, going to the MASQ servers IP address is valid # # ENABLE this line if you want ALL Internet traffic to connect to your # the various servers running on the MASQ server. This includes # web servers, ssh servers, dns servers, etc. # # I DON'T recommend you enable this rule. Instead, only enable specific # access to select server ports under the "OPTIONAL INPUT Section". # An example of enabling HTTP (WWW) has been given below: # # #$IPCHAINS -A input -i $EXTIF -s 0.0.0.0/0 -d $EXTIP/32 -j ACCEPT # loopback interface is valid. # $IPCHAINS -A input -i lo -s 0.0.0.0/0 -d 0.0.0.0/0 -j ACCEPT # ----- Begin OPTIONAL INPUT Section ----- # # HTTPd - Enable the following lines if you either run a WWW server on # the IPMASQ server -OR- plan on PORTFW'ing HTTP traffic to # an internal WWW server # #$IPCHAINS -A input -i $EXTIF -p tcp -s 0.0.0.0/0 -d $EXTIP 80 -j ACCEPT # # ----- End OPTIONAL INPUT Section ----- # catch all rule, all other incoming is denied and logged. pity there is no # log option on the policy but this does the job instead. # $IPCHAINS -A input -s 0.0.0.0/0 -d 0.0.0.0/0 -l -j REJECT ############################################################################# # Outgoing, flush and set default policy of reject. Actually the default policy # is irrelevant because there is a catch all rule with deny and log. # $IPCHAINS -F output $IPCHAINS -P output REJECT # local interface, MASQ server source going to the local net is valid # $IPCHAINS -A output -i $INTIF -s $INTIP -d $INTNET -j ACCEPT # outgoing to local net on remote interface, stuffed routing, deny # $IPCHAINS -A output -i $EXTIF -s 0.0.0.0/0 -d $INTNET -l -j REJECT # outgoing from local net on remote interface, stuffed masquerading, deny # $IPCHAINS -A output -i $EXTIF -s $INTNET -d 0.0.0.0/0 -l -j REJECT # anything else outgoing on remote interface is valid # $IPCHAINS -A output -i $EXTIF -s $EXTIP/32 -d 0.0.0.0/0 -j ACCEPT # loopback interface is valid. # $IPCHAINS -A output -i lo -s 0.0.0.0/0 -d 0.0.0.0/0 -j ACCEPT # ----- Begin OPTIONAL OUTPUT Section ----- # # HTTPd - Enable the following lines if you either run a WWW server on # the IPMASQ server -OR- plan on PORTFW'ing HTTP traffic to # an internal WWW server # #$IPCHAINS -A output -i $EXTIF -p tcp -s $EXTIP 80 -d 0.0.0.0/0 -j ACCEPT # # ----- End OPTIONAL OUTPUT Section ----- # catch all rule, all other outgoing is denied and logged. pity there is no # log option on the policy but this does the job instead. # $IPCHAINS -A output -s 0.0.0.0/0 -d 0.0.0.0/0 -l -j REJECT ############################################################################# # Forwarding, flush and set default policy of deny. Actually the default policy # is irrelevant because there is a catch all rule with deny and log. # $IPCHAINS -F forward $IPCHAINS -P forward DENY # ----- Begin OPTIONAL FORWARD Section ----- # # Put PORTFW commands here # # ----- End OPTIONAL FORWARD Section ----- # Masquerade from local net on local interface to anywhere. # $IPCHAINS -A forward -i $EXTIF -s $INTNET -d 0.0.0.0/0 -j MASQ # # catch all rule, all other forwarding is denied and logged. pity there is no # log option on the policy but this does the job instead. # $IPCHAINS -A forward -s 0.0.0.0/0 -d 0.0.0.0/0 -l -j REJECT #End of file. |
要在此更强大的防火墙规则集在适当的时间自动启动,请参阅 第 3.4.2 节 末尾部分以获取完整详细信息。请确保您进行了正确的将 “rc.firewall-ipchains” 替换为 “rc.firewall-ipchains-stronger” 的操作!!
使用 IPCHAINS,您可以使用 “input”、“output” 和/或 “forward” 规则阻止到特定站点的流量。请记住,规则集是从上到下扫描的,“-A” 告诉 IPCHIANS 将此新规则“附加”到现有规则集中。因此,请记住这一点,任何特定限制都需要在任何全局规则之前出现。例如
使用 “input” 规则
可能是阻止流量的最快和最有效的方法,但此方法仅阻止被 MASQ 的机器,而不阻止防火墙机器本身。当然,您可能希望允许这种组合。
无论如何,要阻止 204.50.10.13
In the /etc/rc.d/rc.firewall-ipchains-stronger ruleset: ... start of "input" rules ... # reject and log local interface, local machines going to 204.50.10.13 # ipchains -A input -s 192.168.0.0/24 -d 204.50.10.13/32 -l -j REJECT # local interface, local machines, going anywhere is valid # ipchains -A input -s 192.168.0.0/24 -d 0.0.0.0/0 -l -j ACCEPT ... end of "input" rules ... |
使用 “output” 规则
这是阻止流量的较慢方法,因为数据包必须在被丢弃之前通过伪装。然而,此规则甚至阻止防火墙机器访问禁止的站点。
... “output” 规则开始 ... # 拒绝并记录到 204.50.10.13 的传出 # ipchains -A output -s $ppp_ip/32 -d 204.50.10.13/32 -l -j REJECT # 远程接口上任何其他传出都是有效的 # ipchains -A output -s $ppp_ip/32 -d 0.0.0.0/0 -l -j ACCEPT ... “output” 规则结束 ...
使用 “forward” 规则
可能比用于阻止流量的 “input” 规则更慢,这仅阻止被伪装的机器(例如,内部机器)。防火墙机器仍然可以访问禁止的站点。
... “forward” 规则开始 ... # 拒绝并记录从 PPP 接口上的本地网络到 204.50.10.13 的流量。 # ipchains -A forward -i ppp0 -s 192.168.0.0/24 -d 204.50.10.13/32 -l -j REJECT # 将本地网络上本地接口的流量伪装到任何地方。 # ipchains -A forward -i ppp0 -s 192.168.0.0/24 -d 0.0.0.0/0 -j MASQ ... “forward” 规则结束 ...
无需特殊规则来允许 192.168.0.0/24 网络上的机器访问 204.50.11.0。为什么?它已被全局 MASQ 规则覆盖。
注意:与 IPFWADM 不同,IPCHIANS 只有一种编码接口名称的方式。IPCHAINS 使用 “-i eth0” 选项,而 IPFWADM 既有用于接口名称的 “-W” 选项,也有用于接口 IP 地址的 “-V” 选项。
本节提供了关于使用 2.0.x 防火墙工具 IPFWADM 的更深入指南。有关 IPCHAINS 规则集,请参阅下文
此示例适用于位于具有静态 PPP 地址的 PPP 链路后的防火墙/伪装系统(包含动态 PPP 说明,但已禁用)。受信任的接口是 192.168.0.1,并且 PPP 接口 IP 地址已更改以保护“有罪者” :)。我已单独列出每个传入和传出接口,以捕获 IP 欺骗以及填充路由和/或伪装。任何未明确允许的内容都是 禁止的(实际上是拒绝的)。如果在实施此 rc.firewall-ipfwadm-stronger 脚本后,您的 IP MASQ 框出现故障,请务必针对您的配置对其进行编辑,并检查您的 /var/log/messages 或 /var/adm/messages SYSLOG 文件中是否有任何防火墙错误。
有关 PPP、有线调制解调器用户等强 IP 伪装 IPFWADM 规则集的更全面示例,请参阅 TrinityOS - 第 10 节 和 GreatCircle 的防火墙 WWW 页面
注意事项 #2: 如果您从 ISP(PPP、DSL、有线调制解调器等)获得动态分配的 TCP/IP 地址,则您无法在启动时加载此强规则集。您要么需要在每次获得新 IP 地址时重新加载此防火墙规则集,要么使您的 /etc/rc.d/rc.firewall-ipchains-stronger 规则集更智能。要为各种类型的连接(如 PPP 或 DHCP 用户)执行此操作,请参阅 第 7.8 节 FAQ 条目以获取所有详细信息。
另请注意,还有几种 GUI 防火墙创建工具可用。有关完整详细信息,请参阅 第 7 章。
最后,如果您使用的是静态 PPP IP 地址,请更改 “ppp_ip="your.static.PPP.address"” 行以反映您的地址。
----------------------------------------------------------------
<rc.firewall-ipfwadm-stronger START>
#!/bin/sh # # /etc/rc.d/rc.firewall-ipfwadm-stronger: An example of a semi-STRONG # IPFWADM firewall ruleset for 2.0 kernels # FWVER=0.74s # # Log: # 0.74s - Updated the commands for dynamically addresses machines and # to point to an expanded FAQ section for more information # # 0.73s - renamed from rc.firewall-2.0-stronger to # rc.firewall-ipfwadm-stronger # # 0.72s - #ed out the rule that would allow all traffic destined for the # MASQ server itself to be accepted. Use the OPTIONAL INPUT # section to only allow explicit services. PATH=/sbin:/bin:/usr/sbin:/usr/bin # testing, wait a bit then clear all firewall rules. # uncomment the following lines if you want the firewall to automatically # disable after 10 minutes. # # Disabled by default # # (sleep 600; \ # ipfwadm -I -f; \ # ipfwadm -I -p accept; \ # ipfwadm -O -f; \ # ipfwadm -O -p accept; \ # ipfwadm -F -f; \ # ipfwadm -F -p accept; \ # ) & # Load all required IP MASQ modules # # NOTE: Only load the IP MASQ modules you need. All current IP MASQ modules # are shown below but are commented from loading. # Needed to initially load modules # /sbin/depmod -a # Supports the proper masquerading of FTP file transfers using the PORT method # /sbin/modprobe ip_masq_ftp # Supports the masquerading of RealAudio over UDP. Without this module, # RealAudio WILL function but in TCP mode. This can cause a reduction # in sound quality # #/sbin/modprobe ip_masq_raudio # Supports the masquerading of IRC DCC file transfers # #/sbin/modprobe ip_masq_irc # Supports the masquerading of Quake and QuakeWorld by default. This modules is # for multiple users behind the Linux MASQ server. If you are going to # play Quake I, II, and III, use the second example. # # NOTE: If you get ERRORs loading the QUAKE module, you are running an old # ----- kernel that has bugs in it. Please upgrade to the newest kernel. # #Quake I / QuakeWorld (ports 26000 and 27000) #/sbin/modprobe ip_masq_quake # #Quake I/II/III / QuakeWorld (ports 26000, 27000, 27910, 27960) #/sbin/modprobe ip_masq_quake 26000,27000,27910,27960 # Supports the masquerading of the CuSeeme video conferencing software # #/sbin/modprobe ip_masq_cuseeme #Supports the masquerading of the VDO-live video conferencing software # #/sbin/modprobe ip_masq_vdolive #CRITICAL: Enable IP forwarding, since it is disabled by default # # Redhat Users: you may try changing the options in /etc/sysconfig/network # from: # # FORWARD_IPV4=false # to # FORWARD_IPV4=true # echo "1" > /proc/sys/net/ipv4/ip_forward #CRITICAL: Enable automatic IP defragmenting since it is disabled by default # in 2.2.x kernels # # This used to be a compile-time option but the behavior was changed # in 2.2.12 # echo "1" > /proc/sys/net/ipv4/ip_always_defrag # Dynamic IP users: # # If you get your IP address dynamically from SLIP, PPP, or DHCP, enable this # following option. This allows dynamic-ip address hacking in IP MASQ, # making the life with Diald and similar programs much easier. # #echo "1" > /proc/sys/net/ipv4/ip_dynaddr # Specify your Static IP address here. # # If you have a DYNAMIC IP address, you need to make this ruleset understand # your IP address everytime you get a new IP. To do this, enable the # following one-line script. (Please note that the different single and # double quote characters MATTER). # # # DHCP (Cablemodem and DSL) and PPP users: # ---------------------------------------- # If you get your TCP/IP address a dynamic IP address **you will need ** to # enable the #ed out command below underneath the PPP section AND replace the word # "ppp0" with the name of your EXTERNAL Internet connection (eth0, eth1, # etc). # # DHCP and PPP users: The remote DHCP or PPP server can and will change # IP addresses on you over time. To deal with this, users should configure # their DHCP or PPP client to re-run the rc.firewall-* ruleset everytime # the IP address is changed. Please see the "masq-and-dyn-addr" FAQ entry # in the IPMASQ howto for full details on how to do this. # # # PPP and DHCP Users: # ------------------- # Remove the # on the line below and place a # in front of the line after that. # #ppp_ip="`/sbin/ifconfig ppp0 | grep 'inet addr' | awk '{print $2}' | sed -e 's/.*://'`" # ppp_ip="your.static.PPP.address" # MASQ timeouts # # 2 hrs timeout for TCP session timeouts # 10 sec timeout for traffic after the TCP/IP "FIN" packet is received # 60 sec timeout for UDP traffic (MASQ'ed ICQ users must enable a 30sec # firewall timeout in ICQ itself) # /sbin/ipfwadm -M -s 7200 10 60 ############################################################################# # Incoming, flush and set default policy of reject. Actually the default policy # is irrelevant because there is a catch all rule with deny and log. # /sbin/ipfwadm -I -f /sbin/ipfwadm -I -p reject # local interface, local machines, going anywhere is valid # /sbin/ipfwadm -I -a accept -V 192.168.0.1 -S 192.168.0.0/24 -D 0.0.0.0/0 # remote interface, claiming to be local machines, IP spoofing, get lost # /sbin/ipfwadm -I -a reject -V $ppp_ip -S 192.168.0.0/24 -D 0.0.0.0/0 -o # remote interface, any source, going to the MASQ servers IP address is valid # # ENABLE this line if you want ALL Internet traffic to connect to your # the various servers running on the MASQ server. This includes # web servers, ssh servers, dns servers, etc. # # I DON'T recommend you enable this rule. Instead, only enable specific # access to select server ports under the "OPTIONAL INPUT Section". # An example of enabling HTTP (WWW) has been given below: # # #/sbin/ipfwadm -I -a accept -V $ppp_ip -S 0.0.0.0/0 -D $ppp_ip/32 # loopback interface is valid. # /sbin/ipfwadm -I -a accept -V 127.0.0.1 -S 0.0.0.0/0 -D 0.0.0.0/0 # catch all rule, all other incoming is denied and logged. pity there is no # log option on the policy but this does the job instead. # /sbin/ipfwadm -I -a reject -S 0.0.0.0/0 -D 0.0.0.0/0 -o ############################################################################# # Outgoing, flush and set default policy of reject. Actually the default policy # is irrelevant because there is a catch all rule with deny and log. # /sbin/ipfwadm -O -f /sbin/ipfwadm -O -p reject # local interface, MASQ server source going to the local net is valid # /sbin/ipfwadm -O -a accept -V 192.168.0.1 -S 0.0.0.0/0 -D 192.168.0.0/24 # outgoing to local net on remote interface, stuffed routing, deny # /sbin/ipfwadm -O -a reject -V $ppp_ip -S 0.0.0.0/0 -D 192.168.0.0/24 -o # outgoing from local net on remote interface, stuffed masquerading, deny # /sbin/ipfwadm -O -a reject -V $ppp_ip -S 192.168.0.0/24 -D 0.0.0.0/0 -o # outgoing from local net on remote interface, stuffed masquerading, deny # /sbin/ipfwadm -O -a reject -V $ppp_ip -S 0.0.0.0/0 -D 192.168.0.0/24 -o # anything else outgoing on remote interface is valid # /sbin/ipfwadm -O -a accept -V $ppp_ip -S $ppp_ip/32 -D 0.0.0.0/0 # loopback interface is valid. # /sbin/ipfwadm -O -a accept -V 127.0.0.1 -S 0.0.0.0/0 -D 0.0.0.0/0 # catch all rule, all other outgoing is denied and logged. pity there is no # log option on the policy but this does the job instead. # /sbin/ipfwadm -O -a reject -S 0.0.0.0/0 -D 0.0.0.0/0 -o ############################################################################# # Forwarding, flush and set default policy of deny. Actually the default policy # is irrelevant because there is a catch all rule with deny and log. # /sbin/ipfwadm -F -f /sbin/ipfwadm -F -p reject # Masquerade from local net on local interface to anywhere. # /sbin/ipfwadm -F -a masquerade -W ppp0 -S 192.168.0.0/24 -D 0.0.0.0/0 # # catch all rule, all other forwarding is denied and logged. Pity there is no # log option on the policy but this does the job instead. # /sbin/ipfwadm -F -a reject -S 0.0.0.0/0 -D 0.0.0.0/0 -o #End of file. |
要在此更强大的防火墙规则集在适当的时间自动启动,请参阅 第 3.4.3 节 末尾部分以获取完整详细信息。请确保您进行了正确的将 “rc.firewall-ipfwadm” 替换为 “rc.firewall-ipfwadm-stronger” 的操作!!
使用 IPFWADM,您可以使用 -I、-O 或 -F 规则阻止到特定站点的流量。请记住,规则集是从上到下扫描的,“-a” 告诉 IPFWADM 将此新规则“附加”到现有规则集中。因此,请记住这一点,任何特定限制都需要在全局规则之前出现。例如
使用 -I (input) 规则
可能是阻止流量的最快和最有效的方法,但它仅阻止被 MASQ 的机器,而不阻止防火墙机器本身。当然,您可能希望允许这种组合。
无论如何,要阻止 204.50.10.13
在 /etc/rc.d/rc.firewall-ipfwadm-stronger 规则集中: ... -I 规则开始 ... # 拒绝并记录本地接口,本地机器访问 204.50.10.13 # /sbin/ipfwadm -I -a reject -V 192.168.0.1 -S 192.168.0.0/24 -D 204.50.10.13/32 -o # 本地接口,本地机器,访问任何地方都是有效的 # /sbin/ipfwadm -I -a accept -V 192.168.0.1 -S 192.168.0.0/24 -D 0.0.0.0/0 ... -I 规则结束 ...
使用 -O (output) 规则
这是阻止流量的较慢方法,因为数据包首先通过伪装,然后才被丢弃。然而,此规则甚至阻止防火墙机器访问禁止的站点。
... -O 规则开始 ... # 拒绝并记录到 204.50.10.13 的传出 # /sbin/ipfwadm -O -a reject -V $ppp_ip -S $ppp_ip/32 -D 204.50.10.13/32 -o # 远程接口上任何其他传出都是有效的 # /sbin/ipfwadm -O -a accept -V $ppp_ip -S $ppp_ip/32 -D 0.0.0.0/0 ... -O 规则结束 ...
使用 -F (forward) 规则
可能比用于阻止流量的 -I (input) 规则更慢,但这仍然只阻止被伪装的机器(例如,内部机器)。防火墙机器仍然可以访问禁止的站点。
... -F 规则开始 ... # 拒绝并记录从 PPP 接口上的本地网络到 204.50.10.13 的流量。 # /sbin/ipfwadm -F -a reject -W ppp0 -S 192.168.0.0/24 -D 204.50.10.13/32 -o # 将本地网络上本地接口的流量伪装到任何地方。 # /sbin/ipfwadm -F -a masquerade -W ppp0 -S 192.168.0.0/24 -D 0.0.0.0/0 ... -F 规则结束 ...
无需特殊规则来允许 192.168.0.0/24 网络上的机器访问 204.50.11.0。为什么?它已被全局 MASQ 规则覆盖。
注意:在上述规则中,有多种编码接口的方法。例如,您可以使用 “-W eth0” 代替 “-V 192.168.255.1”,可以使用 “-W ppp0” 代替 “-V $ppp_ip”。 “-V” 方法已随着迁移到 IPCHAINS 而逐步淘汰,但对于 IPFWADM 用户来说,这更多的是个人选择和文档。