| Home | Forums | Reviews | Guides | Newsgroups | Register | Search |
![]() |
| Thread Tools |
| Aaron Gitlin |
|
|
|
| |
|
Walter Roberson
Guest
Posts: n/a
|
In article <44c1629c$>,
Aaron Gitlin <> wrote: >We have recently inherited a network that has multiple locations with >multiple tunnels over a few PIX units. The existing tunnels work perfectly. >There are three offices: DI, DL and the owner, Dale's, house. There is a >working tunnel between DI and DL, one between DL and Dale and a few from DL >to other offices. We need to configure a tunnel between DI and Dale, but >have had no luck. >DL PIX Config >access-list split permit ip 192.168.7.0 255.255.255.0 19 >0 Unfortunately that line (or those lines) were munged and I can't reasonably interpolate what they are in the configuration. If that line was overly general, it could cause the problem you are seeing. |
|
|
|
|
|||
|
|||
| Walter Roberson |
|
|
|
| |
|
Walter Roberson
Guest
Posts: n/a
|
In article <44c1629c$>,
Aaron Gitlin <> wrote: >DL PIX Config >PIX Version 6.3(5) >sysopt ipsec pl-compatibl You never need that anymore. It's a rare PIX that is still running the Private Link encryption cards. >crypto ipsec transform-set ENCRYPT1 esp-3des esp-md5-hmac >crypto ipsec transform-set AES-256 esp-aes-256 esp-sha-hmac >crypto dynamic-map dynmap 90 set transform-set AES-256 ENCRYPT1 >isakmp policy 10 encryption 3des >isakmp policy 10 hash md5 >isakmp policy 10 group 1 >isakmp policy 10 lifetime 28800 PIX 6.3 limitation: 3DES MD5 is not supported. For 3DES you should use 3DES SHA Group 2 (Group 1 if you -really- need to.) DES MD5 Group 1 -is- supported. >isakmp policy 20 authentication pre-share >isakmp policy 20 encryption 3des >isakmp policy 20 Missing end of line there? >isakmp policy 20 group 2 The default hash is MD5, so unless the missing end of line was for an SHA hash, the only difference between this and the previous is that this one is group 2 instead of group 1. But why put the stronger encryption as lower priority? And if the missing end of line is SHA, then you do not have a corresponding phase 2 encryption setup; differences in encryption between the two phases don't cause problems in theory, but can in practice. >Dale's PIX Config: >PIX Version 6.3(3) There is a PIX security advisory that you can use to take that to 6.3(5)rebuild even if you do not have a support contract. >crypto ipsec transform-set strong esp-3des esp-md5-hmac >crypto ipsec transform-set AES-256 esp-aes-256 esp-sha-hmac >crypto ipsec transform-set DE-DI esp-des esp-md5-hmac >crypto map PIXRemote 20 set peer <*** DL's IP ***> >crypto map PIXRemote 20 set transform-set strong Why not use AES-128? It's actually faster than 3DES on a PIX 501. AES-256 might only be able the same speed as 3DES, but somehow I doubt you are maxing out the crypto tranform rate on this link... >crypto map PIXRemote 25 set peer <*** DI's IP ***> >crypto map PIXRemote 25 set transform-set DE-DI Again, why not AES, considering you are talking to a PIX 6.3 ? Or at least 3DES? >isakmp policy 10 encryption 3des >isakmp policy 10 hash md5 >isakmp policy 10 group 1 >isakmp policy 20 encryption 3des >isakmp policy 20 hash md5 >isakmp policy 20 group 2 As per above: why put the strong encryption as lower priority? >DI PIX Config: >PIX Version 6.3(4) You can get that up to 6.3(5)rebuild via the security advisory. >crypto ipsec transform-set AES-256 esp-aes-256 esp-sha-hmac You wouldn't even be able to enter that command if you didn't have a 3DES/AES license, so you might as well take advantage of the security when communicating with Dale's PIX. >crypto map DI-VPN client configuration address initiate >crypto map DI-VPN client configuration address respond I'd recommend turning those off if Dale is the only client. Alternately, in the isakmp key that matches Dale's potential range of IPs, add no-xauth no-config-mode to the line. You don't appear to have a shared key specific to Dale, but I would suggest that you should: although he has a dynamic IP, his ISP is only going to give him an IP from a limited pool, and things get easier for you if you can allow him to use his internal IP range instead of having him allocated an link IP by the PIXen. |
|
|
|
|
|||
|
|||
| Walter Roberson |
|
Aaron Gitlin
Guest
Posts: n/a
|
Wow...Thank you Walter! I will take a look at your suggestions and work
from there - these pointers are exactly what I needed. Thanks again, I'll post and let you know how this turns out, "Walter Roberson" <> wrote in message news > In article <44c1629c$>, > Aaron Gitlin <> wrote: > >>DL PIX Config > >>PIX Version 6.3(5) > >>sysopt ipsec pl-compatibl > > You never need that anymore. It's a rare PIX that is still running > the Private Link encryption cards. > >>crypto ipsec transform-set ENCRYPT1 esp-3des esp-md5-hmac >>crypto ipsec transform-set AES-256 esp-aes-256 esp-sha-hmac >>crypto dynamic-map dynmap 90 set transform-set AES-256 ENCRYPT1 > >>isakmp policy 10 encryption 3des >>isakmp policy 10 hash md5 >>isakmp policy 10 group 1 >>isakmp policy 10 lifetime 28800 > > PIX 6.3 limitation: 3DES MD5 is not supported. For 3DES you > should use 3DES SHA Group 2 (Group 1 if you -really- need to.) > DES MD5 Group 1 -is- supported. > >>isakmp policy 20 authentication pre-share >>isakmp policy 20 encryption 3des >>isakmp policy 20 > > Missing end of line there? > >>isakmp policy 20 group 2 > > The default hash is MD5, so unless the missing end of line was > for an SHA hash, the only difference between this and the previous > is that this one is group 2 instead of group 1. But why put the > stronger encryption as lower priority? And if the missing end of > line is SHA, then you do not have a corresponding phase 2 encryption > setup; differences in encryption between the two phases don't cause > problems in theory, but can in practice. > > >>Dale's PIX Config: > >>PIX Version 6.3(3) > > There is a PIX security advisory that you can use to take that > to 6.3(5)rebuild even if you do not have a support contract. > >>crypto ipsec transform-set strong esp-3des esp-md5-hmac >>crypto ipsec transform-set AES-256 esp-aes-256 esp-sha-hmac >>crypto ipsec transform-set DE-DI esp-des esp-md5-hmac > >>crypto map PIXRemote 20 set peer <*** DL's IP ***> >>crypto map PIXRemote 20 set transform-set strong > > Why not use AES-128? It's actually faster than 3DES on a PIX 501. > AES-256 might only be able the same speed as 3DES, but somehow > I doubt you are maxing out the crypto tranform rate on this link... > >>crypto map PIXRemote 25 set peer <*** DI's IP ***> >>crypto map PIXRemote 25 set transform-set DE-DI > > Again, why not AES, considering you are talking to a PIX 6.3 ? > Or at least 3DES? > >>isakmp policy 10 encryption 3des >>isakmp policy 10 hash md5 >>isakmp policy 10 group 1 > >>isakmp policy 20 encryption 3des >>isakmp policy 20 hash md5 >>isakmp policy 20 group 2 > > As per above: why put the strong encryption as lower priority? > > >>DI PIX Config: > >>PIX Version 6.3(4) > > You can get that up to 6.3(5)rebuild via the security advisory. > >>crypto ipsec transform-set AES-256 esp-aes-256 esp-sha-hmac > > You wouldn't even be able to enter that command if you didn't > have a 3DES/AES license, so you might as well take advantage of the > security when communicating with Dale's PIX. > >>crypto map DI-VPN client configuration address initiate >>crypto map DI-VPN client configuration address respond > > I'd recommend turning those off if Dale is the only client. > Alternately, in the isakmp key that matches Dale's potential range > of IPs, add no-xauth no-config-mode to the line. You don't appear > to have a shared key specific to Dale, but I would suggest that you > should: although he has a dynamic IP, his ISP is only going to give > him an IP from a limited pool, and things get easier for you if you > can allow him to use his internal IP range instead of having him > allocated an link IP by the PIXen. > |
|
|
|
|
|||
|
|||
| Aaron Gitlin |
|
|
|
| |
![]() |
| Thread Tools | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| One IPsec tunnel and no ISAKMP tunnel. | AM | Cisco | 7 | 07-19-2007 03:11 PM |
| Site to site VPn tunnel and VPN tunnel | Trouble | Cisco | 1 | 08-04-2006 08:09 AM |
| Site to site VPn tunnel and VPN tunnel | Trouble | Cisco | 0 | 08-04-2006 04:23 AM |
| Split Tunnel Blocks http through tunnel but passes http around tunnel | a.nonny mouse | Cisco | 2 | 09-19-2004 12:10 AM |
| Termination of an IPSec VPN tunnel and a GRE Tunnel on one physical interface. | John Ireland | Cisco | 1 | 11-11-2003 04:47 PM |
Powered by vBulletin®. Copyright ©2000 - 2013, vBulletin Solutions, Inc..
SEO by vBSEO ©2010, Crawlability, Inc. |




