I was wondering if the new 2.2 routing code has a solution for this AFAIK
as of yet unsolved problem:
I have a machine on a local ethernet, a connected (default)router and
a second machine somewhere else:
Physical
Host A Ethernet with netmask 255.255.255.0 Router B
5.0.0.1 ------------------------------------------ 5.0.0.2 ---\
|
|
The INTERNET
|
Host C |
4.3.2.1 ----------/
Now, host A has an internal alias IP address of: 6.0.0.1
This internal alias is bound to lo or dummy (whatever is convenient),
it is *not* bound to the ethernet.
However, router B and The INTERNET both know that Host A is the one
to route to whenever you want to reach 6.0.0.1.
This means that you already can ping 6.0.0.1 from host C and get a reply.
The tricky part is the outgoing connections from Host A to The INTERNET
and to Host C. What I would like to configure is that whenever a program
(any program) on Host A initiates a TCP connection to The INTERNET it
should use 5.0.0.1 as the source address (this is the default, of course);
but also that Host A uses 6.0.0.1 as the source address instead of
the 5.0.0.1 whenever it is making a connection to any address in the
range 4.3.2.0-255.
As far as I can determine this is not possible without actually going
over the wire (ethernet) and really making sure that 6.0.0.1 is an alias
bound to the ethernet including creating a physical neighbor on the same
ethernet-subnet which to route the 4.3.2.0-255 subnet to using the different
source address.
--
Sincerely, [EMAIL PROTECTED]
Stephen R. van den Berg (AKA BuGless).
Stewardess: "Tonight's menu: chicken in a red sauce, or beef in a brown gravy.
Because we don't stock 100% of each, please have a second choice in mind."
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
