search for: addnatrule

Displaying 5 results from an estimated 5 matches for "addnatrule".

Did you mean: add_a_rule
2002 Dec 20
0
Another Beta Patch
...ip addr del $external dev $interface fi - if [ -z "$allints" -o "$allints" = "Yes" \ - -o "$allints" = "yes" ] + if [ -z "$allints" -o "$allints" = "Yes" -o "$allints" = "yes" ] then addnatrule nat_in -d $external -j DNAT --to-destination $internal addnatrule nat_out -s $internal -j SNAT --to-source $external --==========1809029384==========--
2003 Aug 25
2
Mandrake Connection Sharing facility problem.
...;'' '']'' + destination=0.0.0.0/0 + ''['' -n '''' '']'' + destnet=-d 0.0.0.0/0 + ''['' -n 192.168.200.0/255.255.255.0 '']'' + ''['' -n '''' '']'' + addnatrule eth0_masq -s 192.168.200.0/255.255.255.0 -d 0.0.0.0/0 -j MASQUERADE + ensurenatchain eth0_masq + havenatchain eth0_masq + eval test ''"$eth0_masq_nat_exists"'' = Yes ++ test '''' = Yes + createnatchain eth0_masq + run_iptables -t nat -N eth0_masq + iptable...
2004 Feb 10
22
Re: [Shorewall-newbies] specific log-prefix ... patch
Let''s move this to the Shorewall Development list.... On Tuesday 10 February 2004 03:14 pm, xavier wrote: > here is a patch to allow this : > |ACCEPT<10/sec:20>:debug fw lan:$ntp_servers udp 123 - - - - ntp > > a problem with the patch is that now the logprefix is mandatory. > i''m trying to debug it, but i can''t find the flaw. Also, with
2004 Aug 19
4
MASQUERADE problem again...
...;['' -n '''' '']'' ++ separate_list 0.0.0.0/0 ++ local list ++ local part ++ local newlist ++ list=0.0.0.0/0 ++ part=0.0.0.0/0 ++ newlist=0.0.0.0/0 ++ ''['' x0.0.0.0/0 ''!='' x0.0.0.0/0 '']'' ++ echo 0.0.0.0/0 + addnatrule eth0_masq -s 192.168.4.0/24 -d 0.0.0.0/0 -j MASQUERADE + ensurenatchain eth0_masq + havenatchain eth0_masq + eval test ''"$exists_nat_eth0_masq"'' = Yes ++ test '''' = Yes + createnatchain eth0_masq + run_iptables -t nat -N eth0_masq + ''[''...
2003 Mar 23
12
Shorewall 1.4.1
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