cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1243
Views
15
Helpful
4
Replies

NAT Doubts

eduangelo
Level 1
Level 1

Hello guys,

I configured the internet output interface with the ip obtained through DHCP.

Now I want to configure static NAT to allow external access to the HTTP server.

But as the external address is the address obtained through DHCP.

There will be times when NAT will fail. Is there a way to resolve this situation?

3 Accepted Solutions

Accepted Solutions

Alan Ng'ethe
Level 3
Level 3

Have you tried to use dynamic dns?

 

External clients coming in would reach out to the dns name of the web server, which would in turn be registered dynamically by the device each time it changes its ip address. I have not used this in practice and have no clue whether its free, but think its worth having a look at.

Remember to rate helpful posts and/or mark as a solution if your issue is resolved.

View solution in original post

Reza Sharifi
Hall of Fame
Hall of Fame

Hi,

That is not an uncommon setup for a small network.  The only time that NAT can fail is if yours or the provider's interface go down or if you switch to a different provider, at which time you would have to switch IP anyway. 

 

HTH

View solution in original post

Francesco Molino
VIP Alumni
VIP Alumni
Hi

You can do a nat for port forwarding without setting up an IP but setting it up with your interface. Then you can configure DDNS on your router to ensure you will always access your web server using this ddns fqdn.

Thanks
Francesco
PS: Please don't forget to rate and select as validated answer if this answered your question

View solution in original post

4 Replies 4

Alan Ng'ethe
Level 3
Level 3

Have you tried to use dynamic dns?

 

External clients coming in would reach out to the dns name of the web server, which would in turn be registered dynamically by the device each time it changes its ip address. I have not used this in practice and have no clue whether its free, but think its worth having a look at.

Remember to rate helpful posts and/or mark as a solution if your issue is resolved.

Reza Sharifi
Hall of Fame
Hall of Fame

Hi,

That is not an uncommon setup for a small network.  The only time that NAT can fail is if yours or the provider's interface go down or if you switch to a different provider, at which time you would have to switch IP anyway. 

 

HTH

Francesco Molino
VIP Alumni
VIP Alumni
Hi

You can do a nat for port forwarding without setting up an IP but setting it up with your interface. Then you can configure DDNS on your router to ensure you will always access your web server using this ddns fqdn.

Thanks
Francesco
PS: Please don't forget to rate and select as validated answer if this answered your question

Hello

I agree with @Francesco Molino for nat internally to outside this can be accomplish by specifying the wan facing interface instead of any ip address for translation, but the problem will occur if your isp allocates another public ip address for your rtr then any external customer connecting to this internal web server will still try connect via the web servers FQDN so this need to be updated every time your wan rtrs ip address changes. -- DDNS is the way to go.

 

As for the NAT configuration - see example below:

access-list 1 permit 192.168.23.0 0.0.0.255 <  - internal lan subnet
ip nat inside source list 1 interface FastEthernet0/0 overload  <--dynamic nat for internal users
ip nat inside source static tcp 192.168.23.3 80 interface FastEthernet0/0 80  <  PAT for internal Web server http
ip route 0.0.0.0 0.0.0.0 <wan interface> dhcp/dialer etc..


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul