netdev
[Top] [All Lists]

Hairy routing question.

To: "netdev@xxxxxxxxxxx" <netdev@xxxxxxxxxxx>
Subject: Hairy routing question.
From: Ben Greear <greearb@xxxxxxxxxxxxxxx>
Date: Mon, 27 Mar 2000 18:50:55 -0700
Cc: Wallace Davis <wallace@xxxxxxxxxxxxxxx>
Organization: Candela Technologies
Sender: owner-netdev@xxxxxxxxxxx
As usual, I seem to be trying to do something that is inherently
not how things work.  But, if you have any ideas, I'd love to hear
them :)

Are there any linux-related mailing lists where this is a more appropriate
question?


Basically, I want a single PC to look like a bunch of PCs.

So, I might have:

                          Ether
--------                    S         ---------
Client -eth0  172.20.20.3   W         | ServerPC
PC     -eth1  172.20.20.4   I    eth0-| 172.20.20.1
       -eth2  172.20.20.5   T         |_________
--------                    C
                            H


Now, I would like to be able to have eth0 have one IP address
(no virtual interfaces, at least in one configuration), and
be able to route packets over a specific eth interface on the 
Client PC.  Assume that a plain old ethernet switch sits between them.

So, can this be done with something like source-routing?  The
ServerPC can just send out it's pkts on eth0, so it's pretty simple, but
what about the Client PC?  Can I somehow tell the kernel that if
the packet is from a certain IP, then it is to send it out a certain
ethernet port?

If that's possible, can I make sure that the ARP fromm ServerPC
is answered correctly so that the pkt comes to the right ClientPC
ethernet device (and right port on the switch)?

Thanks,
Ben


-- 
Ben Greear (greearb@xxxxxxxxxxxxxxx)  http://scry.wanfear.com/~greear 
Author of ScryMUD:  scry.wanfear.com 4444        (Released under GPL)
http://scry.wanfear.com

<Prev in Thread] Current Thread [Next in Thread>