<HTML >
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
</HEAD>
<BODY lang=EN-US link=blue vlink=blue>
<DIV>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>I don’t see how bonding would do
what he wants. He wants to separate traffic – not combine it.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>What we do for separate traffic (we do it
for a backup LAN on GigE network while primary is on 10/100) is simply assign
the IPs to a different <hostname>b instead of just <hostname>. The
only traffic that can find other hosts on the backup LAN have to look for it by
that secondary name with the “b” appended. <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>For example: hostname = winsuck then the secondary
IP would only be known by winsuckb. A configuration for Samba expecting shares
from winsuck wouldn’t see them from winsuckb even if they were there because
it wouldn’t be looking for anything at that name.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'>
ale-bounces@ale.org [mailto:ale-bounces@ale.org] <b><span style='font-weight:
bold'>On Behalf Of </span></b>Dennis Ruzeski<br>
<b><span style='font-weight:bold'>Sent:</span></b> Monday, May 11, 2009 2:52 PM<br>
<b><span style='font-weight:bold'>To:</span></b> <st1:PersonName w:st="on">Atlanta
Linux Enthusiasts - Yes! We run Linux!</st1:PersonName><br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [ale] Multi-homed
server networking</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>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>
<o:p></o:p></span></font></p>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>On Mon, May 11, 2009 at 2:34 PM, Jeff Hubbs <<a
href="mailto:jeffrey.hubbs@gmail.com">jeffrey.hubbs@gmail.com</a>> wrote:<o:p></o:p></span></font></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>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"><span style='color:#888888'><br>
- Jeff<br>
</span></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><o:p></o:p></span></font></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
</DIV>
<DIV> </DIV>
<DIV>
<FONT FACE="Arial" COLOR="green" SIZE="1"><EM>Please consider our environment before printing this e-mail or attachments.</EM></FONT>
</DIV>
<DIV STYLE="FONT-SIZE: 9pt; FONT-FAMILY: Courier New">
<FONT FACE="Arial" SIZE="2">----------------------------------<BR>CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you.<BR>----------------------------------<BR></FONT>
</DIV></BODY></HTML>