Tom Eastep wrote:
> On 05/06/2013 11:22 AM, Dash Four wrote:
>
>> Tom Eastep wrote:
>>
I see your point and is a good one.
Perhaps another alternative could be implemented since the problem
arises only on reboot. Currently, I have shorewall-init as a service
dis
On 5/6/13 2:18 PM, "Tom Eastep" wrote:
>On 05/06/2013 11:22 AM, Dash Four wrote:
>>
>> Tom Eastep wrote:
I see your point and is a good one.
Perhaps another alternative could be implemented since the problem
arises only on reboot. Currently, I have shorewall-init as a service
On 05/06/2013 11:22 AM, Dash Four wrote:
>
> Tom Eastep wrote:
>>> I see your point and is a good one.
>>>
>>> Perhaps another alternative could be implemented since the problem
>>> arises only on reboot. Currently, I have shorewall-init as a service
>>> disabled, simply because ifupdown-local u
Tom Eastep wrote:
>> I see your point and is a good one.
>>
>> Perhaps another alternative could be implemented since the problem
>> arises only on reboot. Currently, I have shorewall-init as a service
>> disabled, simply because ifupdown-local usually takes care of
>> everything. However, if y
On 05/06/2013 10:15 AM, Dash Four wrote:
>
> Tom Eastep wrote:
>> On 05/05/2013 10:17 AM, Dash Four wrote:
>>
>>> I've decided to make a clean break as the AUTOMAKE thread was getting a
>>> bit off-topic. These are my findings so far:
>>>
>>> 1. During boot, when the OS is bringing my loopback
Tom Eastep wrote:
> On 05/05/2013 10:17 AM, Dash Four wrote:
>
>> I've decided to make a clean break as the AUTOMAKE thread was getting a
>> bit off-topic. These are my findings so far:
>>
>> 1. During boot, when the OS is bringing my loopback interface up I am
>> getting the following messages
On 05/05/2013 10:17 AM, Dash Four wrote:
> I've decided to make a clean break as the AUTOMAKE thread was getting a
> bit off-topic. These are my findings so far:
>
> 1. During boot, when the OS is bringing my loopback interface up I am
> getting the following messages:
>
> Bringing up loopback in
