Secure Computing SG300 User Manual
  1. Manuals
  2. Brands
  3. Secure Computing Manuals
  4. Gateway
  5. SG300
  6. User manual

Secure Computing SG300 User Manual

Snapgear gateway
Hide thumbs Also See for SG300:
Table of Contents

Advertisement

Quick Links

Secure Computing SnapGear™
User Manual
Secure Computing
4810 Harwood Road
San Jose, CA 95124-5206
Revision 3.1.4
th
Email: support@au.securecomputing.com
August 15
, 2006
Web: www.securecomputing.com
Part Number 86-0945932-A

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the SG300 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Secure Computing SG300

Summary of Contents for Secure Computing SG300

  • Page 1 Secure Computing SnapGear™ User Manual Secure Computing 4810 Harwood Road San Jose, CA 95124-5206 Revision 3.1.4 Email: support@au.securecomputing.com August 15 , 2006 Web: www.securecomputing.com Part Number 86-0945932-A...

  • Page 3: Table Of Contents

    Contents Document Conventions ..................vi Introduction....................1 SG Gateway Appliances (SG3xx, SG5xx Series)..........1 SG Rack Mount Appliances (SG7xx Series) ............4 SG PCI Appliances (SG6xx Series)............... 7 Getting Started..................11 SG Gateway Appliance Quick Setup ..............12 SG Rack Mount Appliance Quick Setup .............. 23 SG PCI Appliance Quick Setup ................
  • Page 4 Routes ....................... 106 System....................... 115 DNS ........................116 DHCP Server ..................... 118 Web Cache ......................123 QoS Traffic Shaping ..................130 IPv6........................133 SIP ........................133 Firewall ....................135 Incoming Access....................135 Web Management ..................... 137 Customizing the Firewall..................140 Definitions ......................140 Packet Filtering ....................
  • Page 5 IPSec Failover ....................238 IPSec Troubleshooting ..................247 Port Tunnels ...................... 250 USB ......................254 USB Mass Storage Devices ................254 USB Printers ...................... 261 Printer Troubleshooting ..................267 USB Network Devices and Modems..............268 System....................269 Date and Time ....................269 Backup/Restore Configuration................

  • Page 6: Document Conventions

    Document Conventions This document uses different fonts and typefaces to show specific actions. Warning/Note Text like this highlights important issues. Bold text in procedures indicates text that you type, or the name of a screen object (e.g. a menu or button).

  • Page 7: Introduction

    SG Gateway Appliances (SG3xx, SG5xx Series) Note The SG gateway appliance range includes models SG300, SG530, SG550, SG560, SG565, SG570, SG575 and SG580. The SG gateway appliance range provides Internet security and privacy of communications for small and medium enterprises, and branch offices.
  • Page 8 The SG565, SG560, SG570, SG575 and SG580 may also connect to a DMZ (demilitarized zone) network. A DMZ is a separate local network typically used to host servers accessible to the outside world. It is separated both physically and by the firewall, in order to shield your LAN from external traffic.
  • Page 9 Label Activity Description WAN Activity Flashing Network traffic on the Internet network interface. WLAN Flashing Network traffic on the Wireless network interface. DMZ Activity Flashing Network traffic on the DMZ network interface. Serial Flashing For either of the SnapGear unit COM ports, these Activity LEDs indicate receive and transmit data.

  • Page 10: Sg Rack Mount Appliances (Sg7Xx Series)

    SG Rack Mount Appliances (SG7xx Series) Note The SG rack mount appliance range includes models SG710 and SG710+. The SG7xx series is the flagship of Secure Computing’s SG family. It features multi-megabit throughput, rack-optimized form factor, two fast Ethernet ports, and two 4-port fast Ethernet switches as standard, and the option for two additional gigabit ports (SG710+).
  • Page 11 Front panel LEDs The front panel contains LEDs indicating status. An example of the front panel LEDs are illustrated in the following figure and detailed in the following table. Label Activity Description Power Power is supplied to the SnapGear unit. H/B (Heart Flashing The SnapGear unit is operating correctly.
  • Page 12 Rear panel The rear panel contains a power switch and a power inlet for an IEC power cable. Additionally, the SG710+ has two gigabit Ethernet ports (E and F). Specifications Internet link Two 10/100baseT Ethernet ports (C, D) Two GbE ports (E, F – SG710+ only) Serial port Online status LEDs (Online, Failover) Ethernet link and activity status LEDs...

  • Page 13: Sg Pci Appliances (Sg6Xx Series)

    SG PCI Appliances (SG6xx Series) Note The SG PCI appliance range includes models SG630 and SG635. The SG PCI appliance is a hardware-based firewall and VPN server embedded in a 10/100 Ethernet PCI network interface card (NIC). It is installed into the host PC like a regular NIC, providing a transparent firewall to shield the host PC from malicious Internet traffic, and VPN services to allow secure remote access to the host PC.
  • Page 14 The other is the host PC's IP address, which is configurable through the host operating system, identically to a regular NIC. This is the IP address that other PCs on the LAN see. It should be dynamically (DHCP) or statically configured to use the same gateway, DNS, etc.
  • Page 15 Location Activity Description Top right Power is supplied to the SnapGear unit (top right). (Power) Bottom right Flashing The SnapGear unit is operating correctly (bottom right). (Heart beat) Top left Flashing Data is being transmitted or received (top left). (Network activity) Bottom left The SnapGear unit is attached to the network.
  • Page 16 Introduction...

  • Page 17: Getting Started

    Getting Started This chapter provides step-by-step instructions for installing your SnapGear unit. These instructions are identical to those in the printed Quick Install Guide that shipped with your SnapGear unit. Upon completing the steps in this chapter, your SG gateway or rack mount appliance is installed in a network configuration similar that depicted in the figure to the right.

  • Page 18: Sg Gateway Appliance Quick Setup

    Power is ON when power is applied (use only the power adapter packaged with the unit). System/Heart Beat/TST flashes when the SnapGear unit is running. Initially, all appliance models except for the SG300 also have all other front panel LEDs flashing.
  • Page 19 LAN settings. Connect the supplied power adapter to the SnapGear unit: If you are setting up the SG300, attach your PC’s network interface card directly to any network port on its LAN switch using the supplied network cable. If you are setting up the SG560, SG565 or SG580, attach your PC’s network interface card directly any network port on switch A (A1 –...
  • Page 20 Click Start > (Settings >) Control Panel and double-click Network Connections (or in 95/98/Me, double-click Network). Right-click Local Area Connection then select Properties. Note If there is more than one existing network connection, select the one corresponding to the network interface card to which the SnapGear unit is attached. Select Internet Protocol (TCP/IP) and click Properties (or in 95/98/Me, TCP/IP >...
  • Page 21 Note If you wish to retain your existing IP settings for this network connection, click Advanced and Add the secondary IP address of 192.168.0.100, subnet mask 255.255.255.0. Set up the SnapGear unit’s password and LAN connection settings Launch your web browser and navigate to 192.168.0.1. Select Quick Setup Wizard from the center of the page.
  • Page 22 The quick setup wizard is displayed. Changing the Hostname is not typically necessary. Select how you would like to set up your LAN connection, then click Next. Note You must select Manual configuration in order to enable the SnapGear unit’s built-in DHCP server.
  • Page 23 If you have an existing DHCP server, and wish to rely on it to automatically configure the SnapGear unit’s LAN connection settings (not recommended), choose to Obtain LAN IP address from a DHCP server on LAN. Skip to the next step 3. 2.
  • Page 24 Set up the SnapGear unit’s Internet connection settings Attach the SnapGear unit to your modem device or Internet connection medium. If necessary, give the modem device some time to power up. Select your Internet connection type and click Next. The options displayed differ depending on the connection type selected.
  • Page 25 Set up the SnapGear unit’s switch Note This page will only display if you are setting up the SG560, SG565 or SG580. Otherwise skip to the next step. By default, the SnapGear unit’s switch A behaves as a conventional switching hub. However, it may be configured so that each port behaves as if it were physically separate from the others.
  • Page 26 SnapGear unit and the Internet. If you haven’t already done so, connect the SnapGear unit to your LAN. Model/Configuration Instructions SG300 Connect PCs and/or your LAN hub directly to its LAN switch. SG560, SG565, or SG580 and have...
  • Page 27 If you do not want to use a DHCP server, proceed to Manual configuration of your LAN. Automatic configuration of your LAN If you selected Manual Configuration for the SnapGear unit’s LAN connection, and supplying DHCP Server Address Range, then the SnapGear unit’s DHCP server is already set up and running.
  • Page 28 Automatic configuration of your LAN using an existing DHCP server If you chose to have the SnapGear unit Obtain LAN IP address from a DHCP server on LAN, It is strongly recommended that you add a lease to your existing DHCP server to reserve the IP address you chose for the SnapGear unit’s LAN connection.

  • Page 29: Sg Rack Mount Appliance Quick Setup

    Enter the following details: IP address is an IP address that is part of the same subnet range as the SnapGear unit’s LAN connection (if using the default settings, 192.168.0.2 – 192.168.0.254). Subnet mask is the subnet mask of the SnapGear unit’s LAN connection (if using the default settings, 255.255.255.0).
  • Page 30 The status LEDs on the front panel provide information on the operating status of the SnapGear unit. The Power LED is ON when power is applied. H/B (heart beat) flashes when the SnapGear unit is running. Each of the network ports has two LEDs indicating link, activity, and speed. In its factory-default state, the four status LEDs next to Power flash.
  • Page 31 Next, modify your PC’s network settings to enable it to communicate with the SnapGear unit. Click Start > (Settings >) Control Panel and double-click Network Connections (or in 95/98/Me, double-click Network). Right-click Local Area Connection then select Properties. Note If there is more than one existing network connection, select the one corresponding to the network interface card to which the SnapGear unit is attached.
  • Page 32 Note If you wish to retain your existing IP settings for this network connection, click Advanced and Add the secondary IP address of 192.168.0.100, subnet mask 255.255.255.0. Set up the SnapGear unit’s password and LAN connection settings Launch your web browser and navigate to 192.168.0.1. Select Quick Setup Wizard from the center of the page.
  • Page 33 The Quick Setup wizard is displayed. Changing the Hostname is not typically necessary. Select how you would like to set up your LAN connection then click Next. Note You must select Manual configuration in order to enable the SnapGear unit’s built-in DHCP server.
  • Page 34 If you selected Manual configuration, some additional information is required. Otherwise, skip to the next step. Enter an IP address and Subnet Mask for the SnapGear unit’s LAN connection. Note Take note of this IP address and subnet mask, as you will need them later on. To enable the SnapGear unit’s built-in DHCP server, enter a range of addresses to hand out in DHCP Server Address Range.
  • Page 35 Note If you have changed the SnapGear unit’s LAN connection settings, it may become uncontactable at this point. This step describes how to set up the PCs on your network to access the SnapGear unit and the Internet. Connect PCs and/or your LAN hub to switch A on the SnapGear unit. Set up the PCs on your LAN Each PC on your LAN must now be assigned an appropriate IP address, and have the SnapGear unit’s LAN IP address designated as its gateway and as its DNS server.
  • Page 36 Select Internet Protocol (TCP/IP) and click Properties (or in 95/98/Me, TCP/IP > [your network card name] if there are multiple entries) and click Properties (in 95/98/Me, you may also have to click the IP Address tab). Check Obtain an IP address automatically, check Obtain DNS server address automatically and click OK (in 95/98/Me, reboot the PC if prompted to do so).
  • Page 37 Ensure all PCs on the network are set up to automatically obtain network configuration as per Automatic configuration of your LAN, then restart them. Note The purpose of restarting the computers is to force them to update their automatically configured network settings. Alternatively you can use a utility such as ipconfig to release then renew the DHCP lease, or disable and re-enable the network connection.
  • Page 38 Set up the SnapGear unit’s Internet connection settings Choose a port on the SnapGear unit for your primary Internet connection. Port C is used in this guide. Attach Port C to your modem device or Internet connection medium. If necessary, give the modem device some time to power up. Note If you have changed the SnapGear unit’s LAN connection settings, browse to the new LAN IP address.
  • Page 39 If you have a Direct Connection to the Internet (e.g. a leased line), enter the IP settings provided by your ISP. Note For detailed help for each of the options, please refer to the next chapter. After entering the appropriate details, click Finish. Quick setup is now complete.

  • Page 40: Sg Pci Appliance Quick Setup

    SG PCI Appliance Quick Setup Unpack the SnapGear unit Check that the SG CD is included with your appliance: On the SnapGear unit is a single 10/100 network port, a Reset button, and four LEDs (lights). The LEDs provide information on the operating status of your SnapGear unit. The two LEDs closest to the network port indicate network link and network activity.
  • Page 41 Set up your PC to connect to the web management console Note The following steps assume you want to set up your SnapGear unit in bridged mode, so that it sits between your PC and the LAN, transparently filtering network traffic. If you want to set up your SnapGear unit for NAT mode or to connect directly to your ISP, refer to Network Address Translation (NAT) on page 148.
  • Page 42 Select Use the following IP address and enter the following details: IP address: 192.168.0.100 Subnet mask: 255.255.255.0 Leave the Default gateway and DNS server addresses blank. Set up the SnapGear unit’s password and network connection settings Launch your web browser and navigate to 192.168.0.1. Select Network Setup from the Networking menu.
  • Page 43 Note The new password takes effect immediately. You are prompted to enter it when completing the next step. In the row labeled Bridge, click the Modify icon. Note The purpose of this step is to configure the IP address for the web management console. For convenience, this is generally a free IP address on your LAN.
  • Page 44 Check DHCP assigned. Anything in the IP Address and Subnet Mask fields is ignored. Click Update. Click Start > (Settings >) Control Panel and double-click Network Connections. Right-click Local Area Connection (or appropriate network connection for the newly installed PCI appliance) and select Properties. Select Internet Protocol (TCP/IP) and click Properties and click Properties.
  • Page 45 Check Obtain an IP address automatically, check Obtain DNS server address automatically and click OK. Attach your SnapGear unit’s Ethernet port to your LAN’s hub or switch. Quick setup is now complete. Manual configuration Ensure you have two free IP addresses that are part of the subnet range of your LAN, and ensure you know your LAN’s subnet mask, and the DNS server address and gateway address used by PCs on your LAN.
  • Page 46 Enter this address as the IP Address, and the subnet mask for your LAN as the Subnet mask. Ensure DHCP assigned is unchecked. You may also enter one or more DNS Server(s) and a Gateway address to be used by the SnapGear unit, not your PC, for access to the Internet.
  • Page 47 Enter the following details: IP address is the second free IP address that is part of your LAN’s subnet range. Subnet mask is you LAN’s subnet mask. Default gateway is your LAN’s default gateway IP address. Preferred DNS server is the IP address of the DNS server used by PCs on your LAN.

  • Page 48: The Snapgear Management Console

    The SnapGear Management Console The various features of your SnapGear unit are configured and monitored using the management console. Follow the steps from the beginning of this chapter to set up your PC to access the management console. The main menu is displayed on the left hand side. Navigate your way around and get a feel for the SnapGear unit’s features by clicking the corresponding link in the main menu.

  • Page 49: Network Setup

    Network Setup This chapter describes the Network Setup sections of the web management console. Here you can configure each of your SnapGear unit’s Ethernet, wireless and serial ports. To access Network Setup, click the Network Setup under the Network Setup section of the main web management console menu.

  • Page 50: Multifunction Vs. Fixed-Function Ports

    A network interface is configured by selecting a connection type from the Change Type pull-down menu. The current configuration can be viewed or modified by clicking the Edit icon. Clicking the Delete icon unconfigures a network interface; you are prompted to confirm this action.
  • Page 51 Note The switches’ ports can not be configured individually; a switch is configured with a single function only (e.g., LAN switch, DMZ switch). SG560, SG565 and SG580: Multifunction Ports The SG560, SG565 and SG580 have generically named Ethernet ports (ports A1, A2, A3, A4 and B).

  • Page 52: Direct Connection

    Direct Connection A direct connection is a direct IP connection to a network, i.e. a connection that does not require a modem to be established. This is typically a LAN, DMZ or Guest connection, but may also be an Internet connection. Network settings may be assigned statically, or dynamically by a DHCP server.
  • Page 53 To have your SnapGear unit obtain its LAN network settings from an active DHCP server on your local network, check DHCP assigned. Note that anything in the IP Address, Subnet Mask and Gateway fields are ignored. You may also enter one or more DNS servers. To enter multiple servers, enter each IP address separated by commas.
  • Page 54 If an Ethernet port is experiencing difficulties auto-negotiating with another device, Ethernet Speed and duplex may be set manually. On rare occasions, it may be necessary to change the Ethernet hardware or MAC Address of your SnapGear unit. The MAC address is a globally unique address and is specific to a single SnapGear unit.

  • Page 55: Adsl

    For aliases on interfaces that have the DMZ or Internet firewall class, you must also setup appropriate Packet Filtering and/or Port forwarding rules to allow traffic on these ports to be passed onto the local network. See the chapter entitled Firewall for details. IPv6 You must enable IPv6 under the Network Settings Connection tab for each connection that supports IPv6.
  • Page 56 Do not continue until it has reached the line sync state and is ready to connect. Note For PPPoE/PPPoA connections, ensure your DSL modem is set to operate in bridged mode. Typically, for PPPoE connections, your DSL modem must be set to use LLC multiplexing/encapsulation.
  • Page 57 Note If autodetection fails, it may be because your DSL modem is misconfigured for your connection type, or your DSL service has not yet been provisioned by your telco. Click Next to continue. PPPoE To configure a PPPoE or PPPoA connection, enter the user name and password provided by your ISP.
  • Page 58 PPTP To configure a PPTP connection to your ISP, enter the PPTP Server IP Address and a Local IP Address and Netmask for the SnapGear network port through which you are connecting to the Internet. The Local IP address is used to connect to the PPTP server and is not typically your real Internet IP address.
  • Page 59 The latter two settings are optional, but are generally required for normal operation. Multiple DNS addresses may be entered separated by commas. You may also enter a descriptive Connection Name if you wish. Click Finish or Update. Connection (dial on demand) You may choose to bring up a PPPoE/PPPoA DSL, dialout or ISDN connection only when PCs on the LAN, DMZ or Guest network (via a VPN tunnel) are trying to reach the Internet and disconnect again when the connection has been idle for a specified period.

  • Page 60: Cable Modem

    Ethernet configuration See the section entitled Ethernet configuration under Direct Connection. Aliases See the section entitled Aliases under Direct Connection. Cable Modem To connect to the Internet using a cable Internet service, select Cable Modem from the Change Type pull-down menu for the interface that connects to your cable modem. Cable Modem connections have the interface firewall class of Internet.

  • Page 61: Dialout And Isdn

    Ethernet configuration See the section entitled Ethernet configuration under Direct Connection. Aliases See the section entitled Aliases under Direct Connection. Dialout and ISDN To connect to the Internet using a regular dialup or ISDN service, select Dialout from the Change Type pull-down menu for the interface that connects to your dialup modem or ISDN TA.

  • Page 62: Dial-In

    Port settings If necessary, you may set the SnapGear unit’s serial port Baud rate and Flow Control. This is not generally necessary. Static addresses The majority of ISPs dynamically assign an IP address to your connection when you dial- in. However some ISPs use pre-assigned static addresses. If your ISP has given you a static IP address, click the Static Addresses tab and enter it in My Static IP Address and enter the address of the ISP gateway in ISP Gateway IP Address.
  • Page 63 If you wish, you may enter a descriptive Connection Name. In the IP Address for Dial-In Clients enter an available IP address. This IP address must not already be in use on the network (typically the LAN) that the remote user is assigned while connected to the SnapGear unit.
  • Page 64 Unencrypted Authentication (PAP): This is plain text password authentication. When using this type of authentication, the client passwords are transmitted un- encrypted. Select the Required Encryption Level, access is denied to remote users attempting to connect not using this encryption level. Using Strong Encryption (MPPE 128 Bit) is recommended.
  • Page 65 Connecting a dial-in client Remote users can dial in to the SnapGear unit using the standard Windows Dial-Up Networking software or similar. The following instructions are for Windows 2000/XP. Click Start > Settings > Network and Dial-up Connections and select Make New Connection.
  • Page 66 Select Use dialing rules to enable you to select a country code and area code. This feature is useful when using remote access in another area code or overseas. Click Next to continue. Select the option Only for myself to make the connection only available for you. This is a security feature that does not allow any other users who log onto your machine to use this remote access connection: Network Setup...
  • Page 67 Enter a name for the connection and click Finish to complete the configuration. Check Add a shortcut to my desktop to add an icon for the remote connection to the desktop. To launch the new connection, double-click on the new icon on the desktop. The remote access login screen appears as in the next figure.

  • Page 68: Failover, Load Balancing And High Availability

    Internet gateway for your network should the primary SnapGear unit fail Note SnapGear unit models SG300, SG530 and SG550 are limited to Internet availability configurations using a single broadband Internet connection and a single dialout or ISDN connection.

  • Page 69: Internet Failover

    Note If you are using a SnapGear unit model SG560, SG565 or SG580, you may want to skip to information on establishing multiple broadband connetions. This information is in the section entitled Port Based VLANs on page 97. Once the Internet connections have been configured, specify the conditions under which the Internet connections are established.
  • Page 70 Note Internet failover is not stateful, i.e. any network connections that were established through the failed primary connection must be re-established through the secondary connection. Edit connection parameters The first step of configuring failover is to set failover parameters for each connection. These parameters specify how to test whether a connection is up and functioning correctly.
  • Page 71 Select a Test Type. The Ping test is usually appropriate. Ping sends network traffic to a remote host at regular intervals, if a reply is received the connection is deemed to be up. Custom (advanced users only) allows you to enter a custom console command to run to determine whether the connection is up.
  • Page 72 If you selected Custom, enter the custom Test Command that is used to test the connection, e.g.: myscript 5 10 ping -c 1 -I $if_netdev 15.1.2.3 Note If the Test Command exits with a return code of zero (0), the test is deemed to have passed and the connection is considered up.
  • Page 73 Recall that a connection level is one or more connections. These connections may be marked as Required or Enabled. Internet connections that are marked Disabled are not part of this connection level. A connection level is deemed to be up when all connections marked Required at that level are up, and at least one connection (marked Required or Enabled) at that level is up.

  • Page 74: Internet Load Balancing

    This returns you to the main Connection Failover page. You’ll notice that ticks and crosses are display alongside each connection, describing how they are configured for each connection level. A red cross means Disabled, a green ticket means Enabled and a green tick with a small red plus means Required, Internet Load Balancing Once you have configured two or more Internet connections, you may enable Internet...
  • Page 75 Enabling load balancing Under the Failover & H/A tab, click Modify Levels. Check Load Balance for each connection to enable for load balancing. Click Finish. Note Load balancing settings are not specified for each failover level; load balancing occurs when any two or more load balancing connections are up. Limitations of load balancing Load balancing works by alternating outgoing traffic across Internet connections in a round robin manner.

  • Page 76: High Availability

    VPN connections such as IPSec or PPTP tunnels are confined to a single Internet connection, as they are a single connection (that encapsulate other connections). Load balancing is not performed for incoming traffic. This scenario can be addressed using other solutions such as round robin DNS to alternate incoming connections between the two links.
  • Page 77 In this scenario, SnapGear unit #1 is initially the master and therefore the default gateway for the local network and SnapGear unit #2 is the slave on standby. This may be because SnapGear unit #1 booted up before SnapGear unit #2, or SnapGear unit #2 may have previously failed, but has now come back online.
  • Page 78 Later, SnapGear unit #1 comes back online as the slave. SnapGear unit #2 continues its role as the default gateway for the local network. Note Using the default high availability script, a high availability failover is not triggered by the master simply losing Internet connectivity.

  • Page 79: Dmz Network

    IP addresses, and the interface configured as the checked interface. DMZ Network Note Not available on the SG300, SG530, SG550 or SG PCI appliances. A DMZ (de-militarized zone) is a physically separate LAN segment, typically used to host servers that are publically accessible from the Internet.
  • Page 80 By default, machines on the DMZ network have addresses in a private IP address range, such as 192.168.1.0 / 255.255.255.0 or 10.1.0.0 / 255.255.0.0. Real world addresses may be used on the DMZ network by by unchecking Enable NAT from DMZ interfaces to Internet interfaces under the Advanced tab.

  • Page 81: Guest Network

    Guest Network Note Not available on the SG300, SG530, SG550 or SG PCI appliances. The intended usage of Guest connections is for connecting to a Guest network, i.e. an untrusted LAN or wireless networks. Machines connected to the Guest network must establish a VPN connection to the SnapGear unit in order to access the LAN, DMZ or Internet.
  • Page 82 Caution is advised before allowing machines on a Guest network direct access to the Internet, particularly in the case of Guest wireless networks. This may result in unauthorized use of your Internet connection for sending spam, other malicious or illegal activities, or simply Internet access at your expense.

  • Page 83: Wireless

    Wireless Note SG565 only. The SnapGear unit’s wireless interface may be configured as a wireless access point, accepting connections from 802.11b (11 Mbit/s) or 802.11g (54 Mbit/s) capable wireless clients. Typically, the SnapGear unit’s wireless interface is configured in one of two ways; with strong wireless security (WPA) to bridge wireless clients directly onto your LAN, or with weak wireless security as a Guest connection.
  • Page 84 Warning We strongly recommend that the wireless interface be configured as a LAN connection only if wireless clients are using WPA based encryption/authentication. This is discussed in further detail later in this section. Configuring a Direct Connection is described in detail in the section entitled Direct Connection towards the beginning of this chapter.
  • Page 85 Security Method ESSID: (Extended Service Set Identifier) The ESSID is a unique name that identifies a wireless network. This value is case sensitive, and may be up to 32 alphanumeric characters. Broadcast ESSID: Enables broadcasting of the ESSID. This makes this wireless network visible to clients that are scanning for wireless networks.
  • Page 86 Wireless security Encryption and authentication settings for your wireless network are configured under Access Point. Fields vary based on the security method you choose. If Security Method is set to None, any client is allowed to connect, and there is no data encryption.
  • Page 87 Warning Due to flaws in the authentication protocol, this method reduces the security of the WEP key. It is recommended that you use Open System authentication instead. Open System or Shared Key: Allows clients to authenticate using either of the above two methods.
  • Page 88 WPA-Enterprise Wi-Fi Protected Access uses the IEEE 802.1X protocol to provide authenticate the user and dynamically assign the encryption key via a RADIUS server. This is the recommended security method. The RADIUS server must be defined on the RADIUS page (see the RADIUS section of the chapter entitled System).
  • Page 89 Select Allow authentication for MACs in the Access Control List to disallow all but the MAC addresses you specify, or Deny authentication for MACs in the Access Control List to allow all but the MAC address you specify. Click Update. Enter a MAC to allow or deny and click Add.
  • Page 90 There are two common scenarios for WDS: bridging or repeating. WDS bridging is when an Access Point allows wireless clients to connect, and forwards packets from these clients to another Access Point. This is used to connect two wired Ethernet connections via a wireless link.
  • Page 91 1. Configure the wireless settings on the Access Point tab as normal. 2. Select the WDS tab. 3. Set Mode to Automatic. 4. Click Add and enter the MAC of the main Access Point. 5. Click the Connections tab, create a new Bridge. Select the Wireless interface, the LAN interface, and the WDS interface to all be on the bridge.
  • Page 92 Region: Select the region in which the access point is operating. This restricts the allowable frequencies and channels. If your region is not listed, select a region that has similar regulations. Protocol: 802.11b only: Wireless clients can only connect using 802.11b (11 Mbit/s). Note that most wireless clients which support 802.11g also support 802.11b.
  • Page 93 RTS incurs an overhead for transmitting, so enabling it when it is not needed decreases performance. Since the access point is in range of all wireless clients, you would not normally enable RTS for an access point. RTS Threshold: The minimum packet size for which RTS is enabled. Collisions are less likely for smaller packets, and so the overhead of using RTS for these may not be worthwhile.
  • Page 94 Click Wireless Configuration. Enter an appropriate ESSID and select a Channel for your wireless network. Enable Bridge Between Clients to allow wireless clients to intercommunicate, and there is generally no reason not to Broadcast ESSID. Take note of the ESSID and Channel, you need them to configure the wireless clients. Select WPA-PSK as the Security Method, select AES for WPA Encryption if your wireless clients support it, otherwise select TKIP.
  • Page 95 Select Allow authentication for MACs in the Access Control List and click Apply. Select Add to add the MAC address of each wireless client you wish to allow to connect. Click Advanced. Ensure the Region has been set appropriately. You may also restrict the Protocol to 802.11b only or 802.11g only if you wish.
  • Page 96 Under the main table, select Bridge and click Add. Select your wired LAN connection from the Existing Interface Configuration pull-down box. This is the address to share between the interfaces. Click Next. Network Setup...

  • Page 97: Bridging

    Alongside the wireless interface, check Bridged and select LAN from the Firewall Class pull-down menu. Click Finish. Note If your LAN interface was previously configured to obtain an IP address automatically from a DHCP server, the SnapGear unit now uses the MAC address of the wireless device when obtaining an IP address.
  • Page 98 Another advantage is that network traffic not usually routed by unbridged interface, such as broadcast packets, multicast packets, and any non-IP protocols such as IPv6, IPX or Appletalk pass over the bridge to their destination host. Bridging network interfaces involves creating, then associating existing network interfaces with a Bridge interface.
  • Page 99 If you wish to transfer the IP address settings of an existing network connection to the bridge interface, select it from the Existing Interface Configuration pull-down menu. Click Next. Note As the SnapGear unit automatically directs network traffic, hosts on either side do not need to specify this IP address as a gateway to the networks connected to the bridge.

  • Page 100: Vlans

    GRE over IPSec in the Virtual Private Networking chapter. VLANs Note VLANs are not supported by the SG300. VLAN stands for virtual local area network. It is a method of creating multiple virtual network interfaces using a single physical network interface.
  • Page 101 When a packet is routed out the VLAN interface, the VLAN header is inserted and then the packet is sent out on the underlying physical interface. When a packet is received on the physical interface, it is checked for a VLAN header. If present, the router makes it appear as though the packet arrived on the corresponding VLAN interface.
  • Page 102 Interface: Select the network interface on which to add the VLAN. VLAN ID: If this VLAN interface is to participate on an existing VLAN, the VLAN ID number must match the existing VLAN’s ID. Port / Mode: If this table is displayed, this interface has been enabled for port based VLANS;...

  • Page 103: Port Based Vlans

    Port Based VLANs Note SG560, SG565 and SG580 only. The SG560, SG565 and SG580 have a VLAN-capable switch built in. This gives you the flexibility to either use it as a simple switch that allows access between all ports (this is the default), or use port based VLANs to control access between each individual port in the switch.
  • Page 104 Limitations of port based VLANs There are few further limitations to keep in mind when using port based VLANs: The total bandwidth from the switch into the CPU is 100Mbits/s, which is shared between the 4 ports. This may limit the bandwidth available to a single port when perform general routing, packet filtering, and other activities.
  • Page 105 The following settings pertain to port based VLANs: Enable port based VLANs: Check to enable port based VLANs. Default port based VLAN ID: As the default VLAN is always untagged, typically you only need to change this from the default setting of 2 if you want another port to participate on an existing tagged VLAN with the ID of 2.
  • Page 106 The following settings are displayed: Interface: The port based VLAN capable interface on which to add the VLAN. VLAN ID: If you are adding a VLAN interface to participate on an existing VLAN, enter its ID number here. Otherwise enter the next available VLAN ID; if the Default port based VLAN ID has been left at its default setting of 2, Port A2 uses VLAN ID 3, Port A3 uses VLAN ID 4, and so on.

  • Page 107: Gre Tunnels

    Editing port based VLANs Once a VLAN has been added, you may edit the settings you entered in Adding port based VLANs by clicking its Edit icon in the main Network Setup > Connections table. Removing port based VLANs To remove a VLAN, click its Delete icon in the main Network Setup > Connections table.
  • Page 108 A bridged GRE tunnel is useful for transmitting packets across a VPN connection that would normally be dropped by IP routing. This includes broadcast packets, multicast packets and any non-IP protocol such as IP v6, IPX, or Apple Talk. Adding a GRE interface Under the Network Setup >...
  • Page 109 2. Assign unused alias IP addresses to the LAN interfaces at both ends of the tunnel. 3. Create an IPSec tunnel between the alias IP addresses, using a prefix length for each network of /32. 4. Create a GRE tunnel for which the Local Address is the local LAN IP address, and the Remote Address is the remote LAN IP address.
  • Page 110 Add the LAN connection to a bridge, as described in the section entitled Bridging earlier in this chapter. Give the LAN interface bridge a secondary address that is part of the network we want bridged across the tunnel. Adding an alias is described in Aliases in the section entitled Direction Connection earlier in this chapter.
  • Page 111 GRE Tunnel Name: to_slough Remote External Address: 10.254.0.1 Local External Address: 10.254.0.2 Firewall Class: Click Finish to add the interface. Edit the bridge interface that you added at the beginning of these steps. Check Bridged for the GRE interface you have just added, and select a Firewall Class of LAN.

  • Page 112: Routes

    Ensure that the remote GRE end point responds to pings. Note that by default no packets are routed across the GRE tunnel unless there is a route set up on the GRE tunnel. Routes To configure the SnapGear unit’s advanced routing features, click the Routes tab on the Network Setup page.
  • Page 113 Route management Note Route management does not have full GUI configuration support. We recommend that only advanced users familiar with the Zebra routing daemon and/or the RIP, BGP or OSPF routing protocol attempt configuration of this feature. Advanced users may configure the SnapGear unit to automatically manage its routing tables, exchanging routes with other routers using RIP, BGP or OSPF protocol.
  • Page 114 password zebra!password In these examples,! denotes a descriptive comment # indicates a configuration line that is currently commented out, which you may want to uncomment depending on your network setup. In zebra.conf, enter: ! Uncomment and set telnet/vty passwords to enable telnet access on port 2601 #password changeme #enable password changeme...
  • Page 115 #network eth2 ! Define neighbor routers to exchange RIP with if disabling multicast above in zebra.conf, or neighbors don't have multicast enabled #neighbor 192.168.45.238 #neighbor 192.168.45.231 ! Redistribute routing information for interfaces with RIP disabled redistribute connected ! Redistribute routing information from static route entries redistribute static ! Redistribute routing information from kernel route entries e.g.
  • Page 116 OSPF Note This example is adapted from the LARTC (Linux Advanced Routing & Traffic Control) dynamic routing howto, available from: http://lartc.org/howto/ LARTC is an invaluable resource for those wanting to learn about and take advantage of the advanced routing capabilities of Linux systems. OSPF stands for Open Shortest Path First, and some of its principal features as follows: Networks are grouped by areas, which are interconnected by a backbone area which will be designated as area 0.
  • Page 117 The SG is configured to exchange routes with the routers named Atlantis, Legolas and Frodo. Ensure you have enabled OSPF under Route Management, then open zebra.conf and ospfd.conf for editing as described in the Route management section. In zebra.conf, enter: hostname sg ! Uncomment and set telnet/vty passwords to enable telnet access on port 2602...
  • Page 118 ! Uncomment and set telnet/vty passwords to enable telnet access on port 2604 #password changeme #enable password changeme ! Instruct ospfd about our network topology router ospf network 192.168.0.0/24 area 0 network 172.17.0.0/16 area 1 Restart route management to enable the updated configuration: Uncheck Enable route management, click Update, check Enable route management and click Update.
  • Page 119 Note The AS numbers used in this example are reserved. Please get your own AS from RIPE if you set up official peerings. Ensure you have enabled BGP under Route Management, then open zebra.conf and bgpd.conf for editing as described in the Route management section. In zebra.conf, enter: hostname sg ! Uncomment and set telnet/vty passwords to enable telnet...
  • Page 120 access-list local_nets deny any ! Our AS number router bgp 1 ! Our IP address bgp router-id 192.168.0.1 ! Announce our own network to other neighbors network 192.168.0.0/24 ! Advertise all connected routes (directly attached interfaces) redistribute connected ! Advertise kernel routes (manually inserted routes, IPSec) redistribute kernel ! Every 'router bgp' block contains a list of neighbors to which the router is connected:...

  • Page 121: System

    System To configure the SnapGear unit’s network system settings, click the System tab on the Network Setup page. These settings control the SnapGear unit’s identity on the network. Hostname The Hostname is a descriptive name for the SnapGear unit on the network. It is also used as the SNMP sysName field.

  • Page 122: Dns

    To configure the SnapGear unit’s DNS settings, click the DNS tab on the Network Setup page. These settings control the SnapGear unit’s network name services. The DNS configuration information is stored in /etc/config/dnsmasq.conf. For a complete list of the options that may be stored in this file run the following command: # dnsmasq --help DNS proxy The SnapGear unit can be configured to run a domain name server (DNS) proxy.
  • Page 123 Dynamic DNS A dynamic DNS service is useful when you don’t have a static IP address, but need to remain contactable by hosts on the Internet. Dynamic DNS service providers such as TZO.com and dyndns.org can register an Internet domain name that points to your IP address no matter how often it changes.

  • Page 124: Dhcp Server

    DHCP Server Note To configure your SnapGear unit as a DHCP server, you must set a static IP address and netmask on the network interface on which you want the DHCP server to run; see the Direct Connection section of the chapter entitled Network Connections. To begin configuring the SnapGear unit’s DHCP server, select DHCP Server from the Network Setup section of the web management console’s main menu.
  • Page 125 Enter the DNS Address to issue the DHCP clients. If this field is left blank, the SnapGear unit’s IP address is used. Leave this field blank for automatic DNS server assignment. If your SnapGear unit is configured for DNS masquerading, you should either leave this field blank, or enter the IP address of the LAN port of the SnapGear unit.
  • Page 126 There is a trashcan icon to delete the address from the list of addresses to manage. You may also Free addresses that have been leased by hosts on your network. This causes the lease to expire immediately, leaving the address available for the next host that requests IP configuration.
  • Page 127 Reserving IP addresses You may reserve IP addresses for particular hosts, identifying them by hostname and MAC address. These reserved hosts are also added to the /etcconfig/hosts file (static hosts) for DNS purposes; see the Static Hosts section of this chapter. This allows the computers on the LAN to use the names even if there is no other DNS server around.
  • Page 128 The Subnet is the network on which DHCP server is handing out addresses. Free Addresses displays the number of remaining available IP addresses that can be distributed. If this value is 0, you may need to increase the number of IP addresses to hand out.

  • Page 129: Web Cache

    Web Cache Note SG565, SG575, SG580, SG635 and SG rack mount appliances only. Web browsers running on PCs on your LAN can use the SnapGear unit’s proxy-cache server to reduce Internet access time and bandwidth consumption. A proxy-cache server implements Internet object caching. This is a way to store requested Internet objects (i.e., data available via HTTP, FTP, and other protocols) on a server closer to the user's network than on the remote site.
  • Page 130 If you are using a Network Share or Local Storage (recommended, see below), it is generally best to set this to 8 Megabytes. Otherwise, start with a small cache (8 Megabytes or 16 Megabytes) and gradually increase it until you find a safe upper limit where the SnapGear unit can still operate reliably.
  • Page 131 Network storage share Note Network Storage share and Local Storage cannot be used at the same time. Enabling one will automatically disable the other. A network share is a shared folder or drive on a local Windows PC, or a PC running another operating system capable of SMB sharing (such as a Linux PC running the SAMBA service).
  • Page 132 Launch Windows Explorer (Start > (All) Programs > Accessories > Windows Explorer) and open up a folder or drive to dedicate as a network share for use by the SnapGear unit’s web cache. Begin by disabling simple file sharing for this folder. From the Tools menu, select Folder Options.
  • Page 133 Under the Network Share tab, check Use share. Enter the location of the network share in the format: \\HOSTNAME\sharename Enter the maximum size for the cache in Cache size. Warning The size of this cache should be at least as big as the Cache size on the Main tab and not be more than 90% of the space available to the network share.
  • Page 134 Click Advanced, Peers, then New. Tthe messages transmitted by a cache to locate a specific object are sent to Sibling caches, which are placed at the same level in the hierarchy. Then, the caches placed at the Parent level are queried if the replies from sibling caches did not succeed. Enter the host or IP address of an ICP-capable web cache peer in Host, then select its relationship to the SnapGear unit’s web cache (as described above) from Type and click Apply.
  • Page 135 ICAP RESPMOD server is the URL for an ICAP server's RESPMOD service. This allows an ICAP server to modify web transaction responses, i.e. to process traffic that is returned from an external web server, e.g. for virus scanning. It must begin with icap://, e.g.: icap://192.168.0.10:1344/respmod You may choose to Bypass ICAP server if uncontactable.

  • Page 136: Qos Traffic Shaping

    Log File Rotation Time (minutes) specifies how often the logs are checked for rotation. Log File Rotations specifies how many log file rotations should be stored. The minimum default of 1 means 2 files will be kept: the current log file and the previous log file. The maximum of 9 will mean 10 files will be kept.
  • Page 137 QoS autoshaper The Auto Traffic Shaper uses a set of inbuilt traffic shaping rules to attempt to ensure low latency on interactive connections, while maintaining fast throughput on bulk transfers. Click Edit next to the network interface on which you wish to enable the autoshaper. Click Enable and enter the Outbound Speed (upstream speed) of this interface’s network connection in megabits per second.
  • Page 138 Check Enable Traffic Shaping, select a Default priority and click Submit to enable this feature. The Default priority is assigned to all network services other than those specifically added below. To add a service, click New then New again. Select the Protocol and Port on which this service runs.

  • Page 139: Ipv6

    IPv6 Check Enable IPv6 to enable IPv6 routing and packet filtering. Support for IPv6 is currently limited. Note You must also enable IPv6 for each connection that supports IPv6. See the section entitled Direct Connection towards the beginning of this chapter. When IPv6 is enabled, site-local addresses are assigned to LAN connections, the site- local DNS server address (fec0:0:0:ffff::1/64) is assigned to LAN connections if the DNS proxy is enabled, router advertisements are sent on LAN connections and 6to4...
  • Page 140 If you use an external SIP service such as the Gizmo Project or Skype, you typically do not need to use the SIP proxy. These services use STUN (Simple Traversal of UDP through NATs) to facilitate communication from behind a masquerading firewall. The SIP proxy listens on UDP port 5060 for SIP requests (this is the standard SIP port and should not generally need to be changed), and UDP ports 7070-7079 for RTP traffic (the actual voice data).

  • Page 141: Firewall

    Firewall The SnapGear unit is equipped with a fully featured, stateful firewall. The firewall allows you to control both incoming and outgoing access, so that PCs on local networks can have tailored Internet access facilities while being shielded from malicious attacks from external networks.
  • Page 142 Administration services The following figure shows the Administration Services page: By default the SnapGear unit runs a web administration server, a Telnet and an SSH service. Access to these services can be restricted to specific interfaces. Only Administrative users with the Login access control are able to connect via telnet. SSH provides for secure encrypted communication whereas telnet is completely unencrypted.

  • Page 143: Web Management

    Warning If you do want to allow administrative access on interfaces other than LAN Interfaces, there are several security precautions you should take. See the note in the next section for details. Also consider remote administration using a VPN connection as an alternative to opening a hole in the firewall, PPTP in particular is well suited to this task.
  • Page 144 Note Changing the web server port number is recommended if you are allowing Internet access to the Management Console. This may help hide the web management console from casual web surfers who type your SnapGear units Internet IP address into a web browser.
  • Page 145 Once valid SSL certificates have been uploaded or created, A valid SSL certificate has been installed is displayed. The Snap Gear administrative web server can then operate in one of 3 modes: Normal (HTTP) and SSL (HTTPS) web server access Disable SSL (HTTPS) web server access (HTTP only) Disable normal (HTTP) web server access (HTTPS only) To access the web management console securely using SSL encryption, the URL...

  • Page 146: Customizing The Firewall

    Select the appropriate Country and certificate key length from the Generate an RSA key of pull-down menu. All other fields but Host name (Common Name) are optional; they are used to create the certificate’s distinguished name. Generating a certificate usually takes a few minutes, exact time depends on the model of SnapGear unitand the key length.
  • Page 147 Service groups A network service is defined by a protocol and port. Protocol may be either TCP, UDP, ICMP or IP, and port may be any valid network port number (i.e. between 1 and 65535), e.g. HTTP (web) uses the TCP protocol, with a default port of 80. Network packets may be matched by destination service.
  • Page 148 Addresses Addresses are a single IP address, or range of IP addresses, or a DNS hostname. Network packets may be matched by source or destination address. Click the Addresses tab. Any addresses that have already been defined are displayed. Click New to add a new address, or select an existing address and click Modify. There is no need to add addresses for the SnapGear unit’s interfaces, these are predefined.
  • Page 149 Adding or modifying an address is shown in the following figure: You may either add a Single Address or Range or DNS Hostname. You may also group previously added addresses together by defining an Address Group to simplify your firewall ruleset. Select how you would like to add the address or addresses, and click New.

  • Page 150: Packet Filtering

    Packet Filtering Packet filter rules match traffic based on a combination of the source and destination address, incoming and outgoing interface, and destination service. Matched packets may be allowed or disallowed. Packet filter rules Click Packet Filter Rules. Click New to add a new filter rule. Any rules that have already been defined are displayed.
  • Page 151 The Action specifies what to do if the rule matches. Accept means to allow the traffic. Drop means to disallow the traffic. Reject means to disallow the traffic, but also send an ICMP port unreachable message to the source IP address. None means to perform no action for this rule.
  • Page 152 The Outgoing Interface is the interface/network port that the SnapGear unit routes the network traffic out of. Set this to None to match traffic originating from the SnapGear unit itself. The Source Address is the address that the traffic is arriving from. The Destination Address is the address that the traffic is destined to.
  • Page 153 Once you have created a packet filtering rule, you may specify rate limiting settings. These settings are useful for preventing a service from becoming unavailable should many connection attempts occur in a short period of time (e.g. in the case of a denial of service (DOS) attack).

  • Page 154: Network Address Translation (Nat)

    Log Prefix specifies the text to be placed at the start of the log message. This can be used to make it easier to identify which rules are being matched when inspecting the system log. Custom firewall rules The Custom Firewall Rules and Custom IPv6 Firewall Rules tabs allow firewall experts to view the current firewall rules and add custom iptables firewall rules.
  • Page 155 1-to-1 NAT is a combination of destination NAT and source NAT. Both destination NAT and source NAT rules are created for full IP address translation in both directions. This can be useful if you have a range of IP addresses that have been added as interface aliases on the SnapGear unit’s WAN interface, and want to associate one of these external alias IP addresses with a single internal, masqueraded computer.
  • Page 156 Note The example shown in the screenshot above forwards the SSH (secure shell) protocol to an internal server (barry’s server). SSH allows encrypted remote access, typically to a server running Linux, BSD or another Unix-like operating system. In this example, port 2222 is used rather than the standard SSH port of 22. This is to allow remote access using SSH to the SnapGear unit itself, which runs an SSH server on port 22.
  • Page 157 This rule is applied to packets that match the critera described by the next four fields. Destination Address The destination address of the request, this is the address that is altered Protocol The service of the packet, which may be a TCP or UDP destination port, an IP protocol, or an ICMP message type Ports...
  • Page 158 Port forwarding to an internal mail server The following is an example of using port forwarding to allow hosts on the Internet to send and receive mail using a mail server on your LAN. Warning Precautions must be taken when configuring the mail server, otherwise you may become susceptible to such abuse as unauthorized relaying of unsolicited email (spam) using your server.
  • Page 159 Check one or both of IMAP4 (E-Mail) if your server supports IMAP mail retrieval and POP3 (E-Mail) if your server supports POP3 mail retrieval. Enter smtp in Other TCP Ports. This is the protocol remote clients use for sending mail via the server.
  • Page 160 Leave Enable checked. Select your Internet connection in Destination Address. Enter the translated port of the packet. If you leave this blank, then the port will be unchanged. You cannot translate the port for IP protocols or ICMP messages. You should normally set this field to the port of the service on your internal server.
  • Page 161 Click Source NAT. Any rules that have already been defined are displayed, you may Edit or Disable/Enable these rules by clicking the appropriate icon. Click New to add a new rule. You may also add a new rule above an existing one by clicking the Add Above icon, or below with Add Below.
  • Page 162 Outgoing Interface Enter the interface that the packet to masquerade behind, typically Internet. Source Address Enter the address from which the request originated, typically be a private address on the LAN or DMZ. Destination Address Enter the destination address of the request. Services Enter the destination service port or ports of the request.
  • Page 163 1-to-1 NAT This creates both a source NAT and destination NAT rule for mapping all services on an internal, private address to an external, public address. Note After adding a 1-to-1 NAT rule, you must manually create packet filter rules to allow incoming packets on the public address.
  • Page 164 Enable Uncheck to temporarily disable this rule. Private Address Enter the private address to change. Public Address Enter the public address, typically a WAN interface alias. Public Interface Select the interface on which the public address resides, this is typically Internet. Note When adding a rule, you may either use Predefined addresses that have been added under Definitions, or click New to manually enter an address.
  • Page 165 The displayed options apply to the firewall classes, not to the ports with these names. That is, the LAN interface options apply to all interfaces that are configured with a LAN connection type, not just to the port labelled as LAN. It is strongly recommended that you leave Enable NAT from LAN/VPN interfaces to Internet interfaces checked.
  • Page 166 Note The port forwarding rules set up via the UPnP Gateway are temporary. The list of configured UPnP port forwarding rules is cleared should the SnapGear unit be power cycled, or should the internal or external interface become unavailable. The UPnP Gateway is intended for transitory application port forwarding, such as those established by some versions of Microsoft Messenger for file transfers.

  • Page 167: Connection Tracking

    Enter an arbitrary Description of service, the Name or IP address of the computer hosting this service on your network, the External Port number for this service and the Internal Port number for this service. Select whether the service uses the TCP or UDP protocol.
  • Page 168 Note Implementations of protocols such as H.323 can vary, so if you are experiencing problems you can try disabling the module. Check Enable Connection Logging to log connections to the system log as they are established and expire; however, this may result in a lot of log messages if you have a large or busy network.

  • Page 169: Intrusion Detection

    Intrusion Detection Note The SG300, SG530, SG550, SG560, SG570, and SG630 provide Basic Instrusion Detection and Blocking only. The SnapGear unit provides two intrusion detection systems (IDS): the lightweight and simple-to-configure Basic Intrusion Detection and Blocking, and the industrial strength Advanced Intrusion Detection and Prevention.

  • Page 170: Basic Intrusion Detection And Blocking (Idb)

    These attacks can potentially be detected and prevented using an intrusion detection system. Basic Intrusion Detection and Blocking (IDB) Click the IDB tab to configure basic Intrusion Detection and Blocking (IDB). IDB operates by offering a number of services to the outside world that are monitored for connection attempts.
  • Page 171 Warning This is a word of caution regarding automatically blocking UDP requests. Because an attacker can easily forge the source address of these requests, a host that automatically blocks UDP probes can be tricked into restricting access from legitimate services. Proper firewall rules and ignored hosts lists significantly reduce this risk.

  • Page 172: Advanced Intrusion Detection And Prevention (Snort And Ips)

    The Basic button installs a bare bones selection of ports to monitor while still providing sufficient coverage to detect many intruder scans. The Standard option extends this coverage by introducing additional monitored ports for early detection of intruder scans. The Strict button installs a comprehensive selection of ports to monitor and should be sufficient to detect most scans.
  • Page 173 The primary advantage of running Snort IDS (Snort) in front of the firewall is that it sees unfiltered network traffic, and is therefore able to detect a wider range of attacks. The primary advantage of running Snort IPS (IPS) behind the firewall is that suspicious network traffic can be disallowed, rather than simply flagged as suspicious and allowed to pass.
  • Page 174 Rule sets are sets of defined patterns or rules used for the detection of attacks. These are grouped by type such as ddos, exploit, backdoor, netbios, etc. Each group encompasses many attack signatures. The full list of signatures can be viewed at the Snort web site (http://www.snort.org).
  • Page 175 Sensor Name is an arbitrary string that is prepended to the log output. This may be useful if you have deployed more than one intrusion detection system. Enter the User name and Password required for authentication to the remote database. Click Submit to apply your changes.
  • Page 176 PHPlot graph library for charts written in PHP http://www.phplot.com/ BASE analysis console http://secureideas.sourceforge.net/ Snort is running as an IDS sensor on the SnapGear unit, logging to the MySQL database on the analysis server. The Downloads section of the BASE website contains detailed documents that aid in installing the above tools on the analysis server.

  • Page 177: Access Control And Content Filtering

    Access Control and Content Filtering The access control web proxy allows you to control access to the Internet based on the type of web content being accessed (Content or Webwasher), and which user or workstation is accessing the Internet content (Require user authentication, IP Lists). This is useful to minimize inappropriate Internet use.
  • Page 178 0 or very large logs and a noticable system slowdown might result. For normal debugging, set Syslog Level to 1. Higher levels need only be turned on when so directed by Secure Computing Technical support. The Fast Web Mode allows the relatively slow software HTTP proxy to be bypassed under certain conditions.
  • Page 179 User authentication Check Require user authentication if you want to require users to authenticate themselves before browsing the web. When attempting to access a web site on the Internet, the browser displays a dialog similar to the following: Note To add or remove access controls user accounts, select Users from the main menu and click the Local Users tab.
  • Page 180 Note Each browser on the LAN now has to be set up to use the SnapGear unit’s web proxy. Browser setup The example given is for Microsoft Internet Explorer 6. Instructions for other browsers should be similar; refer to their user documentation for details on using a web proxy. From the Internet Options menu, select Tools.
  • Page 181 In the row labeled HTTP, enter your SnapGear unit’s LAN IP address in the Proxy address to use column, and 81 in the Port column. Leave the other rows blank. In the Exceptions text box, enter your SnapGear unit’s LAN IP address. Click OK, OK and OK again.
  • Page 182 Web lists Access is denied to any web address (URL) that contains text Added under URL Block List, e.g. entering xxx blocks access to any URL containing xxx, e.g.: http://www.xxx.com, http://xxx.example.com www.test.com/xxx/index.html The Allow List also enables access to URLs containing the specified text. Note Defining large numbers of URL fragments to match against can result in a significant slowing down of WWW accesses.
  • Page 183 The top level page has a checkbox Block Unscanned Hosts which defines the behavior for a host which hasn't been scanned or is not defined to be scanned. The Simultaneous Probes setting specifies the maximum number of different hosts that should be scanned together.
  • Page 184 Script Management Click the Script Management tab for management and testing of installed NASL scripts. NASL is the part of the Nessus vulnerability scanner that performs the majority of the vulnerability checks. By default, newly uploaded scripts will appear here but will not be available for use with a policy enforcement group.
  • Page 185 View URL filter data for the appropriate unit. Content or Webwasher? Webwasher is Secure Computing’s next generation of content filtering. In time, the original content filtering system (Content) will be phased out. Webwasher offers more categories for rating, and operates significantly faster than the old system.
  • Page 186 All new content filtering subscriptions are for the Webwasher service. The old content filtering system is maintained for backwards compatibility for existing subscribers only. If you have been given a single license key, you have a subscription to the original Content system.
  • Page 187 Under the Categories tab, select the Blocked Categories to block access to. Under the Reports tab, enter your User name and Password and click View Reports to view reporting on blocked accesses, etc. Before content filtering can be enabled, both a certificate and a private key must be provided.

  • Page 188: Antivirus

    Checking Enable Cache stores recently accessed pages’ ratings locally, to lower the response time the next time the page is accessed. It is recommended that you leave this checked. Blocked requests are submitted to the central content filtering server. The user attempting to access blocked content can be identified either through User Accounts (see User Authentication earlier in this chapter) or the IP Address of their machine.
  • Page 189 Antivirus will still be functioning correctly. Contact your reseller for details on how to obtain new SG firmware. As with all firmware updates, Secure Computing will determine an appropriate firmware release schedule based on the nature of the changes made. Serious vulnerabilities are given priority over feature enhancements.
  • Page 190 Check Enable. The Database mirror is the host from which the signature database is updated. Unless there is a specific host from which you want the SnapGear unit to retrieve signature updates, leave this at the default setting of database.clamav.net. Select the frequency to Check for updates from the database mirror.
  • Page 191 Create a new user account: Note We recommend that you create a special user account to be used by the SnapGear unit for reading and writing to the network share. If you have an existing account or wish to make the network share readable and writeable by everyone, you may skip the next step.
  • Page 192 Begin by disabling simple file sharing for this folder. From the Tools menu, select Folder Options. Click the View tab and under the Advanced settings section uncheck Use simple file sharing (Recommended). Click OK. Next, share the folder. Right-click the folder and select Sharing and Security. Select Share this folder and note the Share name, you may change this to something easier to remember if you wish.
  • Page 193 Local storage Note SG565 only. Attach a USB storage device to one of the SnapGear unit’s USB ports. Under the Storage > Local Storage tab, select the partition or device to use from the Device pull-down menu, and click Submit. POP email The SnapGear unit can scan email being sent by PCs on your LAN before delivering it to the destination mail server.
  • Page 194 Check Transparent. If all of your internal email clients (such as Microsoft Outlook) are retrieving email from a single mail server only, enter it as the Default POP server. Uncheck Allow connections to other POP servers. If most, but not all, of your internal email clients are retrieving email from a single mail server, enter this as the Default POP server.
  • Page 195 If there is no single mail server from which most of your internal email clients are retrieving email, leave Default POP server blank and check Allow connections to other POP servers. Note For each of the email clients that is not retrieving email from the default POP server (this may be all email clients), the email client’s POP (or POP3) user name setting must be in the form of user@mail.isp.com, rather than simply user –...
  • Page 196 Note For each of the email clients for which to scan incoming mail, the email client’s POP3 user name setting must be in the form of user@mail.isp.com, rather than simply user – user is the POP3 login, and mail.isp.com is the POP3 mail server. Additionally, the email client’s incoming/POP3 email server setting must be sent to the SnapGear unit’s LAN IP address (e.g.
  • Page 197 When Inform requesting server of rejected mail is enabled the SnapGear unit rejects incoming mail that is detected to have a virus, and informs the requesting SMTP server that the mail has been dropped. This is the default and recommended behavior. When Inform requesting server of rejected mail is disabled the SnapGear unit accepts and then subsequently drops incoming mail that is detected to contain a virus.
  • Page 198 The SnapGear unit can scan files downloaded using FTP for viruses. Check Virus check FTP downloads. Typically there is no need to change the Proxy port on which the transparent proxy listens for connections. If an FTP connection is idle for the number of seconds specified by No activity timeout, it is automatically disconnected.

  • Page 199: Virtual Private Networking

    Virtual Private Networking Virtual Private Networking (VPN) enables two or more locations to communicate securely and effectively, usually across a public network (e.g. the Internet) and has the following key traits: Privacy - No one else can see what you are communicating . Authentication - You know who you are communicating with.

  • Page 200: Pptp And L2Tp

    PPTP and L2TP The SnapGear unit includes a PPTP and an L2TP VPN server. These allow remote Windows clients to securely connect to the local network. PPTP or L2TP are also commonly used to secure connections from a guest network; see the Guest Network section in the chapter entitled Network Setup.
  • Page 201 Check Enable PPTP Server. Enter the IP Addresses to give to remote hosts. This must be a free IP address, or a range of free IP addresses, from the network (typically the LAN) that the remote users are assigned while connected to the SnapGear unit. If you have configured several network connections, select the one that you want to connect remote users to from the IP Address to Assign VPN Server pull-down menu.
  • Page 202 Select the Required Encryption Level. Access is denied to remote users attempting to connect not using this encryption level. Strong Encryption (MPPE 128 Bit) is recommended. Select the Authentication Database. This allows you to indicate where the list of valid clients can be found.
  • Page 203 Your Internet IP address is displayed on the Network Setup page. If your ISP has not allocated you a static IP address, consider using a dynamic DNS service. Otherwise you must modify the PPTP client configuration each time your Internet IP address changes. For details on configuring dynamic DNS, refer to the DNS section of the chapter entitled Network Setup.
  • Page 204 Select Connect to a private network through the Internet and click Next. This displays the Destination Address window: Enter the SnapGear unit’s Internet IP address or fully qualified domain name and click Next. Select the Connection Availability you require on the next window and click Next to display the final window: Virtual Private Networking...
  • Page 205 Enter an appropriate name for your connection and click Finish. Your VPN client is now set up and ready to connect. Windows XP PPTP client setup Login as Administrator or with administrator privileges. From the Start menu, select Settings and then Network Connections. Click Create New Connection from the Network Tasks menu to the left.
  • Page 206 Select Connect to the network at my workplace and click Next. Select Virtual Private Network connection and click Next. Choose a Connection Name for the VPN connection, such as your company name or simply Office. Click Next. Virtual Private Networking...
  • Page 207 If you have set up your computer to connect to your ISP using dial up, select Automatically dial this initial connection and your dial-up account from the pull-down menu. If not, or if you wish to manually establish your ISP connection before the VPN connection, select Do not dial the initial connection.

  • Page 208: L2Tp Vpn Server

    Enter a user name and password added in the Configuring user accounts for VPN server section and click Connect. L2TP VPN Server To setup an L2TP/IPSec connection from a remote Windows XP client to your SnapGear unit and local network: Enable and configure the L2TP VPN server.
  • Page 209 Check Enable L2TP Server. Enter the IP addresses to give to remote hosts. This must be a free IP address, or a range of free IP addresses, from the network (typically the LAN) that the remote users are assigned while connected to the SnapGear unit. If you have configured several network connections, select the one that you want to connect remote users to from the IP Address to Assign VPN Server pull-down menu.
  • Page 210 Select the Required Encryption Level — access is denied to remote users attempting to connect not using this encryption level. Using Strong Encryption (MPPE 128 Bit) is recommended. Select the Authentication Database. This allows you to indicate where the list of valid clients can be found.
  • Page 211 Note Only one shared secret tunnel may be added. The one shared secret is used by all remote clients to authenticate. Select x.509 Certificate Tunnel to use x.509 certificates to authenticate the remote client against a Certificate Authority's (CA) certificate. The CA certificate must have signed the local certificates that are used for tunnel authentication.
  • Page 212 If adding an x.509 Certificate Tunnel, select the Local Certificate that you have uploaded to the SnapGear unit. Enter the Client Distinguished Name; it must match exactly the distinguished name of the remote party's local certificate to successfully authenticate the tunnel. Distinguished name fields are listed Note Certificates need to be uploaded to the SnapGear unit before a tunnel can be configured to use them (see Certificate Management in the IPSec section later in this chapter).
  • Page 213 Select Connect to the network at my workplace and click Next. Select Virtual Private Network connection and click Next. Choose a Connection Name for the VPN connection, such as your company name or simply Office. Click Next. Virtual Private Networking...
  • Page 214 If you have set up your computer to connect to your ISP using dial up, select Automatically dial this initial connection and your dial up account from the pull-down menu. If not, or you wish to manually establish your ISP connection before the VPN connection, select Do not dial the initial connection.

  • Page 215: Pptp And L2Tp Vpn Client

    To authenticate using an x.509 Certificate Tunnel, you must first install the local certificate. The distinguished name of this local certificate must match the name entered in Client Distinguished Name when configuring the x.509 certificate tunnel on the SnapGear unit. See Certificate Management and Using certificates with Windows IPSec in the IPSec section later in this chapter for details on creating, packaging and adding certificates for use by Windows IPSec.
  • Page 216 Select PPTP VPN Client or L2TP VPN Client from the VPN section of the main menu. Any existing client tunnels are displayed alongside icons to Enable/Disable, Delete, and Edit them. To add a new tunnel, click New. Ensure Enable is checked, and enter: A descriptive Name for the VPN connection.

  • Page 217: Ipsec

    A PPTP status icon appears in the system tray on the bottom right hand side of your computer, informing you that you are connected. You can now check your e-mail, use the office printer, access shared files and computers on the network as if you were physically on the LAN. Note Depending on how your remote network is set up, some additional configuration may be required to enable browsing the network (such as Network Neighborhood or My...

  • Page 218: Quick Setup

    Quick Setup This section uses the Quick Setup to connect the two sites together. For more control over the configuration options, see Set Up the Branch Office on page 215. Enable IPSec Select IPSec from the VPN section of the main menu. A page similar to the following is displayed.
  • Page 219 Fill in the Tunnel name field with your name for the tunnel. The name must not contain spaces or start with a number. In this example, enter Headquarters. Leave the Enable this tunnel checkbox checked. Enter The remote party’s IP address, which is the IP address of the remote party’s IPSec endpoint.
  • Page 220 [Siemens] Trust Center Global ID The attribute/value pairs must be of the form attribute=value and be separated by commas. For example: C=US, ST=Illinois, L=Chicago, O=Secure Computing, OU=Sales, CN=SG550. It must match exactly the Distinguished Name of the remote party's local certificate to successfully authenticate the tunnel.

  • Page 221: Set Up The Branch Office

    When making a certificate based tunnel between Secure Computing SnapGear units, you can obtain the Distinguished Name of a remote device's Certificate from the Details column of the appropriate local certificate on the Certificate Lists tab of the IPSec page.
  • Page 222 Warning It may be necessary to reduce the MTU of the IPSec interface if large packets of data are not being transmitted. Configure a tunnel to connect to the headquarters office To create an IPSec tunnel, click the IPSec link on the left side of the web management console and then click the Advanced under Tunnel List.
  • Page 223 Note Select an interface other than the default gateway when you have more than one Internet connection or have configured aliased Internet interfaces, and require the IPSec tunnel to run on an interface other than the default gateway. From the Keying drop-down, select the type of keying for the tunnel to use. The SnapGear unit supports the following types of keying: Main Mode automatically exchanges encryption and authentication keys and protects the identities of the parties attempting to establish the tunnel.
  • Page 224 DNS hostname address to static IP address DNS hostname address to DNS hostname address DNS hostname address to dynamic IP address From the Local address drop-down, select the type of IPSec endpoint this SnapGear unit has on the interface on which the tunnel is going out. The SnapGear unit can either have a static IP, dynamic IP or DNS hostname address.
  • Page 225 In this example, select the Preshared Secret option. Click Next to configure the Local Endpoint Settings. Local endpoint settings Leave the Initiate Tunnel Negotiation checkbox checked. Note This option is not available when the SnapGear unit has a static IP address and the remote party has a dynamic IP address.
  • Page 226 Note If the remote party is a SnapGear unit, the ID must have the form abcd@efgh. If the remote party is not a SnapGear unit, refer the interoperability documents on the SG Knowledge Base (http://www.cyberguard.com/snapgear/knowledgebase.html) to determine what form it must take. In this example, enter: branch@office Leave the IP Payload Compression checkbox unchecked.
  • Page 227 Authentication Key is the ESP Authentication Key. It must be of the form 0xhex, where hex is one or more hexadecimal digits. The hex part must be exactly 32 characters long when using MD5 or 40 characters long when using SHA1 (excluding any underscore characters).
  • Page 228 Enter the Internet IP address of the remote party in The remote party's IP address field. In this example, enter: 209.0.0.1. The Optional Endpoint ID is used to authenticate the remote party to the SnapGear unit. The remote party's ID is optional if it has a static IP address and uses Preshared Secrets for authentication.
  • Page 229 Organizational Unit Common Name Name Given name Surname Initials Personal title E-mail Email E-mail Serial number Description TCGID [Siemens] Trust Center Global ID The attribute/value pairs must be of the form attribute=value and be separated by commas. For example : C=US, ST=Illinois, L=Chicago, O=SecureComputing, OU=Sales, CN=SG550.
  • Page 230 Authentication Key field is the ESP Authentication Key. However, this applies to the remote party. It must be of the form 0xhex, where hex is one or more hexadecimal digits. The hex part must be exactly 32 characters long when using MD5 or 40 characters long when using SHA1 (excluding any underscore characters).
  • Page 231 The Rekeyfuzz value refers to the maximum percentage by which the Rekeymargin should be randomly increased to randomize rekeying intervals. The Key lifetimes for both Phase 1 and Phase 2 are dependent on these values and must be greater that the value of “Rekeymargin x (100 + Rekeyfuzz) / 100.”...
  • Page 232 Local Certificate pull-down menu contains a list of the local certificates that have been uploaded for x.509 authentication. Select the required certificate to be used to negotiate the tunnel. This field appears when x.509 Certificates has been selected. Phase 2 settings page Specify the Local Networks and Remote Networks to link together with the IPSec tunnel.

  • Page 233: Configuring The Headquarters

    Select a Phase 2 Proposal. Any combination of the ciphers, hashes, and Diffie Hellman groups that the SnapGear unit supports can be selected. The supported ciphers are DES, 3DES and AES (128, 196 and 256 bits). The supported hashes are MD5 and SHA and the supported Diffie Hellman group are 1 (768 bit), 2 (1024 bit) and 5 (1536 bits).
  • Page 234 Select the Internet interface the IPSec tunnel is to go out on. In this example, select default gateway interface option. Select the type of keying for the tunnel to use. In this example, select the Aggressive mode with Automatic Keying (IKE) option. Select the type of IPSec endpoint this SnapGear unit has.
  • Page 235 Phase 1 settings page Set the length of time before Phase 1 is renegotiated in the Key lifetime (s) field. In this example, leave the Key Lifetime as the default value of 3600 minutes. Set the time for when the new key is negotiated before the current key expires in the Rekeymargin field.

  • Page 236: Tunnel List

    Tunnel List Connection Once a tunnel has been configured, an entry with the tunnel name in the Connection field is shown. Note You may modify, delete or disable/enable a tunnel by clicking on the corresponding Edit, Delete or Enable/Disable icon. Remote party The Remote Party which the tunnel is configured to connect to is defined either by its Endpoint ID, IP Address or Distinguished Name.
  • Page 237 o IPSec is disabled. o The tunnel is disabled. o The tunnel could not be loaded due to misconfiguration. Negotiating Phase 1 indicates that IPSec is negotiating Phase 1 to establish the tunnel. Aggressive or Main mode packets (depending on tunnel configuration) are transmitted during this stage of the negotiation process.
  • Page 238 Diffie Hellman Groups Loaded lists the Diffie Hellman groups and Oakley group extensions that can be configured for both Phase 1 and Phase 2 negotiations. Connection Details lists an overview of the tunnel's configuration. It contains the following information: An outline of the tunnel's network setup. In this example, it is 192.168.2.0/24===209.0.0.2(branch@office)...209.0.0.1===192.168.1.0/24 Phase 1 and Phase 2 key lifetimes (ike_life and IPSec_life respectively).

  • Page 239: Nat Traversal Support

    Negotiation State reports what stage of the negotiation process the tunnel is in. In this example it has initiated and sent the first aggressive mode packet (AI1) and is expecting its response (AR1) in the line STATE_AGGR_I1 (sent AI1, expecting AR1). Once the Phase 1 has been successfully negotiated, the status displays ISAKMP SA established.
  • Page 240 If you do not have access to certificates issued by a certificate authority (CA), you may create self-signed certificates; see Creating certificates further on. The OpenSSL application The remainder of this section requires OpenSSL application, run from a Windows command prompt (Start > Run > type cmd) or Linux shell prompt. A Windows version of OpenSSL is provided in the openssl directory of the SG CD.
  • Page 241 openssl pkcs12 -nomacver -nocerts -in pkcs12_file -out local_private_key.pem .. where pksc12_file is the PKCS12 file issued by the CA and local_private_key.pem is the local private key certificate to be uploaded into the SnapGear unit. When the application prompts you to Enter Import Password, enter the password used to create the certificate.
  • Page 242 Create the CA certificate, omit the –nodes option if you want to use a password to secure the CA key: openssl req -config openssl.cnf -new -x509 -keyout rootCA/ca.key -out rootCA/ca.pem -days DAYS_VALID -nodes .. where DAYS_VALID is the number of days the root CA is valid for. Create local certificate pairs For each local certificate you wish to create, there are two steps.
  • Page 243 To install the new PCKS12 file, cert1.p12, on Windows XP, open up the Microsoft Management Console (Start > Run > then type mmc). Add the Certificate Snap-in (File > Add/Remove Snap-in > Add > select Certificates > Add > select the account level you want the certificates installed for (i.e. current user vs. all users) (>...

  • Page 244: Ipsec Failover

    Certificates have time durations in which they are valid. Ensure that the certificates uploaded are valid and that the Date and Time settings have been set correctly on the SnapGear unit. IPSec Failover Note SG560, SG565, SG570, SG575, SG580, SG710 only. The SnapGear unit can be configured to failover and fall forward between IPSec connections.
  • Page 245 Keying: Aggressive mode (IKE) Local address: Static IP address Remote address: Dynamic IP address Route to remote endpoint: Internet port's gateway Remote required endpoint ID: primary@branch Local network: 192.168.1.0/255.255.255.0 Remote network: 192.168.2.0/255.255.255.0 Branch office SG configuration: Tunnel name: PrimaryLink Enable this tunnel: Unchecked Local interface: Default gateway interface Keying: Aggressive mode (IKE) Local optional endpoint ID: primary@branch...
  • Page 246 Tunnel name: SecondaryLink Enable this tunnel: Unchecked Local interface: Default gateway interface Keying: Aggressive mode (IKE) Local optional endpoint ID: secondary@branch The remote party's IP address: 209.0.1.1 Local network: 192.168.2.0/255.255.255.0 Setup an unused aliased IP address on the LAN interface of both the Headquarter and Branch Office SGs.
  • Page 247 Local network: 192.168.11.1/255.255.255.255 Remote network: 192.168.12.1/255.255.255.255 Phase 2 key lifetime (sec): 7200 Branch Office SG configuration: Tunnel name: PrimaryLinkTest Enable this tunnel: Unchecked Local Interface: Default gateway interface Keying: Aggressive mode (IKE) Local optional endpoint ID: primarytest@branch The remote party's IP address: 209.0.0.1 Local network: 192.168.12.1/255.255.255.255 Remote network: 192.168.11.1/255.255.255.255 Manually edit the ifmond.conf on both the Branch Office SG to configure for IPSec...
  • Page 248 retry_delay test_delay 5 test ifretry 2 5 ping -I 192.168.2.1 192.168.1.1 -c 3 connection secondarylink parent conn-eth1 start IPSec auto --add SecondaryLink start IPSec auto --up SecondaryLink stop IPSec whack --delete --name SecondaryLink maximum_retries 2147483647 retry_delay test_delay 5 test ifretry 2 5 ping -I 192.168.2.1 192.168.1.1 -c 3 service service-IPSec group primarylinktest group secondarylink...
  • Page 249 Setup an IPSec tunnel between the primary Internet IP Addresses (209.0.0.1 <> 210.0.0.1). Default values are used in the configuration unless otherwise specified below: Headquarters SG configuration: Tunnel name: PrimaryLink Local interface: Internet port Route to remote endpoint: Internet port's gateway The remote party's IP address: 210.0.0.1 Local network: Address of Internet port Remote network: Remote endpoint...
  • Page 250 Local interface: DMZ port Route to remote endpoint: DMZ port's gateway The remote party's IP address: 210.0.1.1 Local network: Address of DMZ port Remote network: Remote endpoint Branch Office SG configuration: Tunnel name: SecondaryLink Enable this tunnel: Checked Local interface: DMZ port Route to remote endpoint: DMZ port's gateway The remote party's IP address: 209.0.1.1 Local network: Address of DMZ port...
  • Page 251 GRE tunnel for primary link: GRE tunnel name: PrimaryLink Remote address: 209.0.0.1 Local address: 210.0.0.1 Firewall class: LAN GRE tunnel for secondary link: GRE tunnel name: SecondaryLink Remote address: 209.0.1.1 Local address: 210.0.1.1 Firewall class: LAN Manually edit the ifmond.conf on both the Headquarter and Branch Office SG to configure for IPSec failover and fall forward.
  • Page 252 retry_delay test_delay 5 connection primary_ping parent conn-gre1 maximum_retries 2147483647 retry_delay test_delay 5 test ifretry 2 5 ping -I 209.0.0.1 210.0.0.1 -c 3 connection secondary_ping parent conn-gre2 maximum_retries 2147483647 retry_delay test_delay 5 test ifretry 2 5 ping -I 209.0.1.1 210.0.1.1 -c 3 service service-IPSec group primary_ping group secondary_ping...

  • Page 253: Ipsec Troubleshooting

    parent secondary_ping start route add -net 192.168.1.0 netmask 255.255.255.0 dev gre2 stop route del -net 192.168.1.0 netmask 255.255.255.0 dev gre2 maximum_retries 2147483647 retry_delay test_delay 5 connection primary_ping parent conn-gre1 maximum_retries 2147483647 retry_delay test_delay 5 test ifretry 2 5 ping -I 210.0.0.1 209.0.0.1 -c 3 connection secondary_ping parent conn-gre2...
  • Page 254 Symptom: Tunnel is always down even though IPSec is running and the tunnel is enabled. Possible Cause: The tunnel is using Manual Keying and the encryption and/or authentication keys are incorrect. The tunnel is using Manual Keying and the SnapGear unit’s and/or remote party's keys do not correspond to the Cipher and Hash specified.
  • Page 255 Symptom: Tunnel goes down after a while Possible Cause: The remote party has gone down. The remote party has disabled IPSec. The remote party has disabled the tunnel. The tunnel on the SnapGear unit has been configured not to rekey the tunnel. The remote party is not rekeying correctly with the SnapGear unit.

  • Page 256: Port Tunnels

    Possible cause: Windows network browsing broadcasts are not being transmitted through the tunnel. Solution: Set up a WINS server and use it to have the remote hosts resolve names to IP addresses. Set up LMHOST files on remote hosts to resolve names to IP adresses. Symptom: Tunnel comes up but the application does not work across the tunnel.
  • Page 257 The SnapGear unit supports two kinds of port tunnels. HTTP Tunnels are port tunnels that send data using the HTTP protocol, and are not encrypted. HTTP tunnels are not encrypted. They can be useful when the SnapGear unit is behind a firewall that only allows outgoing HTTP connections and blocks all other traffic.
  • Page 258 The following field is displayed for SSL Tunnel Server only: You may specify the Protocol to use when negotiating the SSL connection. Leave this set to Raw when incoming connections are from a tunnel client. Setting Protocol to another value allows the tunnel server to accept connections directly from an SSL client other than a tunnel client, e.g.
  • Page 259 If the HTTP proxy is a buffering proxy, then enter the Proxy Buffer Size. Otherwise set this field to 0. You may also specific the timeout before sending padding to fill up the buffer size in Proxy Padding Timeout. The following field is displayed for SSL Tunnel Server only: You may specify the Protocol to use when negotiating the SSL connection.

  • Page 260: Usb

    Note SG565 only. The SG565 has two USB (Universal Serial Bus) ports to which you can attach USB storage devices (e.g. hard drives, flash drives, card readers), USB printers, USB network devices and USB narrowband (non-DSL) modems. A USB hub may be used if you need to attach more than two USB devices simultaneously.
  • Page 261 This section describes how to set up the SnapGear unit for network attached storage. For information on using a USB mass storage device as a print spool, refer to the USB Printers section. Share the storage device Select Shares from the Networking section of the main menu. Click the Storage tab. All USB Devices or device Partitions that are available to share are listed along with their Sizes and for previously configured shares, their Share Names.
  • Page 262 Browsable: Display an icon for the network when browsing the network from a Windows PC. To access the network share when this is unchecked, the user must manually enter the address in the address bar (e.g. \\SG565\public\). Writable: The network share is writable, i.e. users can modify and create new files. Public: A login and password is not required to access the network share.
  • Page 263 Join a Windows workgroup The next step is to configure your SnapGear unit to join your Window workgroup or domain. Select Network Setup from the Networking menu. Click the Advanced tab. Under the Unit Workgroup heading, enter the name of your Windows workgroup or domain and click Apply.
  • Page 264 Partitioning a USB mass storage device Warning This procedure is intended for experts and power users only. The standard Linux command line tools are present on the SnapGear unit for partitioning (fdisk) and creating filesystems (mkfs) on an attached USB mass storage device. Alternatively, you may use the standard Windows tools or a third party utility such as PartitionMagic to partition a USB mass storage device before attaching it to the SnapGear unit.
  • Page 265 Command (m for help): p Disk /dev/sda: 5 heads, 50 sectors, 1024 cylinders Units = cylinders of 250 * 512 bytes Device Boot Start Blocks System /dev/sda1 1024 127975 Win95 FAT32 Delete any existing partitions by typing d the entering the partition number, e.g. enter 1 to delete /dev/sda1.
  • Page 266 Repeat the process for each partition to want to create. For the last partition, the default last cylinder is generally be fine. Command (m for help): n Command action extended primary partition (1-4) Partition number (1-4): 2 First cylinder (526-1024, default 526): Using default value 526 Last cylinder or +size or +sizeM or +sizeK (526-1024, default 1024):...

  • Page 267: Usb Printers

    mkfs.vfat –F 32 /dev/sda1 then mkfs.vfat –F 32 /dev/sda2 From the web management console, select Advanced from the System menu, and click Reboot. The partitions are now ready to use. USB Printers The SnapGear unit’s print server allows you to share attached USB printers with your LAN.
  • Page 268 Select Shares from the Networking section of the main menu. Click the Printing tab. Locate the printer to share and click its Edit icon. Enter a short descriptive Name for the printer. This is the name that is displayed when browsing your Windows workgroup or domain, and the name of the queue for LPR / LPD connections.
  • Page 269 Otherwise, attach the USB mass storage device and select the device or device partition on which to store the print spool from the Spool pull-down menu under the Printing tab. Note You may simultaneously use a USB mass storage device or device partition as a print spool and a Network Attached Storage device.
  • Page 270 Select A network printer, or a printer attached to another computer and click Next. Select Browse for a printer and click Next. Locate the SnapGear unit by expanding your Windows workgroup and locating the SG by its hostname. The hostname is set on the SnapGear unit under Network Setup >...
  • Page 271 You may receive a warning about the SnapGear unit automatically installing print drivers on your PC. Ignore it, the SG does not install print drivers automatically. If a dialog is displayed to inform you that no appropriate print driver could be found on the SnapGear unit, click OK.
  • Page 272 Select your printer model and click OK. If your printer model is not listed, click Have Disk and Browse again. Drivers for several different printers and different operating systems are often distributed together by the manufacturer, so there may by several different .inf files. Follow the onscreen instructions to install the printer driver.

  • Page 273: Printer Troubleshooting

    LPR / LPD setup Note This information is generally not relevant for Windows network environments. Once the print server has been set up, the SnapGear unit also listen on the standard LPR / LPD network port (TCP 515) for incoming print jobs. Set up your LPR client to print to a remote LPD queue as specified by your operating system’s documentation.

  • Page 274: Usb Network Devices And Modems

    Disable Advanced Printing Features by clicking Control Panel Printers and Faxes > > right-click printer Properties Advanced and uncheck Enable Advanced Printing > > > Features. Disable Bidirectional Support by clicking Control Panel Printers and Faxes right- > > click printer Properties Ports and uncheck Enable Bidirectional Support.

  • Page 275: System

    System Date and Time Note For details on how the SnapGear unit stores and retrieves the date and time between reboots, see the appendix entitled System Clock. We recommend setting the SnapGear unit’s clock to the correct date and time, otherwise system log message time stamps do not match the time of the event.
  • Page 276 Network time Select Date and Time from the System section of the main menu, then the NTP Time Server tab. Check the Enabled box under the NTP Time Server heading and click Submit. Local hosts can now synchronize their clocks to the SnapGear unit’s by specifying the SnapGear unit’s IP address as their network time server.

  • Page 277: Backup/Restore Configuration

    Select Date and Time from the System section of the main menu, then the NTP Time Server tab. Enter the IP Address of the NTP server. Select Peer from the Type drop down box. Click Add. Locality Select Date and Time from the System section of the main menu, then the Locality tab. Select your local Region and click Submit.
  • Page 278 Remote backup/restore Click the Remote backup/restore tab. To back up your configuration, enter and confirm a Password with which to protect this file and click Submit. Save the file in a safe place. Note Ensure this is a hard to guess password, as all passwords including IPSec passwords and private keys are downloaded into your saved configuration.
  • Page 279 Enter a Description for this configuration. It is not necessary to include the time and date in the description, they are recorded automatically. Note Each configuration snapshot stores a single configuration only, existing configuration snapshots on the SnapGear unit are not saved inside any subsequent snapshots. Restore locally backed up configurations by click its corresponding Restore icon in the Restore or Delete Configuration.

  • Page 280: Users

    Users This section details adding administrative users, as well as local users for PPTP, L2TP or dial-in access, or access through the access control web proxy (see the Access Control section in the chapter entitled Firewall). Administrative users Administrative user accounts on a SnapGear unit allow administrative duties to be spread amongst a number of different people according to their level of competence and trust.
  • Page 281 You may specify the following access controls for each administrative user. The Login control provides the user with telnet and ssh access to the command-line administration interface of the SnapGear unit. The Administration control provides the user with the ability to make changes to the SnapGear unit’s configuration via the web-based administration interface.
  • Page 282 Warning A user with Encrypted save / restore all access can conceivably create an encrypted config file with an arbitrary root password that they can restore, thus granting them Administration privileges. Therefore, grant Encrypted save / restore all only to users that you trust with Administration access. The Change Password control provides the user with the ability to change their password.
  • Page 283 Enter a User name (login name), an optional Description, and enter and confirm a Password. For dial-in, PPTP and L2TP users, you may also optionally enter a Domain name if your network has a Windows domain server. You may specify the following access controls for each local user. The Dial-in Access control provides the user with the authority to connect to the SnapGear unit’s dial-in server.
  • Page 284 To test your configuration click the Test RADIUS tab and enter the user name and password of a valid user. A RADIUS request is sent to the server and the result are displayed. If no response is received, carefully check the IP address of the RADIUS server and also the shared secret configuration for this device (NAS).

  • Page 285: Management

    The SnapGear unit may be management remotely using Secure Computing Global Command Center (GCC), Secure Computing Centralized Management Server (CMS) or Simple Network Management Protocol (SNMP). To enable remote management by a Secure Computing Global Command Center server, check Enable Central Management. Enter the Global Command Center Server Host Name.
  • Page 286 To enable remote management by a Secure Computing Central Management Server, check Enable Central Management. In IP Address of CMS, enter the IP address of the host on which Secure Computing CMS is running. System...
  • Page 287 Specify the shared Authentication Key with which to authenticates this device against the CMS. This must be the same as the snmp_community configuration setting for CMS. It should be something hard to guess. When configured for centralised management, the device periodically sends a "ping" (SNMP trap) back to the CMS to indicate that it is alive.

  • Page 288: Diagnostics

    Enter the name of a community that is allowed read-write access in Read-Write Community. You may optionally include an IP address or network to restrict who is allowed access. You may optionally include an OID to restrict the fields that are accessible.
  • Page 289 Log output is color coded by output type. General information and debug output is black, warnings and notices are blue, and errors are red. The Display pull-down menu underneath the log output allows you to filter the log output to display this is based on output type. Appendix B contains for details on interpreting log output and configuring advanced log rules.
  • Page 290 Enter the Remote Port on which the remote syslog server is listening for syslog messages. Typically, the default is correct. Set the Filter Level to only send syslog messages at this level or above. You may also Include extended ISO date, which is prepended to syslog messages before being sent.
  • Page 291 Specify the number of seconds to wait after recieving a system log message before sending an email in Delay to Send (s). This allows multiple system log messages to accumulate before sending an email containing them all. Messages per Email is the maximum number of system log messages that are allowed to accumulate before sending the email.

  • Page 292: Advanced

    Advanced The following options are intended for network administrators and advanced users only. Warning Altering the advanced configuration settings may render your SnapGear unit inoperable. Reboot and Reset Rebooting does not erase your SnapGear unit’s configuration, however network connections such as your Internet connection, VPN tunnels, etc. are terminated and re- established when the device is up and running again.

  • Page 293: Flash Upgrade

    This jumper is labeled Remove Link to Disable Erase. Flash upgrade Periodically, Secure Computing may release new versions of firmware for your SnapGear unit. If a new version fixes an issue you’ve been experiencing, or contains a new feature you wish to use, contact SG technical support for information on obtaining the latest firmware.
  • Page 294 Select Advanced from the System section of the main menu and click the Flash Upgrade tab. Click Browse to locate the .sgu file on your local PC and click Upgrade. Enter Extra Parameters only at the request of Secure Computing technical support staff. Flash upgrade via TFTP An alternative method is to install and configure a TFTP server.

  • Page 295: Configuration Files

    Note Although we recommend it, this program is not supported by Secure Computing. Download the binary image file (.sgu). Contact SG technical support for instructions on obtaining this file. Place this file in the directory your TFTP is serving files from, usually: /tftpboot/ Establish a telnet or ssh connection to the SnapGear unit.

  • Page 296: Support

    You may also create a new file by clicking New. Upload file Click Browse to locate the file on your local PC that you want to upload. You may upload it to an alternative file name on the SnapGear unit by specifying a Destination File Name.
  • Page 297 The Technical Support Report should be generated when the issue is occurring on each of the appliances involved, and attached in plain text format. Otherwise, the Secure Computing technical support staff are unlikely to have enough information to assist you.

  • Page 298: Appendix A - Terminology

    Appendix A – Terminology This section explains some of the terms that are commonly used in this document. Term Meaning ADSL Asymmetric Digital Subscriber Line. A technology allowing high-speed data transfer over existing telephone lines. ADSL supports data rates between 1.5 and 9 Mbits/s when receiving data and between 16 and 640 Kbit/s when sending data.
  • Page 299 Term Meaning Certificates A digitally signed statement that contains information about an entity and the entity's public key, thus binding these two pieces of information together. A certificate is issued by a trusted organization (or entity) called a Certification Authority (CA) after the CA has verified that the entity is who it says it is.
  • Page 300 Term Meaning Ethernet A physical layer protocol based upon IEEE standards. Extranet A private network that uses the public Internet to securely share business information and operations with suppliers, vendors, partners, customers, or other businesses. Extranets add external parties to a company's intranet.
  • Page 301 Term Meaning IPSec tunnel The IPSec connection to securely link two private parties across insecure and public channels. IPSec with Dynamic DNS can be run on the IPSec endpoints thereby creating an Dynamic DNS IPSec tunnel using dynamic IP addresses. IKE is a profile of ISAKMP that is for use by IPSec.
  • Page 302 Term Meaning Network Address Translation. The translation of an IP address used on one network to an IP address on another network. Masquerading is one particular form of NAT. Net mask The way that computers know which part of a TCP/IP address refers to the network, and which part refers to the host range.
  • Page 303 Term Meaning Router A network device that moves packets of data. A router differs from hubs and switches because it is "intelligent" and can route packets to their final destination. RSA Digital A public/private RSA key pair used for authentication. The SnapGear Signatures unit can generate these key pairs.
  • Page 304 Term Meaning x.509 Certificates An x.509 certificate includes the format of the certificate, the serial number of the certificate, the algorithm used to sign the certificate, the name of the CA that issued the certificate, the name and public key of the entity requesting the certificate, and the CA's signature.x.509 certificates are used to authenticate the remote party against a Certificate Authority's (CA) certificate.

  • Page 305: Appendix B - System Log

    Appendix B – System Log Access Logging It is possible to log any traffic that arrives at or traverses the SnapGear unit. The only logging that is enabled by default is to take note of packets that were dropped. While it is possible to specifically log exactly which rule led to such a drop, this is not configured by default.
  • Page 306 Commonly used interfaces are: eth0 the LAN port eth1 the WAN/Internet port pppX e.g. ppp0 or ppp1, a PPP session IPSecX e.g. IPSec0, an IPSec interface The firewall rules deny all packets arriving from the WAN port by default. There are a few ports open to deal with traffic such as DHCP, VPN services and similar.

  • Page 307: Creating Custom Log Rules

    A typical Default Deny: looks similar to the following: Mar 27 09:31:19 2003 klogd: Default deny: IN=eth1 OUT=MAC=00:d0:cf:00:ff:01:00:e0:29:65:af:e9:08:00 SRC=140.103.74.181 DST=12.16.16.36 LEN=60 TOS=0x10 PREC=0x00 TTL=64 ID=46341 DF PROTO=TCP SPT=46111 DPT=139 WINDOW=5840 RES=0x00 SYN URGP=0 That is, a packet arriving from the WAN (IN=eth1) and bound for the SnapGear unit itself (OUT=<nothing>) from IP address 140.103.74.181 (SRC=140.103.74.181), attempting to go to port 139 (DPT=139, Windows file sharing) was dropped.
  • Page 308 To log permitted inbound access requests to services hosted on the SnapGear unit, the rule should look something like this: iptables -I INPUT -j LOG -p tcp --syn -s <X.X.X.X/XX> -d <Y.Y.Y.Y/YY> --dport <Z> --log-prefix <prefix> This logs any TCP (-p tcp) session initiations (--syn) that arrive from the IP address/netmask X.X.X.X/XX (-s ...) and are going to Y.Y.Y.Y/YY, destination port Z (-- dport).
  • Page 309 iptables -I FORWARD -j LOG -p tcp --syn -s 5.6.7.8/32 -d 192.168.1.1 --dport 25 --log-prefix "Mail for flubber: " This results in log output similar to: <12> Jan 24 18:17:19 2000 klogd: Mail for flubber: IN=eth1 OUT=eth0 SRC=5.6.7.8 DST=192.168.1.1 LEN=48 TOS=0x00 PREC=0x00 TTL=126 ID=45507 DF PROTO=TCP SPT=4088 DPT=25 WINDOW=64240 RES=0x00 SYN URGP=0 Note how the OUT value has now changed to show which interface the access attempt...

  • Page 310: Rate Limiting

    If we just wanted to look at traffic that went out to the IPSec world, we could use: iptables -I FORWARD -j LOG -o IPSec+ Clearly there are many more combinations possible. It is therefore possible to write rules that log inbound and outbound traffic, or to construct several rules that differentiate between the two.

  • Page 311: Administrative Access Logging

    Administrative Access Logging When a user tries to log onto the web management console, one of the following log messages appears: Jan 30 03:00:18 2000 boa: Authentication successful for root from 10.0.0.2 Jan 30 03:00:14 2000 boa: Authentication attempt failed for root from 10.0.0.2 This message shows the date/time, whether the authentication succeeded or failed, the user attempting authentication (in this case root) and the IP address from which the...

  • Page 312: Appendix C - Firmware Upgrade Practices And Precautions

    Appendix C – Firmware Upgrade Practices and Precautions Prior performing any firmware upgrade, it is important that you save a back up of your existing configuration (see the Save/Restore section in the chapter entitled System) to a local file. While we make every effort to ensure your existing configuration continues working after minor and patch revision upgrades, sometimes compatibility problems may arise.
  • Page 313 If you encounter any problems, reset the device to its factory default settings and reconfigure. You may wish to use your backed up old configuration as a guide in this process, but do not restore it directly. If you are upgrading a device that you do not normally have physical access to, e.g. at a remote or client's site, we strongly recommend that following the upgrade, you reset the device to its factory default configuration and reconfigure as a matter of course.

  • Page 314: Appendix D - Recovering From A Failed Upgrade

    Appendix D – Recovering From a Failed Upgrade Note Please read this appendix before requesting an RMA from customer support. If the Heart beat (or H/B) LED is not flashing 20 – 30 seconds after power is supplied, the SnapGear unit is unable to boot correctly. This is usually because the firmware inside the SnapGear unit has been written incorrectly or incompletely, or in rare cases it may have become corrupted.
  • Page 315 The following details the steps required to perform a recovery boot using the Netflash program on a Windows PC. Attach the SnapGear unit’s LAN port or switch directly to your PC using a crossover cable. Login to your PC with administrator privileges (2000/XP/NT4 only). Ensure there are no DHCP server programs or services (Start >...
  • Page 316 Wait for the recovery procedure to complete and the SnapGear unit to finish reprogramming. Note It may take up to 15 minutes for your SG to finish reprogramming. After it has finished it reboots automatically with its old configuration intact. If it is uncontactable after rebooting, hit the Reset/Erase button twice within 2 seconds to restore factory default configuration, then follow the instructions in the chapter entitled Getting Started to begin reconfiguration of your unit.
  • Page 317 Place the firmware file and recovery file in your BOOTP server’s path, e.g.: /tftpboot/ Edit your BOOTP server configuration to contain an entry for the SnapGear unit. Specify the recovery image file (.sgr) as the file to boot. The entry may look something like: host SG300 { hardware ethernet 00:D0:CF:01:02:03; filename "SG300-Recover_v1.0.2_20060224.sgr";...

  • Page 318: Appendix E - System Clock

    SnapGear unit has been powered down for longer periods of time. Units without a hardware clock Note SG300 only. As these units have no battery-powered hardware clock, the current date and time is not kept across reboots, and particularly will not be accurate after the SnapGear unit has been powered for longer periods of time.

  • Page 319: Appendix F - Null Modem Administration

    Appendix F – Null Modem Administration This section details how to enable your SnapGear unit for administration from a local PC using a null modem serial cable. This allows the local PC to “dial in” directly to the SnapGear unit’s serial port without using a modem.
  • Page 320 Select Set up an advanced connection and click Next. Select Connect directly to another computer and click Next. Select Guest and click Next. In Computer Name, enter an arbitrary name for this connection (e.g. SG null modem) and click Next. From the Select device drop down box, select the local PC’s serial (COM) port to which the null modem is attached, click Next.

  • Page 321: Appendix G - Command Line Interface (Cli)

    ARP SG550, SG560, SG565, cache SG570, SG575, SG580, SG635, SG710, SG810 auth-down SnapGear program to run when SG300, SG530, SG550, pptp/pptpd are brought up SG560, SG565, SG570, SG575, SG580, SG630, SG635, SG710, SG810 auth-up SnapGear program to run when...
  • Page 322 Program Name Description Supported Products SnapGear bridge control SG300, SG530, SG550, program SG560, SG565, SG570, SG575, SG580, SG630, SG635, SG710, SG810 brctl ethernet bridge administration SG300, SG530, SG550, SG560, SG565, SG570, SG575, SG580, SG630, SG635, SG710, SG810 busybox multi-call UNIX utility binary...
  • Page 323 SG565, SG575, SG580, commands SG635, SG710, SG810 date print or set the system date and SG300, SG530, SG550, time SG560, SG565, SG570, SG575, SG580, SG630, SG635, SG710, SG810 convert and copy a file SG565, SG575, SG580,...
  • Page 324 SG565, SG575, SG580, SG635, SG710, SG810 enroll SnapGear GCC program to SG300, SG550, SG560, enroll in a certificate given a ca SG565, SG570, SG575, certificate SG580, SG635, SG710, SG810 erase A tool for erasing MTD partitions SG710...
  • Page 325 Program Name Description Supported Products firewall SnapGear firewall utility SG300, SG530, SG550, SG560, SG565, SG570, SG575, SG580, SG630, SG635, SG710, SG810 firewallenv SnapGear firewall utility SG300, SG530, SG550, SG560, SG565, SG570, SG575, SG580, SG630, SG635, SG710, SG810 flash SnapGear flash utility wrapper...
  • Page 326 Program Name Description Supported Products gcc_get_config SnapGear utility to output config SG300, SG550, SG560, in GCC format SG565, SG570, SG575, SG580, SG635, SG710, SG810 gen-keys ssh key generation program SG550, SG560, SG565, SG570, SG575, SG580, SG635, SG710, SG810 gen-ssl-cert SnapGear openssl wrapper...
  • Page 327 SG530, SG550, SG560, SG565, SG570, SG575, SG580, SG630, SG635, SG710, SG810 httpd fnord http web server daemon SG300, SG530, SG550, SG560, SG565, SG570, SG575, SG580, SG630, SG635, SG710, SG810 https-certgen SnapGear tool to generate SG300, SG550, SG560, default http ssl certificates...
  • Page 328 Program Name Description Supported Products inetd network super-server daemon SG300, SG530, SG550, SG560, SG565, SG570, SG575, SG580, SG630, SG635, SG710, SG810 inetd-echo network echo utility SG300, SG530, SG550, SG560, SG565, SG570, SG575, SG580, SG630, SG635, SG710, SG810 init process control initialization...
  • Page 329 Program Name Description Supported Products iptables-save Save IP Tables SG300, SG530, SG550, SG560, SG565, SG570, SG575, SG580, SG630, SG635, SG710, SG810 iwconfig configure a wireless network SG565 interface iwgetid Report ESSID, NWID or AP/Cell SG565 Address of wireless network Get more detailed wireless...
  • Page 330 SG565 spooling queue list directory contents SG565, SG575, SG580, SG635, SG710, SG810 program to show the status of SG300, SG530, SG550, lsmod modules in the Linux Kernel SG560, SG565, SG570, SG575, SG580, SG630, SG635, SG710, SG810 list all PCI devices...
  • Page 331 SnapGear wrapper program to SG565, SG575, SG580, start the squid Web Cache SG635, SG710, SG810 mtuchk SnapGear MTU checking utility SG300, SG530, SG550, SG560, SG565, SG570, SG575, SG580, SG630, SG635, SG710, SG810 move (rename) files SG565, SG575, SG580, SG635, SG710, SG810...
  • Page 332 Program Name Description Supported Products openssl OpenSSL command line tool SG300, SG550, SG560, SG565, SG570, SG575, SG580, SG635, SG710, SG810 openvpn secure IP tunnel daemon SG565, SG580, SG710 an OSPF v2 routing engine for SG565, SG575, SG580, ospfd use with Zebra...
  • Page 333 Program Name Description Supported Products pptp_callmgr PPTP Call manager for the SG300, SG530, SG550, PPTP client SG560, SG565, SG570, SG575, SG580, SG630, SG635, SG710, SG810 pptpctrl PPTP VPN controller SG300, SG530, SG550, SG560, SG565, SG570, SG575, SG580, SG630, SG635, SG710, SG810...
  • Page 334 Program Name Description Supported Products reboot safely reboot the system SG300, SG530, SG550, SG560, SG565, SG570, SG575, SG580, SG630, SG635, SG710, SG810 redialer SnapGear phone number SG300, SG530, SG550, redialler SG560, SG565, SG570, SG575, SG580, SG710, SG810 reports/activeconn SnapGear GCC tool to generate...
  • Page 335 Program Name Description Supported Products reports/xmlreports.tcl SnapGear GCC tool to generate SG300, SG550, SG560, reports SG565, SG570, SG575, SG580, SG635, SG710, SG810 ripd a RIP routing engine for use SG530, SG550, SG560, with Zebra SG565, SG570, SG575, SG580, SG630, SG635,...
  • Page 336 Program Name Description Supported Products rtmon RTnetlink listener SG300, SG530, SG550, SG560, SG565, SG570, SG575, SG580, SG630, SG635, SG710, SG810 saveall SnapGear configuration saving SG300, SG530, SG550, utility SG560, SG565, SG570, SG575, SG580, SG630, SG635, SG710, SG810 secure copy (remote file copy...
  • Page 337 SMB password SG565 smbumount smbfs umount for normal users SG565, SG575, SG580, SG635, SG710, SG810 smgrd SnapGear Global Command SG300, SG550, SG560, Center (GCC) connector SG565, SG570, SG575, daemon. SG580, SG635, SG710, SG810 snmpd SNMP Daemon SG550, SG560, SG565,...
  • Page 338 OpenSSH SSH daemon SG550, SG560, SG565, SG570, SG575, SG580, SG635, SG710, SG810 sslwrap program that allows plain SG300, SG550, SG560, services to be accessed via SG565, SG570, SG575, SG580, SG635, SG710, SG810 stty change and print terminal line SG565, SG575, SG580,...
  • Page 339 Program Name Description Supported Products telnetd telnet protocol server SG300, SG530, SG550, SG560, SG565, SG570, SG575, SG580, SG630, SG635, SG710, SG810 test-nasl SnapGear utility to test NASL SG565, SG575, SG580, vulnerabilities SG635, SG710, SG810 testvu SnapGear GCC program to test...
  • Page 340 Program Name Description Supported Products unlinkd Squid unlink daemon SG565, SG575, SG580, SG635, SG710, SG810 upnpd Universal Plug and Play SG300, SG530, SG550, Discovery daemon SG560, SG565, SG570, SG575, SG580, SG630, SG635, SG710, SG810 usb-acm SnapGear USB modem helper SG565 program...
  • Page 341 Program Name Description Supported Products wlan SnapGear utility for configuring SG565 wireless LAN connections wlancfg wlan-ng wireless configuration SG565 utility wlan-ng wireless control utility SG565 wlanctl wland wlan-ng wireless access point SG565 daemon is identical to gunzip -c SG565, SG575, SG580, zcat SG635, SG710, SG810 zebra...

This manual is also suitable for:

Sg530Sg570Sg575Sg580Sg550Sg560 ... Show all

Table of Contents