-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Tom
Am 07.10.2015 um 19:48 schrieb Tom Eastep:
I patched the code in lib.core and it appears to be fixed. Would you
consider adapting this in the upcoming releases?
gatekeeper# diff -Nu lib.core lib.core.patched
- --- lib.core
+++
Quick question on interface names.
I'm building a Centos 7 server and the interface names are no longer
eth* but (on this machine) are:-
enp2s0 - Outside world
enp8s0 - Internal network
enp7s0 - Internal network
I've tried checking the documentation but can not find a definitive answer.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Tom
Am 07.10.2015 um 19:48 schrieb Tom Eastep:
> On 10/7/2015 7:06 AM, Erich Titl wrote:
>> Hi Folks
>>
>> I am seeing this in shorewall-init.log, probably some date
>> template glitch.
>>
>> Oct 7 13:44:26 Shorewall configuration compiled to
On 08/10/15 00:44, Mathew Crane wrote:
> Hi Nigel,
>
> The new udev device naming schema is a bit daunting at first. I
> recommend at least looking over Red Hat's own documentation in regards
> to this:
>
Brian,
Looks like the answer is "yes" it will work ok with the new names. Thank
you.
Mathew,
I followed a number of on-line helps. The problem I ran into was that if
the core is updated, as soon as you re-boot it goes back to the newer
naming convention and no interfaces are working
On 10/7/2015 5:45 PM, Nigel Aves wrote:
> Brian,
>
> Looks like the answer is "yes" it will work ok with the new names. Thank
> you.
>
You might also want to look at
http://www.shorewall.org/configuration_file_basics.htm#Logical
Logical names allow you to keep names you choose in the
Hi Nigel,
The new udev device naming schema is a bit daunting at first. I recommend
at least looking over Red Hat's own documentation in regards to this:
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Networking_Guide/ch-Consistent_Network_Device_Naming.html
If you
2015-10-06 17:29 GMT-06:00 Tom Eastep :
ect ping
> http://www.shorewall.org/Multiple_Zones.html.
>
great , work perfect.
regard
--
rickygm
http://gnuforever.homelinux.com
--
Full-scale,
Hi Tom
Am 07.10.2015 um 19:48 schrieb Tom Eastep:
...
> I suspect that the issue is in your version of the 'date' utility. The
> Shorewall-generated script is executing this command:
>
> timestamp=$(date +'%b %_d %T')
>
FWIW
from 'man date'
%e day of month, space padded; same as
Hi Tom
Than
Am 07.10.2015 um 19:48 schrieb Tom Eastep:
> On 10/7/2015 7:06 AM, Erich Titl wrote:
>> Hi Folks
>>
>> I am seeing this in shorewall-init.log, probably some date template glitch.
>>
>> Oct 7 13:44:26 Shorewall configuration compiled to /var/lib/.start
>> Oct %_d 13:44:26 Starting
Hi Folks
I am seeing this in shorewall-init.log, probably some date template glitch.
Oct 7 13:44:26 Shorewall configuration compiled to /var/lib/.start
Oct %_d 13:44:26 Starting Shorewall
Oct %_d 13:44:26 Initializing...
gatekeeper# shorewall version
4.6.13
cheers
Erich
On 10/7/2015 7:06 AM, Erich Titl wrote:
> Hi Folks
>
> I am seeing this in shorewall-init.log, probably some date template glitch.
>
> Oct 7 13:44:26 Shorewall configuration compiled to /var/lib/.start
> Oct %_d 13:44:26 Starting Shorewall
> Oct %_d 13:44:26 Initializing...
>
> gatekeeper#
12 matches
Mail list logo