Welcome …

Posted on

PrivateInternetAccess SOCKS Proxy Tutorial

PrivateInternetAccess SOCKS Proxy Tutorial – Introduction

In a previous series of articles we looked at how to use Squid Proxy to overcome the five devices maximum limit when subscribed to the PrivateInternetAccess VPN anonymising service. While this is useful when needing to browse anonymously, it doesn’t help when using other non-HTTP protocols  e.g. FTP, SMTP, SSH so to that end we present this PrivateInternetAccess SOCKS Proxy tutorial.

To this end, we need to employ a SOCKS (sockets) proxy: A SOCKS proxy is a general purpose proxy server that establishes a TCP connection to another server on behalf of a client and then routes all the traffic back and forth between the client and the server. It works for any kind of network protocol on any port.

In this tutorial we will be building on parts of the previous tutorial but using the Dante SOCKS proxy instead of Squid.

We will be using:

  • Debian Wheezy netinstall ISO
    • OpenVPN – to create our VPN connection
    • dante – to proxy specific traffic or applications through the VPN

Our network diagram for this example is as follows:

PrivateInternetAccess Using OpenVPN And Squid Proxy

The client is sitting on the 172.16.16.0 network and accessing the proxy in the DMZ 192.168.101.0 subnet. Outgoing traffic will then be routed out through the VPN interface (tun0) encrypted and anonymised.

No related posts.

Posted on

CCSE Revision Questions 156-315.77 – Part 3

CCSE Revision Questions 156-315.77 – Part 3

QUESTION 61

Type the command and syntax that you would use to view the virtual cluster interfaces of a ClusterXL environment.

[su_spoiler title=”Answer:” style=”default”] cphaprob -a if [/su_spoiler]

QUESTION 62

Type the command and syntax to view critical devices on a cluster member in a ClusterXL environment.

[su_spoiler title=”Answer:” style=”default”] cphaprob -ia list [/su_spoiler]

QUESTION 63

Type the command and syntax to configure the Cluster Control Protocol (CCP) to use Broadcast.

[su_spoiler title=”Answer:” style=”default”] cphaconf set_ccp broadcast [/su_spoiler]

QUESTION 64

Fill in the blank. In New Mode HA, the internal cluster IP VIP address is 10.4.8.3. The internal interfaces on two members are 10.4.8.1 and 10.4.8.2 Internal host 10.4.8.108 pings 10.4.8.3, and receives replies.

Review the ARP table from the internal Windows host 10.4.8.108. According to the output, which member is the standby machine?

[su_spoiler title=”Answer:” style=”default”] 10.4.8.1 [/su_spoiler]

QUESTION 65

Fill in the blank. In New Mode HA, the internal cluster IP VIP address is 10.4.8.3. An internal host 10.4.8.108 successfully pings its Cluster and receives replies. Review the ARP table from the internal Windows host 10.4.8.108. Based on this information, what is the active cluster member’s IP address?

[su_spoiler title=”Answer:” style=”default”] 10.4.8.2 [/su_spoiler]

QUESTION 66

Fill in the blank. In Load Sharing Unicast mode, the internal cluster IP address is 10.4.8.3. The internal interfaces on two members are 10.4.8.1 and 10.4.8.2. Internal host 10.4.8.108 Pings 10.4.8.3, and receives replies. The following is the ARP table from the internal Windows host 10.4.8.108. Review the exhibit and type the IP address of the member serving as the pivot machine in the space below.

[su_spoiler title=”Answer:” style=”default”] 10.4.8.2

C:>arp
Interface 10.4.8.108 on interface 0x4

Internet Add Physical Address Type
10.4.8.1 00-b0-d0-b7-b5-d5 dynamic
10.4.8.2 00-01-03-34-e3-9d dynamic
10.4.8.3 00-01-03-34-e3-9d dynamic
[/su_spoiler]

QUESTION 67

To stop acceleration on a GAiA Security Gateway, enter command:

[su_spoiler title=”Answer:” style=”default”] fwaccel off [/su_spoiler]

QUESTION 68

To bind a NIC to a single processor when using CoreXL on GAiA, you would use the command

[su_spoiler title=”Answer:” style=”default”] sim affinity [/su_spoiler]

Related posts:

Posted on

Policy Installation Process

Checkpoint Policy Installation Process

This short article describes the process of policy installation when it is initiated via SmartDashboard.

Policy installation flow:

Assuming the initiation was made by the SmartDashboard, as opposed to using command line options, such as fwm load (on Management Server) or fw fetch (on Security Gateway), the Check Point Management Interface (CPMI) policy installation command is sent to FWM process on the Management Server where the verification and compilation takes place.

  1. FWM process forwards the command to CPD process for code generation and compilation.
  2. CPD process invokes the Check Point Policy Transfer Agent (CPTA) command that sends the policy to all applicable Security Gateways.
  3. CPD process on the Security Gateway receives the policy and verifies its integrity.
  4. FWD process on the Security Gateway updates all of the user-mode processes responsible for enforcement aspects. These include VPND process for VPN issues, FWSSD processes for Security Server issues, and so on. Once complete, the CPD process then initiates the update for Check Point kernel.
  5. The new policy is prepared, and the Check Point kernel halts the current traffic and starts queuing all incoming traffic.
  6. The Atomic Load takes place. This process should take a fraction of a second.
    Note: During Atomic Load, SecureXL is disabled and re-enabled afterwards.
  7. The traffic queue is released, and all of the packets are handled by the new security policy.

No related posts.