After far too long a delay, I have resumed packaging Shorewall for
Debian. I have just uploaded packages for 5.1.8.1 to Debian unstable.
They should shortly be available from https://packages.debian.org
If you are not a user of Debian Sid, you can download the packages and
install them using 'dpk
I recently installed debian stretch on my router/firewall (fresh
install including reformat).
In jessie I simply had to set startup=1 in /etc/default/shorewall to
have shorewall start my firewall at boot.
In stretch setting startup=1 was not enough.
I also had to manually enable shorewall init scri
Hi Øyvind,
Thanks for your feedback on the packages.
On Tue, Nov 21, 2017 at 11:46:58AM +0100, Øyvind Lode wrote:
> I recently installed debian stretch on my router/firewall (fresh
> install including reformat).
> In jessie I simply had to set startup=1 in /etc/default/shorewall to
> have shorewa
Hi Roberto,
On 21 November 2017 at 12:40, Roberto C. Sánchez wrote:
>> I even had to replace allow-hotplug with auto on all nics in
>> /etc/network/interfaces to have shorewall startup at boot.
>
> This is strange. I have not encountered this. Can you describe more
> details of your configurati
On 11/21/2017 05:53 AM, Øyvind Lode wrote:
> Hi Roberto,
>
> On 21 November 2017 at 12:40, Roberto C. Sánchez wrote:
>>> I even had to replace allow-hotplug with auto on all nics in
>>> /etc/network/interfaces to have shorewall startup at boot.
>>
>> This is strange. I have not encountered this.
On 11/21/2017 07:59 AM, Tom Eastep wrote:
>> Rebooted again and now shorewall started automatically when the
>> firewall boots up.
>> I found this a bit strange but now it works as expected.
>>
>
> Do you recall what the output of 'systemctl status shorewall' was when
> Shorewall failed to start?
Hi:
On 21 November 2017 at 17:23, Tom Eastep wrote:
> On 11/21/2017 07:59 AM, Tom Eastep wrote:
>
>>> Rebooted again and now shorewall started automatically when the
>>> firewall boots up.
>>> I found this a bit strange but now it works as expected.
>>>
>>
>> Do you recall what the output of 'sys
On 11/21/2017 10:08 AM, Øyvind Lode wrote:
>
> I don't recall output of systemctl status shorewall.
> However, I actually looked in /var/log/shorewall-init.log immediately
> after reboot (when shorewall failed to start) and I was puzzled to
> find that nothing was logged.
Interesting. That would
On Tue, Nov 21, 2017 at 10:45:02AM -0800, Tom Eastep wrote:
>
> I just did a fresh install of 9.2 on a single-NIC system, installed and
> configured Shorewall (one-interface example), and enabled Shorewall
> using systemctl. A 'systemctl start shorewall' succeeded. I then
> rebooted and observed t
On 11/21/2017 10:51 AM, Roberto C. Sánchez wrote:
> On Tue, Nov 21, 2017 at 10:45:02AM -0800, Tom Eastep wrote:
>>
>> So in summary, I am unable to reproduce your findings.
>>
> My experience was the same.
>
As an additional test, I added a second NIC to the system and configured
it with 'allow-
Hm, ok I just did the same and I'm unable to reproduce my own findings.
Enabling shorewall with systemctl enable shorewall is sufficient both
on stable 9.2 and sid.
allow-hotplug is used in /etc/network/interfaces and shorewall starts
just fine when booting up.
Thanks and sorry for wasting your ti
11 matches
Mail list logo
