A default client configuration is automatically generated when the network connector is created; however, you may need to edit this configuration to make it suitable for the majority of your users. Additional client configurations may also be required in some instances, such as for remote users on different platforms that may require different initialization commands. You can create additional additional client configurations for the same Server Interface by copying (click the Copy link associated with the client) the initial client configuration, and then customizing it.
Client settings
The following additional client settings can be configured by editing the network connector client configuration.
| Setting | Description |
|---|---|
| Auto-Launch | This setting determines whether a user logging in to the Barracuda SSL VPN will automatically launch the Network Connector. This does not affect the ability of the stand-alone version of the Network Connector from also running with this particular client configuration. |
| Server Interface | The server interface identifies the network information that this client configuration is associated with. This should match the server interface that caused the creation of this client configuration. |
| Static IP Address | This field should only be used when you expect only one remote user to connect using this configuration. If there is a value specified here, then the remote system that is connecting via the Network Connector will always be assigned this IP address, regardless of any DHCP range that is set in the associated server interface. |
| Authentication Type | If you wish to change the authentication type for the user of this client configuration, then select the desired method here. |
Up- and Down commands
Up commands are executed from a temporary script file created by the Barracuda SSL VPN when a remote client connects with the Network Connector. This script can be used to create the needed static routes when the Barracuda SSL VPN is installed in a DMZ. For more information, see How to Create a Static Route.
Down commands are executed when the remote client disconnects, usually to remove settings added by the up commands.
| Command | Description |
|---|---|
| Up | In the Up Commands area, you can enter any command that is executable from a script file. These can range from initializing environment variables, to adding network printers and mapping of network drives. Example 1: Up command to publish a route:
Example 2: Up command for Mac clients (xx.xx.xx.xx and example.com are the DNS server IP and DNS suffix): #!/bin/bash -x
mkdir -p /etc/resolver
echo "nameserver xx.xx.xx.xx" > /etc/resolver/example.com killall lookupd exit 0 |
| Down | In the Down Commands area, enter the commands that you want the remote system to execute when leaving the secured network. Typically, you will have a corresponding Down command for every Up command that was configured, to reverse any action that was taken. Example 1: Down command to delete a route:
Example 2: Down command for Mac clients (example.com is the DNS suffix): #!/bin/bash -x
rm -Rf /etc/resolver/example.com
killall lookupd
exit 0 |