similar to: logs

Mike Lander wrote: > I am building a shorewall box that the last post has the SSH error and > wanted > some feedback from the list if possible. At first I thought the two ISP''s > I > building this > for had two T-1''s with FQ ip''s as it. I have the box built for this ready > to > go. > Now I find out that one of the T-1''s is

Is there a way to listen on port 25 for repeated dictionary attacks to harvest email address and blacklist that Ip with shorewall? Thanks, Mike

I have built a fedora 3 test box that has 4 pptp client vpn''s from my T-1 to a Group of businesses (test environment). The businesses all have pptp vpn concentrators on their ends. The purpose is that all of the businesses will be at an offsite location together for a 3 day sale. I have the box working now with the latest ver of shorewall with two nics on this fedora box eth0 will

Hello, You may recall some of My Dmz question around Thanksgiving. While I have configured a Proxy arp Dmz. I would like to practice with the routed setup you suggested Tom as your network was simular. Here is one of your quotes "The configuration of eth2 is largely irrelevant but you certainly don''t want to confuse things by assigning any default gateway out of that

Hello! I have a problem using shorewall on an aliased interface. Let me give you a short description of the setup: eth0 uses DHCP and will be assigned a 10.38.0.0/16 address by my ISP; I use a host-route to access their PPTP on 10.0.0.138 with "pptp 10.0.0.138" ppp0 is the Internetconnection then (duh) At the same time I want to connect the box to my LAN using 10.1.0.0/16 or any

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 claas@rootdir.de wrote: > Hello, > > > > #--- file: policy --- > #vpn policies: > loc vpn ACCEPT info > fw vpn ACCEPT info > vpn loc ACCEPT info > vpn fw ACCEPT info > > net

Sorry some email problem, i have change it for more reliable one. I have try this morning to netmasq 192.168.11.0 (eth1) to 192.168.1.0 (eth0), but it is a mistake. Yes thank you for answering so fast ! I have corrected it, here the new diagram and the new routing table. But it still doesn''t work. From the router i can access to 192.168.11.254 I have add the rules : DNAT loc

Hi all, I have a problem with a new Shorewall box I''m trying to migrate from iptables rules to shorewall 2.2.0. I have a 3 interfaces setup: - eth0 ---> internet (ip address) - eth1 ---> remote office (10.0.0.0/8) - eth2 ---> lan (192.168.16.0/24) I''m using a very simple and common setup, with just a few DNAT rules in my /etc/shorewall/rules file, and about twenty

Yes thank you for answering so fast ! I have corrected it, here the new diagram and the new routing table. But it still doesn''t work. >From the router i can access to 192.168.11.254 I have add the rules : DNAT loc priv:192.168.11.254:22 tcp 22 But i can''t connect to 192.168.11.254 from LAN The DNAT fonction doesn''t work, but i can DROP packet arriving on eth0 (loc)

Marta, As Alan pointed out the loc->net policy is Continue, it should probably be loc->net ACCEPT. This is from Tom''s Shorewall Documentation... http://www.shorewall.net/Documentation.htm#Policy CONTINUE - The connection is neither ACCEPTed, DROPped nor REJECTed. CONTINUE may be used when one or both of the zones named in the entry are sub-zones of or intersect with another zone.

Now I have a weird problem I have testing with two networks. This trouble has to do with the hosts file. #ZONE HOST(S) OPTIONS loctw eth1:192.168.50.0/24 loctw ppp+:!192.168.50.0/24 locsa eth1:192.168.75.0/24 locsa ppp+:!192.168.75.0/24 loc eth1:192.168.25.0/24 #vpn3 ppp+:192.168.3.0/24 I can get through only one tunnel at

I''ve installed a bering box acting as a firewall for a lan; the lan is 192.168.1.0/24 the bering box is 192.168.1.254 I''ve installed a squid server 192.168.1.1 It is possible to configure shorewall for a transparent proxy to the squid server? I''ve tryed with REDIRECT loc loc:192.168.1.1:3128 tcp www - !192.168.1.1 in the rules file I get this error: Error:

I''m beginning to believe that the use of the last column in the rules file to designate redirection/forwarding is too subtle for many users. For 1.3, I think I''ll do something like the following: Current rule: ACCEPT net loc:192.168.1.3 tcp 80 - all New rule: FORWARD net loc:192.168.1.3 tcp 80 Current rule: ACCEPT net fw::3128 tcp 80 - all New rule: REDIRECT net

Dear experts, Quick quotation... I have a sendmail server behind the shorewall-2.1.7 server. I would like to do Port forwarding (DNAT) for clients on the internet, who need to access the mail server. Please let me know, which way is the most suitable to accomplish this; using following 2 types of configurations Setup - Internet -- > shorewall -- > sendmail

Hello, Have a question I am new to squid, although I have about 100~150 hours of study in the last month to move up quickly. I have set up rh 7.1 on a 300 mgz intell celeron 128mb ram 8gb hd. shorewall 1.2.9 running webmin with openssl access and squidGuard filter. I set it up this weekend to work with a fairly small network that masquerades through shorewall. It serves 60 windows boxs most

I made a boo boo in my config and put in this rule #PPTP DNAT net:213.67.241.162/217.209.46.204/32 loc:192.168.221.200 tcp 1723 DNAT net:213.67.241.162/32,217.209.46.204/32 loc:192.168.221.200 47 - And the the following happened.. and I wonder why it didn''t complain? I am sure I am just misunderstanding some doc

Hello! We''re seeing a problem that I think is more of a Netfilter or kernel issue than anything to do with Shorewall, but I thought I would ask about it here, too, to see if anyone has suggestions. What we''re seeing is that, when we do a very fast port scan of a system on the other side of a firewall with Shorewall installed and various common rules, a majority of the denied

The rule: ACCEPT loc $FW::3128 tcp www doesn''t work propertly, the http access does not redirect to squid but directly exit. what''s wrong? Thanks ------- Dario Lesca (d.lesca@ivrea.osra.it) -------------------------------------- @@@@@@@ this is my shorewall-1.2.13 config: #[/etc/shorewall/common.def]-----------------------------------------------

Hi all, its a real nightmare for me. Although i have read and searched the web for two weeks i can`t get shorewall to work. problem is that we have only one server that acts as fileserver (samba, nis, nfs) and router/firewall for the lan. the server has two interfaces eth0 = lan and eth1 = internet. The only what we need is full access from the lan to the firewall and restricted access

I have the problem when my localnetwork do telnet to the net Shorewall:FORWARD:REJECT:IN=eth0 OUT=eth2 my files are the following: policy #SOURCE DEST POLICY LOG LEVEL LIMIT:BURST loc net CONTINUE info loc fw ACCEPT info loc loc ACCEPT loc dmz ACCEPT info fw