9 Caching Proxy Server

Total Page:16

File Type:pdf, Size:1020Kb

9 Caching Proxy Server webXaccelerator: Owner's Guide by Luis Soltero, Ph.D., MCS Revision 1.06 February 10, 2010 (v1.2.3.10-RELEASE) Copyright © 2010 Global Marine Networks, LLC Table of Contents 1 Quick Start..............................................................................................................................................5 2 Introduction.............................................................................................................................................8 3 Initial Installation and Configuration......................................................................................................9 3.1 Connections.....................................................................................................................................9 3.2 Power-up..........................................................................................................................................9 3.3 Power-down...................................................................................................................................10 3.4 Web Administrator........................................................................................................................10 3.5 LAN Setup.....................................................................................................................................10 3.6 WAN Setup....................................................................................................................................11 3.7 WAN2 (Backup WAN) Setup........................................................................................................13 3.8 WiFi Hotspot Setup.......................................................................................................................13 3.9 Backup/Restore System Configuration.........................................................................................14 3.10 Locking the Console....................................................................................................................15 4 Time......................................................................................................................................................15 4.1 NTP Client.....................................................................................................................................15 4.2 NTP Server....................................................................................................................................15 4.3 Configuring NTP time client on PCs.............................................................................................16 4.3.1 Enabling NTP Client on a Windows PC................................................................................16 4.3.2 Enabling NTP Client on a Mac..............................................................................................16 4.4 Internet Polling Interval.................................................................................................................16 5 Firewall Rules - Block Unwanted Traffic to/from the Internet.............................................................17 5.1 System vs. User Generated Firewall Rules...................................................................................19 6 VPN access through WAN....................................................................................................................19 6.1 Enabling PPTP..............................................................................................................................19 6.2 Windows 7 PPTP Client Setup......................................................................................................20 6.3 Mac OS X Client Setup.................................................................................................................21 7 Captive Portal........................................................................................................................................22 7.1 Limitations ...................................................................................................................................26 7.2 Setting up the Captive Portal.........................................................................................................26 7.3 Bypassing the Captive Portal........................................................................................................27 7.4 Setting up for the Buy Now links..................................................................................................27 7.5 Pincode Restrictions......................................................................................................................29 8 Assigning Static IP addresses to PCs on the LAN/WLAN...................................................................29 9 Caching Proxy Server...........................................................................................................................30 9.1 Limitations.....................................................................................................................................30 9.2 Customizing the Proxy Server.......................................................................................................31 9.2.1 General Settings.....................................................................................................................31 9.2.2 Bypassing Proxy for access to Satellite Terminals................................................................31 9.2.3 Custom Option.......................................................................................................................32 9.2.4 Caching Options....................................................................................................................32 9.2.5 Traffic Management...............................................................................................................33 9.3 XWeb Compression.......................................................................................................................33 9.3.1 Requirements.........................................................................................................................33 9.3.2 Limitations.............................................................................................................................33 9.3.3 Configuration.........................................................................................................................34 9.4 Transparent vs. Manual Proxy.......................................................................................................34 9.4.1 Configuring Client Browsers for Manual Proxy...................................................................35 9.4.2 Automatic Proxy Configuration............................................................................................36 9.4.3 Dynamically Disabling Web Compression............................................................................36 10 Controlling Access to the Web............................................................................................................37 10.1 Blacklists.....................................................................................................................................38 10.2 Dynamic Content Filtering..........................................................................................................39 10.3 Custom Destinations....................................................................................................................39 10.4 ACL.............................................................................................................................................40 10.5 Whitelists.....................................................................................................................................41 10.6 Don't forget to Apply..................................................................................................................41 11 Web Logging.......................................................................................................................................41 12 Disabling Skype and other p2p applications.......................................................................................43 13 Failover from primary to backup satellite link....................................................................................44 13.1 Scheme 1 - Client Based DNS Lookups.....................................................................................45 13.2 Scheme 2 - Static Routes to DNS Servers...................................................................................45 13.3 Configuring Failover Pool...........................................................................................................46 13.4 Policy Based Routing..................................................................................................................48 13.5 Failover and Firewall Rules........................................................................................................48 13.6 Failover and Captive Portal.........................................................................................................49 13.7 Failover and Proxy Web Services................................................................................................49 13.8 Manual Failover..........................................................................................................................50
Recommended publications
  • Technical Impacts of DNS Privacy and Security on Network Service Scenarios
    - Technical Impacts of DNS Privacy and Security on Network Service Scenarios ATIS-I-0000079 | April 2020 Abstract The domain name system (DNS) is a key network function used to resolve domain names (e.g., atis.org) into routable addresses and other data. Most DNS signalling today is sent using protocols that do not support security provisions (e.g., cryptographic confidentiality protection and integrity protection). This may create privacy and security risks for users due to on-path nodes being able to read or modify DNS signalling. In response to these concerns, particularly for DNS privacy, new protocols have been specified that implement cryptographic DNS security. Support for these protocols is being rapidly introduced in client software (particularly web browsers) and in some DNS servers. The implementation of DNS security protocols can have a range of positive benefits, but it can also conflict with important network services that are currently widely implemented based on DNS. These services include techniques to mitigate malware and to fulfill legal obligations placed on network operators. This report describes the technical impacts of DNS security protocols in a range of network scenarios. This analysis is used to derive recommendations for deploying DNS security protocols and for further industry collaboration. The aim of these recommendations is to maximize the benefits of DNS security support while reducing problem areas. Foreword As a leading technology and solutions development organization, the Alliance for Telecommunications Industry Solutions (ATIS) brings together the top global ICT companies to advance the industry’s business priorities. ATIS’ 150 member companies are currently working to address network reliability, 5G, robocall mitigation, smart cities, artificial intelligence-enabled networks, distributed ledger/blockchain technology, cybersecurity, IoT, emergency services, quality of service, billing support, operations and much more.
    [Show full text]
  • Captive Portal Detection Error May Be Triggered If There Is HTTP 302 Response Code Received PRS-325375 While Connecting to IVE
    Pulse Connect Secure Release Notes 8.1 R4 Build 37085: July 2015 Revision 01 Contents Introduction......................................................................................................................... 1 Interoperability and Supported Platforms ............................................................................ 2 Noteworthy changes in 8.1r4 Release ................................................................................ 2 Problems Resolved in 8.1R4 Release ................................................................................ 2 Known Issues in 8.1R3.2 release ....................................................................................... 4 Problems Resolved in 8.1R3.1 Release ............................................................................. 4 Pulse Connect Secure New Features in 8.1R3 ................................................................... 5 Noteworthy changes in this Release................................................................................... 6 Problems Resolved in 8.1R3 Release ................................................................................ 6 Known Issues in this release .............................................................................................. 7 Pulse Connect Secure Access New Features in 8.1R2 Release ........................................ 8 Disable TLS 1.0 ....................................................................................................... 8 New Functionality to create role mapping rules
    [Show full text]
  • Filtering and Identifying Web Activity by User Name
    Wavecrest®TechBrief Filtering and Identifying Web Activity by User Name www.wavecrest.net When a company implements a Web filtering and monitoring solution, it typically wants to filter and monitor the Web traffic flowing through its network by user name versus IP address for various reasons. Some of these reasons include curtailing casual surfing, protecting against security threats, and conserving bandwidth. Furthermore, a company’s Acceptable Use Policy (AUP) is usually based on user names and/or groups of user names. Therefore, the application that enforces and monitors the company’s AUP needs to identify Web activity by user name. IP addresses can be dynamic, and sometimes more than one employee can log on to a computer, and hence, more than one user name will be using the same IP address. Many an IT administrator is tasked with ensuring that the company’s employees are going through the proxy that is in place, so that Web activity can be monitored by user name. To get user names and authenticate users, IT administrators can choose any of the proxy configuration options and authentication methods described below. Depending on the company’s preference, one proxy configuration option may be more favorable than the other. Here, we will discuss applying browser settings manually, pushing out group policies using Active Directory (AD), using a captive portal, and installing client software. We will also touch on the different ways that you can authenticate your Internet users using our CyBlock products. Applying Browser Settings Manually Applying browser settings involves identifying a proxy server which is required if you need user names.
    [Show full text]
  • Tunneled Internet Gateway Wi-Fi Access for Mobile Devices in High-Security Environments Table of Contents
    WHITE PAPER TUNNELED INTERNET GATEWAY Wi-FI ACCESS FOR MOBILE DEVICES IN High-SECURitY ENVIRONMENTS TABLE OF CONTENTS THE ChALLENGE: Wi-FI ACCESS FOR MOBILE DEVICES IN high-SECURitY ENVIRONMENTS 3 ARUBA TUNNELED INTERNET GATEWAY SOLUtiON 3 HOW thE TUNNELED INTERNET GATEWAY WORKS 3 APPENDIX 5 TOPOLOGY DIAGRAMS 8 ABOUT ARUBA NETWORKS, INC. 9 WHITE PAPER TUNNELED INTERNET GATEWAY THE CHALLENGE: WI-FI ACCESS FOR MOBILE HOW THE TUNNELED INTERNET GATEWAY WORKS DEVICES IN HIGH-SECURITY ENVIRONMENTS Summary Since the debut of the iPhone in 2007, the private sector The Tunneled Internet Gateway is enabled through software has seen a proliferation of personal mobile devices used in configuration to any new or existing controller-based Aruba the workplace. Government customers, while slower to WLAN. Mobile users connect their devices to the Internet adopt commercially available mobile devices in the gateway SSID, creating an encrypted session with an Aruba workplace, recognize the cost and productivity advantages Mobility Controller deployed in the restricted network. and are looking for ways to increase their usage and speed- up adoption. The controller maintains logical separation between Internet sessions and restricted sessions using a Common Criteria Many civilian and military organizations have already begun EAL4+ validated firewall, then routes Internet traffic through large-scale acquisitions of commercial off-the-shelf (COTS) an additional encrypted data tunnel to a router attached to a mobile devices for distribution to relevant personnel. The commercial Internet service provider. The result is a secure, February 2013 purchase by the U.S. Department of Defense simple and low-cost network overlay with strong separation of 630,000 Apple iOS-based mobile devices is just one between restricted and Internet data.
    [Show full text]
  • Anyconnect Captive Portal Detection and Remediation
    Contents Introduction Prerequisites Requirements Components Used Background Information Captive Portal Remediation Requirements Captive Portal Hotspot Detection Captive Portal Hotspot Remediation False Captive Portal Detection AnyConnect Behavior Captive Portal Incorrectly Detected with IKEV2 Workarounds Disable the Captive Portal Feature Introduction This document describes the Cisco AnyConnect Mobility Client captive portal detection feature and the requirements for it to function correctly. Many wireless hotspots at hotels, restaurants, airports, and other public places use captive portals in order to block user access to the Internet. They redirect HTTP requests to their own websites that require users to enter their credentials or acknowledge terms and conditions of the hotspot host. Prerequisites Requirements Cisco recommends that you have knowledge of the Cisco AnyConnect Secure Mobility Client. Components Used The information in this document is based on these software versions: ● AnyConnect Version 3.1.04072 ● Cisco Adaptive Security Appliance (ASA) Version 9.1.2 The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command. Background Information Many facilities that offer Wi-Fi and wired access, such as airports, coffee shops, and hotels, require users to pay before they obtain access, agree to abide by an acceptable
    [Show full text]
  • Configuracion De Un Servidor Proxy Para Filtrado De Contenidos Web En Ubuntu Linux
    Configuracion de un Servidor Proxy para Filtrado de Contenidos Web en Ubuntu Linux ¿Qué es un Proxy? «Proxy» tiene un significado muy general y al mismo tiempo ambiguo, sinónimo del concepto de «Intermediario». Se suele traducir como delegado o apoderado. Un Servidor Intermediario (Proxy) se define como una computadora o dispositivo que ofrece un servicio de red que consiste en permitir a los clientes realizar conexiones de red indirectas hacia otros servicios de red. Durante el proceso ocurre lo siguiente: -Cliente se conecta hacia un Servidor Intermediario (Proxy). -Cliente solicita una conexión, fichero u otro recurso disponible en un servidor distinto. -Servidor Intermediario (Proxy) proporciona el recurso ya sea conectándose hacia el servidor especificado o sirviendo éste desde un caché. -En algunos casos el Servidor Intermediario (Proxy) puede alterar la solicitud del cliente o bien la respuesta del servidor para diversos propósitos. Los Servidores Intermediarios (Proxies) generalmente se hacen trabajar simultáneamente como muro cortafuegos operando en el Nivel de Red, actuando como filtro de paquetes, como en el caso de IPTABLES, o bien operando en el Nivel de Aplicación, controlando diversos servicios, como es el caso de TCP Wrapper. Dependiendo del contexto, el muro cortafuegos también se conoce como BPD o Border Protection Device o simplemente filtro de paquetes. Tipos de Proxy ● Proxy de web / Proxy cache de web ● Proxies transparentes ● Reverse Proxy ● Proxy NAT (Network Address Translation) / Enmascaramiento ● Proxy Abierto ¿Que es Squid? Squid es un programa de software libre que implementa un servidor proxy y un demonio para caché de páginas web. Está especialmente diseñado para ejecutarse bajo entornos tipo Unix.
    [Show full text]
  • Browser History Stealing with Captive Wi-Fi Portals
    Browser History Stealing with Captive Wi-Fi Portals Adrian Dabrowski, Georg Merzdovnik, Nikolaus Kommenda, Edgar Weippl [email protected] Twitter: @atrox_at 2016-05-26 Public Wi-Fi Hotspots ● Like a well in a village Internet ● We gather there, pull up a bucket or two of “Internet” ● Look at the sign from the sponsor ● … and move on. What is a “Captive Portal”? Why Captive Portal ● Omnipresent in Wi-Fi Hotspots ● Used by you probably right now (in this very hotel) ● Has an elevated position on the network ● Man-in-the-Middle by design ● Sponsors of a Wi-Fi want us to see their messages (and accept the disclaimer) ● There is no standard for that ● Let's inject it into your traffic… Browser History Stealing, again? ● Baron, 2002 ● :visited link color TODO: ● Ruderman, 2000 Groundhog ● :visited can load images ● Jang, 2010 ● Sites are actively trying to steal history History, so what? ● Culture & Language ● Amazon.fr, Amazon.jp ● Sexual orientation ● grindr.com, transblog.de ● Other websites that give ● Partnership status interesting insights ● Okcupid.com, parship.com ● Medical conditions ● Employer ● Political campaigns ● intranet.ibm.com ● Religious communities Source: MindSource April 1996 BOF; Client State Tracking with Netscape Cookies; M. Strata Rose; [email protected] Source: MindSource April 1996 BOF; Client State Tracking with Netscape Cookies; M. Strata Rose; [email protected] Cookies (or not enough state for HTTP) ● Two kinds ● Session cookies: usually forgotten when browser closed ● Persistent cookies: stored on disk with expiry date ● Only depend on the FQDN and Protocol ● XSS ● XSRF ● HTTP set cookie also used for HTTPS – Insecure set cookies mixed into the cookies over HTTPS http://cnn.com (+cookies) 302 redirect login.hotspotsys.com/login login.hotspotsys.com/login <html>….
    [Show full text]
  • Captive Portal
    User module Captive Portal APPLICATION NOTE USED SYMBOLS Used Symbols Danger – important notice, which may have an influence on the user’s safety or the function of the device. Attention – notice on possible problems, which can arise in specific cases. Information, notice – information, which contains useful advice or special interest. GPL License Source codes under GPL license are available free of charge by sending an email to: [email protected]. Conel s.r.o., Sokolska 71, 562 04 Usti nad Orlici, Czech Republic Manual issued in CZ, October 6, 2014 i CONTENTS Contents 1 Description of user module 1 2 Configuration 2 2.1 Global ......................................... 2 2.2 Welcome page .................................... 4 2.3 QoS .......................................... 4 3 How to create own welcome page 6 3.1 Simple page ...................................... 6 3.2 Login page ...................................... 6 3.3 Ban page ....................................... 7 3.4 Customized original URL .............................. 7 3.5 Example ........................................ 7 4 Status Overview 9 5 Recommended literature 10 ii LIST OF FIGURES List of Figures 1 Web Interface ..................................... 1 2 Global configuration form .............................. 3 3 Welcome page configuration form ......................... 4 4 QoS configuration form ............................... 5 iii LIST OF TABLES List of Tables 1 Available services .................................. 9 2 Connected customers ................................ 9 iv 1. DESCRIPTION OF USER MODULE 1. Description of user module User module Captive Portal is not contained in the standard router firmware. Uploading of this user module is described in the Configuration manual (see [1, 2]). Please note that this module is compatible only with firmware 4.0.0 or later in v2 routers! The user module is v3 routers platform compatible.
    [Show full text]
  • Securing Debian Manual
    Securing Debian Manual Javier Fernández-Sanguino Peña <[email protected]> ‘Authors’ on this page Version: 3.13, Sun, 30 Jan 2011 19:58:16 +0000 Abstract This document describes security in the Debian project and in the Debian operating system. Starting with the process of securing and hardening the default Debian GNU/Linux distribu- tion installation, it also covers some of the common tasks to set up a secure network environ- ment using Debian GNU/Linux, gives additional information on the security tools available and talks about how security is enforced in Debian by the security and audit team. Copyright Notice Copyright © 2002-2007 Javier Fernández-Sanguino Peña Copyright © 2001 Alexander Reelsen, Javier Fernández-Sanguino Peña Copyright © 2000 Alexander Reelsen Some sections are copyright © their respective authors, for details please refer to ‘Credits and thanks!’ on page 28. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version 2 (http://www.gnu.org/licenses/ old-licenses/gpl-2.0.html) or any later version (http://www.gnu.org/copyleft/ gpl.html) published by the Free Software Foundation. It is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY. Permission is granted to make and distribute verbatim copies of this document provided the copyright notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this document under the conditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one.
    [Show full text]
  • Captive Portal Authentication Via Facebook
    Grandstream Networks, Inc. Captive Portal Authentication via Facebook Table of Content SUPPORTED DEVICES ................................................................................................ 4 INTRODUCTION ............................................................................................................ 5 CAPTIVE PORTAL SETTINGS ..................................................................................... 6 Policy Configuration Page ................................................................................................................7 Landing Page Redirection ....................................................................................................... 10 Pre-Authentication Rules ........................................................................................................ 10 Post-Authentication Rules ....................................................................................................... 10 Guest Page ................................................................................................................................... 11 CONFIGURATION STEPS........................................................................................... 12 Create Facebook App .................................................................................................................... 12 Configure Captive Portal Policy with Facebook Authentication ....................................................... 17 Using GWN Master GUI (Standalone mode) ..........................................................................
    [Show full text]
  • Browser History Stealing with Captive Wi-Fi Portals
    Browser History Stealing with Captive Wi-Fi Portals Adrian Dabrowski∗, Georg Merzdovnik∗, Nikolaus Kommenday and Edgar Weippl∗ ∗SBA Research, Vienna, Austria Email: [email protected] yTechnische Universitat¨ Wien, Vienna, Austria Email: [email protected] Abstract—In this paper we show that HSTS headers and in public Wi Fi hotspot systems such as cafes,´ restaurants, long-term cookies (like those used for user tracking) are so airports, and hotels. The user is informed about the spon- prevailing that they allow a malicious Wi-Fi operator to gain significant knowledge about the past browsing history of users. sor of the access, possible restrictions as well as potential We demonstrate how to combine both into a history stealing payment methods and has to accept terms and conditions. attack by including specially crafted references into a captive After completion, the user is given access to the Internet. portal or by injecting them into legitimate HTTP traffic. Especially in transit areas the majority of users use hand-held Captive portals are used on many Wi-Fi Internet hotspots to devices such as tablets and smart phones. Additionally, these display the user a message, like a login page or an acceptable use policy before they are connected to the Internet. They are devices automatically connect to known Wi Fi access points. typically found in public places such as airports, train stations, or We specifically elaborate on these cases and their implications. restaurants. Such systems have been known to be troublesome for Public hotspots have been known to be troublesome in many many reasons.
    [Show full text]
  • Post-Hearing Comments on Exemption to Prohibition On
    1 UNITED STATES COPYRIGHT OFFICE Rulemaking on Exemptions from Prohibition on Circumvention of Technological Measures that Control Access to Copyrighted Works Docket No. RM 2002-4 RESPONSE TO WRITTEN QUESTIONS OF JUNE 5, 2003 of N2H2, INC., 8e6 Technologies, Bsafe Online Submitted by: David Burt June 30, 2003 N2H2, Inc. 900 4th Avenue, Suite 3600 Seattle, WA 98164 Tel: (206) 982-1130; Fax: (509) 271-4226 Email: [email protected] 2 The Question Posed by the Copyright Office 3 Problems with Narrowing the Exemption to Exclude "Security Suites" 5 First Amendment Concerns Expressed by Proponents are Misplaced 8 Concerns that CIPA Requires Schools and Libraries to Use "Closed Lists" are Misplaced 9 Opponents Do Not Believe the Record Justifies an Exemption 11 The Threats Posed by the Exemption are Real 18 Conclusion 19 Footnotes 20 3 The Question Posed by the Copyright Office On June 5th, 2003, the Copyright Office asked the opponents of the proposed exemption for "Compilations consisting of lists of websites blocked by filtering software applications" for our response to the following: Please clarify, as specifically as possible, the types of applications you believe should or should not be subject to an exception for the circumvention of access controls on filtering software lists, if such an exception is recommended. Please provide any documentation and/or citations that will support any of the factual assertions you make in answering these questions. The opponents of the exemption do not believe any exemption is justified because there is no supporting record to justify it. The opponents further believe that a narrowed exemption designed to exclude "security suite" applications that include lists of blocked websites would unfairly render the databases of some vendors of lists of blocked websites with protection and others without on an arbitrary basis.
    [Show full text]