[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] AW: [FW1] NAT
Adolfo, you simply have to route the packets from one interface to the other. Means, you define a static route from one net to the other, and back, with the interface of the firewall as the gateway. Then, you have to have the firewall interface being the default gateway for that subnet, and you'r set. Something like this: In Voyager, add a static route from 192.168.9.x/x Next Hop Type normal Gateway 192.168.15.1 from 192.168.15.x/x Next Hop Type normal Gateway 192.168.9.1 Assign 192.168.9.1 and 192.168.15.1 to each interface Set the default route and subnet mask on your clients No NAT needed here, as you'r doing just routing. Hope that helps, Joerg ------------------------------------------------------------ Joerg Weber, Systemadministration JET Online GmbH Altenkesseler Straße 17 / Geb. B5 66115 Saarbruecken mailto:[email protected] http://www.jet-online.de ------------------------------------------------------------ -----Ursprüngliche Nachricht----- Von: Cadillo, Adolfo [mailto:[email protected]] Gesendet: Donnerstag, 8. März 2001 15:27 An: '[email protected]' Betreff: [FW1] NAT I have a IP 330 appliance and I have 192.168.9.X configured on one interface and 192.168.15.X configured on the other. Do I have to add a nat rule to allow these two subnets to talk to each other or do they talk to each other by default since they are behind the same gateway that is protecting them?? I thought that the external interface was the place where packets were dropped or accepted. Adolfo ============================================================================ ==== To unsubscribe from this mailing list, please see the instructions at http://www.checkpoint.com/services/mailing.html ============================================================================ ==== ================================================================================ To unsubscribe from this mailing list, please see the instructions at http://www.checkpoint.com/services/mailing.html ================================================================================
|