12-03-2019 12:37 PM
I have some devices (RFID Readers) on their own subnet inside my private network that need to be able communicate with an outside company on a specific UDP port and another specific TCP port. I am trying to configure this on my firewall usinf ASDM.
I have created ACL’s that I think are correct for allowing the ports to communicate on the subnet.
Using ASDM, I have tried to create a Dynamic NAT using a pool of addresses, which didn’t work. So, I tried making a PAT which didn’t work.
I’m used to making Static NATs.
I’m getting confused because I want to use a handful of addresses on a particular subnet.
Solved! Go to Solution.
12-03-2019 02:04 PM
Hello
Are you already using NAT on the firewall(s)
Is this a single ASA or dual ASA HA
Running single or multiple contexts in routed or transparent mode?
Could you post
-interface names (inside/outside)
- internal external addressing/port numbers
or the running configuration if applicable ?
12-03-2019 01:47 PM
Hello,
PAT, in theory, should work, as it translates all ports. Provided of course that you are allowing these ports back into your firewall.
Can you post the running config of your ASA and indicate which UDP and TCP port are required ?
12-03-2019 02:04 PM
Hello
Are you already using NAT on the firewall(s)
Is this a single ASA or dual ASA HA
Running single or multiple contexts in routed or transparent mode?
Could you post
-interface names (inside/outside)
- internal external addressing/port numbers
or the running configuration if applicable ?
12-04-2019 05:45 AM
Yes, we already have a NAT to the outside world.
We have dual ASA HA in routed mode.
Let me see about supplying the information for the other questions.
12-06-2019 05:53 AM
Your questions lead me to see that I needed and ACL for the reverse direction. Thanks!
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