Stefan I have applied your patch with some modification. I have added a new setting called bind. [Main] Bind=xxx.xxx.xxx.xxx This should fix your problem. This will allow you to set the actual IP address seperate from the "home" settings (which is optional). Here is how the logic is suppose to work. The list of IP addresses are automatically generated by GnuGk if you do not set from "home". If you set the home then that is the list GnuGk will use. If there is only one "Home" interface then "bind" is not required and GnuGk will only use the 1 "Home" IP. If there are multiple "Home" IP addresses than then you can instruct GnuGk to "bind" to the IP address specified. If you do not specify a "bind" address then GnuGk will calculate the default IP to use (which is a problem in a multihomed virtual environment). Note: If you are using GnuGk as a border controller (bridging between internal/external networks ie. 1 external, 1+ internal) then you should not use "home" or "bind" and let GnuGk automatically workout internal/external. If you are using GnuGk behind a NAT box then you also should not use "home" or "bind" but instead use "ExternalIP" which creates a seperate virtual routing table in GnuGk . I hope that helps Simon > -----Original Message----- > From: openh323gk-users-bounces@xxxxxxxxxxxxxxxxxxxxx > [mailto:openh323gk-users-bounces@xxxxxxxxxxxxxxxxxxxxx]On Behalf Of > Stefan Anders > Sent: Wednesday, June 25, 2008 4:02 AM > To: openh323gk-users@xxxxxxxxxxxxxxxxxxxxx > Subject: home config option & virtual interfaces > > > Hello, > > we participate in the GDS and are using several gnugk 2.0.7 > with different IPs on one physical machine. Eventually we > want to switch to 2.2.7, but unfortunately this causes problems > with our virtual interfaces. They are indicated in known_bugs.txt > for H.245 sockets, but in our case the focus lies on the > proper LRQ routing, which is rather fragile inside the GDS. > > If gnugk 2.2.7 has to answer or forward a Request, he takes > the sender ip address and looks for a local interface within > the same subnet. If not successful, he falls back to the > interface with the local default route, which is the real > interface of the machine. Now he chooses its ip address as > sender address for the answer or the forwarded request. > > But inside the GDS the correct sender ip address is of > utmost importance, cause it is mentioned in lots of neighbor > tables all around the world, and requests will be eventually > rejected. > > Attached is a patch which changes this default ip address > to the first address given in the Home config option. This > works for us at least for LRQ routing, i can't estimate if > it fixes all the H.245 problems too (or generate new troubles). > Please consider the integration in the gnugk source. > > Regards > Stefan Anders > > -- > German National Research and Education Network > http://www.dfn.de/ > ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________________ 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/
