Displaying 2 results from an estimated 2 matches for "allowoutupnp".
2005 May 31
11
More Tests for 2.4.0-RC2 - strange behaviour
...MOVE''
+ read first rest
+ cut -d# -f1
+ grep -v ''^[[:space:]]*$''
+ echo ''Pre-processing Actions...''
Pre-processing Actions...
+ process_actions1
+ ACTIONS=''dropBcast allowBcast dropNonSyn dropNotSyn rejNotSyn dropInvalid allowInvalid allowinUPnP allowoutUPnP forwardUPnP''
+ USEDACTIONS=
+ strip_file actions
+ local fname
+ ''['' 1 = 1 '']''
++ find_file actions
++ local saveifs= directory
++ case $1 in
++ ''['' -n '''' -a -f /actions '']''
++ saveifs=''
...
2005 May 02
1
Shorewall 2.2.4
...prerouting_chain_name = UPnP
forward_chain_name = forwardUPnP
Shorewall Configuration:
In /etc/shorewall/interfaces, you need the ''upnp'' option on your
external interface.
If your fw->loc policy is not ACCEPT then you need this rule:
allowoutUPnP fw loc
Note: To use ''allowoutUPnP'', your iptables and kernel must
support the ''owner match'' feature (see the output of "shorewall
check").
If your loc->fw policy is not ACCEPT then you need this rule:
allowinUPnP...