Dear All, the problem is now solved using a brute-force approach. I added to /etc/rc.local route add -net default gw ip.of.our.gw eth0 route add -host ip.of.parent.gatekeeper gw ip.of.our.gw eth1 #this is essential route add -host ip.of.external.mcu1 gw ip.of.our.gw eth1 #this is probably overkill but does no harm route add -host ip.of.external.mcu2 gw ip.of.our.gw eth1 #this is probably overkill but does no harm route add -host ip.of.mail.server gw ip.of.our.gw eth0 #this is for dmz-to-dmz ... route add -host ip.of.internal.gatekeeper gw ip.of.our.gw eth1 #this is for external-internal gatkeeper comunication The "Home=" clause in /etc/gatekeeper.ini was not sufficient to make GnuGK run as intended, even with these modifications. Adding also the "Bind=" clause made everything work fine again. Given the low level of the solution, the problem may be related to specific hardware "features". The host is a Dell PowerEdge 1900. Many thanks to Jan for the support Alessandro _______________________________________________________ Posting: mailto:gnugk-users@xxxxxxxxxxxxxxx Archive: https://lists.gnugk.org/pipermail/gnugk-users/ Unsubscribe: https://lists.gnugk.org/lists/listinfo/gnugk-users Homepage: https://www.gnugk.org/
