Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

PIx 525 VS pix 501 vpn with different vlans

Status
Not open for further replies.

Namik

Technical User
Jul 16, 2007
39
AZ
Hi everybody!
I'm not so professional with vpn's and I need your help or advice
My network is cisco 3750 with different vlans - connected to pix525(easy vpn server)-remote sites must be connected through Pix501 vpn (easy vpn hardware client)

As I understand the inside port wich connected to 3750 must be trunk port yes? I can create interfaces for all vlans what i have in 3750 on Pix525,also i can make different users for different vlAns...I need Multiple VPN Group Clients to use Different VLANs after Connecting to a Pix
did any one have such configuration?
 
I just noticed that you dont have a default route.


route outside 0.0.0.0 0.0.0.0 next hop ip
 
I don't need default route, because this Pix will be in center and all branches will be direclty connected to this pix with leased vdsl line.

PIx525 -- vdsl dslam in bridge mode - vdsl modem - pix501 (as hardware vpn client) - customer network

So the outside interface of pix525 and outside interface of pix501 will be in same network
pIX525 outside address 192.168.240.253
pix501 outside address 192.168.240.x
 
That I understand, but if the network behind the 501 is 192.168.10.1 you have to tell the 525 how to get there.
 
but I cannot add on 525 route 0.0.0.0 0.0.0.0 192.168.1.x
because this network is directly connected, on 501 I will add route,but now I'm testing with Cisco VPN Client from my pc
I'm connecting from 192.168.240.70 (ip address of my pc) directly to outside port of pix525 and I can successfully establish vpn, but after vpn i cannot browse or ping the lan witch connected to inside port of 525 (192.168.1.x)
 
I honestly don't see how you are going to get a vpn working between a bridged connection because the PIX will have no idea what interface to send your traffic out of.
 
right now our branche connected through bridge connection to main network
branch network--vdsl modem in bridge mode-vdsl dslam bridge- switch 3750 and they working
why there must be problem for pix? pix will see directly connected 192.168.240.x network. and there will not be problem.
 
You are currently connected as layer 2, putting a PIX in the network requires that both sides are layer 3.
 
brianinms can you help me in way that i connected from pc with vpn client directly to pix outside port, in this case both side is layer 3
 
You would need a route in the 525. I know of no solution to your problem given your current configuration.
 
What kind of route? route 0.0.0.0 0.0.0.0 192.168.1.x for example? it's impossible, 192.168.1.x is directly connected network
route for outside interface also not possible, because outside network also is directly connected network
 
You would need a route to a layer 3 device that is external to your network. You could try..

route outside 0.0.0.0 0.0.0.0 192.168.240.70
 
but it's wrong, my pc is not gateway for 192.168.240.x...
Pix525 outside interface 192.168.240.253 directly connected to 192.168.240.70 and established vpn..why my pc must be gateway? Also I remind to You again Brian, it's imposible add such route that you advised...this network is directly connected!!!
directly connected networks does'nt need any route that's why they calling directly connected networks
 
It is not impossible to add that route to the Pix, if you dont want to take my advise that I will have to say I cant offer additional help. When your computer which is 192.168.240.70 establishes a VPN to the 525 it is assigned an address from the VPN pool such as 10.10.170.1 and in order for the pix to route traffic to you, it has to have a route configured out the outside interface.

The only network that is directly connected is the 192.168.240.x network. The 10.10.170.x network isn't directly connected, nor is the 192.168.1.x network.
 
For testing purpose I've installed Pix501 with following configuration on my lan
My pc adres 192.168.1.7 , I'm connecting using Cisco VPN client, still cannot access lan behind vpn

Any suggestion?

Building configuration...
: Saved
:
PIX Version 6.3(4)
interface ethernet0 auto
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password 8Ry2YjIyt7RRXU24 encrypted
passwd lOkyEYAclKI9EQQq encrypted
hostname idrak-t
domain-name ciscopix.com
fixup protocol dns maximum-length 512
fixup protocol ftp 21
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol http 80
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol sip 5060
fixup protocol sip udp 5060
fixup protocol skinny 2000
fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol tftp 69
names
access-list inside_outbound_nat0_acl permit ip 172.16.1.0 255.255.255.0 192.168.220.0 255.255.255.0
access-list outside_cryptomap_dyn_20 permit ip any 192.168.220.0 255.255.255.0
access-list 101 permit tcp 192.168.220.0 255.255.255.0 any
access-list 101 permit ip 192.168.220.0 255.255.255.0 any
access-list 101 permit icmp 192.168.220.0 255.255.255.0 any
access-list 101 permit icmp any any traceroute
access-list 101 permit icmp any any echo-reply
access-list 101 permit icmp any any unreachable
access-list 101 permit icmp any any time-exceeded
access-list 101 permit udp 192.168.220.0 255.255.255.0 eq dnsix 172.16.1.0 255.255.255.0
access-list 101 permit udp 192.168.220.0 255.255.255.0 eq domain 172.16.1.0 255.255.255.0
access-list 101 permit udp 192.168.220.0 255.255.255.0 172.16.1.0 255.255.255.0
access-list inside_access_in permit tcp 172.16.1.0 255.255.255.0 192.168.220.0 255.255.255.0
access-list inside_access_in permit icmp 172.16.1.0 255.255.255.0 192.168.220.0 255.255.255.0
access-list inside_access_in permit ip 172.16.1.0 255.255.255.0 192.168.220.0 255.255.255.0
access-list inside_access_in permit udp 172.16.1.0 255.255.255.0 192.168.220.0 255.255.255.0
pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside 192.168.1.253 255.255.255.0
ip address inside 172.16.1.239 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
ip local pool mvd 192.168.220.1-192.168.220.250
pdm location 172.16.1.4 255.255.255.255 inside
pdm logging informational 100
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 0 access-list inside_outbound_nat0_acl
nat (inside) 1 172.16.1.0 255.255.255.0 0 0
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
access-group 101 in interface outside
access-group inside_access_in in interface inside
route inside 0.0.0.0 0.0.0.0 172.16.1.239 1
timeout xlate 0:05:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h225 1:00:00
timeout h323 0:05:00 mgcp 0:05:00 sip 0:30:00 sip_media 0:02:00
timeout uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server TACACS+ max-failed-attempts 3
aaa-server TACACS+ deadtime 10
aaa-server RADIUS protocol radius
aaa-server RADIUS max-failed-attempts 3
aaa-server RADIUS deadtime 10
aaa-server LOCAL protocol local
http server enable
http 172.16.1.4 255.255.255.255 inside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
sysopt connection permit-ipsec
crypto ipsec transform-set ESP-3DES-MD5 esp-3des esp-md5-hmac
crypto dynamic-map outside_dyn_map 20 match address outside_cryptomap_dyn_20
crypto dynamic-map outside_dyn_map 20 set transform-set ESP-3DES-MD5
crypto map outside_map 65535 ipsec-isakmp dynamic outside_dyn_map
crypto map outside_map client authentication LOCAL
crypto map outside_map interface outside
isakmp enable outside
isakmp policy 20 authentication pre-share
isakmp policy 20 encryption 3des
isakmp policy 20 hash md5
isakmp policy 20 group 2
isakmp policy 20 lifetime 86400
vpngroup mvd address-pool mvd
vpngroup mvd dns-server 172.16.1.1
vpngroup mvd idle-time 1800
vpngroup mvd password ********
telnet 172.16.1.4 255.255.255.255 inside
telnet timeout 5
ssh timeout 5
console timeout 0
dhcpd auto_config outside
username namik password ****** encrypted privilege 15
terminal width 80
Cryptochecksum:af157182d53bfdecfd1cd063bd0a3577
: end
[OK]

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top