OpenGnsys VLAN support

Great news! VLAN support just landed in OpenGnsys Enterprise.

This new feature allows any OpenGnsys Enterprise administrator to add or delete any valid ogServer address into the database and also modify any client's associated server address.

The server running OpenGnsys Enterprise can now be configured with multiple VLAN interfaces. Clients can boot into the ogLive environment using the corresponding server VLAN interface address thanks to a custom ogClient configuration file based on the ogServer address.

Be sure to update your OpenGnsys Enterprise installation. The related packages and their version in which VLAN support landed is as follows:

• ogCLI 0.3.1-1
• ogClient 1.3.1-4
• ogServer 1.2.4-1

Except for the custom ogClient configuration file, everything related to VLAN in OpenGnsys is configured using ogCLI, the command line frontend of OpenGnsys Enterprise. You can see some examples of use cases below:

• Add a new ogServer address entry to the OpenGnsys database. In this example the server address is 10.141.10.1. Returns the id of this new server.

$ ogcli add server --address "10.141.10.1"
{"id", "2"}

• List all stored ogServer address in the OpenGnsys database

$ ogcli list servers

{
  "servers": [
    {
      "address": "192.168.2.240",
      "id": 1
    },
    {
      "address": "10.141.10.1",
      "id": 2
    }
  ]
}

• Set server with id 2 as the server of client with address 10.141.10.100 (PXE template needs to be rebuilt after this, i.e.: set boot mode)

$ ogcli set server --id 2 --client-ip 10.141.10.100
$ ogcli set mode --mode pxe --client-ip 10.141.10.100

• You can also set the server of a whole room. Just as before, but using the --room-id parameter.

$ ogcli set server --id 2 --room-id 1
$ ogcli set mode --mode pxe --room-id 1

• Check for the server address a client is set to connect to when booting ogLive.

$ ogcli list client --client-ip 10.141.10.100

{
  "boot": "oglive",
  "center": 1,
  ...
  "server_id": 2
}

As a final step we need to create a custom ogClient file so that clients booting ogLive can use the correct configuration based on their VLAN network.

Following this example, to create a new custom ogClient configuration file to connect to ogServer using its 10.141.10.1 address we need to create a copy of the default config file but changing its name to ogclient-10.141.10.1.json:

$ ls -lah /opt/opengnsys/client/ogClient/cfg/
...
-rw-r--r-- 1 root root  372 Sep 14 13:51 ogclient.json
-rw-r--r-- 1 root root  378 Aug 28 11:26 ogclient-10.141.10.1.json
...

After creating the custom configuration file make sure the correct address is used for the "ip" and "ur" fields inside "opengnsys" section. In this example: 10.141.10.1

$ head /opt/opengnsys/client/ogClient/cfg/ogclient-10.141.10.1.json
{
    "opengnsys": {
        "ip": "10.141.10.1",
...
        "url": "https://10.141.10.1/opengnsys/varios/menubrowser.php",
...

After this, any client for which the ogServer address is set to 10.141.10.1 will use this configuration file instead of the default ogclient.json.

Any questions? You can contact us via e-mail at opengnsys@soleta.eu

We also offer technical support and training services, check the support section for more information.