Not the cool way to get PDM... but... 1

[Aluffy]

Hey Folks,
I bought a used Pix (FOS 6.3(1) to kick around and I need to install the pdm BIN... but... don't have access to the CCO... any help/suggestions?

Thx!

 

[Robroy2003]

I personally think the PDM is still very clunky. I prefer to use the command line interface from a console. Commands are not that hard. You might give that a try. Some things still do not work in PDM. Like the alias command etc..


Mark Spencer

 

[Aluffy]

Thanks Mark -- I figure it's a good thing to be forced to learn the CLI anyway - I'm trying to create a VPN tunnel from a Linksys BEFVP41 to the Pix... and for some reason thought the PDM would be a holy grail More fun with hyper terminal!!

Anybody have any success doing that... I figure since both products are ICSA certified, it must be possible.

Cheers,
Andy

 

[br0ck]

Good luck with the vpn I have been working on a pix to WRV54G

after repeted attempts with Linksys's offshore TechSupport
no success

If you get it going please post your findings


BTW:
look in to pixcript

http://teachers.sivan.co.il/yizhar/files/pixcreen.htm

and putty

http://tucows.com/preview/195286.html

to help with the learning

 

[Aluffy]

Hi br0ck,
I was able to get the BEFVP41 to connect to the pix and they work very well.

I am using the BEFVP41 to PIX VPN in order to create a VoIP network for our company (Cisco Call Manager) - the VPN tunnels are pretty reliable, the real noticable negative with the BEFVP41 being no QoS or support for DMVPN (probably where we will end up with Cisco 831's). I will post the configs shortly on how I established the tunnels...

Is the WRV54G ICSA certified? That was one of my requirements when purchasing the BEFVP41...

Best,
Andy

 

[TruBlu01]

I am having a problem with NetBios names with this linksys. I can connect to both my companies tunnels and surf the intranet via IP. Am I missing some type of DNS setting?

 

[Aluffy]

Unforunately I don't think the Linksys keeps information for DNS in the VPN tunnels... You could however, just assign a static IP to your computer and enter a DNS server that serves your intranet zones. That why lookup is assured to occur at the internal DNS machines, with lower priority DNS servers serving the Internet zone.

Best, Andy

 

[TruBlu01]

Hmm, sounds good, but it's for an office which we switched all pc's to DHCP for a reason. With the PIX 501 we are able to add dns servers to it in the config. Anyone else?

Marc

 

[jwashburn]

Hey there afluffy, can you post the relavant config information. I have recently been tasked with connecting 15 of the Linksys devices with our PIX515

 

[Aluffy]

Here is our configuration for our pix:
----------------------------------------
interface ethernet0 auto
interface ethernet1 auto
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password xxxxxxxxxxxxxxxxxxx encrypted
passwd xxxxxxxxxxxxxxxx encrypted
hostname ANYBODY-PIX
domain-name ANYBODY.com
fixup protocol ftp 21
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol http 80
fixup protocol ils 389
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
names
access-list 100 permit ip 10.0.0.0 255.255.255.0 10.0.1.0 255.255.255.0
access-list 100 permit ip 10.0.0.0 255.255.255.0 10.0.2.0 255.255.255.0
access-list 100 permit ip 10.0.0.0 255.255.255.0 10.0.3.0 255.255.255.0
access-list 100 permit ip 10.0.0.0 255.255.255.0 10.0.4.0 255.255.255.0
access-list 100 permit ip 10.0.0.0 255.255.255.0 10.0.5.0 255.255.255.0
access-list 100 permit ip 10.0.0.0 255.255.255.0 192.168.1.0 255.255.255.0
access-list 110 permit ip 10.0.0.0 255.255.255.0 10.0.1.0 255.255.255.0
access-list 110 permit ip 10.0.0.0 255.255.255.0 10.0.2.0 255.255.255.0
access-list 110 permit ip 10.0.0.0 255.255.255.0 10.0.3.0 255.255.255.0
access-list 110 permit ip 10.0.0.0 255.255.255.0 10.0.4.0 255.255.255.0
access-list 110 permit ip 10.0.0.0 255.255.255.0 10.0.5.0 255.255.255.0
access-list 110 permit ip 10.0.0.0 255.255.255.0 192.168.1.0 255.255.255.0
access-list CCM permit tcp any host xxx.xxx.xxx.xxx eq 3389
access-list CCM permit tcp any host xxx.xxx.xxx.xxx eq www
pager lines 24
logging on
logging buffered debugging
mtu outside 1500
mtu inside 1500
ip address outside xxx.xxx.xxx.xxx xxx.xxx.xxx.xxx
ip address inside 10.0.0.1 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
ip local pool XXXX-Vpn-Pool 192.168.1.2-192.168.1.254
no failover
failover timeout 0:00:00
failover poll 15
no failover ip address outside
no failover ip address inside
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 0 access-list 100
nat (inside) 1 10.0.0.0 255.255.255.0 0 0
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 3:00: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 RADIUS protocol radius
aaa-server LOCAL protocol local
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 myset esp-3des esp-md5-hmac
crypto dynamic-map dynmap 30 match address 100
crypto dynamic-map dynmap 30 set pfs
crypto dynamic-map dynmap 30 set transform-set myset
crypto dynamic-map dynmap 40 set transform-set myset
crypto map newmap 20 ipsec-isakmp dynamic dynmap
crypto map newmap interface outside
isakmp enable outside
isakmp key ******** address 0.0.0.0 netmask 0.0.0.0 no-xauth no-config-mode
isakmp identity address
isakmp policy 10 authentication pre-share
isakmp policy 10 encryption 3des
isakmp policy 10 hash md5
isakmp policy 10 group 2
isakmp policy 10 lifetime 86400
vpngroup XXXXXXVPN address-pool xxxxxxx-Vpn-Pool
vpngroup XXXXXXVPN dns-server 10.0.0.3
vpngroup XXXXXXVPN default-domain xxxxxxx.com
vpngroup XXXXXXVPN split-tunnel 100
vpngroup XXXXXXVPN idle-time 1800
vpngroup XXXXXXVPN password ********
telnet xxx.xxx.xxx.xxx 255.255.255.255 outside
telnet xxx.xxx.xxx.xxx 255.255.255.0 outside
telnet xxx.xxx.xxx.xxx 255.255.255.255 outside
telnet 0.0.0.0 0.0.0.0 inside
telnet timeout 5
ssh 0.0.0.0 0.0.0.0 outside
ssh 10.0.1.0 255.255.255.0 outside
ssh timeout 5
console timeout 0
terminal width 80
banner exec ##########################################
banner exec # Welcome to xxxxxxxx PIX Firewall #
banner exec ##########################################
banner exec Authorized users only
banner exec All access may be monitored and/or recorded
banner exec Results may be provided to appropriate officials
banner exec Use implies consent
banner exec
-----------------------------------------------------

This configuration uses a dynamic crypto map to establish the VPN. Searches the access list for a match from the remoting party, validates the group information and walla... tunnel is up. On the linksys side:
Local Secure group maps to a a subnet in access-list 110
Remote Secure Group matches the pix internal interface settings, Encryption is 3DES, Auth is MD5, PFS is enabled, and the key lifetime is 86400 (pix default I believe). Also, the linksys is set to keep the connection alive under the advanced settings button.

Hope this helps... it took me a good bit to get all this coordinated. We will probably be moving our system to Cisco 831 for SOHO because of DMVPN (we have a fully meshed vpn network, and it can be a pain to manage the tunnels).