- Posts: 1
- Thank you received: 0
Static NAT explanation, confusion with an explanation
- blueeyedguy_moi
- Topic Author
- Offline
- New Member
Less
More
15 years 7 months ago #30343
by blueeyedguy_moi
Hello all,
I am reading through the Networking explanation and am at the point, where Static Nat is explained.
There at "Static Network Address Translation (Part 2)" I got confused. In the example with the diagram, there is a Static Nat Mapping.
Private IP 192.168.0.3 maps to 203.31.220.135
this is so far clear. But where I get confused is, that the Public IP of the Router is 203.31.220.134. I assume that in the example there should be also a public IP for 203.31.220.135 in the diagram? Would I be correct with my assumption or did I get something wrong ?
Please help
Thank you
Hello all,
I am reading through the Networking explanation and am at the point, where Static Nat is explained.
There at "Static Network Address Translation (Part 2)" I got confused. In the example with the diagram, there is a Static Nat Mapping.
Private IP 192.168.0.3 maps to 203.31.220.135
this is so far clear. But where I get confused is, that the Public IP of the Router is 203.31.220.134. I assume that in the example there should be also a public IP for 203.31.220.135 in the diagram? Would I be correct with my assumption or did I get something wrong ?
Please help
Thank you
15 years 7 months ago #30351
by S0lo
Studying CCNP...
Ammar Muqaddas
Forum Moderator
www.firewall.cx
Replied by S0lo on topic Re: Static NAT explanation, confusion with an explanation
Hello blueeyedguy_moi
Your question is understood. NO, there is really no problem with the diagram. The static mapped IP (203.31.220.135) does not have to be the same as the IP of the BRI0 interface of the router. The mapped IP can be any IP as long as the ISP/Internet routers can route it back to our router.
Your question is understood. NO, there is really no problem with the diagram. The static mapped IP (203.31.220.135) does not have to be the same as the IP of the BRI0 interface of the router. The mapped IP can be any IP as long as the ISP/Internet routers can route it back to our router.
Studying CCNP...
Ammar Muqaddas
Forum Moderator
www.firewall.cx
15 years 7 months ago #30385
by KiLLaBeE
Replied by KiLLaBeE on topic Re: Static NAT explanation, confusion with an explanation
Do you need to also assign the second IP address to the router's public interface or is this not needed?
15 years 7 months ago #30394
by Smurf
Wayne Murphy
Firewall.cx Team Member
www.firewall.cx
Now working for a Security Company called Sec-1 Ltd in the UK, for any
Penetration Testing work visit www.sec-1.com or PM me for details.
Replied by Smurf on topic Re: Static NAT explanation, confusion with an explanation
It is not needed as long as the traffic is sent through to the router from the ISP.
If you think about it from the point of view from getting a /29 address space, you get 6 valid address, one to the ISP Router. This gives you 5 addresses, one will be assigned your router and if you have setup StaticNat's for the other addresses, then the router will respond to traffic for these addresses.
If you think about it from the point of view from getting a /29 address space, you get 6 valid address, one to the ISP Router. This gives you 5 addresses, one will be assigned your router and if you have setup StaticNat's for the other addresses, then the router will respond to traffic for these addresses.
Wayne Murphy
Firewall.cx Team Member
www.firewall.cx
Now working for a Security Company called Sec-1 Ltd in the UK, for any
Penetration Testing work visit www.sec-1.com or PM me for details.
Time to create page: 0.139 seconds