/* HINT: Search archives @ http://www.indyramp.com/masq/ before posting!
/* ALSO: Don't quote this header. It makes you look lame :-) */
Wondering if anyone can explain to me how the ipmasqadm portfw port
forwarding strategy works?
Does it do the plugboard thing and open it's own tcp connection to the
"forward-to" machine/port, and then act as a proxy, or does it just rewrite
the header, pass it along, and then let MASQ on the router box handle the
outbound rewriting for return traffic? This is an interesting question for
me because I'm curious how I can do the following:
_ _ _
/ \/ \/ \
|Internet |
\_/\_/\_/
|
|ETH0 X.Y.Z.1
|ETH0:0 X.Y.Z.2
|
---------------
| Firewall | -------------DMZ-----
--------------- | |
| -------- --------
| | WWW1 | | WWW2 |
Internal -------- --------
Network
Where traffic to X.Y.Z.1:80 goes to WWW1 and traffic to X.Y.Z.2:80 goes to
WWW2. This would allow me to distribute the load to my various domains
across multiple servers, instead of forcing one server (that supports
virtual domains) to handle everything.
I've come to understand that MASQ can only handle interfaces, not aliases;
and so, if all the forwarder is doing is rewriting the header and sending it
along to the right machine, then response packets from WWW2 will appear as
if they've come from X.Y.Z.1, which is not so great.
Thanks,
-Ben
-------------------------------------------------------------
Ben Mitchell It's Never Over Proud to say:
Semio Corp In A Rover
San Mateo, CA '94 D90 - '70 SIIA "I'm the NRA"
_______________________________________________
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.
