Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Community Member

Traffic inspection & forwarding

Not entirely sure how to approach this.

We have a need to direct traffic from the internet to a single public IP to different destinations internally solely based on the port (and more securely the type of traffic).

Can the ASA (5510 (v. 7.2(2)) accomplish this?

For example:

incoming TCP 25 traffic to public IP 21.21.52.12 gets directed to a SPAM filter with an internal IP of 192.168.66.1 while traffic to the same public IP on port TCP 80 TCP 443 and TCP 1352 is directed to a server with an internal IP of 192.168.45.5.

1 ACCEPTED SOLUTION

Accepted Solutions
Green

Re: Traffic inspection & forwarding

static (inside,outside) tcp 21.21.52.12 25 192.168.66.1 25 netmask 255.255.255.255

static (inside,outside) tcp 21.21.52.12 80 192.168.45.5 25 netmask 255.255.255.255

static (inside,outside) tcp 21.21.52.12 443 192.168.45.5 443 netmask 255.255.255.255

static (inside,outside) tcp 21.21.52.12 1352 192.168.45.5 1352 netmask 255.255.255.255

2 REPLIES
Green

Re: Traffic inspection & forwarding

static (inside,outside) tcp 21.21.52.12 25 192.168.66.1 25 netmask 255.255.255.255

static (inside,outside) tcp 21.21.52.12 80 192.168.45.5 25 netmask 255.255.255.255

static (inside,outside) tcp 21.21.52.12 443 192.168.45.5 443 netmask 255.255.255.255

static (inside,outside) tcp 21.21.52.12 1352 192.168.45.5 1352 netmask 255.255.255.255

Community Member

Re: Traffic inspection & forwarding

Thanks!! I should have known that and something tells me I should feel start feeling dumb now ;)

173
Views
5
Helpful
2
Replies
CreatePlease to create content