Chat now with support
Chat with Support

syslog-ng Store Box 6.1.0 - Administration Guide

Preface Introduction The concepts of SSB The Welcome Wizard and the first login Basic settings User management and access control Managing SSB Configuring message sources Storing messages on SSB Forwarding messages from SSB Log paths: routing and processing messages Configuring syslog-ng options Searching log messages Searching the internal messages of SSB Classifying messages with pattern databases The SSB RPC API Monitoring SSB Troubleshooting SSB Security checklist for configuring SSB

The Welcome Wizard and the first login

This chapter describes the initial steps of configuring SSB. Before completing the steps below, unpack, assemble, and power on the hardware. Connect at least the external network interface to the local network, or directly to the computer from which SSB will be configured.


For details on unpacking and assembling the hardware, see "syslog-ng Store Box Hardware Installation Guide" in the Installation Guide. For details on how to create a high availability SSB cluster, see "Installing two SSB units in HA mode" in the Installation Guide.

The initial connection to SSB

SSB can be connected from a client machine using any modern web browser.


For details on supported browsers, see Supported web browsers

SSB can be accessed from the local network. SSB attempts to receive an IP address automatically via DHCP. If it fails to obtain an automatic IP address, it starts listening for HTTPS connections on the IP address. Note that certain switch configurations and security settings can interfere with SSB receiving an IP address via DHCP. SSB accepts connections via its external interface (EXT, for details on the network interfaces, see Network interfaces).


The SSB console displays the IP address the external interface is listening on.

If SSB is listening on the address, note that the subnet must be accessible from the client. If the client machine is in a different subnet (for example its IP address is 192.168.10.X), but in the same network segment, the easiest way is to assign an alias IP address to the client machine. Creating an alias IP on the client machine virtually puts both the client and SSB into the same subnet, so that they can communicate. To create an alias IP complete the following steps.


The Welcome Wizard can be accessed only using the external network interface of SSB, as the management interface is not configured yet.

Open the page from your browser and accept the certificate shown. The Welcome Wizard of SSB appears.

Creating an alias IP address (Microsoft Windows)


This procedure describes how to assign an alias IP address to a network interface on Microsoft Windows platforms.


To assign an alias IP address to a network interface on Microsoft Windows platforms

  1. Navigate to Start menu > Settings > Network Connections.

  2. Double-click the Local Area Connection and then click Properties.

  3. Select the Internet Protocol (TCP/IP) component in the list and click Properties.

  4. To display the Advanced TCP/IP Settings window, click Advanced.

  5. Select the IP Settings tab and in the IP Addresses section, click Add.

  6. Into the IP Address field, enter Into the Netmask field, enter


    If your internal network uses the IP range, the and addresses might already be in use. In this case, disconnect SSB from the network, and connect directly a computer to its external interface using a standard cross-link cable.

  7. To complete the procedure, click Add.

Creating an alias IP address (Linux)


This procedure describes how to assign an alias IP address to a network interface on Linux platforms.


To assign an alias IP address to a network interface on Linux platforms

  1. Start a terminal console (for example gnome-terminal, konsole, xterm, and so on).

  2. Issue the following command as root:

    ifconfig <ethX>:0

    where <ethX> is the ID of the network interface of the client, usually eth0 or eth1.

  3. Issue the ifconfig command. The <ethX>:0 interface appears in the output, having inet addr:

  4. Issue the ping -c 3 command to verify that SSB is accessible. A similar result is displayed:

    user@computer:~$ ping -c 3
                PING ( 56(84) bytes of data.
                64 bytes from icmp-seq=1 ttl=63 time=0.357 ms
                64 bytes from icmp-seq=2 ttl=63 time=0.306 ms
                64 bytes from icmp-seq=3 ttl=63 time=0.314 ms
                --- ping statistics ---
                3 packets transmitted, 3 received, 0% packet loss, time 2013ms
                rtt min/avg/max/mdev = 0.306/0.325/0.357/0.030 ms
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating