1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<link rel="stylesheet" type="text/css" href="css.css">
<title>FireHOL, a Linux iptables packet filtering firewall builder for humans...</title>
<meta name="author" content="Costa Tsaousis">
<meta name="description" content="Home for FireHOL, an iptables stateful packet filtering firewall builder for Linux (kernel 2.4),
supporting NAT, SNAT, DNAT, REDIRECT, MASQUERADE, DMZ, dual-homed, multi-homed and router setups,
protecting and securing hosts and LANs in all kinds of topologies. Configuration is done using
simple client and server statements while it can detect (and produce) its configuration
automatically. FireHOL is extremely easy to understand, configure and audit.">
<meta name="keywords" content="iptables, netfilter, filter, firewall, stateful, port, secure, security, NAT, DMZ, DNAT, DSL, SNAT, redirect, router, rule, rules, automated, bash, block, builder, cable, complex, configuration, dual-homed, easy, easy configuration, example, fast, features, flexible, forward, free, gpl, helpme mode, human, intuitive, language, linux, masquerade, modem, multi-homed, open source, packet, panic mode, protect, script, service, system administration, wizard">
<meta http-equiv="Expires" content="Wed, 19 Mar 2003 00:00:01 GMT">
</head>
<body bgcolor="#ffffff">
<center>
<script type="text/javascript"><!--
google_ad_client = "pub-4254040714325099";
google_ad_width = 728;
google_ad_height = 90;
google_ad_format = "728x90_as";
google_ad_channel ="";
google_page_url = document.location;
google_color_border = "336699";
google_color_bg = "FFFFFF";
google_color_link = "0000FF";
google_color_url = "008000";
google_color_text = "000000";
//--></script>
<script type="text/javascript" src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script>
</center>
<table border="0" cellpadding="10" cellspacing="0" width="100%">
<tbody>
<tr>
<td valign="top" width="60%">
<!-- -------------- START OF NEWS ------------------ -->
<table border="0" cellpadding="10" cellspacing="0" width="100%">
<tbody>
<tr>
<td bgcolor="#eeeeee"><b>Latest News</b></td>
</tr>
</tbody>
</table>
<br>
<b>July 31, 2008</b> FireHOL R5 v1.273 released.<br>
<font color="#555555">Updated to parse the latest format of the IANA reservations page.<br>
<br>
Added support for custom actions for services. This opens a way for allowing actions that can be controlled externally without restarting the firewall.
<br>
Fixed several minor issues (better NAT support for all services, handling for external pager command, kernel config parsing, config wizard, etc).
<br>
<hr noshade="noshade">
<b>May 20, 2007</b> FireHOL R5 v1.255 released.<br>
<font color="#555555">Fixed kernel 2.6.20+ compatibility issues, fixed BASH 3.2 compatibility issues, fixed various iptables compatibility issues.<br>
<br>
FireHOL now supports external definitions of <a href="commands.html#RESERVED_IPS"><span style="font-weight: bold;">RESERVED_IPS</span></a>, <a href="commands.html#PRIVATE_IPS"><span style="font-weight: bold;">PRIVATE_IPS</span></a>, <a href="commands.html#MULTICAST_IPS"><span style="font-weight: bold;">MULTICAST_IPS</span></a>, <a href="commands.html#UNROUTABLE_IPS"><span style="font-weight: bold;">UNROUTABLE_IPS</span></a> in /etc/firehol. Also, complains if <a href="commands.html#RESERVED_IPS"><span style="font-weight: bold;">RESERVED_IPS</span></a> is older that 90 days.<br>
<br>
<a href="commands.html#policy">Policy</a>, now works on <a href="commands.html#router">routers</a> too.<br>
<br>
Updated services: <a href="services.html#nfs"><span style="font-weight: bold;">nfs</span></a>, <a href="services.html#OSPF"><span style="font-weight: bold;">OSPF</span></a>, <a href="services.html#sip"><span style="font-weight: bold;">sip</span></a>, <a href="services.html#vmwareweb"><span style="font-weight: bold;">vmwareweb</span></a>. Added protections: <a href="commands.html#protection"><span style="font-weight: bold;">bad-packets</span></a>, <a href="commands.html#protection"><span style="font-weight: bold;">all-floods</span></a>. Added actions: <a href="commands.html#tarpit"><span style="font-weight: bold;">tarpit</span></a>. Added support for the <a href="commands.html#accept"><span style="font-weight: bold;">recent</span></a> iptables module. Added <span style="font-weight: bold;">addrtype</span> (<a href="commands.html#srctype">srctype</a>, <a href="commands.html#dsttype">dsttype</a>) support in optional rule parameters.<br>
<br>
Added <a href="commands.html#FIREHOL_DROP_ORPHAN_TCP_ACK_FIN"><span style="font-weight: bold;">FIREHOL_DROP_ORPHAN_TCP_ACK_FIN</span></a> for busy servers.<br>
Added <a href="commands.html#FIREHOL_LOG_PREFIX"><span style="font-weight: bold;">FIREHOL_LOG_PREFIX</span></a> to improve logging.</font>
<hr noshade="noshade">
<b>Jan 30, 2005</b>, FireHOL R5 v1.226 released.<br>
<font color="#555555">
This release fixes vulnerabilities where malicious local
system users could use FireHOL's temporary files to overwrite
arbitrary files on the system (See <a href="http://secunia.com/advisories/13970/">Secunia Advisory SA13970</a>).
</font>
<p>
<font color="#555555"><b>All users are advised to update to this version.</b>
</font></p>
<p>
<font color="#555555">This release includes new service definitions:
<a href="services.html#anystateless">ANYSTATELESS</a>,
<a href="services.html#timestamp">TIMESTAMP</a> and
<a href="services.html#dict">DICT</a>.
The following helpers have been added:
<a href="commands.html#transparent_proxy">TRANSPARENT_PROXY</a>.
Also, added support for <a href="http://www.zeroflux.org/knock/">knockd</a> as an argument to the <a href="commands.html#accept">accept</a> action.
</font>
</p>
<hr noshade="noshade">
<b>2003-2004</b> FireHOL remains as one of the BEST RATED open source applications.<br>
<font color="#555555">
FireHOL is ranked in <b>TOP 20 BEST RATED</b> of <a href="http://freshmeat.net">FreshMeat II</a>.
See the current <b>rating rank</b> at <a href="http://freshmeat.net/projects/firehol/">FireHOL's FreshMeat page</a>
(note that this page changes dynamically, so the rating might have changed).
<br>
I really thank you all for this...
</font>
<p>
<font color="#555555">Are you using FireHOL too? Tell us your opinion: rate it <a href="http://freshmeat.net/rate/30942/">here</a>.
</font>
</p>
<hr noshade="noshade">
<b>May 3, 2004</b>, Latest CVS tarballs available.<br>
<font color="#555555">
You can download a nightly-build CVS version of FireHOL at <a href="http://firehol.sf.net/firehol.tar.gz">http://firehol.sf.net/firehol.tar.gz</a>
<br>
Although I try to keep CVS versions fully operational, please keep in mind that this CVS version might have bugs.
</font>
<p>
<font color="#555555">You can always see what has changed using
<a href="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/firehol/firehol/firehol.sh">FireHOL's WebCVS Change Log viewer</a>.
</font>
</p>
</td>
<!-- -------------- END OF NEWS ------------------ -->
<td valign="top" width="40%">
<table border="0" cellpadding="10" cellspacing="0" width="100%">
<tbody>
<tr>
<td bgcolor="#eeeeee"><b>Testimonials</b></td>
</tr>
</tbody>
</table>
<small>
<b>Date:</b> Thu, Mar 30, 2006 19:21
</small>
<p>
<small><font color="#333333">
FireHOL is an amazing tool. It leverages the incredible power of
netfilter/iptables to turn Linux into a viable firewall solution, even
for complex scenarios where people would think "Cisco PIX" or "Check
Point FW-1".<br>
Right now I'm using it on a box that filters the traffic passing
between the public Internet, 4 VLANs, 1 DMZ and 2 VPN endpoints, with
address forwardings (DNAT) thrown in for good measure. This amounts to
over 3000 iptables rules (according to "iptables-save") and I still
haven't lost my sanity!<br>
Needless to say, I'm using it on all the other Linux servers too. :)
</font></small></p>
<p>
<small><font color="#333333">Carlos Rodrigues
</font></small></p>
<hr noshade="noshade">
<small><b>Date:</b> Wed, July 7, 2004 03:55
</small>
<p>
<small><font color="#333333">
I want to thank you for making such a brilliant firewall configuration tool.
I have just finished configuring a firewall with 5 ethernets (two office LANs,
two DMZs and one ISP upstream with aliased IPs) for two companies with a
shared broadband internet connection, and it works perfectly.<br>
I still marvel at the shortness and simplicity of your configuration language
contrasted against the completeness and tightness of the fully stateful
iptables rules!
</font></small></p>
<p>
<small><font color="#333333">Brian Hoy
</font></small></p>
<hr noshade="noshade">
<small><b>Date:</b> Fri, October 31, 2003 21:39
</small>
<p>
<small><font color="#333333">
After six hours of nothing but trouble, frustration and desperation with
fwbuilder, I installed FireHOL and within minutes I got everything to work
as desired. Once more: why making things complicate, when you can make it
easy. Thanks a lot.
</font></small></p>
<p>
<small><font color="#333333">cassielix
</font></small></p>
<hr noshade="noshade">
<small><b>Date:</b> Sat, September 27, 2003 19:23
</small>
<p>
<small><font color="#333333">
Hello, I just wanted to thank you for making FireHOL. Explaining firewalls
to my girlfriend is, well, a tough thing to do. After getting your
script configured
and our new DSL connection working, she said "Wow that was fast", then
the inevitable "What did you do?". I showed her the short script and she
read it like it was english. I can't stop smiling.
</font></small></p>
<p>
<small><font color="#333333">Erik Peterson
</font></small></p>
<hr noshade="noshade">
<small><b>Date:</b> Thu, July 31, 2003 23:52
</small>
<p>
<small><font color="#333333">
Just wanted to drop you a quick note to let
you know that I just installed FireHOL 1.120
on my Linux router/firewall, and it worked like
a champ!<br>
Super-easy (your example on the FireHOL web page
is a perfect starting point for setups like mine,
which is a single PC doing NAT/MASQ and firewalling
over DSL for an internal LAN) and much more
effective than my old stateless firewall that
it replaced (which wouldn't even let me ftp without
shutting it down).<br>
Just wanted to say thanks for a job well done, and
for making your work available to the rest of us!
</font></small></p>
<p>
<small><font color="#333333">Scott Taylor<br>
ALVE Technology Corporation
</font>
</small></p>
</td>
</tr>
</tbody>
</table>
<p>
<table border="0" cellpadding="10" cellspacing="0" width="100%">
<tbody>
<tr>
<td bgcolor="#eeeeee"><b>What is FireHOL?</b></td>
</tr>
</tbody>
</table>
<br>
FireHOL is... firewalling made easy:
</p>
<center>
<table border="0" cellpadding="15" cellspacing="20" width="70%">
<tbody>
<tr>
<td bgcolor="#f0f0f0">
<b>
<pre> <a href="commands.html#transparent_squid">transparent_squid</a> 8080 "squid root" <a href="commands.html#inface">inface</a> eth0<br> <br> <a href="commands.html#interface">interface</a> eth0 mylan<br> <a href="commands.html#policy">policy</a> accept<br> <br> <a href="commands.html#interface">interface</a> ppp+ internet<br> <a href="commands.html#server">server</a> <a href="services.html#smtp">smtp</a> accept<br> <a href="commands.html#server">server</a> <a href="services.html#http">http</a> accept<br> <a href="commands.html#server">server</a> <a href="services.html#ftp">ftp</a> accept<br> <a href="commands.html#server">server</a> <a href="services.html#ssh">ssh</a> accept <a href="commands.html#src">src</a> trusted.example.com<br> <br> <a href="commands.html#client">client</a> <a href="services.html#all">all</a> accept<br> <br> <a href="commands.html#router">router</a> mylan2internet <a href="commands.html#inface">inface</a> eth0 <a href="commands.html#outface">outface</a> ppp+<br> <a href="commands.html#masquerade">masquerade</a>
<a href="commands.html#route">route</a> <a href="services.html#all">all</a> accept</pre>
</b>
</td>
</tr>
</tbody>
</table>
</center>
FireHOL is an iptables firewall generator producing stateful iptables packet filtering firewalls, on Linux hosts and routers
with any number of network interfaces, any number of routes, any number of services served, any number of complexity
between variations of the services (including positive and negative expressions).
<p>
FireHOL is a <b>language to express firewalling rules</b>, not just a script that produces some kind of a firewall.
</p>
<p>
The goals of FireHOL are:
</p>
<ul>
<li>Make firewalling an easy, straight forward task for everyone, independently of the security skills he/she has.
<br>
FireHOL configuration files are very easy to type and read. To understand a complex firewall you will need
just a few seconds.
<br>
Take a look bellow for an example configuration.
</li>
<li>Be as secure as possible by allowing explicitly only the wanted traffic to flow.
<br>
FireHOL produces <b>stateful</b> rules for any service or protocol, <b>in both directions</b> of the firewall.
</li>
<li>Be a resource of knowledge around services and their peculiarities, as far as firewalling is concerned.
<br>
Check the <a href="services.html">services</a> list.
</li>
<li>Be open enough for any firewalling need. Although FireHOL is pre-configured for a large number of services, you
can configure any service you like and FireHOL will turn it into a <b>client</b>, a <b>server</b>, or a <b>router</b>.
</li>
<li>Be flexible enough to be used by end users and guru administrators requiring extremely complex firewalls.
<br>
FireHOL configuration files are BASH scripts; you can write in them anything BASH accepts, including variables,
pipes, loops, conditions, calls to external programs, run other BASH scripts with FireHOL directives in them, etc.
</li>
<li>Be simple to install on any modern Linux system; only one file is required, no compilations involved.
</li>
</ul>
<table border="0" cellpadding="10" cellspacing="0" width="100%">
<tbody>
<tr>
<td bgcolor="#eeeeee"><b>Is it secure?</b></td>
</tr>
</tbody>
</table>
<br>
FireHOL is <b>secure</b> because it has been designed with the right firewalling concept: <b>deny everything,
then allow only what is needed</b>.
<p>
Also, FireHOL produces <b>stateful</b> iptables packet filtering firewalls (and possibly, the only generic tool today that
does that for all services in both directions of the firewall).
</p>
<p>
Stateful means that traffic allowed to pass is part of a valid connection that has been initiated the right way.
Stateful also means that you can have control based on
who initiated the traffic. For example: you can choose to be able to ping anyone on the internet, but no one to be able
to ping you. If for example you don't need to run a server on your Linux host, you can easily achieve a situation where
you are able to do anything to anyone, but as far as the rest of world is concerned, <b>you do not exist</b>!
</p>
<p>
<table border="0" cellpadding="10" cellspacing="0" width="100%">
<tbody>
<tr>
<td bgcolor="#eeeeee"><b>Learn another language?</b></td>
</tr>
</tbody>
</table>
<br>
FireHOL has been designed to allow you configure your firewall the same way you think of it.
Its language is extremely simple. Basically you have to learn four commands:
</p>
<ul>
<li><a href="commands.html#interface">interface</a>, to setup a firewall on a network interface
</li>
<li><a href="commands.html#router">router</a>, to setup a firewall on traffic routed from one network interface to another
</li>
<li><a href="commands.html#server">server</a>, to setup a listening service within an interface or router.
The same command can be used as <a href="commands.html#route">route</a> within routers.
</li>
<li><a href="commands.html#client">client</a>, to setup a service client within an interface or router
</li>
</ul>
<b>Client</b> and <b>server</b> commands have exactly the same syntax.
<b>Interface</b> has two mandatory arguments and <b>router</b> has only one (and this is the same with one of the two <b>interface</b> requires).
All the <a href="commands.html#parameters">optional parameters</a> are the same to all of them. This sounds like just one command
is to be learned...
<p>
Of course there are a <a href="commands.html">few more commands</a> defined, but all of them exist just to give you finer control on these four.
</p>
<p>
If you don't believe it is simple, consider this example:</p>
<center>
<table border="0" cellpadding="10" cellspacing="5" width="80%">
<tbody>
<tr bgcolor="black">
<th width="60%"><b><font color="white">Thoughts...</font></b></th>
<th width="40%"><b><font color="white">In FireHOL</font></b></th>
</tr>
<tr>
<td> I have a Linux host with two network interfaces.
<ul>
<li>The first is <b>eth0</b> that connects to my <b>LAN</b>
</li>
<li>
The other is a <b>PPP</b> device that connects to the <b>internet</b>
</li>
</ul>
</td>
<td>
<b></b>
<pre><b><font color="red">
interface eth0 lan
interface ppp+ internet
</font></b></pre>
<b><font color="red"> </font></b></td>
</tr>
<tr bgcolor="#f0f0f0">
<td> To the <b>internet</b> my Linux provides:
<ul>
<li>a MAIL server
</li>
<li>a WEB server
</li>
<li>a FTP server
</li>
<li>a SSH server, but only for my office computer
</li>
</ul>
</td>
<td>
<b><font color="gray"></font></b>
<pre><b><font color="gray"><font color="red">office="my-office-pc.example.com"</font>
interface eth0 lan
interface ppp+ internet<font color="red">
server smtp accept
server http accept
server ftp accept
server ssh accept src $office
</font></font></b></pre>
<b><font color="gray"><font color="red"> </font></font></b></td>
</tr>
<tr>
<td> My Linux is also a workstation, I want to run any client I wish.
</td>
<td>
<b><font color="gray"></font></b>
<pre><b><font color="gray">office="my-office-pc.example.com"<br><br>interface eth0 lan<br><br>interface ppp+ internet<br> server smtp accept<br> server http accept<br> server ftp accept<br> server ssh accept src "$office"<br> <font color="red">
client all accept
</font></font></b></pre>
<b><font color="gray"><font color="red"> </font></font></b></td>
</tr>
<tr bgcolor="#f0f0f0">
<td> My <b>LAN</b> is trusted.
<p>
If a server is running on my Linux I want my LAN PCs to use it.
</p>
</td>
<td>
<b><font color="gray"></font></b>
<pre><b><font color="gray">office="my-office-pc.example.com"<br><br>interface eth0 lan<font color="red">
policy accept</font>
interface ppp+ internet
server smtp accept
server http accept
server ftp accept
server ssh accept src "$office"
client all accept
</font></b></pre>
<b><font color="gray"> </font></b></td>
</tr>
<tr>
<td> I would like my <b>LAN</b> PCs to use this Linux as a gateway
for connecting, as clients, to the <b>internet</b> for all the services
they wish.
</td>
<td>
<b><font color="gray"></font></b>
<pre><b><font color="gray">office="my-office-pc.example.com"<br><br>interface eth0 lan<br> policy accept<br> <br>interface ppp+ internet<br> server smtp accept<br> server http accept<br> server ftp accept<br> server ssh accept src "$office"<br> <br> client all accept<br> <font color="red">
router lan2internet inface eth0 outface ppp+
route all accept
</font></font></b></pre>
<b><font color="gray"><font color="red"> </font></font></b></td>
</tr>
<tr bgcolor="#f0f0f0">
<td> My LAN PCs have private IPs, unroutable to the Internet.
<p>
I need to masquerade somehow their IP addresses for internet access.
</p>
</td>
<td>
<b><font color="gray"></font></b>
<pre><b><font color="gray">office="my-office-pc.example.com"<br><br>interface eth0 lan<br> policy accept<br> <br>interface ppp+ internet<br> server smtp accept<br> server http accept<br> server ftp accept<br> server ssh accept src "$office"<br> <br> client all accept<br> <br>router lan2internet inface eth0 outface ppp+<br> <font color="red">masquerade</font>
route all accept
</font></b></pre>
<b><font color="gray"> </font></b></td>
</tr>
</tbody>
</table>
</center>
<p>
<b><u>This is it!</u></b> The firewall is ready. I hope you have noticed that all the rules given match just one direction of the traffic: <b>the request</b>.
They don't say anything about replies (see for example the <b>src</b>, <b>inface</b> or <b>outface</b> parameters). This is because FireHOL handles the replies
automatically. You don't have to do anything about them: If a request is allowed, then the corresponding reply is also allowed.
This also means that FireHOL produces the iptables statements to exactly match what is allowed <b>in both directions</b> and nothing more. If for example we remove the <b>client all accept</b>
from the <b>internet</b> interface, our Linux will not be able to do anything with its PPP device except to send replies matching the <b>server</b> statements within this interface;
no pings, no DNS, no web browsing, no nothing!
</p>
<p>
The complete configuration file (a little bit enriched) of the above example could be (all FireHOL directives are clickable):
</p>
<center>
<table border="0" cellpadding="15" cellspacing="20" width="70%">
<tbody>
<tr>
<td bgcolor="#f0f0f0">
<b>
<pre> <font color="gray"># Require release 5 of FireHOL configuration directives</font>
<a href="commands.html#version">version</a> 5<br> <br> <font color="gray"># A space separated list of all the IPs on the internet, I trust</font>
office="my-office-pc.example.com"
<font color="gray"># The IP address of this Linux and LAN for the rest of the world</font>
public_ip="1.2.3.4"
<font color="gray"># My LAN. Everything is allowed here.</font>
<a href="commands.html#interface">interface</a> eth0 lan<br> <a href="commands.html#policy">policy</a> accept <font color="gray"># The default is 'drop'.</font>
<font color="gray"># Make sure the traffic coming in, comes from valid Internet IPs,<br> # and that is targeting my public IP</font>
<a href="commands.html#interface">interface</a> ppp+ internet <a href="commands.html#src">src</a> not "$<a href="commands.html#UNROUTABLE_IPS">UNROUTABLE_IPS</a>" <a href="commands.html#dst">dst</a> "$public_ip"<br> <font color="gray"># Protect me from various kinds of attacks.</font>
<a href="commands.html#protection">protection</a> strong<br> <br> <font color="gray"># Public servers.</font>
<a href="commands.html#server">server</a> <a href="services.html#smtp">smtp</a> accept<br> <a href="commands.html#server">server</a> <a href="services.html#http">http</a> accept<br> <a href="commands.html#server">server</a> <a href="services.html#ftp">ftp</a> accept<br> <a href="commands.html#server">server</a> <a href="services.html#ssh">ssh</a> accept <a href="commands.html#src">src</a> "$office"<br> <br> <font color="gray"># Make sure idents do not timeout.</font>
<a href="commands.html#server">server</a> <a href="services.html#ident">ident</a> reject <a href="commands.html#with">with</a> tcp-reset<br> <br> <font color="gray"># This is also a workstation.</font>
<a href="commands.html#client">client</a> <a href="services.html#all">all</a> accept<br> <br> <br> <font color="gray"># Route the LAN requests to the internet.</font>
<a href="commands.html#router">router</a> lan2internet <a href="commands.html#inface">inface</a> eth0 <a href="commands.html#outface">outface</a> ppp+<br> <br> <font color="gray"># Masquerading on outface.</font>
<a href="commands.html#masquerade">masquerade</a>
<font color="gray"># Route all requests from inface to outface<br> # and their replies back.</font>
<a href="commands.html#route">route</a> <a href="services.html#all">all</a> accept</pre>
</b>
</td>
</tr>
</tbody>
</table>
</center>
FireHOL is completely <b>dynamic</b>, since with its <a href="language.html">language</a> you can describe any firewall
configuration you wish using simple <a href="commands.html">commands</a>.
<p>
<table border="0" cellpadding="10" cellspacing="0" width="100%">
<tbody>
<tr>
<td bgcolor="#eeeeee"><b>Why?</b></td>
</tr>
</tbody>
</table>
<br>
As an IT executive, responsible for many dozens of Linux systems, I
needed a firewalling solution that would allow me and my team to have a
clear and simple view of what is happening on each server, as far as
firewalling is concerned. I also needed a solution that will allow my
team members to produce high quality and homogeneous firewalls
independently of their security skills and knowledge. After searching
for such a tool, I quickly concluded that no tool is flexible, open,
easy, and simple enough for what I needed.</p>
<p>I decided to write FireHOL in a way that will allow me, or anyone
else, to view, verify and audit the firewall of any linux server or
linux router <b>in seconds</b>. FireHOL's configuration is extremely
simple... you don't have to be an expert to design a complicated but
secure firewall.
</p>
<p>
<table border="0" cellpadding="10" cellspacing="0" width="100%">
<tbody>
<tr>
<td bgcolor="#eeeeee"><b>What features does it have?</b></td>
</tr>
</tbody>
</table>
<br>
FireHOL handles firewalls protecting one host on all its interfaces
and any combination of stateful firewalls routing traffic from one
interface to another. There are no limitations on the number of
interfaces or on the number of routing routes (except the ones iptables
has, if any).
</p>
<p>FireHOL, still lacks a few features: QoS for example is not supported directly.
You are welcome to extend FireHOL and send me your patches to integrate within FireHOL.
In any case however, you can embed normal iptables commands in a FireHOL
configuration to do whatever iptables supports.</p>
<p>
Since FireHOL produces stateful commands, for every supported service
it needs to know the flow of requests and replies. Today FireHOL
supports the following services:</p>
<ul>
<li>Many single socket protocols, such as HTTP, NNTP, SMTP, POP3,
IMAP4, RADIUS, SSH, LDAP, MySQL, Telnet, NTP, DNS, etc.
There are a few dozens of such services defined in FireHOL. Check <a href="services.html">this list.</a>
Even if something is missing, you can <a href="adding.html">define it</a>.
</li>
</ul>
<ul>
<li>Many complex protocols, such as FTP, NFS, SAMBA, PPTP, etc.
If you need some complex protocol that is not present, you will have
to program it (in simple BASH scripting - there are many commented
examples on how this is done). Again, you will just create one BASH
function with the rules of the protocol, and FireHOL will turn it to
a client, a server or a router.</li>
</ul>
<hr noshade="noshade" size="1">
<table border="0" width="100%">
<tbody>
<tr>
<td align="center" valign="middle">
<a href="http://sourceforge.net"><img src="http://sourceforge.net/sflogo.php?group_id=58425&type=5" alt="SourceForge Logo" border="0" height="62" width="210"></a>
</td>
<td align="center" valign="middle">
<small>$Id: overview.html,v 1.37 2008/07/31 01:03:28 ktsaou Exp $</small>
<p>
<b>FireHOL</b>, a firewall for humans...<br>
© Copyright 2004
Costa Tsaousis <a href="mailto:%20costa@tsaousis.gr"><costa@tsaousis.gr></a>
</p>
</td>
</tr>
</tbody>
</table>
</body>
</html>
|