search for: logflag

...ACCEPT net all DROP # info all all REJECT # warn I have an ipod touch on 192.168.10.20. It has Skype for the iphone/ipod on it. when skype is connected a get a lot of messages in the log like this: [2824567.893299] Shorewall:logflags:DROP:IN=eth0 OUT=eth1 SRC=192.168.10.20 DST=66.36.158.200 LEN=64 TOS=0x00 PREC=0x00 TTL=63 ID=44929 DF PROTO=TCP SPT=51608 DPT=443 WINDOW=65535 RES=0x00 SYN FIN URGP=0 [2824568.296145] Shorewall:logflags:DROP:IN=eth0 OUT=eth1 SRC=192.168.10.20 DST=66.36.158.200 LEN=64 TOS=0x00 PREC=0x00 TTL=63 ID=...

...Chain loc2net (1 references) pkts bytes target prot opt in out source destination 45 13229 ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED 11 528 ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 Chain logflags (5 references) pkts bytes target prot opt in out source destination 0 0 LOG all -- * * 0.0.0.0/0 0.0.0.0/0 LOG flags 4 level 6 prefix `Shorewall:logflags:DROP:'' 0 0 DROP all -- * * 0.0.0.0/0 0.0.0.0/0...

...OMMIT *filter :INPUT DROP [0:0] :FORWARD DROP [0:0] :OUTPUT DROP [0:0] :Drop - [0:0] :Reject - [0:0] :all2all - [0:0] :blacklst - [0:0] :dropBcast - [0:0] :dropInvalid - [0:0] :dropNotSyn - [0:0] :dynamic - [0:0] :eth0_fwd - [0:0] :eth0_in - [0:0] :eth0_out - [0:0] :fw2wan - [0:0] :logdrop - [0:0] :logflags - [0:0] :logreject - [0:0] :reject - [0:0] :smurfs - [0:0] :tcpflags - [0:0] :wan2fw - [0:0] -A INPUT -i eth0 -j eth0_in -A INPUT -i lo -j ACCEPT -A INPUT -j Drop -A INPUT -j DROP -A FORWARD -i eth0 -j eth0_fwd -A FORWARD -j Drop -A FORWARD -j DROP -A OUTPUT -o eth0 -j eth0_out -A OUTPUT -o lo -j...

...) pkts bytes target prot opt in out source destination 793 96461 ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED 2 160 ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 Chain logflags (5 references) pkts bytes target prot opt in out source destination 0 0 LOG all -- * * 0.0.0.0/0 0.0.0.0/0 LOG flags 4 level 6 prefix `Shorewall:logflags:DROP:'' 0 0 DROP all -- * *...

...All this is good now? All i see in the iptables rules regarding NFLOG is: -A INPUT -j NFLOG --nflog-prefix "Shorewall:INPUT:REJECT:" -A FORWARD -j NFLOG --nflog-prefix "Shorewall:FORWARD:REJECT:" -A OUTPUT -j NFLOG --nflog-prefix "Shorewall:OUTPUT:REJECT:" -A logflags -j NFLOG --nflog-prefix "Shorewall:logflags:DROP:" -A net-fw -j NFLOG --nflog-prefix "Shorewall:net-fw:DROP:" -A net-vpn -j NFLOG --nflog-prefix "Shorewall:net-vpn:DROP:" -A smurflog -j NFLOG --nflog-prefix "Shorewall:smurfs:DROP:" -A vpn-net -j NFLO...

...0 20 1180 AllowWeb all -- * * 0.0.0.0/0 0.0.0.0/0 20 1180 all2all all -- * * 0.0.0.0/0 0.0.0.0/0 Chain loc2net (1 references) pkts bytes target prot opt in out source destination 0 0 ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED 12 576 ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 Chain logflags (5 references) pkts bytes target prot opt in out source destination 0 0 LOG all -- * * 0.0.0.0/0 0.0.0.0/0 LOG flags 4 level 6 prefix `Shorewall:logflags:DROP:'' 0 0 DROP all -- * * 0.0.0.0/0 0.0.0.0/0 Chain modem2fw (1 references) pkts bytes target prot opt in out source destination 482...

Hello! I am using shorewall shorewall-2.0.11-1 on fedora core2 (iptables-1.2.9-95.7). My box has 2 physical nic´s plus one virt. ipsec interface for a freeswan-vpn connection. A few days ago, portsentry spit out a lot of connections from windows clients (port 135, 445). Ooops. I review my shorewall settings but could not find a mistake. So I took a win-client and established a second

...0.0.0.0/0 0.0.0.0/0 multiport dports 21,22,25,53,80,110,443 1 57 ACCEPT udp -- * * 0.0.0.0/0 0.0.0.0/0 udp dpt:53 0 0 ACCEPT icmp -- * * 0.0.0.0/0 0.0.0.0/0 46 6904 all2all all -- * * 0.0.0.0/0 0.0.0.0/0 Chain logflags (5 references) pkts bytes target prot opt in out source destination 0 0 LOG all -- * * 0.0.0.0/0 0.0.0.0/0 LOG flags 4 level 6 prefix `Shorewall:logflags:DROP:'' 0 0 DROP all -- * * 0.0.0.0/0 0.0.0.0/0 Chain net2...

...0.0.0.0/0 state RELATED,ESTABLISHED > 0 0 ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 > > Chain icmpdef (0 references) > pkts bytes target prot opt in out source destination > > Chain logflags (5 references) > pkts bytes target prot opt in out source destination > 0 0 LOG all -- * * 0.0.0.0/0 0.0.0.0/0 LOG flags 4 level 6 prefix `Shorewall:logflags:DROP:'' > 0 0 DROP all...

I''m having a problem with the Shorewall firewall and CUPS printing interfering with each other. My Linux firewall machine is acting as both a CUPS server and client for all of my tests. Shorewall 2.0.13 CUPS 1.1.22-2 Linux kernel 2.6.9 CUPS was working fine to print to my Epson C84 (network connected via a Netgear PS101 print server using lpd://PS101.IP.address/raw ) until I

...0.0.0.0/0 state NEW tcp flags:!0x16/0x02 0 0 LOG all -- * * 0.0.0.0/0 0.0.0.0/0 LOG flags 0 level 6 prefix `Shorewall:loc2road:ACCEPT:'' 0 0 ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 Chain logflags (5 references) pkts bytes target prot opt in out source destination 0 0 LOG all -- * * 0.0.0.0/0 0.0.0.0/0 LOG flags 4 level 6 prefix `Shorewall:logflags:DROP:'' 0 0 DROP all -- * *...

Good day to all. I don''t like to Post unless I am really stuck. Guess what? Redhat with Shorewall. Been using this for years. I have a new client that we have setup with Redhat and Shorewall. The problem is that his outside address (ETH0 = NET) is dynamic (i.e. DHCP enabled). All the rules work fine when we use a STATIC address on Eth0, so we know the rules, filters, tos etc work fine

...0.0.0.0/0 tcp dpt:445 LOG flags 0 level 6 prefix `Shorewall:loc2net:REJECT:'' 0 0 reject tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:445 0 0 ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 Chain logflags (5 references) pkts bytes target prot opt in out source destination 0 0 LOG all -- * * 0.0.0.0/0 0.0.0.0/0 LOG flags 4 level 7 prefix `Shorewall:logflags:DROP:'' 0 0 DROP all -- * *...

...destination 0 0 LOG all -- * * 0.0.0.0/0 0.0.0.0/0 limit: avg 10/min burst 5 LOG flags 0 level 6 prefix `Shorewall:rfc1918:DROP:'' 0 0 DROP all -- * * 0.0.0.0/0 0.0.0.0/0 Chain logflags (5 references) pkts bytes target prot opt in out source destination 0 0 LOG all -- * * 0.0.0.0/0 0.0.0.0/0 limit: avg 10/min burst 5 LOG flags 6 level 6 prefix `Shorewall:logflags:DROP:'' 0 0 DROP...

Hi, I''m running Slackware 13.37 x86 using Shorewall 4.4.21 with OpenVPN and the VPN options I''m using in Slackware 13.37 will not work in Shorewall, but in Slackware 13.1 using the same Shorewall version and files, the ''interfaces'', ''policy'' and ''zone'', are all I have configured, it was working and this also works in Arch at