Options
Configuring 5510 ASA with TP-Link and Dynamic IP Address
Hi all,
This is a first time for me I have only worked with static IP addresses before. And, you can say I am not as keen as most of the networking guys/girls in here. But, I am studying a lot and trying to figure it out.
This is for a flat network of 192.168.10.101-200 (workstation scope)
name-server 192.168.10.100
I have assigned the IP Address 192.168.1.1 (Please let me know if this is an error and if it should be .1.254) to the outside interface, and 192.168.10.100 inside interface.
Please let me know what the nat ip address should be. I have been fishing around on the internet for this but I don't seem to understand.
Please ask me any questions if you need anymore info.
Thanks!
This is a first time for me I have only worked with static IP addresses before. And, you can say I am not as keen as most of the networking guys/girls in here. But, I am studying a lot and trying to figure it out.
This is for a flat network of 192.168.10.101-200 (workstation scope)
name-server 192.168.10.100
I have assigned the IP Address 192.168.1.1 (Please let me know if this is an error and if it should be .1.254) to the outside interface, and 192.168.10.100 inside interface.
Please let me know what the nat ip address should be. I have been fishing around on the internet for this but I don't seem to understand.
Please ask me any questions if you need anymore info.
Thanks!
“Our greatest glory is not in never falling, but in rising every time we fall.” Confucius
Comments
-
Options
Edificer
Member Posts: 187 ■■■□□□□□□□
My company's boss wants the added security of NAT by changing the source addresses of packets when it goes through the outside interface.“Our greatest glory is not in never falling, but in rising every time we fall.” Confucius -
Options
SecurityThroughObscurity
Member Posts: 212 ■■■□□□□□□□
In that case you can configure dynamic PAT.
NAT ip address will be the ip address of the outside interface. -
OptionsEdificer
Member Posts: 187 ■■■□□□□□□□
Thanks! Issue has been solved. The NAT command is deprecated in version 9.0(1) had to surf the internet for new ones. Thanks again.“Our greatest glory is not in never falling, but in rising every time we fall.” Confucius