/* HINT: Search archives @ http://www.indyramp.com/masq/ before posting! */
Tim Uckun wrote:
> /* HINT: Search archives @ http://www.indyramp.com/masq/ before posting! */
>
>
> Hello all.
>
> I am interesting in applying the bumper patch. Micheal Best says.
>
> "Also your firewall script must be
> set to masq based on the source address and not the destination (or it should
> masq to both your internal and external interfaces)."
>
> Currently I have two IP addresses on the external interface each of which
> port forward to different internal IPs here is my current setup.
>
>
>
> ipchains -F
> ipchains -P forward DENY
> ipchains -A forward -i eth0 -j MASQ
> ipchains -A forward -i eth0:0 -j MASQ
>
> echo "1" > /proc/sys/net/ipv4/ip_forward
>
> ipmasqadm portfw -f
> ipmasqadm portfw -a -P tcp -L $IP1 80 -R 192.168.0.8 80
> ipmasqadm portfw -a -P tcp -L $IP2 80 -R 192.168.0.7 80
> ipmasqadm portfw -a -P tcp -L $IP2 443 -R 192.168.0.7 443
> ipchains -L
> ipmasqadm portfw -l
>
> If I set the forward as
>
> ipchains -A forward -s 192.168.0.0/24 -j MASQ
>
> will it mess me up?
no. that's the right way to do it.
note: the line "ipchains -A forward -i eth0:0 -j MASQ" is meaningless.
eth0:0 is not an interface. it is an "alias" which (since 2.2) is no
different to any other address on an interface. to ipchains, this line
means exactly the same thing as the line before it and so is redundant.
raf
_______________________________________________
Masq maillist - [EMAIL PROTECTED]
Admin requests can be handled at http://www.indyramp.com/masq-list/ -- THIS INCLUDES
UNSUBSCRIBING!
or email to [EMAIL PROTECTED]
PLEASE read the HOWTO and search the archives before posting.
You can start your search at http://www.indyramp.com/masq/
Please keep general linux/unix/pc/internet questions off the list.
