|
||||||||
I think in your rule you have to put in External Port "any" because you don't know the port of the client. ------------------------------------ Jorge Ramírez Herrera ------------------------------------ Administración de Sistemas Área General tecsidel Avda. República Argentina 6, 5a planta 08023 Barcelona Tel: (+34) 93 292 21 10 Fax: (+34) 93 292 28 28 mailto:<mailto:jorge dot ramirez at tecsidel dot es> http://www.tecsidel.es/ -----Mensaje original----- De: Matt Smith [mailto:sysmatt at gmail dot com] Enviado el: viernes, 26 de noviembre de 2004 16:50 Para: m0n0wall at lists dot m0n0 dot ch Asunto: [m0n0wall] Terminal Server & m0n0 Ok, i was asking about connectivity yesterday through NAT, and it appears that I have to set the termservers gateway to be the m0n0wall in order for this to work properly. Ideally I kind of like the idea of having a 2nd firewall that routes to the terminal server (handy for failover) Is there anyways around this issue? here's how it is currently setup Term Server: IP: 192.168.0.31, Nmask: 255.255.255.0, GW: 192.168.0.1 m0n0: Internal ip 192.168.0.252 NAT: IF - PROTO - Ext. Port Range - NAT IP - Int. Port Range - Description WAN - TCP - 3389 - 192.168.0.31 - 3389 - Terminal Server Rule: Proto - Source - Port - Destination - Port - Description TCP - * - 3389 - 192.168.0.31 - 3389 - TermServer *************************************************************** Right now the only other rule I have enabled is the default of: Proto - Source - Port - Destination - Port - Desctiption * - LAN net - * - * - * - Default LAN -> Any --------------------------------------------------------------------- To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch |