Bueno esto es un monologo mas que una lista de ayuda entre usuarios.He conseguido resolver el problema, por si a alguien le sirve de algo el fallo estaba en la configuración del gnugk en el que hay que poner como red 0.0.0.0/0.0.0.0 ya que el cortafuegos es transparente, y hay que decirle que esta conectado a todo internet (yo pensaba que al entrar los clientes por el cortafuegos se les remapeaba la dirección a la de la red interna (192.168.1.1) pero encontré por hay que no. Además de la lista de smoothwall me mandaros la siguiente relación de puertos
Ok from the website I found this
http://www.gnomemeeting.org/index.php?rub=3&pos=0&faqpage=x266.html
Most of them will require that you disable H.245 Tunneling and Fast
Start in the "H.323 Advanced Settings" section of GnomeMeeting.
Here is the list of ports that you need to allow and forward to your
internal computer:
*
TCP port 1720, that port can be changed if you modify the
"/apps/gnomemeeting/ports/listen_port" key using gconf-editor,
*
TCP port range [30000-30010], that range of ports can be changed
if you modify the "/apps/gnomemeeting/ports/tcp_port_range" key using
gconf-editor, if you and the remote H.323 software calling you are both
using H.245 Tunneling, then you don't need to allow and forward this
range of ports. Netmeeting doesn't support H.245 Tunneling, so you
always need to allow and forward this range of ports if you plan to call
or be called by Netmeeting clients.
*
UDP port range [5000-5007], that range of ports can be changed if
you modify the "/apps/gnomemeeting/ports/rtp_port_range" key using
gconf-editor. This port range is used for the RTP and RTCP channels for
audio and video transmission/reception. This port range is mandatory.
*
UDP port range [5010-5013], that range of ports can be changed if
you modify the "/apps/gnomemeeting/ports/udp_port_range" key using
gconf-editor. This port range is used when registering to a gatekeeper.
You don't need to allow and forward those ports if you don't plan to
register to a gatekeeper.
Albricias.