Cisco PIX VPN access-lists

Cisco PIX VPN access-lists

NewsGroups | Search | Tools
 comp.dcom.sys.cisco  Post an article  get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content  add this group's latest topics to your Google content  YahooMyWeb Yahoo!  Google Google  Windows Live Favorites Windows Live  del.icio.us del.icio.us  digg digg  Add to Netscape Netscape
Subject Author Date
Cisco PIX VPN access-lists Lone 06-16-2008
Posted by Lone on June 16, 2008, 1:18 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
I am having difficulty configuring the VPN access-lists on LAN to LAN
IPSec tunnel between a Cisco PIX and a Juniper SSG 20. I'm running
PIX version 7.1(2) and I have sysopt connection permit-vpn enabled,
which, from what I understand would then force access-list
restrictions to be determined by the VPN group-policy and the access-
list specified by the vpn-filter value setting. Currently, I am able
to set traffic restrictions for the tunnel on the SSG, but I would
prefer to be able to do this on the PIX. If I remove the traffic
restrictions set on the SSG, then I have unfiltered access to the
hosts on the PIX side of the tunnel. This is the case whether or not
I have an access-list specified for the vpn-filter value setting. Is
there something else simple that I'm missing?

Thanks,
Lone

NMFall 20%
Posted by Walter Roberson on June 16, 2008, 1:32 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
>I am having difficulty configuring the VPN access-lists on LAN to LAN
>IPSec tunnel between a Cisco PIX and a Juniper SSG 20. I'm running
>PIX version 7.1(2) and I have sysopt connection permit-vpn enabled,
>which, from what I understand would then force access-list
>restrictions to be determined by the VPN group-policy and the access-
>list specified by the vpn-filter value setting.

I haven't used PIX 7 (but used PIX 6 extensively), so I am
not familiar with VPN group policies or vpn-filter.

In PIX 6, specifying sysopt connection permit-vpn
would indicate that packets coming in over the VPN were exempt
from all access-list restrictions. (Though whether the packet
was allowed to cross the VPN at all would be determined by the
crypto map access-list .)

Posted by Lone on June 16, 2008, 2:58 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
On Jun 16, 10:32 am, rober...@hushmail.com (Walter Roberson) wrote:
>
> >I am having difficulty configuring the VPN access-lists on LAN to LAN
> >IPSec tunnel between a Cisco PIX and a Juniper SSG 20. I'm running
> >PIX version 7.1(2) and I have sysopt connection permit-vpn enabled,
> >which, from what I understand would then force access-list
> >restrictions to be determined by the VPN group-policy and the access-
> >list specified by the vpn-filter value setting.
>
> I haven't used PIX 7 (but used PIX 6 extensively), so I am
> not familiar with VPN group policies or vpn-filter.
>
> In PIX 6, specifying sysopt connection permit-vpn
> would indicate that packets coming in over the VPN were exempt
> from all access-list restrictions. (Though whether the packet
> was allowed to cross the VPN at all would be determined by the
> crypto map access-list .)

Can you specify host and port access lists using that crypto map match
address command? Unfortunately, since this is a PIX to SSG tunnel, I
don't believe I can add additional entries to this access list because
the entries in this list need to match the entry on the SSG side.
Unfortunately, I can only designate a subnet on the SSG side. If I
were to change this, I'm fairly sure that the tunnel will not build.

Posted by Lone on June 16, 2008, 3:14 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
> On Jun 16, 10:32 am, rober...@hushmail.com (Walter Roberson) wrote:
>
>
>
> > In article
>
> > >I am having difficulty configuring the VPN access-lists on LAN to LAN
> > >IPSec tunnel between a Cisco PIX and a Juniper SSG 20. I'm running
> > >PIX version 7.1(2) and I have sysopt connection permit-vpn enabled,
> > >which, from what I understand would then force access-list
> > >restrictions to be determined by the VPN group-policy and the access-
> > >list specified by the vpn-filter value setting.
>
> > I haven't used PIX 7 (but used PIX 6 extensively), so I am
> > not familiar with VPN group policies or vpn-filter.
>
> > In PIX 6, specifying sysopt connection permit-vpn
> > would indicate that packets coming in over the VPN were exempt
> > from all access-list restrictions. (Though whether the packet
> > was allowed to cross the VPN at all would be determined by the
> > crypto map access-list .)
>
> Can you specify host and port access lists using that crypto map match
> address command? Unfortunately, since this is a PIX to SSG tunnel, I
> don't believe I can add additional entries to this access list because
> the entries in this list need to match the entry on the SSG side.
> Unfortunately, I can only designate a subnet on the SSG side. If I
> were to change this, I'm fairly sure that the tunnel will not build.

I've been working off of the information provided by this site:

http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a00808c9a87.shtml

It's describing everything that I want to do. I can also successfully
use the vpn-filter command on the Remote Access connections that I've
created on the same PIX. It's just the L2L tunnel that I'm having
trouble with.

Posted by jcle on June 18, 2008, 8:35 am
If you were  Registered and logged in, you could reply and use other advanced thread options
sounds like maybe there acls may not be right I always built three
acls for this one to nonat, one to phase two, and one to the group
policy vpn filter.
the first two for nonat and phase two are typical
access-list 101 permit ip (local net) (remote net)
the filter is a little tricky you reverse the logic
access-list 102 permit tcp (remote net) (local net)
you then allow access by adding eq protocol number following the
network you want to allow access to for example if I wanted to allow a
host behind the juniper to access a webserver behind te asa you would
do this 192.168.1.2 = juniper host 192.168.2.2 = cisco host

access-list 102 permit tcp host 192.168.1.2 host 192.168.2.2 eq www

you the have to renegiote phase 1 any time you make a change to the
group policy acl by running the cl isakmp sa


Lone wrote:
> > On Jun 16, 10:32 am, rober...@hushmail.com (Walter Roberson) wrote:
> >
> >
> >
> > > In article
> >
> > > >I am having difficulty configuring the VPN access-lists on LAN to LAN
> > > >IPSec tunnel between a Cisco PIX and a Juniper SSG 20. I'm running
> > > >PIX version 7.1(2) and I have sysopt connection permit-vpn enabled,
> > > >which, from what I understand would then force access-list
> > > >restrictions to be determined by the VPN group-policy and the access-
> > > >list specified by the vpn-filter value setting.
> >
> > > I haven't used PIX 7 (but used PIX 6 extensively), so I am
> > > not familiar with VPN group policies or vpn-filter.
> >
> > > In PIX 6, specifying sysopt connection permit-vpn
> > > would indicate that packets coming in over the VPN were exempt
> > > from all access-list restrictions. (Though whether the packet
> > > was allowed to cross the VPN at all would be determined by the
> > > crypto map access-list .)
> >
> > Can you specify host and port access lists using that crypto map match
> > address command? Unfortunately, since this is a PIX to SSG tunnel, I
> > don't believe I can add additional entries to this access list because
> > the entries in this list need to match the entry on the SSG side.
> > Unfortunately, I can only designate a subnet on the SSG side. If I
> > were to change this, I'm fairly sure that the tunnel will not build.
>
> I've been working off of the information provided by this site:
>
>
http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a00808c9a87.shtml
>
> It's describing everything that I want to do. I can also successfully
> use the vpn-filter command on the Remote Access connections that I've
> created on the same PIX. It's just the L2L tunnel that I'm having
> trouble with.

Similar ThreadsPosted
Business VoIP Solutions Using Cisco Gateways, Cisco Call Agent, And Cisco IP Phones October 2, 2007, 8:02 pm
Discussion about segregating bandwidth with Cisco 7513, Cisco 3750 and Cisco 3640 June 17, 2006, 8:34 am
cable-modem->d-link 614+-> cisco 3620->cisco 2501->my workstation setup help July 25, 2004, 10:57 am
good cisco and juniper IPS site for intrusion prevention and cisco switch info January 5, 2007, 4:59 pm
Re: Q: Cisco AP 1131 -- "Unsupported device type" error in Cisco Network Assistant November 27, 2007, 1:19 pm
Connect a cisco catalyst 3524XL to a Cisco 6500 ? Auto-MDI or crossover cable August 15, 2008, 6:40 am
Re: Connect a cisco catalyst 3524XL to a Cisco 6500 ? Auto-MDI or crossover cable August 15, 2008, 7:32 am
Cisco 2970 strange traffic problem - stumped cisco support February 10, 2005, 9:19 am
Cisco owned (linksys wet11b) is cisco failing to see market demands? March 10, 2005, 10:02 pm
Cisco Custom Historical Report for Cisco Customer Response Applications January 17, 2006, 12:34 pm

other useful resources:
The Federal Communications Commission (FCC)
Telecommunications Industry Association
Electronic and Software Security Products and Services
International Telecommunication Union

Custom CGI Perl and PHP programming by 1-Script.com

Contact Us | Privacy Policy
The site map in XML format XML site map