Hi, I'd love to see that feature in GnuGk, but GnuGk needs to have control which exact IP is used for each outgoing message. Doing that on a listener on 0.0.0.0 isn't possible on all OS and is implemented differently on those OS that support it. That would be a major change to GnuGk's routing architecture. Adding listeners for new IPs on the fly seems much more doable, but either way we'd need somebody to fund that development. Please contact me off list if you are able to do that. Regards, Jan Mikael Grehn wrote: > Hi Jan and thank you for the answer. > > Wouldn't it be a quite important step to implement a setting that makes it possible for gnugk to bind on 0.0.0.0 for all clustered environments out there (instead of scanning and binding to the ones that is available on the standby node)? > We could add the gnugk as a part of the standby/active node switch, i.e. start it when a node is active but at the same time we would like to avoid adding services in the cluster since it is quite sensitive and would prefer to have a much running at all times on all nodes in the cluster. > > Something you could add in the coming releases? :) > > Best Regards, > Mikael > > -----Ursprungligt meddelande----- > Från: Jan Willamowius [mailto:jan@xxxxxxxxxxxxxx] > Skickat: den 22 april 2013 10:15 > Till: openh323gk-users@xxxxxxxxxxxxxxxxxxxxx > Ämne: Re: Gnugk fail to get signals from a new IP while running? > > Hi Mikael, > > GnuGk indeed listens to individual IPs and not 0.0.0.0. This gives us a more fine grained control over the IP routing, but the downside is that it doesn't automatically listen on IPs that weren't present when GnuGk started. > > One solution would be to re-scan the IPs when we re-load the config, so you could just do a "kill -HUP" whenever you add new IPs, but thats not implemented, yet. > > Regards, > Jan > > > Mikael Grehn wrote: > > Hi! > > > > We use gnugk in a clustered environment where gnugk is running on both sides (all the time) but only one side have the cluster IP where the incoming/outgoing H323 is going. > > If we start gnugk on the running node(with cluste IP) gnugk receives incoming H323 signals without problems. > > > > But if we switch side, the (already running) gnugk on the new cluster node (where we have set the cluster IP after fail-over) does not get any incoming H323 signals?? > > It seems like gnugk does not bind on 0.0.0.0 but only on the IP's that it can find when starting? After restarting gnugk on the running node everything is working again. > > > > Or have I missed a configuration setting? > > > > Best Regards, > > Mikael -- Jan Willamowius, jan@xxxxxxxxxxxxxx, http://www.gnugk.org/ ------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter _______________________________________________________ Posting: mailto:Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_name=openh323gk-users Unsubscribe: http://lists.sourceforge.net/lists/listinfo/openh323gk-users Homepage: http://www.gnugk.org/
