Package: shorewall Version: 4.0.15-1 Severity: normal
The system does not forward masqueraded connections, while this is configured in shorewall. After restarting shorewall once, everything does work fine. I have the package insserv installed with dependency based booting and it seems that shorewall depends on procps being started: adding it to /etc/init.d/shorewall: # Required-Start: $network $procps solves the issue. I have 'IP_FORWARDING=Yes' in shorewall.conf and the following entries in /etc/sysctl.conf: net.ipv4.conf.default.rp_filter=1 net.ipv4.conf.all.rp_filter=1 net.ipv4.ip_forward=1 Regards, Jaap Eldering -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages shorewall depends on: ii shorewall-shell 4.0.15-1 Shoreline Firewall, Netfilter conf shorewall recommends no packages. shorewall suggests no packages. -- debconf information: shorewall/upgrade_20_22: shorewall/upgrade_14_20: shorewall/upgrade_to_14: shorewall/warnrfc1918: shorewall/warn_about_klogd_floods: * shorewall/dont_restart: * shorewall/major_release: false -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
