> Now I see two possible solutions: > 1. Don't validate Home IPs. > 2. Parse somehow route table to detect IP aliases. > But here I have a few doubts how to be sure that > a given IP is really an alias (is it enough to check > that netmask is 0xffffffff?). I think 1.) makes more sense and gnugk could just issue a warning. That way the user is in control and he still gets a hint why an incorrect config isn't working. My guess would be that there are other situations where we can't detect if an IP is valid or not. So we should just downgrade the check to a warning. - Jan -- Jan Willamowius, jan@xxxxxxxxxxxxxx, http://www.willamowius.de/ ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________________ List: Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Homepage: http://www.gnugk.org/
