NIC.FUNET.FI Usage restrictions

## Usage restrictions

### Number of users

This FTPSERVER counts the number of anonymous customers on several classes defined by IP-connection origin. Finns, and NORDUnet-users are not limited (in practice limits are very high and usually don't limit anything.), FOREIGN (from outside Finland/NORDUnet) anonymous users are limited on max 100 users. Each user class is also limited on how much bandwidth they are given, Finland and NORDUnet are infinite (well, no limit, just real-time logging), FOREIGN get some lower values (1280 B/s).

(Note: These "current" values are subject to day-to-day management actions, and can be changed without advance notice. These were current values when this part of the document was written.)

Note that we are located far away from the USA. Our connection to the USA is a 1024 kbits/sec terrestrial link (which is used by all the scandinavian countries). Our main purpose is to be central repository for finnish users. Lately traffic on that link has been TWICE as great TO the USA as it has been to Finland, think about that... (Our funders ask tough questions about that..)

### MINIMUM OF MAXIMUM RETRIEVAL RATE

Due to above mentioned resource limits, this server implements a throttle to limit individual users usage of scarce resource: line capacity.

    Algorithm goes like follows:
    	max_rate  =   Max_anonymous_logins * minimum_maximum_rate /
    			present_count_of_data_transfers
    Where:
    	max_rate 	is in (k)bytes/sec
    	Max_anonymous_logins  is count shown at anonymous FTP login (32)
    			(Current value listed to you when you login.)
    	minimum_maximum_rate  is rate  shown at anonymous FTP login (1kB/s)
    	present_count_of_data_transfers
    			is a figure derived from ftp-server internal
    			mechanism -- It tells (at sample time) how many
    			are really transferring out of those who have
    			logged in under your limited class.

If user can't use the share s/he has been allocated, nobody else will get the leftovers (well, that line will be saturated anyway...)

This yields a rate which can be anything in between 1kB/s and 32kB/s. (32kB/s is when you are only one transferring at the moment.)

### IP-REVERSAL AND VALID "PASSWD" REQUIREMENTS

Any system without a valid IP reversal mapping will get a view of directories which is even more restricted than the usual anonymous user. The same is true when the email address you have entered as password does not conform with RFC822 rules.

If your IP address does not have IN-ADDR.ARPA. -reverse mapping defined, this is a task for your network administrator. Your NetAdmin must register reversing database into IN-ADDR.ARPA. -domain, and make sure all of your local hosts have IP reversals defined! (This registration is done with HOSTMASTER@Internic.NET, once your local DNS service provides the data.)

What we expect of IP reversals is valid top 2 domains: 130.232.7.250 --> non-registered-pc.utu.fi We are NOT interested in truly valid reversals, unless you want to upload something!

This reversal is achieved with IP reversal entry in named.reverse:

    	---------
    	$ ORIGIN 232.130.in-addr.arpa.
    	; all KNOWN 130.232.7.XX hosts here before "fallback"
    	*.7	IN	PTR	non-registered-pc.utu.fi.
    	---------

Simple and effective! Talk with your network management, they should know what this is all about. (If they don't, they can ask us.)

Passwords for anonymous FTP are expected to be email addresses. They are expected to contain `@'-character in them, and be according to RFC822: Luser.Name@Host.Domain Luser%OtherHost@RelayHost.Domain This address need NOT be on host you are using for FTP, but it must be valid address to you in your preferred system.

Valid email addresses are especially important if you want to upload something. On uploads email address validity is enforced by area moderators, who may not want to make uploaded material public, if it isn't traceable.

NOTE: If your IP-reversal fails, but you do have a host with globally accessible name->IP-address entry, and that host is in the same network as is the host you are using, then you can get past the restriction by using username@host-in-the-same.net as your password. Special case: Use the name of your host itself, if it has a valid address entry.