I've just got Arch installed and running a few days ago and I'm in the process of moving the system to pure systemd setup.I installed iptables and shoreline firewall (shorewall) but I don't know if I need to have both process loading in my daemon boot scripts or not?Currently I do but my boot list shows that iptables and ip6tables fail to load, whilst shorewall/shorewall6 load but t
I am new Fedora and selinux and got caught out by shorewall not being able to start because of a policy problem with perl not being allowed to access a shorewall directory ..... at least that is what the journal log shows.
From my searching the net, this sort of thing was an issue back in F14 days ..
I got the real fix from user Omache on #shorewall:Omache | that failure is caused by Perl 5.20.Omache | You can work around it by reducing the setting of OPTIMIZE by 8Omache | So if OPTIMIZE=all or OPTIMIZE=31, set it to 23 and it will work My dirty hack was to remove 'use strict' from /usr/share/shorewall/Shorewall/Chains.pm.
In my previous article, we took a look at Shorewall, how to install it, set up the configuration files, and configured port forwarding over NAT. In this article, we are going to explore some of Shorewall’s common errors, some solutions, and get an introduction to its command line options. Shorewall...
[[ This is a content summary only. Visit my website for full links, other content, and more!
I have a Linux box being used as a firewall with Fedora 10 and shorewall 4.2.10.
Secondary IPs are loaded on the WAN (eth1)card through Shorewall NAT and Rules file. The problem is that if there is a network hickup or if the circuit bounces, the primary IP comes back but I have to reload Shorewall to get the secondary ips back.
I'm using shorewall as the firewall and gateway for a production site. The site also has a couple of VPNs running into it that are hosted on a different server on the same site (in the protected zone).