You could try this:
http://www.cyberciti.biz/tips/linux-bond-or-team-multiple-network-interface…
(regarding the network aliases)
Cheers
Marius
-----Original Message-----
From: users-bounces(a)lists.kamailio.org on behalf of Laszlo
Sent: Mon 11/30/2009 7:02 AM
To: users(a)lists.kamailio.org
Subject: Re: [Kamailio-Users] Binding to multiple IP addresses on the sameinterface.
Hi,
2009/11/29 Geoffrey Mina <geoffreymina(a)gmail.com>
Sorry to have a conversation with myself here :)
I just tried removing both my "listen" directives and the server
successfully bound to all my IP on all interfaces. There was one
downside though. Within a few minutes of coming up I received these:
Nov 29 15:14:16 atl-sipgateway1 /usr/local/sbin/kamailio[28285]:
NOTICE:lcr:gw_set_state: trunk "208.93.XX.XX:5060" from group: <4> is
OFFLINE!
Nov 29 15:14:16 atl-sipgateway1 /usr/local/sbin/kamailio[28285]:
NOTICE:lcr:gw_set_state: trunk "75.150.XX.XX:5060" from group: <99> is
OFFLINE!
Nov 29 15:14:16 atl-sipgateway1 /usr/local/sbin/kamailio[28285]:
NOTICE:lcr:gw_set_state: trunk "209.249.XX.XX:5060" from group: <4> is
OFFLINE!
Nov 29 15:14:16 atl-sipgateway1 /usr/local/sbin/kamailio[28285]:
NOTICE:lcr:gw_set_state: trunk "216.82.XX.XX:5060" from group: <1> is
OFFLINE!
Nov 29 15:14:16 atl-sipgateway1 /usr/local/sbin/kamailio[28285]:
NOTICE:lcr:gw_set_state: trunk "216.82.XX.XX:5060" from group: <3> is
OFFLINE!
Nov 29 15:14:16 atl-sipgateway1 /usr/local/sbin/kamailio[28285]:
NOTICE:lcr:gw_set_state: trunk "216.82.XX.XX:5060" from group: <5> is
OFFLINE!
Nov 29 15:14:16 atl-sipgateway1 /usr/local/sbin/kamailio[28285]:
NOTICE:lcr:gw_set_state: trunk "216.82.XX.XX:5060" from group: <1> is
OFFLINE!
Nov 29 15:14:16 atl-sipgateway1 /usr/local/sbin/kamailio[28285]:
NOTICE:lcr:gw_set_state: trunk "216.82.XX.XX:5060" from group: <3> is
OFFLINE!
Nov 29 15:14:16 atl-sipgateway1 /usr/local/sbin/kamailio[28285]:
NOTICE:lcr:gw_set_state: trunk "216.82.XX.XX:5060" from group: <5> is
OFFLINE!
I have "ping" set to 1 on all my LCR gateways... I was forced to go
back to the listen=eth0:5060 directive to correct the problem.
Anyone have any ideas?
Are you sure the lcr gateways are accessible through both eth0 and eth0:1?
-Laszlo