hello,
i have almost the same problem, but the setup a little bit more clear.
i have two pcs: PC1 and PC2; each has 2 net interfaces; pcs are interconnected
by two crossover ethernet twisted pairs;
cabling and net cards r ok and working.
10.0.1.0/24
+----------------------------------+
eth1 | 10.0.1.1 eth1 | 10.0.1.2
+-----+-----+ +-----+------+
| PC1 | | PC2 |
| | | |
+-----+-----+ +-----+------+
eth0 | 10.0.2.1 eth0 | 10.0.2.2
+----------------------------------+
10.0.2.0/24
i need to use PC1 as a traffic generator for PC2 (to stresstest it).
so what i need is that traffic goes:
10.0.1.1 -> 10.0.1.2 -> 10.0.2.2 -> 10.0.2.1
e.g. i want to have traffic sending application send it thru eth0/10.0.1.1
and traffic receiver listen at eth1/10.0.2.1
for now all the traffic gets routed locally, i.e. does not leave the PC1
i was expecting the problem, but thought it's possible to overcome it but
playing with routing table entries. can u pls advise on this problem or point
to the direction to study ?
wbr,
Denis.
--
("\''/").__..-''"`-. . denis.karpov@necsom.com
`9_ 9 ) `-. ( ).`-._.`) Necsom Oy
(_Y_.)' ._ ) `._`. " -.-' +358 (0)40 502 0931
_..`-'_..-_/ /-'_.'
(l)-'' ((i).' ((!.'
*** Lottery: A tax on people who are bad at math. ***
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
