global / nat for outbound connections --- static / access-list (conduit for backward compatibility) for inbound connections
You are correct re: NAT / PAT configuration but again, those are for outbound connections (internal users to internet or to DMZ). Jaime At 06:48 AM 2/21/2002 -0800, kk downing wrote: >Hello, > >For a mahine in a DMZ with a private IP address is it >better to use NAT/PAT or just map it to a public IP >via the static command and then provide a conduit? >Also correct me if I am wrong but isn't the only >difference between NAT and PAT is in that in PAT you >only specify one IP instead of network range? Am I >missing something there? Lastly in order for machines >on my inside network to access machines on the DMZ do >I need to specify a conduit from the publicIP my >inside machines get NAT's to to the public IP my >machine on the DMZ gets NAT'd to? I greatly appreciate >any help. Thank you. > >__________________________________________________ >Do You Yahoo!? >Yahoo! Sports - Coverage of the 2002 Olympic Games >http://sports.yahoo.com >_______________________________________________ >Firewalls mailing list >[EMAIL PROTECTED] >http://lists.gnac.net/mailman/listinfo/firewalls _______________________________________________ Firewalls mailing list [EMAIL PROTECTED] http://lists.gnac.net/mailman/listinfo/firewalls
