search for: load_helpers_on

...per:RAS }'' entry as well. Shorewall believes my kernel has H323 capabilities: # shorewall show capabilities | grep H323 H323 Helper: Available The HELPERS entries in the /etc/shorewall/shorewall.conf file are: # grep HELPER /etc/shorewall/shorewall.conf AUTOHELPERS=No HELPERS= LOAD_HELPERS_ONLY=No If I try to force the h323 by defining HELPERS in shorewall.conf like so: HELPERS=ftp,h323,irs,netbios-ns,pptp,sip,snmp,tftp Then shorewall check now results in: # shorewall check Checking... Processing /etc/shorewall/params ... Processing /etc/shorewall/shorewall.conf... Loading Mod...

All, I have been using Shorewall successfully for years on many different machines and configurations. However, I just built a new box and wanted to setup shorewall on it. I''m running SuSE Linux Enterprise Server 11 and Shorewall 4.4.8 (latest version as of this e-mail) using the RPM download. I am able to install Shorewall just fine and I''m able to setup everything except

Hi, I was reading document http://shorewall.net/MultiISP.html#idp3634200. Inspired by the document I was trying to establish the following changes: * one additional interface: COMA_IF * COM[A,B,C]_IF interfaces request IP address via DHCP * all non-RFC 1918 destined trafic is NATed from INT_IF to COMA_IF * all non-RFC 1918 destined trafic from GW is routed via COMB_IF by default * non-RFC 1918

...CLAMPMSS=No CLEAR_TC=Yes COMPLETE=No DELETE_THEN_ADD=Yes DETECT_DNAT_IPADDRS=No DISABLE_IPV6=Yes DONT_LOAD= DYNAMIC_BLACKLIST=Yes EXPAND_POLICIES=Yes EXPORTMODULES=Yes FASTACCEPT=No FORWARD_CLEAR_MARK= IMPLICIT_CONTINUE=Yes IPSET_WARNINGS=Yes IP_FORWARDING=On KEEP_RT_TABLES=No LEGACY_FASTSTART=Yes LOAD_HELPERS_ONLY=No MACLIST_TABLE=filter MACLIST_TTL= MANGLE_ENABLED=Yes MAPOLDACTIONS=No MARK_IN_FORWARD_CHAIN=No MODULE_SUFFIX=ko MULTICAST=No MUTEX_TIMEOUT=60 NULL_ROUTE_RFC1918=No OPTIMIZE=0 OPTIMIZE_ACCOUNTING=No REQUIRE_INTERFACE=No RESTORE_DEFAULT_ROUTE=Yes RETAIN_ALIASES=No ROUTE_FILTER=No SAVE_IPSETS=No...

...f the capability was not detected. 4) If an interface named in the INTERFACE column was not defined in tcdevices and if the REDIRECTED column for that entry was non-empty, then compile-time Perl diagnostics were generated and an invalid firewall script was generated. 5) When LOAD_HELPERS_ONLY=No, the ''compile'' command previously left behind a temporary chain in the raw table. 6) Under very rare circumstances involving exclusion in multiple Netfilter tables, optimization level 8 could result in start/restart failure or jumps to the wrong exclusion cha...

...f the capability was not detected. 4) If an interface named in the INTERFACE column was not defined in tcdevices and if the REDIRECTED column for that entry was non-empty, then compile-time Perl diagnostics were generated and an invalid firewall script was generated. 5) When LOAD_HELPERS_ONLY=No, the ''compile'' command previously left behind a temporary chain in the raw table. 6) Under very rare circumstances involving exclusion in multiple Netfilter tables, optimization level 8 could result in start/restart failure or jumps to the wrong exclusion cha...