On 5/26/2015 12:36 PM, PGNd wrote:
Tom
On Tue, May 26, 2015, at 12:15 PM, Tom Eastep wrote:
Is the OpenVPN tunnel also a provider?
yes, it is.
Then I think that the most straight-forward thing to do is:
a) Make the OpenVPN interface 'optional' with no 'wait=' specified in the
interfaces
On Tue, May 26, 2015, at 12:47 PM, Tom Eastep wrote:
Then I think that the most straight-forward thing to do is:
a) Make the OpenVPN interface 'optional' with no 'wait=' specified in the
interfaces file.
Done.
b) Start OpenVPN after Shorewall-lite.
Starting it with a script from within
On 5/25/2015 2:58 PM, PGNd wrote:
I have OpenVPN Shorewall-lite installed on an Opensuse server, running its
'wicked' networking stack.
It's an all systemd-controlled init environment.
I'm interested in ordering the system network stack, openvpn and shorewall
service starts correctly to
Tom
On Tue, May 26, 2015, at 12:15 PM, Tom Eastep wrote:
Is the OpenVPN tunnel also a provider?
yes, it is.
--
___
Shorewall-users mailing list
On 5/26/2015 1:01 PM, PGNd wrote:
On Tue, May 26, 2015, at 12:47 PM, Tom Eastep wrote:
Then I think that the most straight-forward thing to do is:
a) Make the OpenVPN interface 'optional' with no 'wait=' specified in the
interfaces file.
Done.
b) Start OpenVPN after Shorewall-lite.
I have OpenVPN Shorewall-lite installed on an Opensuse server, running its
'wicked' networking stack.
It's an all systemd-controlled init environment.
I'm interested in ordering the system network stack, openvpn and shorewall
service starts correctly to ensure that there's no
