4/11/2023 0 Comments Simple port forwarding crackeadoAdding the "after-auto" in the configuration should take it to the very bottom where it would be applied only if no other more specific rules were found. I haven't tested the situation but to me it seems the only thing that might cause this is the fact that you have the default PAT configuration at the very top of your NAT configurations. TCP it gets dropped by the ACL on the outside interface. Same thing happens in the packet tracer, a packet destined for my external interface on that port for UDP is allowed and NAT'd just fine. Port count goes up on line 2 (UDP) but never for line 1. ![]() Nat (OUTSIDE,INSIDE) source static any any destination static interface MY_SERVER service TCP_MY_SERVICE TCP_MY_SERVICEĪccess-list OUTSIDE_IN line 1 extended permit tcp any object MY_SERVER eq 47500Īccess-list OUTSIDE_IN line 2 extended permit udp any object MY_SERVER eq 47500Īccess-list OUTSIDE_IN line 3 extended deny ip any any log Nat (OUTSIDE,INSIDE) source static any any destination static interface MY_SERVER service UDP_MY_SERVICE UDP_MY_SERVICE ![]() It works fine for UDP, but all TCP packets are dropped on the outside interface, even though the configuration for UDP and TCP is basically the same! This is my config: ![]() I've tried setting up some simple port forwarding on my ASA, where I want to forward one port on the external interface for both UDP and TCP to the same port on an internal server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |