Displaying 20 results from an estimated 700 matches similar to: "ulog support in shorewall?"
2001 Jul 13
2
corrupt patch upload
Hi,
after trying to download the newest 2.4.6 patch
(http://www.zip.com.au/~akpm/ext3-2.4-0.9.2-246.gz) I noticed that the
file appears to be corrupt.
gunzip: ext3-2.4-0.9.2-246.gz: unexpected end of file
Tried a few times, on different machines.
( o>
///\
_\V_/_____________________________
[Sam]<mailto:sam@breakfree.com>
http://www.xplo.org/
"finger
2004 Jul 23
4
shorewall 2.0.3a, (ULOG) doesn''t log anything
Dear all:
Im using shorewall 2.0.3a (debian) w/ ULOG. shorewall starts ok, and the
firewall is running, but nothing is printed on the logs.
I try, for example, to do a connection to a port that is opened on the
server but closed by the FW and I get a connection refused. If I stop
the firewall, this port is accesible from the outside.
I think I''ve followed all the steps on
2009 Aug 25
1
[PATCH] A default log level of ULOG is ignored by the shorewall-perl compiler (but not by shorewall-shell)
Hello,
I tried Shorewall for the first time today. I am currently using an up-to-date
installation of Debian Sid, which has shorewall 4.2.10, shorewall-shell 4.2.10
and shorewall-perl 4.2.10.1.
I noticed that even though I had the following /etc/shorewall/policy file,
iptables would still show LOG rules at the end of the INPUT and OUTPUT chains
instead of ULOG rules. (Other logging related rules
2005 Jan 07
5
ULOG weirdness with 2.0.10
I''m noticing some weirdness in my ulog files with version 2.0.10. Here
is a portion of the log:
Jan 7 11:01:37 rancor Shorewall:loc2fw:AllowWOL: IN=eth1 OUT=
MAC=ff:ff:ff:ff:ff:ff:00:0a:95:b2:11:4c:08:00 SRC=192.168.0.100
DST=192.168.0.255 LEN=97 TOS=00 PREC=0x00 TTL=64 ID=44155 CE PROTO=UDP
SPT=631 DPT=631 LEN=77
Jan 7 11:01:39 rancor Shorewall:loc2fw:AllowWOL: IN=eth1 OUT=
2014 Nov 07
7
[Bug 986] New: ulogd fails to build against linux headers >= 3.17.0 due to ULOG target removal
https://bugzilla.netfilter.org/show_bug.cgi?id=986
Bug ID: 986
Summary: ulogd fails to build against linux headers >= 3.17.0
due to ULOG target removal
Product: ulogd
Version: SVN (please provide timestamp)
Hardware: x86_64
OS: Gentoo
Status: NEW
Severity: major
Priority:
2004 Aug 08
1
using ULOG
hi,
if i would like to use ulog (in order to split netfilter messages from
other kernel messages), than i have to set all loglevel to ULOG? and
then is there any way to define diferent loglevel for eg. maclist?
thanks in advance.
yours.
ps. it''s a bit confusing that all loglevel parameter name is LOG_LEVEL
except BLACKLIST_LOGLEVEL:-(
--
Levente
2011 Sep 13
1
[Bug 748] New: Range check for ulog-cprange is wrong
http://bugzilla.netfilter.org/show_bug.cgi?id=748
Summary: Range check for ulog-cprange is wrong
Product: iptables
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P5
Component: iptables
AssignedTo: netfilter-buglog at lists.netfilter.org
ReportedBy:
2008 Jan 10
5
Want to log all ISP traffic to ULOG
I want to use fprobe-ulog (http://fprobe.sourceforge.net/) to generate
NetFlow information about traffic going through my router. The question
is how to get the logging rules added to the appropriate chains (I''m
assuming eth2_in and eth2_out in my case)? I''m using the perl version
of shorewall 4.0.6.
--
Orion Poplawski
Technical Manager 303-415-9701
2001 Jul 17
1
enable fulldata journaling
Hi,
well I've deployed ext3 on two machines already and so far it does its
job excellently at no (for me) noticable performance loss. I hope it
gets incorporated into stock kernels by Linus soon.
Anyways I've been hearing about ext3 supporting full-data journalling
on a per-file basis but couldn't find any detailed info about it. Even
tried grep'ing throught the source. How
2001 Jul 12
1
A few quick questions regarding the journal.
Hi,
I've just recently noticed that the ext3 projects is being actiavely
maintained (again?). And looking at the new pages for 2.4.x it really
made me interested. But I've got a few small questions I'd like to
clarify before I start to use it.
1) Tune2fs and mke2fs talk about a "default journal size" that is
depending on the partition size but don't give
2006 Dec 15
1
catching DNAT''ed packet
Hi.
I have a Server''s network with some servers in it, all with
192.168.1.0/25 ips. There is also a router in that network with ip
192.168.1.1. This router also connected to a client''s network
10.10.0.0/16 with ip 10.10.100.1.
All services on each server are given their virtual address from one of
two virtual networks 192.168.1.128/28 and 192.168.1.144/28.
192.168.1.128/28 is
2014 May 07
1
[Bug 921] New: log, ulog and nflog: command-line parameters are not supported
https://bugzilla.netfilter.org/show_bug.cgi?id=921
Summary: log, ulog and nflog: command-line parameters are not
supported
Product: nftables
Version: unspecified
Platform: x86_64
OS/Version: All
Status: NEW
Severity: normal
Priority: P5
Component: nft
AssignedTo: pablo at
2002 Jan 31
0
[ANNOUNCE] problems with recent ULOG patch and old ulogd
--/aVve/J9H4Wl5yVO
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Hi Everybody!
I had to change the ulog.patch in recent patch-o-matic to use a different
netlink family (it's now 5 instead of 4).
This means, you will have to recompile your ulogd or any other application
in order to make it work.
That's also why I have
2003 Oct 22
2
help seeing DMZ from LOC
I have a three interface network (net,loc,dmz).
The internet interface (eth0) has a static IP.
Windows machine in the local network (eth1) use DHCP to get IPs from
the 192.168.10.0/24 netblock.
The Debian machine in the DMZ (eth2) gets a fixed IP through DHCP in
the 192.168.11.0/24 netblock.
The DHCP server is running on the firewall machine (not ideal, I know,
but that''s the way
2004 Jul 15
3
slight simplification to firewall log_rule_limit code
I think you can change the existing firewall logging code for
log_rule_limit (where you have one case for for LOGRULENUMBERS and
another almost identical case without) down to this slightly shorter
version with no duplication (excerpt):
if [ -n "$LOGRULENUMBERS" ]; then
eval rulenum=\$${chain}_logrules
[ -z "$rulenum" ] && rulenum=1
fi
case
2002 Dec 13
0
ULOG Support now in CVS
Anywhere that a syslog level can appear, you can now specify ULOG (must be
upper case) and logging will occur to the ulog target. You can download
ulogd from http://www.gnumonks.org/projects/ulogd.
Only the ''firewall'' file is required. None of the comments in the other
config files are updated yet but I''m working on it.
-Tom
--
Tom Eastep \ Shorewall - iptables
2003 Jul 29
1
Web Interface to browse ULOG messages real time
Going deeper on last post "[Shorewall-users] logging", I found a very nice
package that handles ULOG messages in a web interface, where you can browse
the events from a MySql database produced by ULOGD. Real time.
The name is: ULOGD-PHP
From the site:
-------------------------------------------
ulogd-php is able to :
show the last hosts that broke packets on your firewall.
show the
2013 Sep 20
0
logging with ULOG and SYSLOG
Hi,
I have a legal requirement to log all connections and I will use ULOG
to log all ACCEPTED conenctions.
However it is so much easier to look at text log file compared to
binary log file. So I would like to log DROPPED/REJECTED packets with
SYSLOG for rule testing/debuging purposes.
Is it possible to use both ULOG for ACCEPTED packets and SYSLOG for
DROPPED packets?
Thank you for your help.
2009 Jul 10
1
[Bug 600] New: ULOG target does not support --log-uid
http://bugzilla.netfilter.org/show_bug.cgi?id=600
Summary: ULOG target does not support --log-uid
Product: iptables
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P1
Component: iptables
AssignedTo: laforge at netfilter.org
ReportedBy: dom at
2007 Jun 29
1
ipp2p traffic not rejected
Hi,
I''m using following rule in /etc/shorewall/rules
REJECT:ULOG:P2P loc net ipp2p:all ipp2p
iptables -L :
Chain loc2net (1 references)
target prot opt source destination
ACCEPT all -- anywhere anywhere state
RELATED,ESTABLISHED
ULOG all -- anywhere anywhere ipp2p
v0.8.2--ipp2p ULOG