On 11/15/2014 2:49 PM, Tom Eastep wrote:
> On 11/15/2014 11:01 AM, Thomas D. wrote:
>> Hi,
>>
>> we have missed IPv6:
>>
>>> /var/lib/shorewall6/.restart: line 1929: echo: write error: No such file or
>>> directory
>>>WARNING: Unable to set log backend to nf_log_ipv6
>>
>> Reason:
>>
>> It is
Hi,
On 2014-11-15 23:57, Tom Eastep wrote:
> I think the more important question is why would a kernel upgrade
> prevent the 'nat' table from being initialized. What do 'shorewall show
> capabilities' and 'shorewall6 show capabilities' say about the Nat table?
They changed "CONFIG_NF_NAT_IPV4" to
On 11/15/2014 11:15 AM, Thomas D. wrote:
> Hi,
>
> Situation:
> - Running kernel: 3.16.6
> - Running Shorewall: 4.6.5
> - shorewall.conf: AUTOMAKE=Yes
>
> All the firewall scripts are current.
> I upgraded to kernel 3.17.3 and rebooted.
>
> On boot:
>
>> rc boot logging started at Sat Nov 15 19
On 11/15/2014 11:01 AM, Thomas D. wrote:
> Hi,
>
> we have missed IPv6:
>
>> /var/lib/shorewall6/.restart: line 1929: echo: write error: No such file or
>> directory
>>WARNING: Unable to set log backend to nf_log_ipv6
>
> Reason:
>
> It is named *ip6t_LOG* but the script is grep'ing for *i
Hi,
Situation:
- Running kernel: 3.16.6
- Running Shorewall: 4.6.5
- shorewall.conf: AUTOMAKE=Yes
All the firewall scripts are current.
I upgraded to kernel 3.17.3 and rebooted.
On boot:
> rc boot logging started at Sat Nov 15 19:09:07 2014
>
> [...]
>
> * Checking "/var/lib/shorewall/firewa
Hi,
we have missed IPv6:
> /var/lib/shorewall6/.restart: line 1929: echo: write error: No such file or
> directory
>WARNING: Unable to set log backend to nf_log_ipv6
Reason:
It is named *ip6t_LOG* but the script is grep'ing for *ip6t_log*...
^^^
On 11/15/2014 4:40 AM, Evangelos Foutras wrote:
> I've also included a random third patch that is specific to Arch Linux.
>
Applied. Thanks Evangelos!
I'll be uploading 4.6.5.1 later this morning.
-Tom
--
Tom Eastep\ When I die, I want to go like my Grandfather who
Shoreline, \
On 11/15/2014 7:46 AM, Thomas D. wrote:
> Hi,
>
> before the patch (DESTDIR = "/tmp/shorewall-4.6.5"; INITDIR =
> "/etc/init.d"),
>
>> [...]
>> SysV init script init.gentoo.sh installed in
>> /tmp/shorewall-4.6.5//etc/init.d/shorewall-lite
>
> after the patch
>
>> [...]
>> SysV init script ini
Hi,
before the patch (DESTDIR = "/tmp/shorewall-4.6.5"; INITDIR =
"/etc/init.d"),
> [...]
> SysV init script init.gentoo.sh installed in
> /tmp/shorewall-4.6.5//etc/init.d/shorewall-lite
after the patch
> [...]
> SysV init script init.gentoo.sh installed in
> /tmp/shorewall-4.6.5/etc/init.d/s
I've also included a random third patch that is specific to Arch Linux.
--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notific
This was omitted from commit e3b1034 (Change SYSTEMDDIR to SERVICEDIR).
Signed-off-by: Evangelos Foutras
---
Shorewall-core/shorewallrc.apple | 2 +-
Shorewall-core/shorewallrc.archlinux | 2 +-
Shorewall-core/shorewallrc.cygwin| 2 +-
Shorewall-core/shorewallrc.debian| 2 +-
Shorewa
The previous syntax resulted in:
./configure: line 199: [SERVICEDIR]=: command not found
Signed-off-by: Evangelos Foutras
---
Shorewall-core/configure | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Shorewall-core/configure b/Shorewall-core/configure
index c192c24..37f71d3
/usr/bin is the directory used for all binaries that were previously
installed to /bin, /sbin or /usr/sbin. This unification occurred in
Arch Linux in mid-2013, so might as well change it in Shorewall too.
Signed-off-by: Evangelos Foutras
---
Shorewall-core/shorewallrc.archlinux | 2 +-
1 file c
13 matches
Mail list logo