#18 : worked for me on 16.10 (yakkety)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1511869
Title:
shorewall does not start at boot
To manage notifications about this bug go to:
https://bugs.launc
Ditto to #18; that solution worked for me (for both shorewall and
shorewall6).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1511869
Title:
shorewall does not start at boot
To manage notifications
In 16.04 e-Vent's service file exists at
/lib/systemd/system/shorewall.service. If you run:
sudo systemctl enable /lib/systemd/system/shorewall.service
a symlink will be created in /etc/systemd/system/basic.target.wants/ and
shorewall will start on boot.
--
You received this bug notification be
Solution from #8 works on 16.04 but I would expect that the ubuntu
shorewall package includes a running systemd configuration instead of
leaving that up to the users ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
I can confirm that the solution outlined in #13 works for me on 16.04.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1511869
Title:
shorewall does not start at boot
To manage notifications
Still affects shorewall 5.0.4-1 on Ubuntu server 16.04. Besides the
already mentioned workaround, (temporarily) using to ufw for firewall
management is an option.
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
B
I'm on 16.04 and I tried installing shorewall-init and configuring
/etc/default/shorewall-init per http://shorewall.net/Shorewall-init.html
as well as setting safestop=1 in /etc/default/shorewall but was still
able to ping my firewall's external IP for a couple seconds upon every
reboot.
I had to
It would appear a solution to the firewall being open before shorewall
start is to use the 'shorewall-init' package.
http://shorewall.net/Shorewall-init.html
The extra init package closes the firewall prior to shorewall startup
avoiding that issue (assuming you set the product in
/etc/default/sh
On further inspection, the reload command in 4.6.4.3 is clearly not
doing what the manpage is saying on shorewall which I will put down to
not being shorewall 5.X, pre-5.X reload appears to be a reload of a
remote host which was moved to a separate command (remote-restart) in
5.X
So yes, is should
I pulled this as I said from the Deb service file, I cannot remember the
rationale behind waiting for the network to start but I remember
something to do with PPPOE connections being potentially problematic for
some reason.
I ran this past a Shorewall guru in their IRC but frankly I am not too
wor
Also I believe that the line:
ExecReload=/sbin/shorewall $OPTIONS reload $RELOADOPTIONS
should rather be:
ExecReload=/sbin/shorewall $OPTIONS restart $RESTARTOPTIONS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
@fmaster
Since you moved shorewall to start after network-online.target, there
will be a brief moment that the network is up but the firewall is not
configured yet. Or do you have a different solution for this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Can confirm this bug in 15.10, init.d script not really needed.
Correction to Poldi's workaround (didn't work for me), I pulled the
Debian service file from the Shorewall tgz which appears to be fully
functional, same as poldi, make the service file and enable it and you
are good to go:
#
# T
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: shorewall6 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1511869
Title:
** Also affects: shorewall6 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1511869
Title:
shorewall does not start at boot
To manage notification
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: shorewall (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1511869
Title:
The forum post is
http://ubuntuforums.org/showthread.php?t=2282688&p=13412197#post13412197
and the credit for the workaround needs to go to BCSharp as it's his.
Given that there has been no feedback from any of the
developers/security gurus despite this issue leaving the system
completely unsecur
This issue affects me as well, was driving me up the wall. Thanks for
your suggested workaround Poldi it appears to work well for me as well.
Hopefully they will fix this at some point.
Kubuntu 15.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
As I have posted the problem in the forum first I had the following reply
I have exactly the same problem. Also in my case, upgrade to 15.10 did not
help. Searching the Internet for workarounds did not help either (except that
this thread and a Debian bug
** Information type changed from Public Security to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1511869
Title:
shorewall does not start at boot
To manage notifications about this bug go to
Hello and thanks for the bug report. I'm going to make it a public
security bug so that it'll get more attention.
** Package changed: ifupdown (Ubuntu) => shorewall (Ubuntu)
** Information type changed from Private Security to Public Security
--
You received this bug notification because you ar
21 matches
Mail list logo
