Displaying 20 results from an estimated 900 matches similar to: "logging with ULOG and SYSLOG"
2013 Sep 19
0
DNAT from external to a internal device which doesn't have default gateway
I need to access externally (via Internet) one device in internal network
which has no default gateway configured.
As the device doesn''t have default gateway, the response to SYN (ie,
SYN/ACK) don''t come back to Internet.
What I need is a setup to make this connection appears to come from
firewall''s internal IP address instead of the public IP of originating
requester
2013 Sep 20
2
touch complain when shorewall start
hello, while starting shorewall4.5.20 on debian7 I get the following
from touch
touch: cannot touch `/var/lock/subsys/shorewall'': No such file or
directory
The needed file can not be created because the directory subsys is
not present!
If I creat the folder manuallly touch does not complain when
shorewall start! Thus it would be nice if durring start shorewall
could check if the
2013 Sep 16
7
Rsync rules for Shorewall
Hi folks,
I''m having an issue with rsync between my firewall and an internal
box. It seems to be a shorewall issue (or correctly speaking, an
issue with my shorewall config) because if I disable shorewall my
rsync works fine.
And I just can''t find it documented anywhere what I need to do.
I have rules like this :
root@userver:/etc/shorewall# grep -i Rsync rules
2013 Sep 23
3
Custom iptables rules to drop DNS Amplification Attacks
Hi all, I need an help to implement this kind of rules on shorewall:
iptables --insert INPUT -p udp --dport 53 -m u32 --u32 "0x28&0xFFDFDFDF=0x055a5a47 && 0x2c&0xDFDFFFDF=0x53540343 && 0x30&0xDFDFFFFF=0x4f4d0000" -j DROP
This kind of rules need to block a DNS Amplification Attack.
I found this file
2013 Sep 01
2
ICMP rate limit terminates shorewall
I''m using the following rule on 3 different systems running
shorewall-4.5.18 on Gentoo:
ACCEPT all all icmp - - - 10/sec:20
shorewall starts fine on 2 of the systems but on the 3rd it fails to
start with the following error:
iptables-restore: line 119 failed
ERROR: iptables-restore Failed. Input is in
/var/lib/shorewall/.iptables-restore-input
/usr/share/shorewall/lib.common: line 113:
2013 Aug 29
2
Multiple gateways
hello
need a little help
i have 2 NIC router with shorewall
client PCs goes to internet fine with shorewall help.
but i need to reroute traffic for one net via other gateway not ISPs.
Gateway is on LAN NIC.
192.168.1.0/24 LAN
x.x.x.x WAN
router(shorewall) IP 192.168.1.15
i need to reroute traffic for 192.168.2.0/24 network to 192.168.1.1 gateway
I know how to do it via route and iptables, bu just
2013 Aug 29
2
shorewall and snort - recommendation
Dear all,
I''m setting up a new gateway for a small network (under 30 users)Gw will host the following services:shorewalldnsproxy
i''m considering installing snort.can i do so on the same exact box ? is there any security risk of doing so ?
box would have 4 ISPs and two internal interfaces.
Any recommendation about the optimal setup of snort and shorewall (or if you suggest
2013 Sep 08
2
Fwd: Where to put custom rules
Hi All,
I have a custom TC configuration where I''m building the tc hierarchy
manually with the tcstart script. I also need to add custom iptables
rules in the mangle table to classify the packets.
Currently I''m using started to insert the iptables commands, but
that''s way too late in the process.
I tried putting them into the initdone file, but it''s trying to
2013 Sep 06
3
Shorewall OpenVPN, routing back from a LAN
When using shorewall with a road warrior openvpn setup, how can I get the
tun interface to masq through a lan interface?
Example Setup:
Machine A (tun0 10.0.0.1) -----------VPN---------(tun0
10.0.0.2)---------Machine B(10.10.10.1)
When I ping Machine B from Machine B, Machine B is receiving the echo
request, but it doesn''t know the route back to the 10.0.0.0/24, and there
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
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:
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 Mar 17
2
ulog support in shorewall?
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
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
2013 Sep 08
5
shorewall-lite
Hi I''m running on a debian box shorewall-4.5.17.
My main gateway is a router running on openwrt and I want to use the
shorewall-lite packet provided by openwrt. The openwrt''s provided
shorewall-lite packet is 4.5.7.
So my questions would be:
1: Do I need to make some modifications before installing
shorewall-core-4.5.7/shorewall-4.5.7 on my debian box?
2: if I have both
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
2013 Sep 10
6
lsm configuration issues...
Hi,
I use shorewall-4.5.4 + lsm-0.143 and it does not seem to work as expected...
When all providers are up, everything seems fine.
When one goes down, lsm says "link <provider> down event"... and it seems
ok but we then experience some problems such as a few unreachable sites,
DNS problems...
If I remove the downed provider from all confs and restart, everything works again.