Hi Bruno, the InternalNetwork switch is only meant to be used for the decision when to proxy a call. You want to use an authentication policy like FileIPAuth to decide who may use your gatekeeper. http://www.gnugk.org/gnugk-manual-8.html#ss8.2 Regards, Jan Bruno Richard wrote: > Hi all, > > I use two clients to get h323 communications via gk : M100 and EVO (http://evo.caltech.edu/evoGate/). > - M100 could registered on the gk, no pb with it. > - but EVO could not. > > So if I want to use EVO with gk, I have to set the param : "AcceptUnregisteredCalls=1". > For obvious security reasons I want to restrict the IP range that can acces my gk. > I thought that I could restrict it with the param InternalNetwork (proxy is enable on my gk) > However even with the config bellow, I can connect to the gk with an EVO client that has the IP 172.16.7.... > > [Proxy] > Enable=1 > ProxyAlways=1 > InternalNetwork=192.168.0.0/255.255.0.0 > > > I hope I'm clear !! > Thanks in advance. > Bruno > > > > -- Jan Willamowius, jan@xxxxxxxxxxxxxx, http://www.gnugk.org/ ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________________ 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/
