1. Home
  2. Cisco Systems
  3. Newbie VPN Question

Newbie VPN Question

Hello,

First, thanks for all the input I've received so far.

My intentions are as follows for my PIX501:

Allow 9 individuals VPN accessability (L2TP) from their homes to the internal network via cable modem.

I have configured the PIX via the PDM GUI's VPN Wizard to test one of the users as noted in the config file below. The individuals' home computer is WinXP. I have configured a new L2TP VPN connection via the internet on the home computer.

I have the following questions on the config file I've posted.

  1. Access-list inside crypto-map lists 10.0.0.16 255.255.255.240. Why? Gateway is 10.0.0.1 255.255.0.0

  1. PDM location is the same IP and Subnet Mask as #1 above. Why?

  2. When setting up the VPN via GUI I was confused on the first option......Do I set the vpdn enabled to inside, outside or both? Couldn't get a clear idea so I said inside (assuming I wanted to access the inside server at x.x.x.x address from outside)?

When I tried to connect to the office via the home computer, no luck. Received an error 678 Not responding. I can successfully ping the static IP address assigned to the outside IP address of the PIX.

Any input to help me get on the right track would be appreciated.

I can post the Wind VPN connection properties if needed.

PIX501 config follows: I have intentionally double spaced after any line wrap.

Building configuration... : Saved PIX Version 6.3(4) interface ethernet0 auto interface ethernet1 100full nameif ethernet0 outside security0 nameif ethernet1 inside security100 enable password xxxxxxxxxxxxxxx encrypted passwd xxxxxxxxxxxxxxx encrypted hostname pixfirewall domain-name xxxxx 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_cryptomap_dyn_20 permit ip any 10.0.0.16

255.255.255.240

pager lines 24 mtu outside 1500 mtu inside 1500 ip address outside xxx.xxx.56.29 255.255.255.xxx ip address inside 10.0.0.1 255.255.0.0 ip audit info action alarm ip audit attack action alarm ip local pool xxxxxxx 10.0.0.20-10.0.0.29 pdm location 10.0.0.16 255.255.255.240 inside pdm logging informational 100 pdm history enable arp timeout 14400 global (outside) 1 interface nat (inside) 1 0.0.0.0 0.0.0.0 0 0 route outside 0.0.0.0 0.0.0.0 xxx.xxx.xxx.xxx 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 10.0.0.0 255.255.0.0 inside no snmp-server location no snmp-server contact snmp-server community public no snmp-server enable traps floodguard enable sysopt connection permit-l2tp crypto ipsec transform-set TRANS_ESP_3DES_MD5 esp-3des esp-md5-hmac crypto ipsec transform-set TRANS_ESP_3DES_MD5 mode transport crypto dynamic-map inside_dyn_map 20 match address inside_cryptomap_dyn_20 crypto dynamic-map inside_dyn_map 20 set transform-set TRANS_ESP_3DES_MD5 crypto map inside_map 65535 ipsec-isakmp dynamic inside_dyn_map crypto map inside_map interface inside isakmp enable inside isakmp key ******** address 0.0.0.0 netmask 0.0.0.0 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 telnet timeout 5 ssh timeout 5 console timeout 0 vpdn group L2TP-VPDN-GROUP accept dialin l2tp vpdn group L2TP-VPDN-GROUP ppp authentication chap vpdn group L2TP-VPDN-GROUP client configuration address local xxxxxx vpdn group L2TP-VPDN-GROUP client authentication local vpdn group L2TP-VPDN-GROUP l2tp tunnel hello 60 vpdn username xxxxxx password ********* vpdn enable inside dhcpd address 10.0.0.2-10.0.0.129 inside dhcpd dns xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx dhcpd lease 3600 dhcpd ping_timeout 750 dhcpd auto_config outside dhcpd enable inside terminal width 80 Cryptochecksum:1365a1deee1be253d19ebb1b7cc54cd7 : end [OK] pixfirewall(config)#

Regards,

Buck

_______________________________________________________________________________ Posted Via Uncensored-News.Com - Accounts Starting At $6.95 -

formatting link
The Worlds Uncensored News Source

Reply to
Buck Rogers
Loading thread data ...

In article , Buck Rogers wrote: :My intentions are as follows for my PIX501:

:Allow 9 individuals VPN accessability (L2TP) from their homes to the :internal network via cable modem.

That's getting close to the limit for the 501 -- maximum 10 peers.

:I have configured the PIX via the PDM GUI's VPN Wizard to test one of :the users as noted in the config file below.

:I have the following questions on the config file I've posted.

:1. Access-list inside crypto-map lists 10.0.0.16 255.255.255.240. :Why? Gateway is 10.0.0.1 255.255.0.0

Probably has to do with #3.

:2. PDM location is the same IP and Subnet Mask as #1 above. Why?

Ditto.

:3. When setting up the VPN via GUI I was confused on the first :option......Do I set the vpdn enabled to inside, outside or both? :Couldn't get a clear idea so I said inside (assuming I wanted to :access the inside server at x.x.x.x address from outside)?

You wanted outside, not inside. It's the interface that the remote devices need to talk to in order to establish the connection.

Once you have the interface wrong, other things go wrong in order to compensate for the inherent IP address conflicts.

Speaking of address conflicts: the IP pool you use for the clients must not be part of your inside address range when the clients are on the outside. The PIX uses routing to determine which interface to send the packets to, so if it sees 10.0.0.20 as an address, it is going to think that packets for that destination should be sent to the inside interface and the packets will never make it "across" the PIX from the inside to the VPN tunnel that is connected to the outside interface.

Reply to
Walter Roberson

Correct..We have 6 full time users and 3 who need it in a very limited way monthly.

Thanks for the clarification.

Ahhhh!

I'm gonna make the adjustments tomorrow and try again. Will post any successes or more questions later.

Once again, Walter, you've been a tremendous help.

Thank You

Buck

_______________________________________________________________________________ Posted Via Uncensored-News.Com - Accounts Starting At $6.95 -

formatting link
The Worlds Uncensored News Source

Reply to
Buck Rogers

Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.