Am 01.06.2014 um 23:08 schrieb Michael Kress:
>
> OK, all things solved, thanks for pointing me to the right docs.
>
Uhm, one case has added to my config and I cannot make it work.
One host in the DMZ zone (192.168.0.15) which is connected over eth0
(192.168.0.1) should go out over tun1 (vpn) ma
On Thu, Aug 14, 2014 at 10:29:26PM +0100, ray klassen wrote:
>Aha, so you're the maintainer of those packages are you... Didn't see
>that. So at least you could reliably tell me if running the latest
>shorewall won't trigger any other issues with any other wheezy package?
>generally
Aha, so you're the maintainer of those packages are you... Didn't see that. So
at least you could reliably tell me if running the latest shorewall won't
trigger any other issues with any other wheezy package? generally I avoid sid
on production machines. (that said, to solve a specific problem I
On Thu, Aug 14, 2014 at 09:17:11PM +0100, ray klassen wrote:
>If I can, I stay current with the distro, unless there is a compelling
>reason to switch.
>
I understand.
If it helps you decide, the packages available on my site are virtually
identical to the packages I upload into Debian.
If I can, I stay current with the distro, unless there is a compelling reason
to switch.
On Thursday, 14 August 2014, 12:01, Roberto C. Sánchez
wrote:
On Thu, Aug 14, 2014 at 07:47:00PM +0100, ray klassen wrote:
> debian wheezy
> Kernel 3.2.0-4-amd64
> shorewall 4.5.5.3
>
That
On Thu, Aug 14, 2014 at 07:47:00PM +0100, ray klassen wrote:
>debian wheezy
>Kernel 3.2.0-4-amd64
>shorewall 4.5.5.3
>
That is a very old version of Shorewall. I don't use ipsets so I
haven't been particularly paying attention to the changes that Tom has
made in regard to ipsets, but
debian wheezy
Kernel 3.2.0-4-amd64
shorewall 4.5.5.3
On Thursday, 14 August 2014, 11:04, Roberto C. Sánchez
wrote:
On Thu, Aug 14, 2014 at 06:49:00PM +0100, ray klassen wrote:
> So back to thjs question. I figured I should wait with pursuing this until
> was more up to date. I am
On Thu, Aug 14, 2014 at 06:49:00PM +0100, ray klassen wrote:
>So back to thjs question. I figured I should wait with pursuing this until
>was more up to date. I am now current with the latest kernel and shorewall
>in debian (issues with openswan were hindering) and I tried ppp+ in my
>
So back to thjs question. I figured I should wait with pursuing this until was
more up to date. I am now current with the latest kernel and shorewall in
debian (issues with openswan were hindering) and I tried ppp+ in my masq file
and shorewall check gave me something like "invalid ipset ppp+ "
Shorewall 4.6.3 RC1 is now available for testing.
This version includes defect repair from 4.6.2.5.
Thank you for testing,
-Tom
--
Tom Eastep\ When I die, I want to go like my Grandfather who
Shoreline, \ died peacefully in his sleep. Not screaming like
Washington, USA \ all
Shorewall 4.6.2.5 is now available for download.
Problems Corrected:
1) Previously, when an interface specified the 'physical=' option and
the physical interface name was specified in the INTERFACES column
of the providers file, compilation would fail with diagnostics
similar to the
11 matches
Mail list logo
