Tom Eastep wrote:
> On 8/12/2014 8:38 PM, cac...@quantum-sci.com wrote:
>> Tom Eastep wrote:
>>> So you felt that your setting of AUTOHELPERS was irrelevant because your
>>> kernel is earlier that 3.5?
>> I don't understand what you're saying. That page says, "By making
>> AUTOHELPERS=Yes the def
On 8/13/2014 6:58 AM, cac...@quantum-sci.com wrote:
>
> Tom Eastep wrote:
>> On 8/12/2014 8:38 PM, cac...@quantum-sci.com wrote:
>>> Tom Eastep wrote:
So you felt that your setting of AUTOHELPERS was irrelevant because your
kernel is earlier that 3.5?
>>> I don't understand what you're s
Attached.
Tom Eastep wrote:
> On 8/13/2014 6:58 AM, cac...@quantum-sci.com wrote:
>> Tom Eastep wrote:
>>> On 8/12/2014 8:38 PM, cac...@quantum-sci.com wrote:
Tom Eastep wrote:
> So you felt that your setting of AUTOHELPERS was irrelevant because your
> kernel is earlier that 3.5?
>>
On 8/13/2014 8:16 AM, cac...@quantum-sci.com wrote:
>
> Attached.
>
Hmmm -- that's not good.
Please forward:
- the setting of HELPERS in shorewall.conf
- the output of 'shorewall show -f capabilities'
- the contents of /etc/shorewall/conntrack
Thanks,
-Tom
--
Tom Eastep\ When I die,
Tom Eastep wrote:
> On 8/13/2014 8:16 AM, cac...@quantum-sci.com wrote:
>> Attached.
>>
> Hmmm -- that's not good.
>
> Please forward:
>
> - the setting of HELPERS in shorewall.conf
HELPERS=
as from the factory.
> - the output of 'shorewall show -f capabilities'
Attached.
> - the contents of /et
On 8/13/2014 9:05 AM, cac...@quantum-sci.com wrote:
>
> Tom Eastep wrote:
>> On 8/13/2014 8:16 AM, cac...@quantum-sci.com wrote:
>>> Attached.
>>>
>> Hmmm -- that's not good.
>>
>> Please forward:
>>
>> - the setting of HELPERS in shorewall.conf
> HELPERS=
> as from the factory.
>
>> - the output
After an upgrade from Opensuse_13.1-packaged shorewall 4.6.2.4-144.1 ->
4.6.2.4-146.1
grep "shorewall|" * | tail -n 2
2014-08-08
07:30:05|install|shorewall|4.6.2.4-144.1|noarch||Netfilter|8a7f834d22683013aba57ba4548d97fc53eb64e0b562cbdf65e716544aba45ba|
20
On 8/13/2014 2:26 PM, PGNd wrote:
> After an upgrade from Opensuse_13.1-packaged shorewall 4.6.2.4-144.1 ->
> 4.6.2.4-146.1
>
> grep "shorewall|" * | tail -n 2
> 2014-08-08
> 07:30:05|install|shorewall|4.6.2.4-144.1|noarch||Netfilter|8a7f834d22683013aba57ba4548d97fc53eb64e0b5
> PHYSICALNAME.patch fixed the specific problem one user was having but
> broke other working configurations. That having been said, it generated
> errors in the providers file, not in the masq file. A follow-on patch
> was committed to the 4.6.2 branch to correct the initial patch.
I'll look for
I'm trying to get nfsen setup on my router/firewall box and I'm
running into the issue where nfcapd is not generating any data.
All my searching around basically seems to come down to people saying
firewalls sometimes block it from working (without much more data than
that or any resolutions)
On 8/13/2014 3:16 PM, PGNd wrote:
>> PHYSICALNAME.patch fixed the specific problem one user was having but
>> broke other working configurations. That having been said, it generated
>> errors in the providers file, not in the masq file. A follow-on patch
>> was committed to the 4.6.2 branch to corr
> Looks like one of your variables is empty!
Hm. Wasn't before the upgrade.
I'm staring at the above, but ... what are you seeing? is it EXTIF that's
empty?
--
___
Shorewall
On 8/13/2014 3:06 PM, Mark D. Montgomery II wrote:
> I'm trying to get nfsen setup on my router/firewall box and I'm running
> into the issue where nfcapd is not generating any data.
> All my searching around basically seems to come down to people saying
> firewalls sometimes block it from working
On 8/13/2014 3:36 PM, PGNd wrote:
>> Looks like one of your variables is empty!
>
> Hm. Wasn't before the upgrade.
>
> I'm staring at the above, but ... what are you seeing? is it EXTIF that's
> empty?
There aren't enough columns.
#INTERFACE SOURCE ADDRESS PROTO P
Togan is the SuSE Shorewall maintainer.
-Tom
Forwarded Message
Subject: Re: [Shorewall-devel] [Shorewall-users] after upgrade of
distro-shorewall 4.6.2.4-144.1 -> 4.6.2.4-146.1, compile "ERROR:
Invalid/Unknown leaf-1 port/service (tcp) "
Date: Thu, 14 Aug 2014 00:43:00 +0200
Fr
In the section where shorewall shows the /proc output rp_filter is 0
for default, all, and all interfaces except eth0.
Quoting Tom Eastep :
On 8/13/2014 3:06 PM, Mark D. Montgomery II wrote:
I'm trying to get nfsen setup on my router/firewall box and I'm running
into the issue where nfcapd
Turns out that the problem was in my Eclipse instance not syncing correctly
between its locally cached workspace -- which I'm editing directly -- and the
remote data, which shorewall is acting on/compiling.
In the local instance, everything looks OK. IN the remote, there's a #-comment
in front
Tom Eastep wrote:
> You need one. There is a populated file included with Shorewall; which
> distro are you running and how did you install Shorewall? Which
> Shorewall version (command: shorewall version -a). -Tom
Ok I'cw installed the one fron /usr/share/shorewall:
?FORMAT 3
#ACTION
18 matches
Mail list logo
