similar to: iptables update hoses shorewall

hi, i create rule such action.AllowPostGrey: ----------------------------------------------- ###################################################################################### #TARGET SOURCE DEST PROTO DEST SOURCE RATE USER/ # PORT PORT(S) LIMIT GROUP ACCEPT $A_IP $PORTAL_IP tcp 10023 ACCEPT

Dear , My current samba versiion is samba-4.4.4 and running on centos 7.2 My current samba have recycle enable . I want to age limit for recycle bin . Please kindly let me know any parameter for recycle bin age limit . Best Regards, Si Thu.

Hi I have recently reconfigured my system to a Bridge based architecture on the basis that I have an ADSL Modem/Router with a Public address on the Wan side and a Private address on the Lan side. I am running a Debian based system kernel 2.6.7 and the Bridging software is installed and working correctly, including startup etc. The problem that I have is in "shorewall start" The

Hi iam running FEDORA, i have installed Source of iptable 1.2.9 with the patch layer7-iptables patch done with out any errors and i applied patch in kernel to the layer 7 patch and i have select the required option by doing make menyconfig done make dep make bzImage make modules make modules_install make install and rebooted with customer kernel when i type iptables -t mangle -A

I have upgraded to trustix 2.1 (kernel 2.4.25-2trfirewall), there is a problem with shorewall (both 1.4.10d and 2.0) and iptables 1.2.9-2tr when I start shorewall I have the following errror: iptables v.1.2.9: Unknown arg ''--icmp-type'' Try ''iptables -h'' or ''iptables --help'' for more information with trustix 2.0 (kernel 2.4.25-2trfirewall)

The version of Shorewall currently in CVS (Shorewall2/ project) has been integrated with iptables-save/iptables-restore. This provides the means to start and restart shorewall very quickly (mine restarts in under a second) in the case where you are not changing your configuration. The release notes are attached. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I''ve built a 1.2.9 iptables RPM that corrects the two iptables-save problems that I know about. It is available at: http://shorewall.net/pub/shorewall/iptables/iptables-1.2.9-95.7.i386.rpm ftp://shorewall.net/pub/shorewall/iptables/iptables-1.2.9-95.7.i386.rpm I''m using this on SuSe 9.1 -- for other distros, YYMV... This RPM works

Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://lists.shorewall.net/pipermail/shorewall-devel/attachments/20041014/45aef157/attachment-0001.bin

http://bugzilla.netfilter.org/show_bug.cgi?id=536 pavlin at icsi.berkeley.edu changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|trivial |blocker Priority|P2 |P1 ------- Comment #1 from pavlin at icsi.berkeley.edu 2008-12-19

Hi, I''ve just recently switched off my (lame) hardware firewall onto an old box running linux 2.4.18, iptables 1.2.6 and shorewall 1.2.9. I''m kinda new to linux firewalling myself but so far Shorewall has taken much work from me. While reading myself into iptables I saw that just recently something called ULOG (userspace logging) has been implemented in newer kernels and

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everybody, this is my first post here, i''ve just syubscribed and i woud like to ask a question. i''m running shorewall latest version with mrtg and rrdtool, with the perl shorewall-stats.pl for reporting. the problem is that the pearl gets the stats by the shorewall show command and it''s human readeable bytes form, so

Dear All, Kindly let me know if there is a version compatibility issue between Shorewall 1.4 and iptables. Last month I received an update that seemed to have upgraded iptables in my Linux box. When I tried to reboot, Shorewall would not start, it would bring up a message complaining of a syntax error. Thank you for your time, Ama

I have a bunch of servers and workstations, all with the Shorewall one-interface setup. On one, which happens to be my test box, I get tons of lines like this: Sep 2 14:23:34 chibba Shorewall:net2all:DROP:IN=eth0 OUT= MAC=00:50:8d:a4:0a:dd:00:04:80:6b:dc:07:08:00 SRC=128.192.1.72 DST=128.192.66.165 LEN=265 TOS=0x00 PREC=0xC0 TTL=60 ID=61540 PROTO=ICMP TYPE=3 CODE=3 [SRC=128.192.66.165

http://shorewall.net/pub/shorewall/Beta ftp://shorewall.net/pub/shorewall/Beta -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net

Hi, I''m trying to add following iptables rules to shorewall: iptables -I INPUT -d 192.168.1.1 iptables -I OUTPUT -s 192.168.1.1 What should I put in my custom action or any ware else? I need these rules for munin accounting. iptables -L INPUT -v -n -x Chain INPUT (policy DROP 5 packets, 260 bytes) pkts bytes target prot opt in out source destination 7175

Hi all, I''m using Shorewall since one year (1.4, then 2.0) I''m trying to migrate a linux firewall from iptables rules to shorewall. The firewall has three zones - net internet - loc1 lan - loc2 second lan I have a lot of rules like this, to SNAT the ip addresses of some computers on loc1 (192.168.16.0/24) when they connect to loc2 (10.0.0.0/8) iptables -v -t nat -I

Hey all- Trying to run sh 1.2.8 and iptables 1.2.5 on my linux 2.4.17 box. I build the kernel from kernel.org sources, and then patched it with iptables 1.2.5 by doing %make pending-patches KERNEL_DIR=/usr/src/linux I let it run and patched these: Welcome to Rusty''s Patch-o-matic! Each patch is a new feature: many have minimal impact, some do not. Almost every one has bugs, so I

Tom, I''m setting up a new firewall using shorewall-2.0.3a. The box was installed with the minimum, almost only the kernel. before installing shorewall, I installed iptables 1.2.9 and iproute2. Then I did a manual ./install.sh from the directory extracted from the tarball. When I issued a shorewall start, I received hundreds of errors like: /usr/share/shorewall/firewall: line 5520:

Hello, I use Shorewall 2.0.16 on my server. I would like to auhtorized some external desktop to connect my network. The desktop''s IP change always, because they use dynamic addresses and they haven''t static IP. So I would like to filter those desktop...With shorewall, I can use an IP to drop, reject...But in my case, I can use it. So I think to use a filter on the MAC address.

Hi !, I have this problem. On a Mandrake 10.0 server with all the updates (Kernel 2.6.3-15mdk, iptables-1.2.9-7mdk and shorewall-2.0.3a-1mdk), one of our internal users have to FTP some files to our external web server. I think we have the correct configuration and rules in shorewall, and have read the http://www.shorewall.net/FTP.html document. Still, our users can''t FTP to the