On 02/10/2018 08:52 AM, Matt Darfeuille wrote:
>
> It's always interesting to learn how Shorewall works!
> Given your explanation it clearly makes no sense to nitpick about this.
> The reason why I was asking is that my interface is configure by dhcp.
> My understanding is that shorewall should
On 2/8/2018 6:46 PM, Tom Eastep wrote:
> On 02/08/2018 08:45 AM, Matt Darfeuille wrote:
>> On 2/8/2018 5:17 PM, Tom Eastep wrote:
>>> On 02/08/2018 04:20 AM, Matt Darfeuille wrote:
Hi,
From:
http://shorewall.org/manpages/shorewall.html
"Reload is similar to
On 02/08/2018 08:45 AM, Matt Darfeuille wrote:
> On 2/8/2018 5:17 PM, Tom Eastep wrote:
>> On 02/08/2018 04:20 AM, Matt Darfeuille wrote:
>>> Hi,
>>>
>>> From:
>>>
>>> http://shorewall.org/manpages/shorewall.html
>>>
>>> "Reload is similar to shorewall start except that it assumes that the
>>>
On 2/8/2018 5:17 PM, Tom Eastep wrote:
> On 02/08/2018 04:20 AM, Matt Darfeuille wrote:
>> Hi,
>>
>> From:
>>
>> http://shorewall.org/manpages/shorewall.html
>>
>> "Reload is similar to shorewall start except that it assumes that the
>> firewall is already started. Existing connections are
On 02/08/2018 04:20 AM, Matt Darfeuille wrote:
> Hi,
>
> From:
>
> http://shorewall.org/manpages/shorewall.html
>
> "Reload is similar to shorewall start except that it assumes that the
> firewall is already started. Existing connections are maintained."
>
> If I do 'shorewall stop' followed
Hi,
From:
http://shorewall.org/manpages/shorewall.html
"Reload is similar to shorewall start except that it assumes that the
firewall is already started. Existing connections are maintained."
If I do 'shorewall stop' followed by 'shorewall reload' the firewall
will be started:
$ shorewall
