mirror of
https://gitlab.com/shorewall/code.git
synced 2024-12-15 19:01:19 +01:00
07d90b6fe4
git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@672 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb
86 lines
2.8 KiB
HTML
86 lines
2.8 KiB
HTML
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||
<html>
|
||
<head>
|
||
|
||
<meta http-equiv="Content-Language" content="en-us">
|
||
|
||
<meta http-equiv="Content-Type"
|
||
content="text/html; charset=windows-1252">
|
||
|
||
<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
|
||
|
||
<meta name="ProgId" content="FrontPage.Editor.Document">
|
||
<title>DHCP</title>
|
||
</head>
|
||
<body>
|
||
|
||
<table border="0" cellpadding="0" cellspacing="0"
|
||
style="border-collapse: collapse;" bordercolor="#111111" width="100%"
|
||
id="AutoNumber1" bgcolor="#3366ff" height="90">
|
||
<tbody>
|
||
<tr>
|
||
<td width="100%">
|
||
<h1 align="center"><font color="#ffffff">DHCP</font></h1>
|
||
</td>
|
||
</tr>
|
||
|
||
</tbody>
|
||
</table>
|
||
|
||
<h2 align="left">If you want to Run a DHCP Server on your firewall</h2>
|
||
|
||
<ul>
|
||
<li>
|
||
<p align="left">Specify the "dhcp" option on each interface to be served
|
||
by your server in the <a href="Documentation.htm#Interfaces">/etc/shorewall/interfaces</a>
|
||
file. This will generate rules that will allow DHCP to and from your firewall
|
||
system. </p>
|
||
</li>
|
||
<li>
|
||
<p align="left">When starting "dhcpd", you need to list those interfaces
|
||
on the run line. On a RedHat system, this is done by modifying /etc/sysconfig/dhcpd.
|
||
</p>
|
||
</li>
|
||
|
||
</ul>
|
||
|
||
<h2 align="left">If a Firewall Interface gets its IP Address via DHCP</h2>
|
||
|
||
<ul>
|
||
<li>
|
||
<p align="left">Specify the "dhcp" option for this interface in the
|
||
<a href="Documentation.htm#Interfaces">/etc/shorewall/interfaces</a>
|
||
file. This will generate rules that will allow DHCP to and from your firewall
|
||
system. </p>
|
||
</li>
|
||
<li>
|
||
<p align="left">If you know that the dynamic address is always going to
|
||
be in the same subnet, you can specify the subnet address in the interface's
|
||
entry in the <a href="Documentation.htm#Interfaces">/etc/shorewall/interfaces</a>
|
||
file. </p>
|
||
</li>
|
||
<li>
|
||
<p align="left">If you don't know the subnet address in advance, you should
|
||
specify "detect" for the interface's subnet address in the <a
|
||
href="Documentation.htm#Interfaces">/etc/shorewall/interfaces</a> file
|
||
and start Shorewall after the interface has started. </p>
|
||
</li>
|
||
<li>
|
||
<p align="left">In the event that the subnet address might change while
|
||
Shorewall is started, you need to arrange for a "shorewall refresh"
|
||
command to be executed when a new dynamic IP address gets assigned to
|
||
the interface. Check your DHCP client's documentation. </p>
|
||
</li>
|
||
|
||
</ul>
|
||
|
||
<p align="left"><font size="2">Last updated 11/03/2002 - <a
|
||
href="support.htm">Tom Eastep</a></font></p>
|
||
|
||
<p><font face="Trebuchet MS"><a href="copyright.htm"><font size="2">Copyright</font>
|
||
© <font size="2">2001, 2002 Thomas M. Eastep.</font></a></font></p>
|
||
<br>
|
||
<br>
|
||
</body>
|
||
</html>
|