I think this has to do with an age old issue (problem or feature, you decide). Linux (and most other unicies and other OSs in general) will pick the first interface on a subnet to use as the source interface to send the traffic out. I think, this is more akin to what bonding is designed to answer. I question are you wanting to really have the 2nd leg of the teql link be via a different path or were you just doing that to test to see if you were really sending traffic out both interfaces? If you can have a direct cross over cable on both interfaces and you are wanting more aggregate bandwidth take a look at bonding, I think it will serve you better. Disclaimer, I have not worked with teql or bonding my self directly and this is based on what reading I have done, that being more on bonding than teql. Grant. . . . Li, Ji wrote: > Yesterday I posted a question, but I guess too much detail is provided > that no one would bother to read, so I rephrase the question and > hopefully some one may be willing to read. Sorry to spam. > > I am using TEQL on two computers, each with two network interfaces. The > two eth0 are connected directly, and the two eth1 are connected via a > gateway (a linux machine). The problem is that when I send packets > through teql0 to the other machine (ping -I teql0), the packets can't go > through eth1 and all packets go via eth0. But I can send packets via > eth1 directly (ping -I eth1). What's wrong? > > P.S. I put eth1 and teql0 on one computer, and the gateway interface on > the same side into one subnet. I only found TEQL configuration for two > direct links. My routing tables are attached below. > > Thanks a lot, > -Ji _______________________________________________ LARTC mailing list LARTC@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
