>> On 10/7/2013 6:18 AM, Simon Matter wrote:
>>> Hi Tom and all,
>>>
>>> I started to play a bit with the AutoBL action on a CentOS 6 box and
>>> ran
>>> into the following problems:
>>>
>>> 1) The action.AutoBL doesn't work for me until I patch it like so:
>>>
>>> --- /usr/share/shorewall/action.A
On 8/10/2013 11:25 PM, Tom Eastep wrote:
>
> Jim,
>
> There is a bug.
>
> Patch attached.
>
> patch /usr/share/shorewall/Shorewall/Config.pm < H323.patch
>
> -Tom
Thank you.
The patch has fixed the problem.
- Jim Barber
Shorewall 4.5.21.1 is now available for download.
Problems Corrected:
1) Problems with the Shorewall Init installer (install.sh) were
corrected. These problems affected initial Gentoo and Debian
installs.
2) A problem that prevented multiple ICMP/ICMP6 types to be specified
in a ru
A lot of information exists online, yet none are thorough enough.i've read both
complex and simple traffic shaping on shorewall.net my goal is the following:
users are shaped to 50 KB/s unless connection is idle and that's where they
can use it all.
i tested the following, with no luck.
/etc/sh
Quoting Tom Eastep :
On 10/08/2013 09:09 AM, Mark D. Montgomery II wrote:
Quoting Tom Eastep :
On 10/7/2013 10:25 PM, Mark D. Montgomery II wrote:
I had to restart one of my routers tonight and since then shorewall on
it has been dropping SIP packets coming in from one machine instead of
Hi everybody, I have a question about this:
I have a web-server with a 1gb up-link and with 3 virtual devices
eth0
eth0:0
eth0:1
I have an apache running in eth0 and streaming services running in eth0:0
and eth0:1
every virtual device with a different IP.
So, if I would like to implement QoS to
Hi,
>> Undefined subroutine &Shorewall::Chains::list_split called at
>> /usr/share/shorewall/Shorewall/Chains.pm line 4488, <$currentfile> line 25.
>>
>
> Patch attached.
>
Thanks Tom, this solves the issue!
Mark
--
On 10/08/2013 09:09 AM, Mark D. Montgomery II wrote:
>
> Quoting Tom Eastep :
>
>> On 10/7/2013 10:25 PM, Mark D. Montgomery II wrote:
>>>
>>> I had to restart one of my routers tonight and since then shorewall on
>>> it has been dropping SIP packets coming in from one machine instead of
>>> forw
Aha!
I did conntrack -D -s and it removed a bunch of entries and
the trunk came right back up.
Thanks!
Quoting Tom Eastep :
On 10/7/2013 10:25 PM, Mark D. Montgomery II wrote:
I had to restart one of my routers tonight and since then shorewall on
it has been dropping SIP packets coming
Quoting Tom Eastep :
On 10/7/2013 10:25 PM, Mark D. Montgomery II wrote:
I had to restart one of my routers tonight and since then shorewall on
it has been dropping SIP packets coming in from one machine instead of
forwarding them to the freebpx server.
Shorewall:net2all:DROP:IN=eth0 OUT= MA
On 10/8/2013 2:19 AM, Jim Barber wrote:
> Hi all.
>
> I can't seem to get the h323 connection tracking configured correctly for
> Shorewall.
> I am using the Debian Shorewall 4.5.16.1 package.
> I am running a Debian 3.9 kernel like so:
>
> # uname -a
> Linux gw 3.9-1-amd64 #1 SMP De
On 10/8/2013 5:35 AM, Mark van Dijk wrote:
> Hi Tom and list members,
>
> I had the following in my shorewall6 rules file:
>
> ACCEPT wan lan icmp 135,136
>
> to accept ICMPv6 packets of type rtsol/adv.
>
> When restarting shorewall the following output was observed:
>
> Undefined subrouti
On 10/7/2013 10:25 PM, Mark D. Montgomery II wrote:
>
> I had to restart one of my routers tonight and since then shorewall on
> it has been dropping SIP packets coming in from one machine instead of
> forwarding them to the freebpx server.
>
> Shorewall:net2all:DROP:IN=eth0 OUT= MAC= SRC= extern
Hi Tom and list members,
I had the following in my shorewall6 rules file:
ACCEPT wan lan icmp 135,136
to accept ICMPv6 packets of type rtsol/adv.
When restarting shorewall the following output was observed:
Undefined subroutine &Shorewall::Chains::list_split called at
/usr/share/shorewall/
Hi all.
I can't seem to get the h323 connection tracking configured correctly for
Shorewall.
I am using the Debian Shorewall 4.5.16.1 package.
I am running a Debian 3.9 kernel like so:
# uname -a
Linux gw 3.9-1-amd64 #1 SMP Debian 3.9.8-1 x86_64 GNU/Linux
My version of iptables
15 matches
Mail list logo