|
Posted by Cowboy \(Gregory A. Beamer\) on July 24, 2008, 10:56 am
If you were Registered and logged in, you could reply and use other advanced thread options That is what I thought, as well. I am just not very Cisco savvy, so I
figured I would ping.
--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA
Subscribe to my blog
http://gregorybeamer.spaces.live.com/lists/feed.rss
or just read it:
http://gregorybeamer.spaces.live.com/
********************************************
| Think outside the box! |
********************************************
> Cowboy (Gregory A. Beamer) wrote:
>> We have a VPN into our colocation facility and need to enable the
>> following scenarios for different vendors/clients.
>>
>> 1. Forward all messages on a port to a vendor/client address. Two options
>> here
>> a) Down another VPN on the ASA - preferred
>> b) Directly to an external address
>>
>> 2. Same as above, but also configure an internal route on the same port
>>
>> We have been told by one consltant that this will probably require
>> another ASA, but I am not sure we are getting the correct answer. Does
>> anyone know if this is possible?
>>
>
> Are the different vendors on different subnets? If so I do not see any
> reason why you would not be able to create ACL's sufficient to restrict
> traffic to the specified ports/IP address.
>
>
>
http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a00808c9a87.shtml
>
|