- Posts: 438
- Thank you received: 9
Static Nat Requirement
13 years 5 months ago #37186
by Nevins
I'm using the same topology I used to ping from private host to public server (4.4.4.2) in this case. Now I want to be able to ping from private host to private host. Knowing that 192.168.x is private and does not get passed over wan links there is a requirement for some sort of translation to take place. I know static nat will do the job but I'm wondering if it is the ONLY method to get PC0 to ping PC1.
Essentially I'm wondering if I have correctly identified a need for static nat addressing in this case.
Useful Threads
================================
www.firewall.cx/forum/2-basic-concepts/3...e-resource-page.html
Static Nat Requirement was created by Nevins
I'm using the same topology I used to ping from private host to public server (4.4.4.2) in this case. Now I want to be able to ping from private host to private host. Knowing that 192.168.x is private and does not get passed over wan links there is a requirement for some sort of translation to take place. I know static nat will do the job but I'm wondering if it is the ONLY method to get PC0 to ping PC1.
Essentially I'm wondering if I have correctly identified a need for static nat addressing in this case.
Useful Threads
================================
www.firewall.cx/forum/2-basic-concepts/3...e-resource-page.html
Time to create page: 0.121 seconds