Hi Tom,
I think there's some big progress on this.
After changing configuration /etc/shorewall/masq as recommended by your
I can find this entry in dump:
Chain POSTROUTING (policy ACCEPT 79 packets, 5548 bytes)
pkts bytes target prot opt in out source
destination$
2
On 04/01/2016 01:29 PM, Florian Piekert wrote:
> Dear Shorewall-Users, dear Tom,
>
> for quite some time I am using Shorewall on top of OpenSuse. Over the years
> my shorewall.conf has been modified to incorporate the new stuff, my rules
> file has stayed similar most of the time.
>
> I experie
Dear Shorewall-Users, dear Tom,
for quite some time I am using Shorewall on top of OpenSuse. Over the years my
shorewall.conf has been modified to incorporate the new stuff, my rules file
has stayed similar most of the time.
I experience multiple things, and I hope you can be of help to root ou
No, this isn't an April Fool's joke -- after I uploaded Beta 1, I
realized that I hadn't merged all of the contents that I intended.
Problems Corrected:
1) If a physical interface name was used in the INTERFACE column of an
entry in /etc/shorewall/masq, then previously a Perl diagnostic was
Hi Wouter,
You are correct. The only packaging difference between 5.0.4-1 and
5.0.7-1 is that it now correctly enables the systemd service on
installation and disables it on removal.
Regards,
-Roberto
On Fri, Apr 01, 2016 at 08:57:29PM +0200, Wouter Deurholt wrote:
>Aha!
>I see now (ove
Aha!
I see now (overlooked it before) that the
/etc/systemd/system/shorewall.service I made myself (first post) was not
necessary... and even pointless :).
If you just do a 'sudo systemctl enable shorewall.service' after you
installed shorewall 5.0.4: all is well :).
I recon this is the only chan
Wouter,
That is a problem that I discovered a few weeks after I uploaded 5.0.4.
I was actually surprised that (a) I overlooked it, and (b) nobody ever
reported it. The problem was corrected with the 5.0.7-1 upload to
Debian unstable last week.
Executing 'systemctl enable shorewall.service' is th
Greetings,
I installed Shorewall (5.0.4) on my Ubuntu server 16.04 (currently beta).
It is functioning perfectly fine when started. There is however one
problem. It is not starting at boot-time.
I even tried to add a wait_interface="eno1" and wait_interface="eno2" to
my /etc/default/shorewall.
On 01/04/2016 00:01, Tom Eastep wrote:
>> >Do you see a workaround in the meantime (I tried creating the extra
>> >chain in shorewall.init, but it gets deleted during subsequent startup?)
> In /etc/shorewall/start:
>
> run_iptables -t nat -N MINIUPNPD-POSTROUTING
> run_iptables -t nat -I POSTROUTIN
