similar to: System Boot problem...

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:

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]-----------------------------------------------

Hello, on my old system I''m using ipchains. Can anyone help me with converting rule /sbin/ipchains -A forward -j MASQ -s source_addr -d destination_addr 443 -p tcp to shorewall. I know that I can write eth0 source_addr to /etc/shorewall/masq file but I can''t found where I can specify the destination address. The reason for this is to allow one user (computer) access only to

Warning .... The two interface samples contain samples of the three interface... [root@multilinux temp]# tar xvfz samples-1.4.4/two-interfaces.tgz three-interfaces/ three-interfaces/interfaces three-interfaces/routestopped three-interfaces/masq three-interfaces/policy three-interfaces/rules three-interfaces/zones ------- Dario Lesca (d.lesca@ivrea.osra.it)

Version 1.0 of the Quick Start Guide and accompanying sample configurations is available at: http://www.shorewall.net/shorewall_quickstart_guide.htm. Comments and suggestions are most welcome. Thanks, -Tom -- Tom Eastep \ Shorewall - iptables made easy AIM: tmeastep \ http://www.shorewall.net ICQ: #60745924 \ teastep@shorewall.net

mdew:~# tc qdisc add dev imq0 handle 1: root htb default 12 r2q 1 Cannot find device "imq0" mdew:~# lsmod Module Size Used by Not tainted ipt_REDIRECT 728 0 (autoclean) ipt_MARK 728 2 (autoclean) iptable_mangle 2100 1 (autoclean) ipt_REJECT 2712 4 (autoclean) iptable_filter 1672 1 (autoclean)

While I''m in temporary retirement, I''ve decided spend a little time experimenting with new things and making some updates to the web site. The biggest result of this effort to date has been: http://shorewall.sf.net/Shorewall_Squid_Usage.html This outlines how to use Squid as a transparent proxy running on the firewall, in the DMZ or in the local network. In the latter two

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

Hello, I run Shorewall 2.0.3a backport on a debian woody box (with 2.4.18 homemade kernel). When I start shorewall I got the following errors. Oct 30 11:13:12 fwr modprobe: modprobe: Can''t locate module ipt_conntrack Oct 30 11:13:17 fwr modprobe: modprobe: Can''t locate module ipt_pkttype Oct 30 11:13:18 fwr modprobe: modprobe: Can''t locate module ipt_pkttype Oct 30

I''m trying to get Shorewall to use ulogd for logging, but I''m not seeing any logging in either the file I set up for logs, nor in /var/log/messages (where the logs used to be). I''m running a stock Debian 3.0 woody system, with a custom 2.4.21 kernel. I used all the settings as described on shorewall.net when configuring the kernel. ulogd (0.97-1) and shorewall

Hello Tom and others on the list. Tom - you might recall that the other day (night) I had problems with my axip setup (protocol 93) and we made some changes to the policy, zones and interfaces files. You added ''peers and tunl+'' Following that change nothing seemed to work. In fact you wanted to see the shorewall status file, among other things. Well - tonight, I carefully put

Hi, Thanks for your reply . I am attaching the files needed by you herewith. The NAT device is called Pronto gateway which has two interfaces , namely eth0 and eth1. ''eth0'' has an ip address of 203.124.152.66 and eth1 has an ip address of 192.168.1.3 . All the client PCs are in 192.168.1.0 network [behind the NAT, the Pronto gateway] and use 192.168.1.3 as the default

Clients using W2k Sp2 are randomly no longer connecting to my Samba PDC server running 2.2.5 so i thought to upgrading to 2.2.6 but the problem still remains. What can be appened? Just a few days ago all was running very very fine!! THE ERROR IS: THE DOMAIN IS NOT DISPOSABLE AT THE MOMENT! =============================================================== I only have activated Bind9 and DHCP but I

I have a perferctly working shorewall system, with basic configuration (external real IP, one private address internal network with some forwarded services), and log handling with fwlogwatch. My problem is that I can''t find out how to make something like this with shorewall (TCP-connections only): - Allow protocol x connections from IP x.x.x.x without logging - Allow protocol x

Hallo, in CentOS 5 fwlogwatch is available. CentOS 6: I have found nothing. Snort: installation from source? Other idea? Alternative software? OSSEC? Thank you for help in advance Best regards Helmut -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20110905/1c409912/attachment.html>

Hi, I've got a question, mostly out of curiosity, because my Mandrake Linux 9.0 + Samba 2.2.8a is actually working fine. Whenever I (re)start Samba by issuing "service smb start", I get the following output: [root@localhost marco]# service smb start Avvio servizi SMB: [ OK ] Avvio servizi NMB:

Hi, We have 2 offices interconnected with a VPN. This is the policy file in both of the Firewalls: fw loc ACCEPT loc fw ACCEPT #fw net DROP info fw net ACCEPT loc net DROP info loc vpn ACCEPT vpn loc

Hi! Already searched for it and asked in IRC channel but all replies talk about ip_conntrack_irc and ip_nat_irc. I have a rule in 'NEW' section of 'shorewall/rules' to irc: ACCEPT fw net tcp 6667 #IRC and 'lsmod|grep irc' shows: ip_nat_irc 3648 0 ip_nat 22572 8 [...] ip_conntrack_irc

I''m trying to setup Shorewall 2.0.8 with the one-interface settings on my LFS (kernel 2.6.5) system. I''ve read the troubleshooting guide, recompiled my kernel with just about every netfilter/iptables module I could find, but I''m still getting this error: # tail /tmp/trace + prefix=Shorewall:smurfs:DROP: + ''['' 22 -gt 29 '']'' +

On Wed, 21 Jun 2017 14:10:24 +0200 Marco Gaiarin <gaio at sv.lnf.it> wrote: > Mandi! Rowland Penny via samba > In chel di` si favelave... > > > You will probably be better off using a later version of Samba, 4.2 > > is EOL as far as Samba is concerned. You can easily do this by > > going here: http://apt.van-belle.nl/ > > Sorry, i've tried to upgrade