similar to: [Fwd: Re: Shorewall and webmin, partialy solved !]

What about Webmin Module compatbility ? If I do not create any rule violating any of that new features, it will work ? Or the module is unusable until someone make necessary modifications ? F?bio Rabelo

I remember to see something about that in shorewall.net some time ago, but I could not find it today ... The case : Debian Etch, Shorewall 3.2.6, squid3 and Apache 2 . The first 3 where already running fine for some time ... Now I need to setup an Apache server to allow some web mannagement, things like PHPsysinfo, phppgadmin, just for internal net, no web access . but port 80 is redirected to

Jens wrote: > It seems that the standard setup as per my debian system has > the following : IP_FORWARDING=keep > To make my system work I had to change this to IP_FORWARDING=on. > > I have a pretty basic/stock debian (unstable) box sitting here for shorewall. > As far as I remember, nothing on this box as relating to ip_forwarding was > changed. > > I

I want to use lastest version of Shorewall in my fresh debian squeeze instalation, so I follow http://www.shorewall.net/Install.htm#Debian but, modify preferences file was not enough for me, I have to modify/add some other files in /etc/apt/ directory: 1.) include testing repo to source.list 2.) add APT::Default-Release "stable"; to apt.conf and pinning all other packages to stable

Hi to all For is just az concept question : There are a need to change something in Squid3 config when it are running in the same box as shorewall with 2 ISP ? I''ve been thinking in do this at home, as a proof of concept for future implememtations ... I allways use Roberto''s Debian package to implement Shorewall . Fábio Rabelo

Hi for all ... I just read all doc about ip alias in Shorewall . If I am right, I can not use ip alias with masq, it is right ? What I am trying to do is create an ip alias in my internal network interface and use it for tests purpose ( specifically for getting familiar with multi ISP shorewall config ) The actual system is working fine with the ip 192.168.1.1 in eth1, eth0 is my dsl provider .

My description of the incorrect use of the term ''SNAT'' on the Static NAT Webmin page was apparently misunderstood. Attached is a patch against the Webmin-1.070 Shorewall module that corrects this problem and also adds the ''DNAT-'' action for rules. To apply the patch, you will need the ''patch'' utility: cd <webmin shorewall directory - on

Anybody ever consider writing a Shorewall module for Webmin? Sincerely, Jim Hubbard Visit us online at www.dyersinc.com

I just updated my webmin on my server and noticed that the module for Shorewall looked different. It looks like someone really cleaned it up and had it added to the Standard Webmin Module list. Woohoo. -- Joe *** I can only please one person a day. Today is not your day and tomorrow doesn''t look good either. ***

I just updated my webmin on my server and noticed that the module for Shorewall looked different. It looks like someone really cleaned it up and had it added to the Standard Webmin Module list. Woohoo. -- Joe *** I can only please one person a day. Today is not your day and tomorrow doesn''t look good either. ***

Hey folks! I need to allow smartcard authentication of a third party certificate generated with an UPN that has a suffix that is not my domain name. From AD literature, it's possible. I followed these guidelines to make an additional UPN available for login: https://technet.microsoft.com/en-us/library/cc772007.aspx But I'm missing something. Kerberos does a part of the job, but then

Since a couple of days I have a very strang thing... Machine-A : eth0 192.168.5.37 (linux) eth1 x.x.5.37 Machine-B : eth0 192.168.5.10 (win2k) eth1 x.x.5.10 eth3 not configured Machine-C : eth0 192.168.89.10 (win2k) Machine-B was mounted on Machine-A on /mnt/d (through 192.168.5.10) Machine-C was mounted on Machine-B on /mnt/c (through 192.168.89.10) After a power-failure on

My reason for patching circa line 225 is that I think it is clearer. The reason for patching circa line 575 is http://bugs.debian.org/647603. They concluded that a .0 file is recognized not only by PXELINUX. And what is NBP? --- a/doc/syslinux.txt 2011-12-07 04:53:29.201556663 +0200 +++ b/doc/syslinux.txt 2011-12-07 04:50:11.000000000 +0200 @@ -221,7 +221,6 @@ LABEL label The following

As Shorewall reaches maturity, it seems unlikely that the pace of development typical of the past 9 years will be sustained. Over that time, major releases have occurred approximately once per year; the last major release (4.4) was in August 2009. I do not currently have an active 4.5 development branch so it is very unlikely that we will see a 4.6 release this year. Going forward, I would

As Shorewall reaches maturity, it seems unlikely that the pace of development typical of the past 9 years will be sustained. Over that time, major releases have occurred approximately once per year; the last major release (4.4) was in August 2009. I do not currently have an active 4.5 development branch so it is very unlikely that we will see a 4.6 release this year. Going forward, I would

Oi F?bio. Pelo IP tamb?m n?o acessa. A minha suspeita de que era um problema ligado a interface est? errada. Aleat?riamente usu?rios nas duas interfaces perdem o acesso. Ainda assim, somente usu?rios com Windows XP tem esse problema. Vou testar suas indica??es. F?bio Rabelo wrote: > > > 2010/3/23 Leonardo Carneiro - Veltrac <lscarneiro at veltrac.com.br > <mailto:lscarneiro

Shorewall 1.3.9 is available. In this release: 1. DNS Names are now allowed in Shorewall config files (I still recommend against using them however). 2. The connection SOURCE may now be qualified by both interface and IP address in a Shorewall rule. 3. Shorewall startup is now disabled after initial installation until the file /etc/shorewall/startup_disabled is removed. 4. The

Hello, I believe there may be a bug in shorewall version 2.0.8. I''ve been using shorewall for years without problems (last installed version was 1.4.6b-1). I''ve posted previously with the subject line "After upgrade people can no longer connect" dated on Sunday, September 19, 2004 which contains all the information for the upgrade. Today I uninstalled shorewall

This is a bug-fix roll-up. Problems corrected since 1.4.6: 1) Corrected problem in 1.4.6 where the MANGLE_ENABLED variable was being tested before it was set. 2) Corrected handling of MAC addresses in the SOURCE column of the tcrules file. Previously, these addresses resulted in an invalid iptables command. 3) The "shorewall stop" command is now disabled when

Rela??o de aprovados Mar Vermelho: ?gua Clara: ANA PAULA RODRIGUES DA SILVA, LUCAS ARAUJO GOMES FROTA, GABRIEL VICTOR BARROS FORTE DA SILVA, QUIT?RIA DA SILVA G?IS, JO?O CARLOS MOREIRA DE CARVALHO, DAYANA MARIA DE SOUSA TAVARES, MARIA JULIENE CORDEIRO, JO?O PAULO DA SILVA. TALITA FERNANDES GONCALVES, BRUNO RAMOS FERNANDES, LUIZ HENRIQUE ALVES DAMASCENO, IAGO DA SILVA NOBRE, RITA ANGELA DA SILVA.