AMIGIFT Documentation

Browsing /General Usage/Preferences Window/OpenFT




top

MAIN
detail_prefs_openft1

- Class Type

Node classification. This value is very important and will determine your role on the network.

The following settings are allowed:

At time of this write, AMIGIFT only supports USER node types, hence you must not change this value, same applyes to the Class Allow value, whose default value of 3 must be keep.

- Default Port

Core listening port. OpenFT uses a compacted binary protocol for the core communication with other nodes. If this machine is unable to provide both port and http_port to the outside directly (blocked by either by a firewall or a NAT setup) you should select 0 here.

NOTE: If you are unable to route this port (along with the HTTP port) you will be unable to download from other users with that same inability. You will, however, maintain the ability to upload to other non-firewalled users. Selecting non-zero when the port is not available to the outside will cause very broken behavior, namely search results will be extremely unreliable.



- HTTP Server Port

OpenFT's implementation also makes use of HTTP for all file transfers. See above for more details. Please provide a valid port here regardless of your firewall state.



- Alias

Arbitrary name you'd like to associate with your node. This field is optional and it is NOT to be trusted. The name is not unique to the network. Please do not choose useless aliases.



- Max Active Connections

Maximum number of "active" nodes that are allowed connection at any given time. The default value (-1) is used to calculate a suitable value for most search nodes based on their current max child configuration and other parameters. If you wish to take on additional connections, please note that you must set your maximum file descriptor limit accordingly (provided that the internal setrlimit() call is unable to sufficiently increase your current limits). Consult your shell's manual regarding ulimits for more details.



- LAN Mode

OpenFT offers a special configuration for users who wish to operate a network from within a local area network (LAN). This mode causes giFT to reject authorization from any non-local address as well as advertising it's presence via the local UDP broadcast. If this switch is non-zero you will not be able to contact the main network.



- Host Allow

When LAN mode is enabled, this configuration switch is used to verify which hosts are allowed connection to the core OpenFT port. It is highly recommended that you just don't touch this, regardless of what lan_mode's value is.

NOTE: This switch provides a very crude loophole that could allow you to create a "private" OpenFT network between a list of known nodes. Using this "feature" is going to be quite cumbersome as it is intended to be used by developers only. You have been warned.


SEARCH
detail_prefs_openft2

The first group of settings (Childrens, DBPath, and Cache Size) are used while operating as a Node Class other than USER, Since (at time of this write) AMIGIFT only supports USER nodes, you shouldn't bother about those settings.

The rest of options from this page are considered for developers/testings purposes and/or undocumented, and therefore you should not change them. - However, if you are in need of fine tunning OpenFT please ask on our mailing-list for further info.





PROTOCOLS
go to index
Gnutella




 $Id: index.php,v 2.0 2009/08/06 22:47:32 diegocr Exp $