Jeff <[EMAIL PROTECTED]> wrote:
>
> I would like to have eth4 masq'd out eth0, and eth5 masq'd out eth1.
Masquerading is not a specification of route policy. Rather, it
specifies what happens after routing policy has determined where a
packet will go.
Your IP Masq ruleset does not say "if you see a packet coming in on
eth4, send it to eth0 and masquerade it." Instead, it says "if you see
a packet coming in from eth4 and going out eth0, then masquerade it."
Once you can convince your masq box to route all traffic from eth4 to
eth0, and all traffic from eth5 to eth1, then you will have found your
solution.
> I can specify multiple default routes, out eth0 and eth1 to the ISP0
> and ISP1 routers, and I can give one a higher preference by setting
> one with a metric of 0 and another with a metric of 1.
Route tables only specify target addresses as their parameters. In
other words, the route table doesn't care where the packet came from.
It only determines where the packet will go. Thus, the routing entry
with the lowest metric will be the one chosen, no matter whether the
packet came from eth4 or eth5.
> Despite changing routing about, I cannot get the desired results- eth4
> masq'd out eth0 and eth5 masq'd out eth1.
I imagine so.
I think you might want to investigate the various routing options that
are available within the Linux kernel. Myself, I have no experience
with them, but the way these questions keep coming up, it might just pay
off to learn something about how they work.
--
[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]
