This reminded me of a recent issue doing just what you are asking about.  I had an issue with sending traffic out an aliased interface on a bonded interface a few weeks ago. I needed certain traffic to look like it was from the aliased interfaces IP so the ACL on the receiving side would allow posts.  But ALL traffic was still looking like it came from the real interface&#39;s IP address.<div>
and this caused the ACL to deny it.  I solved it using  iptables.</div><div><br></div><div><br></div><div>-rick<br><div><br><br><div class="gmail_quote">On Sun, Sep 5, 2010 at 12:08 PM, Benjamin Donnachie <span dir="ltr">&lt;<a href="mailto:benjamin@py-soft.co.uk">benjamin@py-soft.co.uk</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">On 5 Sep 2010, at 18:35, Robert Arkiletian &lt;<a href="mailto:robark@gmail.com">robark@gmail.com</a>&gt; wrote:<br>

<br>
&gt;&gt; Has anyone successfully created a bonded interface (bond0) with say<br>
&gt;&gt; two nics AND also then aliased that interface to get bond0 and bond0:1<br>
&gt;&gt; (for an alias ip)<br>
&gt;&gt;<br>
&gt;&gt; I just want to know if it&#39;s possible and reliable<br>
</div><div class="im">&gt; Oh I forgot to mention I would be using link aggregation mode 4,<br>
&gt; 802.3ad bonding.<br>
<br>
</div>Possible and very reliable, at least with Intel quad NICs (can&#39;t<br>
remember model) and Procurve 2900 switches in my last job.<br>
<br>
Ben<br>
<div><div></div><div class="h5">_______________________________________________<br>
CentOS mailing list<br>
<a href="mailto:CentOS@centos.org">CentOS@centos.org</a><br>
<a href="http://lists.centos.org/mailman/listinfo/centos" target="_blank">http://lists.centos.org/mailman/listinfo/centos</a><br>
</div></div></blockquote></div><br></div></div>