Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
Bill Bogstad wrote: > For example, just because you can send packets to the same machine > from both ports doesn't mean that they will arrive at different ports > on the destination machine. I figured that would be the next challenge... > 2. Don't depend on automatic ARP to do IP to Ethernet addressing. > Instead force an entry into the ARP table on both sides to send to > either the Ethernet broadcast address (or possibly a multicast > address) when sending to the IP destination address. > > The above is still dependent on a way to round-robin packets across > multiple physical ports. What if you bond interfaces on both ends of the link, so you end up with a 10 Gbps virtual interface composed of 10 1 Gbps links that use normal IP/ARP to establish the individual links? Your round-robin logic would need to be embedded in the client-side bonding driver. Not a good general solution, but might work when you need to link a specific client machine to a specific server. -Tom -- Tom Metro Venture Logic, Newton, MA, USA "Enterprise solutions through open source." Professional Profile: http://tmetro.venturelogic.com/
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |