Pages

Tuesday, October 8, 2013

DSL Line - PPPoE on Cisco Router Configuration Template

interface GigabitEthernet0/0
 no ip address
 ip virtual-reassembly
 duplex auto
 speed auto
 pppoe enable group global
 pppoe-client dial-pool-number 1



interface GigabitEthernet0/1
 ip address 100.199.14.7 255.255.255.0
 ip nat inside
 ip virtual-reassembly
 duplex auto
 speed auto

interface Dialer1
 ip address negotiated
 ip mtu 1492
 ip nat outside
 ip virtual-reassembly
 encapsulation ppp
 ip tcp adjust-mss 1452
 dialer pool 1
 dialer-group 1
 ppp authentication pap callin
 ppp pap sent-username dsl@net.ca password 0 123456
!

ip nat inside source list 1 interface Dialer1 overload
ip nat inside source static 100.199.38.3 9.1.1.8
ip route 0.0.0.0 0.0.0.0 Dialer1

access-list 1 permit 100.199.38.0 0.0.0.255



Thursday, October 3, 2013

Upgrade Juniper JUNOS on SRX using USB Storage

1. Insert USB Pen Driver into USB port on SRX Firewall


2. log into SRX Firewall with root account. 

Create /var/tmp/usb folder
root@fw-1-1% cd /var/tmp
root@fw-1-1% ls
cleanup-pkgs.log        gksdchk.log             idp_license_info        krt_gencfg_filter.txt   policy_status           sec-download            vi.recover
eedebug_bin_file        gres-tp                 install                 pics                    rtsdb                   spu_kmd_init
root@fw-mex1-1% mkdir usb

3. Get usb device name

root@fw-1-1% cd /var/log
root@fw-1-1% cat messages 

then find out following messages:
Oct  3 17:55:23  fw-mex1-1 /kernel: %KERN-2: umass1: HP v220w, rev 2.00/11.00, addr 4
Oct  3 17:55:24  fw-mex1-1 /kernel: %KERN-2: da1 at umass-sim1 bus 1 target 0 lun 0
Oct  3 17:55:24  fw-mex1-1 /kernel: %KERN-2: da1: <hp v220w 1100> Removable Direct Access SCSI-4 device 
Oct  3 17:55:24  fw-mex1-1 /kernel: %KERN-2: da1: 40.000MB/s transfers
Oct  3 17:55:24  fw-mex1-1 /kernel: %KERN-2: da1: 7788MB (15950592 512 byte sectors: 255H 63S/T 992C)
Oct  3 17:55:30  fw-mex1-1 sshd[27752]: %AUTH-6: Did not receive identification string from 10.4.20.5

Device name will be da1s1


4. Mount device to folder /var/tmp/usb

root@fw-1-1% cd /dev/
root@fw-1-1% ls
altroot         bo0s3e          bpf10           bpf3            cfi0            da0             da0s3           da0s4e          fileassoc       md0             nfslock         ptyp1           stdout          usb
ata             bo0s3f          bpf11           bpf4            console         da0s1           da0s3c          da1             gblmem          md1             null            random          ttyp0           usb0
bo0s1a          bo0s4a          bpf12           bpf5            cpld            da0s1a          da0s3e          da1s1           geom.ctl        md2             octpkt          root            ttyp1           usb1
bo0s1c          bo0s4c          bpf13           bpf6            ctty            da0s1c          da0s3f          devctl          gpio            md3             pass0           rtfifo          ttyu0           veriexec
bo0s2a          bo0s4e          bpf14           bpf7            cuau0           da0s2           da0s4           devstat         klog            mdctl           pass1           smb             ttyu0.init      xpt0
bo0s2c          bpf0            bpf15           bpf8            cuau0.init      da0s2a          da0s4a          fd              kmem            mem             pci             stderr          ttyu0.lock      zero
bo0s3c          bpf1            bpf2            bpf9            cuau0.lock      da0s2c          da0s4c          fido            log             nfs4            ptyp0           stdin           urandom
root@fw-mex1-1% mount -t msdos /dev/da1s1 /var/tmp/usb

5. copy the file to folder /var/tmp/usb


6. add package into system software

root@fw-1-1> request system software add /var/tmp/usb/junos-srxsme-11.4R7.5-domestic.tgz no-copy no-validate

Follow the screen notification to do upgrade firewall.



Monday, September 16, 2013

Cisco IOS IPSec VPN with External Trusted PKI Certs - Verisign

Topology:

using IOU Rack v3 from post

My Cisco IOU Racks - from flyxj IOUv3


It looks like following screenshot:
The goal is to achieve ipsec with third party trusted PKI certs - verisign. This lab will use verisign trial version  to demonstrate procedures.

Enabled R6 and R7 as PC to do testing. Logical topology looks like following:

1. Delete all existing configuration then reload those four routers:


R2#delete nvram:startup-config
Delete filename [startup-config]?
Delete nvram:startup-config? [confirm]
[OK]
R2#reload


2. Make vpn up using pre-share key:

@R1
crypto isakmp policy 10
 authentication pre-share
 group 2
crypto isakmp key cisco1234 address 10.94.200.47
!
crypto ipsec transform-set VPN1 ah-sha-hmac esp-3des esp-sha-hmac 
!
crypto map VPN-MAP 10 ipsec-isakmp 
 set peer 10.94.200.47
 set transform-set VPN1 
 match address ACL-VPN
!
interface Ethernet0/0
 ip address 10.94.200.37 255.255.255.0
 crypto map VPN-MAP

ip route 0.0.0.0 0.0.0.0 10.94.200.37
ip access-list extended ACL-VPN
 permit ip 192.168.177.0 0.0.0.255 192.168.99.0 0.0.0.255

@R2:
crypto isakmp policy 10
 authentication pre-share
 group 2
crypto isakmp key cisco1234 address 10.94.200.37
!
crypto ipsec transform-set VPN1 ah-sha-hmac esp-3des esp-sha-hmac 
!
crypto map VPN-MAP 10 ipsec-isakmp 
 set peer 10.94.200.37
 set transform-set VPN1 
 match address ACL-VPN
!
interface Ethernet0/0
 ip address 10.94.200.47 255.255.255.0
 crypto map VPN-MAP
ip route 0.0.0.0 0.0.0.0 10.94.200.37
!
ip access-list extended ACL-VPN
 permit ip 192.168.99.0 0.0.0.255 192.168.177.0 0.0.0.255

Test Result by ping  R7's ip 192.168.99.1 from R6
R6#ping 192.168.99.1  
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.99.1, timeout is 2 seconds:
.!!!!
Success rate is 80 percent (4/5), round-trip min/avg/max = 4/8/12 ms

Debug Crypto Isakmp Output @R1:

R1(config)#
*Mar 11 02:14:55.159: ISAKMP:(0): SA request profile is (NULL)
*Mar 11 02:14:55.159: ISAKMP: Created a peer struct for 10.94.200.47, peer port 500
*Mar 11 02:14:55.159: ISAKMP: New peer created peer = 0xB6803C58 peer_handle = 0x80000002
*Mar 11 02:14:55.159: ISAKMP: Locking peer struct 0xB6803C58, refcount 1 for isakmp_initiator
*Mar 11 02:14:55.159: ISAKMP: local port 500, remote port 500
*Mar 11 02:14:55.159: ISAKMP: set new node 0 to QM_IDLE      
*Mar 11 02:14:55.159: ISAKMP:(0):insert sa successfully sa = B6803240
*Mar 11 02:14:55.159: ISAKMP:(0):Can not start Aggressive mode, trying Main mode.
*Mar 11 02:14:55.159: ISAKMP:(0):found peer pre-shared key matching 10.94.200.47
*Mar 11 02:14:55.159: ISAKMP:(0): constructed NAT-T vendor-rfc3947 ID
*Mar 11 02:14:55.159: ISAKMP:(0): constructed NAT-T vendor-07 ID
*Mar 11 02:14:55.159: ISAKMP:(0): constructed NAT-T vendor-03 ID
*Mar 11 02:14:55.159: ISAKMP:(0): constructed NAT-T vendor-02 ID
*Mar 11 02:14:55.159: ISAKMP:(0):Input = IKE_MESG_FROM_IPSEC, IKE_SA_REQ_MM
*Mar 11 02:14:55.159: ISAKMP:(0):Old State = IKE_READY  New State = IKE_I_MM1 

*Mar 11 02:14:55.159: ISAKMP:(0): beginning Main Mode exchange
*Mar 11 02:14:55.159: ISAKMP:(0): sending packet to 10.94.200.47 my_port 500 peer_port 500 (I) MM_NO_STATE
*Mar 11 02:14:55.159: ISAKMP:(0):Sending an IKE IPv4 Packet.
*Mar 11 02:14:55.163: ISAKMP (0): received packet from 10.94.200.47 dport 500 sport 500 Global (I) MM_NO_STATE
*Mar 11 02:14:55.163: ISAKMP:(0):Input = IKE_MESG_FROM_PEER, IKE_MM_EXCH
*Mar 11 02:14:55.163: ISAKMP:(0):Old State = IKE_I_MM1  New State = IKE_I_MM2 

*Mar 11 02:14:55.183: ISAKMP:(0): processing SA payload. message ID = 0
*Mar 11 02:14:55.183: ISAKMP:(0): processing vendor id payload
*Mar 11 02:14:55.183: ISAKMP:(0): vendor ID seems Unity/DPD but major 69 mismatch
*Mar 11 02:14:55.183: ISAKMP (0): vendor ID is NAT-T RFC 3947
*Mar 11 02:14:55.183: ISAKMP:(0):found peer pre-shared key matching 10.94.200.47
*Mar 11 02:14:55.183: ISAKMP:(0): local preshared key found
*Mar 11 02:14:55.183: ISAKMP : Scanning profiles for xauth ...
*Mar 11 02:14:55.183: ISAKMP:(0):Checking ISAKMP transform 1 against priority 10 policy
*Mar 11 02:14:55.183: ISAKMP:      encryption DES-CBC
*Mar 11 02:14:55.183: ISAKMP:      hash SHA
*Mar 11 02:14:55.183: ISAKMP:      default group 2
*Mar 11 02:14:55.183: ISAKMP:      auth pre-share
*Mar 11 02:14:55.183: ISAKMP:      life type in seconds
*Mar 11 02:14:55.183: ISAKMP:      life duration (VPI) of  0x0 0x1 0x51 0x80 
*Mar 11 02:14:55.183: ISAKMP:(0):atts are acceptable. Next payload is 0
*Mar 11 02:14:55.183: ISAKMP:(0):Acceptable atts:actual life: 0
*Mar 11 02:14:55.183: ISAKMP:(0):Acceptable atts:life: 0
*Mar 11 02:14:55.183: ISAKMP:(0):Fill atts in sa vpi_length:4
*Mar 11 02:14:55.183: ISAKMP:(0):Fill atts in sa life_in_seconds:86400
*Mar 11 02:14:55.183: ISAKMP:(0):Returning Actual lifetime: 86400
*Mar 11 02:14:55.183: ISAKMP:(0)::Started lifetime timer: 86400.

*Mar 11 02:14:55.183: ISAKMP:(0): processing vendor id payload
*Mar 11 02:14:55.183: ISAKMP:(0): vendor ID seems Unity/DPD but major 69 mismatch
*Mar 11 02:14:55.183: ISAKMP (0): vendor ID is NAT-T RFC 3947
*Mar 11 02:14:55.183: ISAKMP:(0):Input = IKE_MESG_INTERNAL, IKE_PROCESS_MAIN_MODE
*Mar 11 02:14:55.183: ISAKMP:(0):Old State = IKE_I_MM2  New State = IKE_I_MM2 

*Mar 11 02:14:55.183: ISAKMP:(0): sending packet to 10.94.200.47 my_port 500 peer_port 500 (I) MM_SA_SETUP
*Mar 11 02:14:55.183: ISAKMP:(0):Sending an IKE IPv4 Packet.
*Mar 11 02:14:55.183: ISAKMP:(0):Input = IKE_MESG_INTERNAL, IKE_PROCESS_COMPLETE
*Mar 11 02:14:55.183: ISAKMP:(0):Old State = IKE_I_MM2  New State = IKE_I_MM3 

*Mar 11 02:14:55.191: ISAKMP (0): received packet from 10.94.200.47 dport 500 sport 500 Global (I) MM_SA_SETUP
*Mar 11 02:14:55.191: ISAKMP:(0):Input = IKE_MESG_FROM_PEER, IKE_MM_EXCH
*Mar 11 02:14:55.191: ISAKMP:(0):Old State = IKE_I_MM3  New State = IKE_I_MM4 

*Mar 11 02:14:55.191: ISAKMP:(0): processing KE payload. message ID = 0
*Mar 11 02:14:55.195: ISAKMP:(0): processing NONCE payload. message ID = 0
*Mar 11 02:14:55.195: ISAKMP:(0):found peer pre-shared key matching 10.94.200.47
*Mar 11 02:14:55.195: ISAKMP:(1001): processing vendor id payload
*Mar 11 02:14:55.195: ISAKMP:(1001): vendor ID is Unity
*Mar 11 02:14:55.195: ISAKMP:(1001): processing vendor id payload
*Mar 11 02:14:55.195: ISAKMP:(1001): vendor ID is DPD
*Mar 11 02:14:55.195: ISAKMP:(1001): processing vendor id payload
*Mar 11 02:14:55.195: ISAKMP:(1001): speaking to another IOS box!
*Mar 11 02:14:55.195: ISAKMP:received payload type 20
*Mar 11 02:14:55.195: ISAKMP (1001): His hash no match - this node outside NAT
*Mar 11 02:14:55.195: ISAKMP:received payload type 20
*Mar 11 02:14:55.195: ISAKMP (1001): No NAT Found for self or peer
*Mar 11 02:14:55.195: ISAKMP:(1001):Input = IKE_MESG_INTERNAL, IKE_PROCESS_MAIN_MODE
*Mar 11 02:14:55.195: ISAKMP:(1001):Old State = IKE_I_MM4  New State = IKE_I_MM4 

*Mar 11 02:14:55.199: ISAKMP:(1001):Send initial contact
*Mar 11 02:14:55.199: ISAKMP:(1001):SA is doing pre-shared key authentication using id type ID_IPV4_ADDR
*Mar 11 02:14:55.199: ISAKMP (1001): ID payload 
        next-payload : 8
        type         : 1 
        address      : 10.94.200.37 
        protocol     : 17 
        port         : 500 
        length       : 12
*Mar 11 02:14:55.199: ISAKMP:(1001):Total payload length: 12
*Mar 11 02:14:55.199: ISAKMP:(1001): sending packet to 10.94.200.47 my_port 500 peer_port 500 (I) MM_KEY_EXCH
*Mar 11 02:14:55.199: ISAKMP:(1001):Sending an IKE IPv4 Packet.
*Mar 11 02:14:55.199: ISAKMP:(1001):Input = IKE_MESG_INTERNAL, IKE_PROCESS_COMPLETE
*Mar 11 02:14:55.199: ISAKMP:(1001):Old State = IKE_I_MM4  New State = IKE_I_MM5 

*Mar 11 02:14:55.199: ISAKMP (1001): received packet from 10.94.200.47 dport 500 sport 500 Global (I) MM_KEY_EXCH
*Mar 11 02:14:55.199: ISAKMP:(1001): processing ID payload. message ID = 0
*Mar 11 02:14:55.199: ISAKMP (1001): ID payload 
        next-payload : 8
        type         : 1 
        address      : 10.94.200.47 
        protocol     : 17 
        port         : 500 
        length       : 12
*Mar 11 02:14:55.199: ISAKMP:(0):: peer matches *none* of the profiles
*Mar 11 02:14:55.199: ISAKMP:(1001): processing HASH payload. message ID = 0
*Mar 11 02:14:55.199: ISAKMP:(1001):SA authentication status:
        authenticated
*Mar 11 02:14:55.199: ISAKMP:(1001):SA has been authenticated with 10.94.200.47
*Mar 11 02:14:55.199: ISAKMP: Trying to insert a peer 10.94.200.37/10.94.200.47/500/,  and inserted successfully B6803C58.
*Mar 11 02:14:55.199: ISAKMP:(1001):Input = IKE_MESG_FROM_PEER, IKE_MM_EXCH
*Mar 11 02:14:55.199: ISAKMP:(1001):Old State = IKE_I_MM5  New State = IKE_I_MM6 

*Mar 11 02:14:55.199: ISAKMP:(1001):Input = IKE_MESG_INTERNAL, IKE_PROCESS_MAIN_MODE
*Mar 11 02:14:55.199: ISAKMP:(1001):Old State = IKE_I_MM6  New State = IKE_I_MM6 

*Mar 11 02:14:55.203: ISAKMP:(1001):Input = IKE_MESG_INTERNAL, IKE_PROCESS_COMPLETE
*Mar 11 02:14:55.203: ISAKMP:(1001):Old State = IKE_I_MM6  New State = IKE_P1_COMPLETE 

*Mar 11 02:14:55.203: ISAKMP:(1001):beginning Quick Mode exchange, M-ID of 1780039293
*Mar 11 02:14:55.203: ISAKMP:(1001):QM Initiator gets spi
*Mar 11 02:14:55.203: ISAKMP:(1001): sending packet to 10.94.200.47 my_port 500 peer_port 500 (I) QM_IDLE      
*Mar 11 02:14:55.203: ISAKMP:(1001):Sending an IKE IPv4 Packet.
*Mar 11 02:14:55.203: ISAKMP:(1001):Node 1780039293, Input = IKE_MESG_INTERNAL, IKE_INIT_QM
*Mar 11 02:14:55.203: ISAKMP:(1001):Old State = IKE_QM_READY  New State = IKE_QM_I_QM1
*Mar 11 02:14:55.203: ISAKMP:(1001):Input = IKE_MESG_INTERNAL, IKE_PHASE1_COMPLETE
*Mar 11 02:14:55.203: ISAKMP:(1001):Old State = IKE_P1_COMPLETE  New State = IKE_P1_COMPLETE 

*Mar 11 02:14:55.207: ISAKMP (1001): received packet from 10.94.200.47 dport 500 sport 500 Global (I) QM_IDLE      
*Mar 11 02:14:55.207: ISAKMP:(1001): processing HASH payload. message ID = 1780039293
*Mar 11 02:14:55.207: ISAKMP:(1001): processing SA payload. message ID = 1780039293
*Mar 11 02:14:55.207: ISAKMP:(1001):Checking IPSec proposal 1
*Mar 11 02:14:55.207: ISAKMP: transform 1, AH_SHA
*Mar 11 02:14:55.207: ISAKMP:   attributes in transform:
*Mar 11 02:14:55.207: ISAKMP:      encaps is 1 (Tunnel)
*Mar 11 02:14:55.207: ISAKMP:      SA life type in seconds
*Mar 11 02:14:55.207: ISAKMP:      SA life duration (basic) of 3600
*Mar 11 02:14:55.207: ISAKMP:      SA life type in kilobytes
*Mar 11 02:14:55.207: ISAKMP:      SA life duration (VPI) of  0x0 0x46 0x50 0x0 
*Mar 11 02:14:55.207: ISAKMP:      authenticator is HMAC-SHA
*Mar 11 02:14:55.207: ISAKMP:(1001):atts are acceptable.
*Mar 11 02:14:55.207: ISAKMP:(1001):Checking IPSec proposal 1
*Mar 11 02:14:55.207: ISAKMP: transform 1, ESP_3DES
*Mar 11 02:14:55.207: ISAKMP:   attributes in transform:
*Mar 11 02:14:55.207: ISAKMP:      encaps is 1 (Tunnel)
*Mar 11 02:14:55.207: ISAKMP:      SA life type in seconds
*Mar 11 02:14:55.207: ISAKMP:      SA life duration (basic) of 3600
*Mar 11 02:14:55.207: ISAKMP:      SA life type in kilobytes
*Mar 11 02:14:55.207: ISAKMP:      SA life duration (VPI) of  0x0 0x46 0x50 0x0 
*Mar 11 02:14:55.207: ISAKMP:      authenticator is HMAC-SHA
*Mar 11 02:14:55.207: ISAKMP:(1001):atts are acceptable.
*Mar 11 02:14:55.207: ISAKMP:(1001): processing NONCE payload. message ID = 1780039293
*Mar 11 02:14:55.207: ISAKMP:(1001): processing ID payload. message ID = 1780039293
*Mar 11 02:14:55.207: ISAKMP:(1001): processing ID payload. message ID = 1780039293
*Mar 11 02:14:55.207: ISAKMP:(1001): Creating IPSec SAs
*Mar 11 02:14:55.207:         inbound SA from 10.94.200.47 to 10.94.200.37 (f/i)  0/ 0
        (proxy 192.168.99.0 to 192.168.177.0)
*Mar 11 02:14:55.207:         has spi 0xA14845AE and conn_id 0
*Mar 11 02:14:55.207:         lifetime of 3600 seconds
*Mar 11 02:14:55.207:         lifetime of 4608000 kilobytes
*Mar 11 02:14:55.207:         outbound SA from 10.94.200.37 to 10.94.200.47 (f/i) 0/0
        (proxy 192.168.177.0 to 192.168.99.0)
*Mar 11 02:14:55.207:         has spi  0x85C87ECF and conn_id 0
*Mar 11 02:14:55.207:         lifetime of 3600 seconds
*Mar 11 02:14:55.207:         lifetime of 4608000 kilobytes
*Mar 11 02:14:55.207: ISAKMP:(1001): Creating IPSec SAs
*Mar 11 02:14:55.207:         inbound SA from 10.94.200.47 to 10.94.200.37 (f/i)  0/ 0
        (proxy 192.168.99.0 to 192.168.177.0)
*Mar 11 02:14:55.207:         has spi 0x87C3AC12 and conn_id 0
*Mar 11 02:14:55.207:         lifetime of 3600 seconds
*Mar 11 02:14:55.207:         lifetime of 4608000 kilobytes
*Mar 11 02:14:55.207:         outbound SA from 10.94.200.37 to 10.94.200.47 (f/i) 0/0
        (proxy 192.168.177.0 to 192.168.99.0)
*Mar 11 02:14:55.207:         has spi  0xFD71F9A9 and conn_id 0
*Mar 11 02:14:55.207:         lifetime of 3600 seconds
*Mar 11 02:14:55.207:         lifetime of 4608000 kilobytes
*Mar 11 02:14:55.207: ISAKMP:(1001): sending packet to 10.94.200.47 my_port 500 peer_port 500 (I) QM_IDLE      
*Mar 11 02:14:55.207: ISAKMP:(1001):Sending an IKE IPv4 Packet.
*Mar 11 02:14:55.207: ISAKMP:(1001):deleting node 1780039293 error FALSE reason "No Error"
*Mar 11 02:14:55.207: ISAKMP:(1001):Node 1780039293, Input = IKE_MESG_FROM_PEER, IKE_QM_EXCH
R1(config)#
*Mar 11 02:14:55.207: ISAKMP:(1001):Old State = IKE_QM_I_QM1  New State = IKE_QM_PHASE2_COMPLETE

3. Next step is to install Certifications from Verisign Trial Site based on the steps on my previous post:



@R1 and @R2

crypto isakmp policy 5
 group 2

4. Last Step is to do testing:

clear crypto sa

16th-Markham#show crypto isakmp sa 
IPv4 Crypto ISAKMP SA
dst             src             state          conn-id status
10.94.200.37      10.94.200.47      QM_IDLE           9031 ACTIVE


16th-Markham#show crypto isakmp sa  detail
Codes: C - IKE configuration mode, D - Dead Peer Detection
       K - Keepalives, N - NAT-traversal
       T - cTCP encapsulation, X - IKE Extended Authentication
       psk - Preshared key, rsig - RSA signature
       renc - RSA encryption
IPv4 Crypto ISAKMP SA

C-id  Local           Remote          I-VRF  Status Encr Hash   Auth DH Lifetime Cap.

10.94.200.37      10.94.200.47             ACTIVE des  sha    rsig 2  23:56:03     
       Engine-id:Conn-id =  SW:31

5. Notes:

a. We should note that ISAKMP Phase 1 policy is defined globally. This means that if we have five different remote sites and configured five different ISAKMP Phase 1 policies (one for each remote router), when our router tries to negotiate a VPN tunnel with each site it will send all five policies and use the first match that is accepted by both ends.

b. If your router does not have Internet Access to fetch CRL list, you will have to put following command into your trustpoint:
revocation-check none

c. Debug Commands
  • show crypto session
  • clear crypto sa
  • show crypto pki certificate



Thursday, September 12, 2013

Using Symantec Verisign PKI to authenticate Checkpoint Site-to-Site IPSec VPN

This lab will use Symantec Verisign Trial SSL Certificate and Checkpoint R76 installed on VMware to demonstrate the steps how to use external OPSEC PKI to authenticate IPSec VPN Tunnel

Topology:
The goal is to ping from 192.168.177.1 to 192.168.99.1 with RSA signature authentication method.



1. Create a VPN community 
Create a VPN community for both firewalls without use external trusted third party PKI. Since both firewalls are managed by same management server, they will automatically use internal.ca to do authentication.
a. Create a VPN community with default settings. Add both firewalls cpmodule (vpn1) and cp_2 (vpn2) into participating gateways list.
b. Confirm they will use any of its certificate.

c. Create firewall rules
Those rules allow traffic encrypted to pass through vpn tunnel

d. verify by ping from one end to another end.

2. Import Symantec Verisign Trial Root CA and Intermediate CA certificates
a. Download both CA certificates from website URL:
https://knowledge.verisign.com/support/ssl-certificates-support/index?page=content&actp=CROSSLINK&id=AR1738

you will find link for both CA certificates:


b. Add them into servers tab:



3. Create CSR on both firewalls.
a. Add a new certificate, then select verisigntrialinternediate as enroll source. Click generate to generate CSR. Use view to check CSR and save it to a file.
 DN: CN=vpn.yourdomain.com,O=Your Company,L=City,ST=Ontario,C=CA
note: ST has to be full name of province. You can not use ON to replace Ontario



4. Submit CSR to Get your Signed Certificates
Go to Verisign free trail web page to apply the certificate with CSR you just saved.
https://trustcenter.websecurity.symantec.com/process/retail/trial_product_selector?uid=d6f070aaef900487ba6bf0edafdaa23c&locale=VRSN_US&language=en
It will expire in 30 days, but should be enough for a lab to prove your concept.


At final step , it will notify you the order number and tell you a email will send to you with approved certificate in it. It may take 8 hours to delivery it.
Also you always can check status of your order at http://www.verisign.com/status
you can check if you request has been approved or not, also if certificate issued.

5. Complete your CSR request and import certificates into your firewall.

Click complete on your firewall IPsec VPN tab. Select the file which Verisign sent to you in the email.

6. Change firewall authentication method to use Verisign CA PKI.
Do it on both firewalls.

7. Push firewall policy on both firewalls. 
Use ping to do test and check logs from Smartview Tracker. It will still have CRL retrieval error. After fixed that, you should be able to see traffic going through tunnel without problem.


Reference:

Wednesday, September 11, 2013

TekRADIUS Usage for AD Authentication

TekRADIUS is a RADIUS software which can be easily integrated with AD. I have tested on one of pc , which even it is not in the domain. But AD authentication is still working, but not with group property.
Here are some configuration settings:

I set up two groups. One is admin group with privilege 15. Another is admin-read group.
 Authentication-Method, I select Active Directory with server ip 10.94.16.242.
 Clients is default, which means any. Secret is cisco.
 Please make sure Vendor ID 42214 kaplansoft is in this dictionary editor. The version I download from website is not including this. I requested it from the discussion board.
 Authentication port is set to 1812 and Accounting port is 1645. debug logging is for troubleshooting, although not too much info in there.

Configuration on the Radius Clients:
1. Checkpoint SmartDashboard: host_mgmt_1 is the RADIUS server ip address.
Create a new administrator with exactly same name as your AD account. Of course please choose authentication method as RADIUS.


2. Juniper NSM:

Similar as checkpoint configuration. Create a new authentication nserver then add a same ad name account with Remote authenticated.