> And everything has been working fine. > > Now I want to add an IPSEC tunnel on my ISDN link between 192.168.3.1 > and 192.168.3.2. The problem is that both gatekeepers (in routed & proxy > mode) send packets to each other with their IP address on the ISDN line > (3.1 and 3.2 respectively). The result is that these packets cannot go > through the IPSEC tunnel (looking only at the subnets 192.168.0.0 and > a.b.c.0) and they usually get blocked preventing the communication. This is off-topic. Better change your IPSec config instead the gatekeeper config. Take Linux native IPSec instead of FreesWAN. http://www.ipsec-howto.org, 1st example. You can use the backport for kernel 2.4 if you don want to switch to 2.6 greetings, Steffen -- Steffen Pfendtner <steffen@wh-netz.de> GPG Key fingerprint = DF91 11BB 498F 573B 8002 6E0B 3AE3 FF88 EADD B3BC ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ List: Openh323gk-users@lists.sourceforge.net Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Homepage: http://www.gnugk.org/
