When you first start BitFling, it will generate a certificate for your machine. It then displays an icon in the system tray (for Windows) or a draggable icon for Linux and Mac. If you click on the icon, a window appears that allows you to configure BitFling as well as view the log etc.
You should then add authorized users. It is recommended that you use their email address as the username and allocate a password. Then you need to set what addresses they can connect from. They may be able to tell you what addresses, or you need to find out.
To find out, tell them to try to connect and then examine your log. You should see a line something like:
17:10:38.546: No defined users for address ('192.168.1.25', 39480)
The numbers in quotes 192.168.1.25 are the address
the connection tried to come from. For the more advanced users,
you can also put in wildcards (eg 192.168.1.*) as well as
DNS names (with no wildcards, such as machineA.example.com)
The expires field is not used and will be removed.
In the future you will be able to limit what devices can be accessed in the lower pane.
To alter the settings, edit the configuration. On Windows, this
is the registry HKEY_CURRENT_USER\Software\BitFling
and on Linux and Mac is .bitfling in your home
directory.
The following configuration directives are available:
| Key | Default | Description |
|---|---|---|
| certificatefile | .bitfling.key
in your home directory (Linux, Mac) or My Documents (Windows)
| Where the certificate for your machine is stored. If one is not present when BitFling starts, it will generate a new certificate. |
| bindaddress | "" (Empty string, all interfaces)
| This is the interface to bind to. If you have multiple network interfaces in your machine, you can make BitFling only use one of them. |
| port | 12652 | An integer for what port number to use |
BitPim Online Help built 17 January 2010