search for: lan2fw

Shorewall 4.3.7 is available for testing. ---------------------------------------------------------------------------- P R O B L E M S C O R R E C T E D I N 4 . 3 . 7 ---------------------------------------------------------------------------- 1) Klemens Rutz reported a problem that affects all Shorewall-perl 4.2 and 4.3 versions. The problem: a) Only occurs when

...produces an invalid iptables rule if any of the following OPTIONS are also specified in the entry: blacklist maclist norfc1918 tcpflags 2) Shorewall-shell generates inversion rules which produce warnings with iptables 1.4.3. Example: iptables -A lan2fw -p 6 --dport 999 -s ! 192.168.20.1 -j ACCEPT with iptables 1.4.3.1 the following information message is produced: Using intrapositioned negation (`--option ! this`) is deprecated in favor of extrapositioned (`! --option this`). We don''t intend to fix this. It'...

...eridian kernel: [618522.262747] Shorewall:phys2vpn:ACCEPT:IN=br0 OUT=br0 PHYSIN=eth0 PHYSOUT=tap0 SRC= 192.168.1.1 DST=239.255.255.250 LEN=429 TOS=0x00 PREC=0x00 TTL=4 ID=0 DF PROTO=UDP SPT=1900 DPT=1900 LEN=409 ping(vpn client->server) Sep 14 23:50:50 veridian kernel: [618753.216549] Shorewall:lan2fw:REJECT:IN=br0 OUT= PHYSIN=tap0 MAC=00:01:29:f5:f0:26:00:ff:09:52:47:a0:08:00 SRC=192.168.1.225 DST= 192.168.1.6 LEN=60 TOS=0x00 PREC=0x00 TTL=128 ID=101 PROTO=ICMP TYPE=8 CODE=0 ID=1 SEQ=3 ping(vpn server->client) Sep 14 23:52:34 veridian kernel: [618857.273217] Shorewall:fw2lan:ACCEPT:IN= OUT=...

This is a minor release of Shorewall. WARNING: This release introduces incompatibilities with prior releases. See http://www.shorewall.net/upgrade_issues.htm. Changes are: a) There is now a new NONE policy specifiable in /etc/shorewall/policy. This policy will cause Shorewall to assume that there will never be any traffic between the source and destination zones. b) Shorewall no longer