Hi I am hoping for some guidance on how to do this. I don''t expect the rules! :) I want to make sure that any potentially infected machines do not spread to other machines. What I want to do is to force all traffic from clients in loc sending email to go to my mail server. This will force any email being transmitted to other hosts to go through the virus and spam checker and not allow any machines to send email straight through the shorewall machine. I am using shorewall 2.4.2 on 2.6.12 kernel. Any ideas? Regards Ray -- Ray Booysen rj_booysen@rjb.za.net ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
Simply block port 25 from loc to net and configure all your local machines to use your mail server (I suppose it''s local). When a PC is infected, the virus code connects directly to port 25 of the recipient''s mail server, and if you block this kind of connections you''re fine. This is not a limitation (your PCs in loc shouldn''t use any external mail server for any legitimate use). Regards, Elio ----- Original Message ----- From: "Ray Booysen" <rj_booysen@rjb.za.net> To: <shorewall-users@lists.sourceforge.net> Sent: Friday, December 09, 2005 11:06 AM Subject: [Shorewall-users] Forwarding internal traffic to Firewall Hi I am hoping for some guidance on how to do this. I don''t expect the rules! :) I want to make sure that any potentially infected machines do not spread to other machines. What I want to do is to force all traffic from clients in loc sending email to go to my mail server. This will force any email being transmitted to other hosts to go through the virus and spam checker and not allow any machines to send email straight through the shorewall machine. I am using shorewall 2.4.2 on 2.6.12 kernel. Any ideas? Regards Ray -- Ray Booysen rj_booysen@rjb.za.net ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Shorewall-users mailing list Shorewall-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-users ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
Hi Ray: Use the squid docs as a starting point, just change the port number, nothing special is needed on the mail scanner, just skip that part. Jerry ----- Original Message ----- From: "Ray Booysen" <rj_booysen@rjb.za.net> To: <shorewall-users@lists.sourceforge.net> Sent: Friday, December 09, 2005 04:06 Subject: [Shorewall-users] Forwarding internal traffic to Firewall> Hi > > I am hoping for some guidance on how to do this. I don''t expect the > rules! :) > I want to make sure that any potentially infected machines do not spread > to other machines. What I want to do is to force all traffic from > clients in loc sending email to go to my mail server. This will force > any email being transmitted to other hosts to go through the virus and > spam checker and not allow any machines to send email straight through > the shorewall machine. > > I am using shorewall 2.4.2 on 2.6.12 kernel. > > Any ideas? > > Regards > Ray > > -- > Ray Booysen > rj_booysen@rjb.za.net > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > Shorewall-users mailing list > Shorewall-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/shorewall-users------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
Configure ALL my local machines? This process is simpler. Configure shorewall to take all outgoing SMTP connections and redirect to my mail server (the shorewall box as well - prevents a very interesting mail-loop ) :) Thanks Ray Elio Tondo wrote:> Simply block port 25 from loc to net and configure all your local > machines to use your mail server (I suppose it''s local). When a > PC is infected, the virus code connects directly to port 25 of the > recipient''s mail server, and if you block this kind of connections > you''re fine. This is not a limitation (your PCs in loc shouldn''t use > any external mail server for any legitimate use). > > Regards, > > Elio > > ----- Original Message ----- > From: "Ray Booysen" <rj_booysen@rjb.za.net> > To: <shorewall-users@lists.sourceforge.net> > Sent: Friday, December 09, 2005 11:06 AM > Subject: [Shorewall-users] Forwarding internal traffic to Firewall > > > Hi > > I am hoping for some guidance on how to do this. I don''t expect the > rules! :) > I want to make sure that any potentially infected machines do not spread > to other machines. What I want to do is to force all traffic from > clients in loc sending email to go to my mail server. This will force > any email being transmitted to other hosts to go through the virus and > spam checker and not allow any machines to send email straight through > the shorewall machine. > > I am using shorewall 2.4.2 on 2.6.12 kernel. > > Any ideas? > > Regards > Ray > >-- Ray Booysen rj_booysen@rjb.za.net ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
Hi Jerry Thanks for the guidance. Regards Ray Jerry Vonau wrote:> Hi Ray: > > Use the squid docs as a starting point, just change the port number, > nothing special is needed on the mail scanner, just skip that part. > > Jerry > > > ----- Original Message ----- > From: "Ray Booysen" <rj_booysen@rjb.za.net> > To: <shorewall-users@lists.sourceforge.net> > Sent: Friday, December 09, 2005 04:06 > Subject: [Shorewall-users] Forwarding internal traffic to Firewall > > > >> Hi >> >> I am hoping for some guidance on how to do this. I don''t expect the >> rules! :) >> I want to make sure that any potentially infected machines do not spread >> to other machines. What I want to do is to force all traffic from >> clients in loc sending email to go to my mail server. This will force >> any email being transmitted to other hosts to go through the virus and >> spam checker and not allow any machines to send email straight through >> the shorewall machine. >> >> I am using shorewall 2.4.2 on 2.6.12 kernel. >> >> Any ideas? >> >> Regards >> Ray >> >> -- >> Ray Booysen >> rj_booysen@rjb.za.net >> >> >> >> ------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files >> for problems? Stop! Download the new AJAX search engine that makes >> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! >> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click >> _______________________________________________ >> Shorewall-users mailing list >> Shorewall-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/shorewall-users >> > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_idv37&alloc_id865&op=click > _______________________________________________ > Shorewall-users mailing list > Shorewall-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/shorewall-users >-- Ray Booysen rj_booysen@rjb.za.net ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
Hi Ray. If you want to send e-mail from the clients in the first place, you have already configured the clients. So there will be no additional configuring on the clients apart from that. So I would guess that to block SMTP out as Elio described is a good solution. Redirection to your own server is also an extra issue if an infected machine tries to connect directly to an external server, and your mail server accepts this e-mail and send it trough. Or in the case one machine gets infected with a virus that sends random spam e-mail directly with no virus attached. Then all/most of that mail will probably be sent via your server. Since there will always be a windows in time between a new virus or worm starts spreading to a remedy is available, your main outgoing server may be the sending these a while. Both solutions will give added security, but I personally would go for Elio''s solution. (But as stated earlier, I''m no expert) /K -----Original Message----- From: shorewall-users-admin@lists.sourceforge.net [mailto:shorewall-users-admin@lists.sourceforge.net] On Behalf Of Ray Booysen Sent: 9. desember 2005 12:30 To: shorewall-users@lists.sourceforge.net Subject: Re: [Shorewall-users] Forwarding internal traffic to Firewall Configure ALL my local machines? This process is simpler. Configure shorewall to take all outgoing SMTP connections and redirect to my mail server (the shorewall box as well - prevents a very interesting mail-loop ) :) Thanks Ray Elio Tondo wrote:> Simply block port 25 from loc to net and configure all your local > machines to use your mail server (I suppose it''s local). When a > PC is infected, the virus code connects directly to port 25 of the > recipient''s mail server, and if you block this kind of connections > you''re fine. This is not a limitation (your PCs in loc shouldn''t use > any external mail server for any legitimate use). > > Regards, > > Elio > > ----- Original Message ----- > From: "Ray Booysen" <rj_booysen@rjb.za.net> > To: <shorewall-users@lists.sourceforge.net> > Sent: Friday, December 09, 2005 11:06 AM > Subject: [Shorewall-users] Forwarding internal traffic to Firewall > > > Hi > > I am hoping for some guidance on how to do this. I don''t expect the > rules! :) > I want to make sure that any potentially infected machines do not spread > to other machines. What I want to do is to force all traffic from > clients in loc sending email to go to my mail server. This will force > any email being transmitted to other hosts to go through the virus and > spam checker and not allow any machines to send email straight through > the shorewall machine. > > I am using shorewall 2.4.2 on 2.6.12 kernel. > > Any ideas? > > Regards > Ray > >-- Ray Booysen rj_booysen@rjb.za.net ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Shorewall-users mailing list Shorewall-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-users ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
K wrote:> Hi Ray. > > If you want to send e-mail from the clients in the first place, you have > already configured the clients. > So there will be no additional configuring on the clients apart from that. >No, I don''t want them sending email. This is extra protection in case of a virus or worm infecting the PC. This forces all the email originating from the loc zone to be forced to my mail server where proper disinfection can take place> So I would guess that to block SMTP out as Elio described is a good > solution. > > Redirection to your own server is also an extra issue if an infected machine > tries to connect directly to an external server, and your mail server > accepts this e-mail and send it trough. Or in the case one machine gets > infected with a virus that sends random spam e-mail directly with no virus > attached. Then all/most of that mail will probably be sent via your server. >I have proper virus checking on the mailserver. I have postfix running ClamAV and F-Prot (in case ClamAV falls over) If mail originates in the loc zone, this is an anomily to begin with and I want to deal with it appropriately. The only machine that mail should originate from is my shorewall machine and the exchange server. The exchange server already uses the postfix machine as it''s smart host so this won''t be affected.> Since there will always be a windows in time between a new virus or worm > starts spreading to a remedy is available, your main outgoing server may be > the sending these a while. > > Both solutions will give added security, but I personally would go for > Elio''s solution. > (But as stated earlier, I''m no expert) > > /K > > -----Original Message----- > From: shorewall-users-admin@lists.sourceforge.net > [mailto:shorewall-users-admin@lists.sourceforge.net] On Behalf Of Ray > Booysen > Sent: 9. desember 2005 12:30 > To: shorewall-users@lists.sourceforge.net > Subject: Re: [Shorewall-users] Forwarding internal traffic to Firewall > > Configure ALL my local machines? This process is simpler. Configure > shorewall to take all outgoing SMTP connections and redirect to my mail > server (the shorewall box as well - prevents a very interesting > mail-loop ) :) > > Thanks > Ray > > Elio Tondo wrote: > >> Simply block port 25 from loc to net and configure all your local >> machines to use your mail server (I suppose it''s local). When a >> PC is infected, the virus code connects directly to port 25 of the >> recipient''s mail server, and if you block this kind of connections >> you''re fine. This is not a limitation (your PCs in loc shouldn''t use >> any external mail server for any legitimate use). >> >> Regards, >> >> Elio >> >> ----- Original Message ----- >> From: "Ray Booysen" <rj_booysen@rjb.za.net> >> To: <shorewall-users@lists.sourceforge.net> >> Sent: Friday, December 09, 2005 11:06 AM >> Subject: [Shorewall-users] Forwarding internal traffic to Firewall >> >> >> Hi >> >> I am hoping for some guidance on how to do this. I don''t expect the >> rules! :) >> I want to make sure that any potentially infected machines do not spread >> to other machines. What I want to do is to force all traffic from >> clients in loc sending email to go to my mail server. This will force >> any email being transmitted to other hosts to go through the virus and >> spam checker and not allow any machines to send email straight through >> the shorewall machine. >> >> I am using shorewall 2.4.2 on 2.6.12 kernel. >> >> Any ideas? >> >> Regards >> Ray >> >> >> > > >-- Ray Booysen rj_booysen@rjb.za.net ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
If you just want to grab all connections from, for example, zone ''loc'' to any other zone, then all you need to do is add this to your ''rules'' file. #ACTION SOURCE DEST PROTO DEST PORT(S) SOURCE ORIGINAL # PORT(S) DEST REDIRECT loc 25 tcp 25 - - ...which will grab every connection destined for port 25, coming from the ''loc'' zone, and forward it to port 25 on the machine running Shorewall. you''ll want to test it to make sure it works correctly, of course. If you change the port that the rule redirects to, be careful, as it''ll open up this port regardless of whether you want it to or not. (see below example) #ACTION SOURCE DEST PROTO DEST PORT(S) SOURCE ORIGINAL # PORT(S) DEST REDIRECT loc 80 tcp 1001 - - this rule would mean that for the zone ''loc'', entering http://server:80would redirect the connection to port 1001 on that server - but also importantly, entering http://server:1001 would bring up the same thing. (this is in the context of running a http server on port 1001 on the firewall machine) Just something to bear in mind. This shouldn''t be a problem for your application. Hope this actually answers your question o_o Jan Mulders On 09/12/05, Ray Booysen <rj_booysen@rjb.za.net> wrote:> > K wrote: > > Hi Ray. > > > > If you want to send e-mail from the clients in the first place, you have > > already configured the clients. > > So there will be no additional configuring on the clients apart from > that. > > > No, I don''t want them sending email. This is extra protection in case > of a virus or worm infecting the PC. This forces all the email > originating from the loc zone to be forced to my mail server where > proper disinfection can take place > > > > So I would guess that to block SMTP out as Elio described is a good > > solution. > > > > Redirection to your own server is also an extra issue if an infected > machine > > tries to connect directly to an external server, and your mail server > > accepts this e-mail and send it trough. Or in the case one machine gets > > infected with a virus that sends random spam e-mail directly with no > virus > > attached. Then all/most of that mail will probably be sent via your > server. > > > I have proper virus checking on the mailserver. I have postfix running > ClamAV and F-Prot (in case ClamAV falls over) If mail originates in the > loc zone, this is an anomily to begin with and I want to deal with it > appropriately. The only machine that mail should originate from is my > shorewall machine and the exchange server. The exchange server already > uses the postfix machine as it''s smart host so this won''t be affected. > > > Since there will always be a windows in time between a new virus or worm > > starts spreading to a remedy is available, your main outgoing server may > be > > the sending these a while. > > > > Both solutions will give added security, but I personally would go for > > Elio''s solution. > > (But as stated earlier, I''m no expert) > > > > /K > > > > -----Original Message----- > > From: shorewall-users-admin@lists.sourceforge.net > > [mailto:shorewall-users-admin@lists.sourceforge.net] On Behalf Of Ray > > Booysen > > Sent: 9. desember 2005 12:30 > > To: shorewall-users@lists.sourceforge.net > > Subject: Re: [Shorewall-users] Forwarding internal traffic to Firewall > > > > Configure ALL my local machines? This process is simpler. Configure > > shorewall to take all outgoing SMTP connections and redirect to my mail > > server (the shorewall box as well - prevents a very interesting > > mail-loop ) :) > > > > Thanks > > Ray > > > > Elio Tondo wrote: > > > >> Simply block port 25 from loc to net and configure all your local > >> machines to use your mail server (I suppose it''s local). When a > >> PC is infected, the virus code connects directly to port 25 of the > >> recipient''s mail server, and if you block this kind of connections > >> you''re fine. This is not a limitation (your PCs in loc shouldn''t use > >> any external mail server for any legitimate use). > >> > >> Regards, > >> > >> Elio > >> > >> ----- Original Message ----- > >> From: "Ray Booysen" <rj_booysen@rjb.za.net> > >> To: <shorewall-users@lists.sourceforge.net> > >> Sent: Friday, December 09, 2005 11:06 AM > >> Subject: [Shorewall-users] Forwarding internal traffic to Firewall > >> > >> > >> Hi > >> > >> I am hoping for some guidance on how to do this. I don''t expect the > >> rules! :) > >> I want to make sure that any potentially infected machines do not > spread > >> to other machines. What I want to do is to force all traffic from > >> clients in loc sending email to go to my mail server. This will force > >> any email being transmitted to other hosts to go through the virus and > >> spam checker and not allow any machines to send email straight through > >> the shorewall machine. > >> > >> I am using shorewall 2.4.2 on 2.6.12 kernel. > >> > >> Any ideas? > >> > >> Regards > >> Ray > >> > >> > >> > > > > > > > > > -- > Ray Booysen > rj_booysen@rjb.za.net > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > Shorewall-users mailing list > Shorewall-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/shorewall-users >
Thanks, it does and is the same as the Squid rules, just the ports are different (obviously) :) Thanks Ray Jan Mulders wrote:> If you just want to grab all connections from, for example, zone ''loc'' > to any other zone, then all you need to do is add this to your ''rules'' > file. > > #ACTION SOURCE DEST PROTO DEST PORT(S) SOURCE ORIGINAL > # PORT(S) DEST > REDIRECT loc 25 tcp 25 - - > ...which will grab every connection destined for port 25, coming from > the ''loc'' zone, and forward it to port 25 on the machine running > Shorewall. > > you''ll want to test it to make sure it works correctly, of course. If > you change the port that the rule redirects to, be careful, as it''ll > open up this port regardless of whether you want it to or not. (see > below example) > #ACTION SOURCE DEST PROTO DEST PORT(S) SOURCE ORIGINAL > # PORT(S) DEST > REDIRECT loc 80 tcp 1001 - - > this rule would mean that for the zone ''loc'', entering > http://server:80 would redirect the connection to port 1001 on that > server - but also importantly, entering http://server:1001 would bring > up the same thing. (this is in the context of running a http server on > port 1001 on the firewall machine) > > Just something to bear in mind. This shouldn''t be a problem for your > application. > > Hope this actually answers your question o_o > > Jan Mulders > > > On 09/12/05, *Ray Booysen* <rj_booysen@rjb.za.net > <mailto:rj_booysen@rjb.za.net>> wrote: > > K wrote: > > Hi Ray. > > > > If you want to send e-mail from the clients in the first place, > you have > > already configured the clients. > > So there will be no additional configuring on the clients apart > from that. > > > No, I don''t want them sending email. This is extra protection in case > of a virus or worm infecting the PC. This forces all the email > originating from the loc zone to be forced to my mail server where > proper disinfection can take place > > > > So I would guess that to block SMTP out as Elio described is a good > > solution. > > > > Redirection to your own server is also an extra issue if an > infected machine > > tries to connect directly to an external server, and your mail > server > > accepts this e-mail and send it trough. Or in the case one > machine gets > > infected with a virus that sends random spam e-mail directly > with no virus > > attached. Then all/most of that mail will probably be sent via > your server. > > > I have proper virus checking on the mailserver. I have postfix > running > ClamAV and F-Prot (in case ClamAV falls over) If mail originates > in the > loc zone, this is an anomily to begin with and I want to deal with it > appropriately. The only machine that mail should originate from is my > shorewall machine and the exchange server. The exchange server > already > uses the postfix machine as it''s smart host so this won''t be affected. > > > Since there will always be a windows in time between a new virus > or worm > > starts spreading to a remedy is available, your main outgoing > server may be > > the sending these a while. > > > > Both solutions will give added security, but I personally would > go for > > Elio''s solution. > > (But as stated earlier, I''m no expert) > > > > /K > > > > -----Original Message----- > > From: shorewall-users-admin@lists.sourceforge.net > <mailto:shorewall-users-admin@lists.sourceforge.net> > > [mailto: shorewall-users-admin@lists.sourceforge.net > <mailto:shorewall-users-admin@lists.sourceforge.net>] On Behalf Of Ray > > Booysen > > Sent: 9. desember 2005 12:30 > > To: shorewall-users@lists.sourceforge.net > <mailto:shorewall-users@lists.sourceforge.net> > > Subject: Re: [Shorewall-users] Forwarding internal traffic to > Firewall > > > > Configure ALL my local machines? This process is > simpler. Configure > > shorewall to take all outgoing SMTP connections and redirect to > my mail > > server (the shorewall box as well - prevents a very interesting > > mail-loop ) :) > > > > Thanks > > Ray > > > > Elio Tondo wrote: > > > >> Simply block port 25 from loc to net and configure all your local > >> machines to use your mail server (I suppose it''s local). When a > >> PC is infected, the virus code connects directly to port 25 of the > >> recipient''s mail server, and if you block this kind of connections > >> you''re fine. This is not a limitation (your PCs in loc > shouldn''t use > >> any external mail server for any legitimate use). > >> > >> Regards, > >> > >> Elio > >> > >> ----- Original Message ----- > >> From: "Ray Booysen" <rj_booysen@rjb.za.net > <mailto:rj_booysen@rjb.za.net>> > >> To: < shorewall-users@lists.sourceforge.net > <mailto:shorewall-users@lists.sourceforge.net>> > >> Sent: Friday, December 09, 2005 11:06 AM > >> Subject: [Shorewall-users] Forwarding internal traffic to Firewall > >> > >> > >> Hi > >> > >> I am hoping for some guidance on how to do this. I don''t > expect the > >> rules! :) > >> I want to make sure that any potentially infected machines do > not spread > >> to other machines. What I want to do is to force all traffic from > >> clients in loc sending email to go to my mail server. This > will force > >> any email being transmitted to other hosts to go through the > virus and > >> spam checker and not allow any machines to send email straight > through > >> the shorewall machine. > >> > >> I am using shorewall 2.4.2 on 2.6.12 kernel. > >> > >> Any ideas? > >> > >> Regards > >> Ray > >> > >> > >> > > > > > > > > > -- > Ray Booysen > rj_booysen@rjb.za.net <mailto:rj_booysen@rjb.za.net> > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through > log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD > SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > <http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click> > _______________________________________________ > Shorewall-users mailing list > Shorewall-users@lists.sourceforge.net > <mailto:Shorewall-users@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/shorewall-users > >-- Ray Booysen rj_booysen@rjb.za.net ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click