similar to: slight simplification to firewall log_rule_limit code

Let''s move this to the Shorewall Development list.... On Tuesday 10 February 2004 03:14 pm, xavier wrote: > here is a patch to allow this : > |ACCEPT<10/sec:20>:debug fw lan:$ntp_servers udp 123 - - - - ntp > > a problem with the patch is that now the logprefix is mandatory. > i''m trying to debug it, but i can''t find the flaw. Also, with

This rule with a long name and logging: AllowInternetPrintingProtocol:debug causes this iptables error: Processing /etc/shorewall/rules... Rule "AllowSSH:info net fw" added. Rule "AllowPing:info net fw" added. Rule "AllowWeb:debug net fw" added. iptables v1.2.9: Maximum prefix length 29 for --log-prefix Try `iptables

I have /bin/ash from rh8 installation and I have following error when I tried to change using ash instead of sh with shorewall-1.4.7: + eval options=$tap0_options + options= + list_search newnotsyn + local e=newnotsyn + [ 1 -gt 1 ] + return 1 + run_user_exit newnotsyn + find_file newnotsyn + [ -n -a -f /newnotsyn ] + echo /etc/shorewall/newnotsyn + local user_exit=/etc/shorewall/newnotsyn + [

>From a diff of my current shorewall firewall script with the new one from the CVS today : $ diff -w /usr/share/shorewall/firewall /usr/src/shorewall/s/firewall [...] 673c910 < for network in $networks; do --- > for networks in $networks; do I don''t think that "for networks in $networks" works well. -- -IAN! Ian! D. Allen Ottawa, Ontario,

I want to use --min-size to copy just large files (and their necessary parent directories), but everything I've tried copies *all* the source directories, and creates them empty on the destination even if they don't have any big files in them. I only want the minimal directory hierarchies that contain the big files. This doesn't work: $ rm -rf /tmp/foo $ rsync -ai --min-size

Hello every body: I have RedHat fedora core 2 machine, using iptables and squid. I am having a lot of problems with peer2peer traffic. (bittorrent, kazaa, etc.) so I have installed ipp2p from rpm. Every thing was ok until I use iptables rules. I get this error. [root@router iptables]# iptables -A INPUT -p tcp -m ipp2p --ipp2p -j DROP iptables: No chain/target/match by that name sames

http://bugzilla.netfilter.org/show_bug.cgi?id=590 Summary: iptables unknown target data Product: iptables Version: CVS (please indicate timestamp) Platform: i386 OS/Version: Ubuntu Status: NEW Severity: normal Priority: P1 Component: iptables AssignedTo: laforge at netfilter.org ReportedBy:

Dear All, After installing Shorewall, on a router with 4 NIC, seems running ok. Next day, when connecting from clients, (MS) we keep getting ip conflict for non-conflicting ip addresses. Any help is appreciated. Detals of Startup: + shift + nolock= + ''['' 1 -gt 1 '']'' + trap ''my_mutex_off; exit 2'' 1 2 3 4 5 6 9 + command=start +

Any updates .. On 3/18/20 18:04, Amit Kumar wrote: > > Hello, > > smbclient cannot create log file when log-basename is specified in > samba-master. > > ?????? -l|--log-basename=logdirectory > ?????????? Base directory name for log/debug files. The extension > ".progname" will > ?????????? be appended (e.g. log.smbclient, log.smbd, etc...). The log >

rsync-2.4.6-2mdk I ran an rsync into a file system that filled up. I got no error message out of rsync - it just stopped and exited sliently. I stuck an fprintf into the receiving code and verified that the proper error was being generated - it just never gets printed by the rsync sending process. I submitted a bug report about it; but, I can't believe that other people haven't had

Any BFD/AFP softwares available for FreeBSD 4.10? Im getting flooded with ssh and ftp attempts.

Hi, I''ve attached a patch which fixes a logging problem with log_rule_limit in custom actions. E.g. this action: ,----[ Whitelist ] | if [ -n "$LEVEL" ]; then | run_iptables -N ${CHAIN}Add | log_rule_limit $LEVEL ${CHAIN}Add WhitelistAdd DROP "$LOG_LIMIT" $TAG | run_iptables -A ${CHAIN}Add -j DROP | run_iptables -N ${CHAIN}Del | log_rule_limit

Hi all, I am having an issue with a multiple ISP setup. I have followed the docs online and I think I have everything setup correctly but I can get the desired traffice to go out my secondary ISP. A quick run down on what I am trying to acomplish. I want to send all sip/iax traffic out one ISP in the net zone and then send all other traffic out my secondary ISP in the dsl zone. Attached is

I almost always use "-u" with rsync so that I don't overwrite remote files that have changed. The only way to get rsync to tell me which remote files are "newer" is to use a double-v (-vv), which produces way more output than I care to see. (In true Unix fashion, I don't care to see what was done successfully; I only want to see what failed.) I've always had to

I have some pictures that I unload from the camera into: dir/tmp and at night I automatically rsync all of dir/ to some remote:dir/ Then days or weeks later I do some local sorting, and I make lots of image moves of the sort where image dir/tmp/bar goes to to dir/category1/bar, possibly linked also into dir/category2/bar. Then rsync runs the next night, notices the "new" image

These two small changes enable 3.0.6 to compile and link on AIX 3.2: diff -r rsync-3.0.6/lib/getaddrinfo.c rsync-3.0.6-new/lib/getaddrinfo.c 298c298 < if (!inet_aton(node, &ip)) { --- > if (!inet_pton(AF_INET, node, &ip)) { diff -r rsync-3.0.6/lib/sysacls.c rsync-3.0.6-new/lib/sysacls.c 1817a1818 > #if defined(ENOTSUP) 1818a1820,1822

Rsync version: rsync-2.5.6-3mdk (Mandrake 9.2) I see from the CVS log that some of the following awkwardness may be fixed (or at least different) in the next public release. I'm looking forward to that. In the interim, here are some problems: --------- Problem 1 - unexpected consequence of replacing / with ** --------- The following exclude works because the explicit slash causes a match

Ian has proposed that we change the way that logging interacts with defined actions. Currently, if logging is specified on the invocation of an action (e.g., "AllowFTP:info all all"), all traffic sent to the AllowFTP chain is logged. In most cases, this isn''t what the user intended and other people have expressed surprise about this behavior in the past. The way I see this

My Linux workstation (Mandrake 10.1 kernel 2.6.8.1) is dual-homed to two ADSL Internet providers. Card eth0 (192.168.9.250) is the default route and leads to an SMC router (192.168.9.254). Card eth1 (192.168.1.250) leads to a Linksys router (192.168.1.1). I''m not doing any NAT or PPPoE in the workstation - the SMC and Linksys handle it all. I know four commands that let you set an IP

What I want is a client-side log file itemized list of *all* the changes that rsync did on the remote machine. Using "--log-file" doesn't show everything. In particular, --log-file says nothing if the remote directory was populated using hard links from a --link-dest source. Any number of remote links and directories can be created, with no mention of any of it in the log file.