Pages

Thursday, October 9, 2014

Juniper UAC Appliance IC4500 Step by Step Configuration (Part 1) - Basic Configuration

If not sure what is Juniper UAC Products, Here is the URL for review
http://www.juniper.net/us/en/products-services/security/uac/ic4500/

Actually there is similar Juniper Secure Access / SSL vpn product introduced before here.
Just recently configured an IC4500 to implementation access control. Here is some steps to share out. Hopefully it can save some others time for their task.

1. Log into system


2. Upgrade Package 

Upgrade it to latest version 4.2.R1 build 19091. It can be done from Maintenance->System-> Upgrade/Downgrade:

3. Set up Internal Port network info while others can keep default settings.

4. Licensing

5. Add a new Infranet Enforcer


6. Configure SRX to interact with IC4500

root@fw-srx1-1> show configuration services
unified-access-control {
    infranet-controller ic4500 {
        address 10.9.0.6;
        interface reth0.2;
        password "$9$f5F/CA0hSeO1eWx7sn/9A1R"; ## SECRET-DATA
    }
    inactive: test-only-mode;
}

Note: Updated on Oct 25 2012, Interface reth5.200 can not be in any routing instance except the main one.  By the way, you also can use fxp interface to do connection with UAC device (Updated Feb 24 2016)

{primary:node1}
admin@fw-trn1-2> show services unified-access-control status    
node1:
--------------------------------------------------------------------------
Host           Address         Port   Interface     State
ic4500         10.9.0.6      11123   fxp0.0        connected

7. Create new Users Realms

8 Create new User Role

9. Enable Agentless Access and Disable Agent Odyssey Access

In this case, only agentless method used.


10. Create User Sign in Page



11. Create user in the Users tab under Auth. Servers menu


12. Access Authentication Page

At this moment, all basic setup has been finished. User created, and can be authenticated by accessing url https://10.9.2.14/users webpage.

13. Grant User to Access Resources

Last step is to tell how UAC going to grant access to resource. Go to Infranet Enforcer ->Resource tab, click button New Policy to create one:

14. Done, testing




Reference:


Friday, October 3, 2014

Creating Checkpoint VSX and Virtual System - Part 2 - VSX Deployment Example

This lab is an example for a typical VSX Deployment scenario - one shared external Interface to Internet and separate Internal interfaces for each VSX virtual firewall.

This lab also is second part of earlier post :
Creating Checkpoint VSX and Virtual System - Part 1 

In that previous post, it already shows how to create a new VSX gateway through SmartConsole. This lab will show the steps how to create two VSX virtual firewalls and how to set up a virtual router. Two internal interfaces will be used to test the traffics from two different networks. 

Topologies:


Basically, in this lab, there is one physical VSX gateway with two logical VSX virtual firewalls. Each virtual VSX virtual firewall has two interfaces , External and Internal.

Steps:


1. Follow the previous post "Creating Checkpoint VSX and Virtual System - Part 1" to add a new VSX gateway into Smart Dashboard.


The new VSX Gateway has four physical interfaces as shown in the following:
  • Eth0 Mgmt:192.168.2.41
  • Eth1 EXT: for 172.17.3.x External Network
  • Eth2 LAN1: for 192.168.99.x - VSX1 Internal Network
  • Eth3 LAN2: for 10.94.200.x - VSX2 Internal Network

After new VSX Gateway (CP-VSX) added into Smart Dashboard, the webUI in browser will show:
Web UI is not supported in VSX mode. Please use Clish for OS configuration.


 2.Adding vsx1 and vsx2 into CP-VSX






3.  Check Network Topologies on both vsx1 and vsx2



Wednesday, October 1, 2014

Mac Address Flapping between ports because of Multiple Checkpoint Cluster on Same Switch and Same Vlan

Our log system shows there are port flapping in one of our switches. Actually it was experienced before when configured ClusterXL. It seems there is another new Checkpoint cluster connecting to same switch and not considering Magic Mac Address Conflicting. Here are the steps to resolve this issue.

1. Symptoms.

Switch Logs: 
655033: .Oct  1 11:48:27.091 EDT: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.0000.fe00 in vlan 3 is flapping between port Gi0/6 and port Po1
655034: .Oct  1 11:48:41.615 EDT: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.0000.fe01 in vlan 3 is flapping between port Gi0/6 and port Gi0/5
655035: .Oct  1 11:48:42.134 EDT: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.0000.fe00 in vlan 3 is flapping between port Gi0/6 and port Po1
655036: .Oct  1 11:48:57.030 EDT: %SW_MATM-4-MACFLAP_NOTIF: Host 0000.0000.fe01 in vlan 3 is flapping between port Gi0/6 and port Gi0/5

2. Solutions

Basically it is caused by multiple Checkpoint ClusterXL firewalls connecting to same switch and same vlan. It is well described at SK25977. Based on your ClusterXL configuration, either Load Sharing or High Availability mode, either Mulitcast or BroadCast mode, you will have to change magic Source Mac Address or Destination Mac Address. In my case, it is using High Avaliability ClusterXL mode, Magic Source Mac Address change will resolve this issue.

a. Verify the magic mac addresses on both cluster members

[Expert@CP1:0]# fw ctl get int fwha_mac_magic
fwha_mac_magic = 254
[Expert@CP1:0]# fw ctl get int fwha_mac_forward_magic
fwha_mac_forward_magic = 253

[Expert@cp2:0]# fw ctl get int fwha_mac_magic
fwha_mac_magic = 254
[Expert@cp2:0]# fw ctl get int fwha_mac_forward_magic
fwha_mac_forward_magic = 253

b. Change the magic mac addresses on both cluster members

[Expert@CP1:0]# fw ctl set int fwha_mac_magic 40
[Expert@CP1:0]# fw ctl set int fwha_mac_forward_magic 41

[Expert@cp2:0]# fw ctl set int fwha_mac_magic 40
[Expert@cp2:0]# fw ctl set int fwha_mac_forward_magic 41

c. Make a permanent change on booting configuration file

Previous changes are on the fly and taking effect right away, but not able to survive a reboot. To make those change saved to survive reboot, booting configuration file has to be changed with following instructions.

Edit the $FWDIR/boot/modules/fwkern.conf file in Vi editor:

[Expert@CP1:0]# cd /opt/CPsuite-R77/fw1/boot/modules/
[Expert@CP1:0]# vi fwkern.conf


Add the following line (spaces are not allowed):

fwha_mac_magic=40
fwha_mac_forward_magic=41


Reboot each cluster member one by one.

3. Reference:

Monday, September 29, 2014

GNS3 VoIP Lab (Cisco 3725 and CME 4.3)

Here is a simple VoIP Lab in GNS3 environment. It is only used for my lab test and recorded here for future reference.

1. Topology:

  • GNS3 Topology:


  • Logic Topology:
xp(192.168.2.60)--------C3725 Router(192.168.2.10)

2. Enviroment:


    •  Router 3725 R1's configuration in GNS3. Flash card is 32 96 MB to hold CME4.3 files.


3.  Basic Networking Setup 

  • @R1 : Show Version Information for C3725-AdventerpriseK9_IVS-M IOS, Version 12.4(15)T9.
  • @R1, Basic TCP configuration:
interface FastEthernet0/0
 ip address 192.168.2.10 255.255.255.0
 duplex auto
 speed auto
  • By default, telephony-service is not enabled: 
R1#show telephony-service
telephony-service is not enabled
  • Enable Telephony-Service by configure some commands under telephony-service.

4. Install CME on GNS3 3725 Router

  • Set up Environment:
    • C3725 Router ip is 192.168.2.10
    • XP Machine with TFTPD ip is 192.168.2.60
  • Copy cme-full-4.3.0.0.tar into C3725 Router. I tried another tftp server Pumpkin, but it gave me an error. FTP service should be faster than tftp. TFTP took 1 hour and 44 minutes to get whole package extracted. This lab is using tftp to make things simple. From C3725 router, run following three commands:
erase flash:
format flash:
archive tar /xtract tftp://192.168.2.60/cme-full-4.3.0.0.tar flash:



To be Continued:::



Notes:



Reference:

  • http://resources.intenseschool.com/ccna-voice-labs-in-gns3-with-vtgo-pc-multilab/
  • http://ciscoshizzle.blogspot.de/2012/06/cisco-voice-lab-using-gns3.html
  • http://www.i-1.nl/blog/?p=145




Friday, September 26, 2014

Shellshock (Bash Computer Bug) Exploited - Responding from Venders


Heartbleed Extension Vulnerability caused lots of worries for Internet system. The affects still do not go away and now Shellshock coming.  This latest vulnerability affects the command line software Bash operating at Linux , Unix and Mac OS X.


Vendors have been posting the patches and suggestions on their websites already. Here is some quick collections for my environment.


1. Checkpoint's Responding:

https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk102673

2. Cisco's Responding: 

http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20140926-bash

3. Juniper's Responding:

https://kb.juniper.net/InfoCenter/index?page=content&id=JSA10648&actp=RSS

4. Vmware:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2090740


Note: How it happened? (from Symantec)

An attacker can potentially use CGI to send a malformed environment variable to a vulnerable Web server. Because the server uses Bash to interpret the variable, it will also run any malicious command tacked-on to it.