01-19-2019 10:34 AM - edited 03-08-2019 05:05 PM
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?
Solved! Go to Solution.
01-19-2019 11:28 AM
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.
01-19-2019 02:10 PM
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
01-19-2019 06:57 PM
01-19-2019 11:28 AM
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.
01-19-2019 02:10 PM
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
01-19-2019 06:57 PM
01-20-2019 03:51 PM
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..
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide