<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Iptables on Michael’s Domain</title><link>https://jeltsch.org/en/tags/iptables/</link><description>Recent content in Iptables on Michael’s Domain</description><generator>Hugo</generator><language>en-us</language><copyright>Copyright © 2002 - 2026 Michael Jeltsch.</copyright><lastBuildDate>Fri, 24 Jul 2026 00:18:18 +0300</lastBuildDate><atom:link href="https://jeltsch.org/en/tags/iptables/index.xml" rel="self" type="application/rss+xml"/><item><title>Firewall configuration programs (fwbuilder, yast2, iptables, Brickwall/Brickhouse)</title><link>https://jeltsch.org/en/firewall_configuration_programs_fwbuilder_yast2_iptables_brickwall_brickhouse/</link><pubDate>Wed, 04 Apr 2007 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/firewall_configuration_programs_fwbuilder_yast2_iptables_brickwall_brickhouse/</guid><description>&lt;p&gt;Configuring the firewall by hand using iptables is quite difficult. When we still used RedHat 8.1 we have been doing it but now not anymore. We have been using yast2 now for firewall configuration. An alternative to yast2 is 
 &lt;a href="http://www.fwbuilder.org/" target="_blank" rel="noopener noreferrer nofollow"&gt;fwbuilder&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
. We tried it once and it seems to work although the code it produces is quite large compared to manual configuration. An obvious advantage is that fwbuilder can be used together with many different types of firewalls and operating systems (e.g. also Mac OS X). I still think 
 &lt;a href="http://brianhill.dyndns.org/site/modules.php?op=modload&amp;amp;name=News&amp;amp;file=article&amp;amp;sid=15&amp;amp;mode=thread&amp;amp;order=0&amp;amp;thold=0" target="_blank" rel="noopener noreferrer nofollow"&gt;Brickhouse (formerly Brickwall)&amp;nbsp;






 
 
 
 &lt;svg class="svg-inline--fa fas fa-up-right-from-square fa-2xs" fill="currentColor" aria-hidden="true" role="img" viewBox="0 0 512 512" overflow="visible"&gt;&lt;use href="#fas-up-right-from-square"&gt;&lt;/use&gt;&lt;/svg&gt;&lt;/a&gt;
 is a very good - probably the best and easiest - configuration script for the inbuilt firewall/routing functions of Mac OS X. I think the Linux community needs such a project since Brickhouse is way easier to use than fwbuilder.&lt;/p&gt;</description></item><item><title>How to enable VPN clients to access LAN computers that are not running VPN software</title><link>https://jeltsch.org/en/how_to_enable_vpn_clients_to_access_lan_computers_that_are_not_running_vpn_software/</link><pubDate>Tue, 08 Aug 2006 00:00:00 +0000</pubDate><guid>https://jeltsch.org/en/how_to_enable_vpn_clients_to_access_lan_computers_that_are_not_running_vpn_software/</guid><description>&lt;p&gt;I installed an OpenVPN service on our server. The default setup worked right out of the box. However, I wanted to use a VPN client to perform offsite backups of the computers in our LAN (using the backuppc software). First I installed OpenVPN clients on all of the LAN computers to be backed up, but OpenVPN on MacOS X seems to be a bit unreliable. Therefore I wanted to setup the VPN server to forward requests to our LAN network. The following changes were necessary:&lt;/p&gt;</description></item></channel></rss>