Scott,

How does this work exactly? I ask because when I was running sipx under 
OpenVZ using venet interfaces, sipx was completely non-workable because 
there was venet0 and venet0:0. The only way I could fix it was to switch 
to bridging so that I could get an actual eth0 interface in the guest.

With bonding, eth0 and eth1 would still be present but not configured 
with an address, and bond0 would be the actual IP'd interface. Sounds 
like this would confuse the software as well.

-- Robert


On 4/25/2010 5:49 AM, Scott Lawrence wrote:
> On Sun, 2010-04-25 at 03:22 +0100, Hiral Patel wrote:
>    
>> We would like to know if using port bonding on CentOS to provide
>> redundant network interfaces would work with sipXecs or if any one has
>> tried this?
>>      
> Yes, it works fine.
>
>
> _______________________________________________
> sipx-users mailing list [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-users
> Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
> sipXecs IP PBX -- http://www.sipfoundry.org/
>
>    

_______________________________________________
sipx-users mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to