David A. Ranch <[EMAIL PROTECTED]> wrote:
>
> But, the next issue is, you need to find out what is the status of
> "asymetrical routing" is for Linux and how to set it up.
I think in this case he's got it easy, because asymmetric routing is
difficult to set up on the sender's side, but it's easy to set up on the
receiver side.
Basically, if you have a cable modem and a phone line, you end up with
two interfaces, eth0 and ppp0. You send packets out the ppp0 interface,
and they come in over the eth0 interface. If you think about it, you
don't have to do anything special in order to receive packets. They'll
just show up. And if they happen to come in over eth0 instead of ppp0
where you sent them out, you don't have to care. :)
The main thing your masq box will be concerned about is how to
masquerade outgoing packets. Since you will set your "default" route to
point to the ppp0 interface, you will want to tell the system to
masquerade packets going out that interface. I'm rather sure that
incoming packets coming in over eth0 will be de-masqueraded properly,
because they will be in the proper masq-port range, and will be matched
by the masq table. I don't think the masq box will care that they came
in from a different interface.
You will almost certainly want to set the ppp0 MTU to be the same as the
eth0 MTU (i.e. 1500), but that goes without saying, these days...
Make sure that if you set up strict firewalling, that you make sure you
write your rules to understand that generic incoming traffic comes from
eth0, not ppp0 (which is how a lot of the canned firewall rulesets will
appear).
--
[EMAIL PROTECTED] (Fuzzy Fox) || "Nothing takes the taste out of peanut
sometimes known as David DeSimone || butter quite like unrequited love."
http://www.dallas.net/~fox/ || -- Charlie Brown
_______________________________________________
Masq maillist - [EMAIL PROTECTED]
http://tiffany.indyramp.com/mailman/listinfo/masq
Admin requests can be handled by web (above) or [EMAIL PROTECTED]
