What you want to do is enable channel bonding. It's a fairly easy setup (google 'linux bond0') and make sure your switch supports fast etherchannel or some other compatible trunking protocol.<br><br>--Dennis<br>
<br><br><br><div class="gmail_quote">On Mon, May 11, 2009 at 2:34 PM, Jeff Hubbs <span dir="ltr"><<a href="mailto:jeffrey.hubbs@gmail.com">jeffrey.hubbs@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I have a series of Linux servers that, for reasons beyond my control, have only 10/100 Ethernet for connecting to their clients. Because the servers are multi-homed, however, I have the option of connecting them to each other via a 10/100/1000 switch on a private IP range and that's what I would like to do. However, I don't want doing so to make this "backchannel" visible to the client population in an untoward way.<br>
<br>For instance, if one of the servers is a Samba server and Samba listens/talks over both eth0 and eth1, I don't want machines on either eth0 or eth1 see the Samba server twice, i.e., once directly and again "through" the server itself to the other side. I don't want Windows or other Samba clients to freak. <br>
<font color="#888888">
<br>- Jeff<br>
</font><br>_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
<br></blockquote></div><br>