Корпорация Дженерал Сателайт — российская научно-производственная компания, представляющая на российском и международном рынке высокотехнологичное радиоэлектронное оборудование, характеристики которого отвечают самым высоким стандартам. Надежность и профессионализм за многие годы успешной работы позволили компании занять место лидера в телекоммуникационном бизнес-сообществе России.
Цифровой спутниковый ресивер GS-8300
Описание файлов конфигурации Sat4U 0.7
Наковыряно из внутренностей клиента/сервера.
Client Configuration File (recv.ini)
This file has to be put in the working directory of the Client program and has to be named 'recv.ini'.Section [recipient]
The section [recipient] specifies the recipient. The entries have to be identical with the entries in the Recipient File(s) (*.rcv) of the Server.
| user_name | Name of the recipient as unique ASCII string. |
| user_name_prefix | User name prefix of the recipient as ASCII string.
Only useful when using with Authentication. When using Authentication the user may have to enter its user name into a web base login form. If you want to make sure that independent of the user name typed into the login form the user name always starts with a fixed prefix (e.g. company!) you can set user_name_prefix within send.ini. The resulting user name (used within the software and within the Server Recipient Files) is always the sum of user_name_prefix and user_name. |
| user_key | Specifies the key of the recipient. This key is necessary for encrypted transmissions. It will be used to encrypt the distributed data key. This entry will be ignored when an entry 'user_key_crypt' is available. |
| user_key_crypt | The user can choose the option 'Save password' on the authentication login form for ______. The password will then be encrypted and stored in the Receiver Configuration File with the entry 'user_key_crypt'. The next time the user is logging in, a password is not required, because the password specified with the entry 'user_key_crypt' is used. The user_key_crypt can also be entered manually (for ______and ______). Please use the tool _____ to manually transform a plain user key into the crypted user key. The crypted_used_key is a scrambled variant of the plain user_key. |
Section [shell]
The Client can provide an HTML based web interface which can be accessed from any standard web browser. The parameters for the web interface are specified in this section.
| login | Specifies a login for the web interface. This includes a username and a password and has to be written as: "<name>:<password>". If it is "none" then the access is possible without a password (default: the access to the web interface is not possible).
The parameter 'login' can be given multiple times if more than one user should have access to the web interface. |
| port | The port to be used for the web interface (default: 2517). |
| refresh | Specifies the time interval between automatic updating of the web interface pages in seconds (default: 3 seconds). |
| graphic_port | The web interface contains graphics giving an overview of the currently used bandwidth for _____. The Client uses the port configured here to communicate the bandwidth values for the graphics to the web interface (default: a port is chosen randomly). |
| allowed_address | Specifies the IP address or DNS name of a host that is allowed to connect to the web interface port of the Client and open the web interface. The entry can be given multiple times to allow more than one host to connect to the web interface of the Client. (Default: All external hosts have permission to connect to the web interface of the Client.) |
| interface_address | In case the Server host is equipped with more than one interface, this entry can be used to bind the web interface to a specific network interface only.
Please note that the entry can only be given once and that the use of 'localhost:<port>' instead of '<ip address>:<port>' is not possible to access the web interface locally when the entry 'interface_address' is made. |
Section [locations]
The section [locations] tells the Client where to find the files and directories it needs for its configuration. There are default values for all entries and thus the whole section or some entries may be left out. In this case the default values are used.
All locations are relative to the working directory of the Client.
| log_file | The name of the Log File containing the debugging output (default: recv.log). |
| channels_file | Specifies the Client Channel File containing the parameters for the reception of the ______data channels. |
| file_database_directory | The directory for caching data fragments. The path is relative to the program directory (default: receiving/tmp). |
| webbroadcast_cache_directory | Directory used as web cache containing ______WebBroadcast data (default: received/webbroadcast). The entry has the format "<directory>/<subdirectory>". The "<directory>" has to be the same as the 'target_directory' specified in the Client Channel File and the "<subdirectory>" has to be the same as the 'target_directory' specified in the Job File for WebBroadcast. This entry has to be made when other than the default value is used for one or both of the 'target_directories'. |
| prefetching_cache_directory | The directory used as web cache containing HTTP-Prefetching data (default: receiving/pushed_data). |
| license_file | The name of the License File containing the product license (default: license.ini). |
Section [logging]
The section [logging] can be used to fine tune the log output.
| log_file_size | Specifies the maximum size of the Log File in bytes. When the Log File gets larger than log_file_size, it is stored as '<log_file>.1', a new Log File is created for new logging and all previous Log Files are shifted: the old '<log_file>.1' is renamed to '<log_file>.2' etc. (default: 1000000). |
| log_file_number | Specifies the number of Log Files to store. Each time a Log File is shifted, it is stored with a higher number. When the new name will be '<log_file>.<log_file_number>', the file is removed (default: 4). |
| log_level | Specifies the amount of log output. Possible values are "none", "quiet", "normal" and "verbose" (default: normal). |
Section [mail]
The [mail] section can be used to send a mail in case of errors / warnings to the user (Runtime Error Mail) and to send a mail to the operator / support in case the user needs help with the system (Feedback Mail). Runtime Error Mail will be sent when mail_server_address, sender_address and runtime_error_mail_recipient are specified. To use the Feedback Mail it is sufficient to specify the mail_server_address.
| mail_server_address | Address of the mail server that is used as SMTP-Server for outgoing mails. This entry is necessary to activate the functionality of both Feedback Mail and Runtime Error Mail. |
| sender_address | E-mail address of the sender of the 'Feedback Mail' or 'Runtime Error Mail'.
It is not possible to specify more than one sender e-mail address, i. e. the entry can not be given multiple times. The entry is mandatory to activate the Runtime Error Mail functionality. For the Feedback Mail functionality the entry is optional, as the sender e-mail address can also be specified directly in the Feedback Mail form of the web interface. The sender e-mail address specified here is given as default value in the respective field of the form. |
| default_feedback_mail_recipient | E-mail address of the recipient of the 'Feedback Mail'.
The entry can be given multiple times if more than one recipient should be specified. Recipients can also be specified directly in the 'Feedback Mail' form of the web interface. The recipients specified here are given as default values in the respective field of the form. |
Section [announcement_channel]
The announcement channel is constantly received by the Client to get the invitations for reception and the data keys in case of encrypted data transmissions. The name and parameters of the announcement channel have to be the same as used in the Server.
| address | Specifies the multicast address and port to be used for the announcements in the format "<address>", "<address>:<port>", or ":<port>" (default: 229.1.1.1:2511). |
| name | Specifies the name of the announcement channel (default: TSL Announcement Channel). |
| bandwidth | Specifies the reserved bandwidth for the announcement channel in bit/s. (This parameter is only used when the entry 'total_bandwidth' in the section [parameters] is available.) |
Section [parameters]
The section [parameters] contains general configuration parameters for ______ functionality.
| total_bandwidth | This entry specifies the maximum allowed bandwidth for multicast reception with _______. |
| interface_address | Address of the interface that is used to receive multicast data packets with ______ |
| acknowledgement_proxy_address | Address and port number of the proxy host that will be used to send acknowledgements in case that the acknowledgements should pass a proxy. This entry should be made when the Client is located behind a firewall operating with a proxy. Without specification of the proxy the acknowledgements may not pass the firewall. The format is "<address>:<port>" or "<proxy host name>:<port>" (default: no proxy is used for transmission of acknowledgements). |
| packet_naks | Specifies whether NAKs are sent to the _______ in case that single packets of a transmission are missing.
Possible entries are "1" and "0": 0 = no NAKs are sent. 1 = NAKs are sent. (Default: 0, i. e. no NAKs are sent) |
| potential_repetitor | Specifies, whether this Client can be repetitor for a group of ____ _____s. The _____s of the group send the NAKs to the repetitor instead of sending them to the _______ . The repetitor then transmits the missing data packets to the ______ that sent the NAK.
With this mechanism it is possible to reduce the bandwidth used back to the _____. Which ____ in a group is repetitor will be negotiated automatically between the potential repetitors inside the goup. Possible entries are "1" and "0": 0 = Client cannot be repetitor. 1 = Client can be repetitor. (Default: 0, i. e. Client is not a potential repetitor) |
| repetitor_retransmission_rate | Specifies the maximum percentage of the overall transmission rate of a channel that can be used for repetitor retransmission caused by NAKs from the ____s of the repetitor's group.
The rate for repetitor retransmission is added to the current bandwidth of the channel used from the ____s. The parameter can be used to make sure that transmissions from the ____are not delayed because the available bandwidth is used completely for NAK retransmissions. (Default: 100%, i. e. no restriction for repetitor retransmissions) |
| allow_execute | This entry determines, whether the automatic execution of files on the Client host after reception is accepted.
With the entry of "1" execution is accepted, and with the entry of "0" execution is refused, i. e. executable files are only stored in the incoming directory without being executed. (default: execution is refused) When Clients are configured to refuse the execution, they will receive the executable files, but the files are not executed automatically. |
| file_database_size | Spezifies the maximum size of the ____ directory for caching data fragments. |
The delivery of big files from the ____ cache database directly to the target directory needs time and therefore may cause problems because the user may open the files while the storing process is still not complete. To avoid that, two mechanisms are available:
the files are complete. The following entries specify the parameters for the above described methods: |
|
| temp_directory | Specifies a directory used to store the data before they are stored to the target directory.
Please note that the temp_directory has to be located on the same file system as the target_directory to allow a quick shifting of the file. |
| temp_prefix | A prefix that mark incomplete files. |
| temp_suffix | A suffix that mark incomplete files. |
Section [webbroadcast]
| min_file_lifetime | Specifies the minimum life time for web content in the proxy directory of the Client. Normally files in that directory are automatically erased when either the expire date sent with the file by the web server or the max_file_lifetime configured in the _______ Server is reached. In case the recipient wants to make sure that the files are kept in the cache directory for a certain time, even if the expire date or the max_file_lifetime are reached, (e. g. because in the meantime a connection to the internet is not possible and the recipient is dependent on cache content to see the web page), the minimum_file_lifetime can be set (in seconds).
(Default: 0, i. e. files are always deleted at expire date or max_file_lifetime) |
Section [news]
| server_address | Address or host name and port of the external news server receiving the articles transmitted by ______ in the format "<address>:<port>".
The entry has to be repeated for every news server that should receive articles from the _____ Client. |
| connection_timeout | Specifies the time (in seconds) that the Client is keeping a connection to the news server open after the last activity (default: 30 seconds). When no further article to be tranmitted is coming in during this period, the connection is closed until the next transmission. |
Section [etcp_parameters]
The section [etcp_parameters] specifies the parameters for enhanced TCP and web content push.
| server_proxy_host_name | Name or numeric address of the Server Proxy host that the Client Proxy will connect to (default: a default value will be determined according to the Server Proxy host name given by the customer).
When a host name is entered and the DNS system is configured to assign more than one address to this name, multiple hosts can be addressed with one entry. It is also possible to address more than one host by repeating the entry. When more than one Server Proxy host is specified, a Server Proxy is chosen randomly for every new connection. |
| server_proxy_port | Port of the Server Proxy for incoming connections from the Client Proxy. This port has to be identical with the listen_port_number specified in the Server Configuration File of the Server Proxy (default: 9200). |
| http_listen_address | Local address and port for incoming connections from the browser in the format "<address>:<port>" or "<port>" (default: any interface, port 9202). |
| socks_listen_address | Local address and port for incoming connections from socks clients in the format "<address>:<port>" or "<port>" (default: any interface, port 9203). |
| max_send_data_rate | Maximum bandwidth for outgoing ETCP connections. |
| max_receive_data_rate | Maximum bandwidth for incoming ETCP connections. |
| multicast_receive_interface | Interface for the reception of UDP packets from the Server Proxy while the speed mode is on. |
| allowed_address | This entry can be used to restrict the right to connect to the Client to a specific host. It specifies the address of the interface allowed to connect to the Client. The entry can be given multiple times to allow more than one host to connect to the Client. (Default: connections are accepted from any host.) |
| default_speed_state | Specifies the speed mode at the start of the Client Proxy. Possible entries are:
0 = the Client Proxy is not in the speed mode when started, 1 = the Client Proxy is in the speed mode when started. (Default: 0, i. e. the Client Proxy is not in the speed mode when started) |
| toggle_speed_listen_port | Specifies the port used to switch the speed mode on Unix systems (default: 9205). |
| toggle_speed_allowed_address | IP address or host name of a computer that can be used to connect to the toggle_speed_listen_port and change the speed mode (the local host can also be specified as "127.0.0.1"). In case the switch of the speed mode should be possible from more than one computer, this entry has to be repeated for every computer. |
| authentication | Activates the user authentication for ______ . Possible entries are:
1 = authentication is activated. 0 = authentication is deactivated. (default: 0, i. e. authentication of the Clients is not required for _____ transmissions). |
| use_icon | Specifies, whether the Speed Button should be displayed in the task bar on Windows systems. Possible entries are:
1 = the Speed Button is displayed 0 = the Speed Button is not displayed (default: 1, i. e. the Speed Button is displayed) |
| use_etcp_when_speed_off | This entry specifies, whether ETCP is used for transmissions when the speed mode is off, i. e. when no satellite connection is used.
With the entry of "0", ETCP is not used in the non speed mode and the Client is directly connecting e. g. to the FTP / HTTP or mail servers. With the entry of "1", ETCP is used in the non speed mode and the Client is connecting to the _____ Server Proxy also for terrestrial connections (default: 1, i. e. ETCP is always used) |
| use_http_prefetching | This entry specifies, whether HTTP-Prefetching is used. Possible entries are:
"on" or "1" = HTTP-Prefetching is used, "off" or "0" = HTTP-Prefetching is not used, "auto" or "2" = HTTP-Prefetching is used in the speed mode and not used in the non speed mode (default: auto). |
| http_proxy | In case a cache proxy should be used for the connection to HTTP servers when the speed mode is off and ETCP is not used, the _______ Client Proxy can be configured to connect to the proxy instead of the HTTP server istself. This entry specifies the address and port of the intermediate proxy that the Client Proxy is connecting to in the format "<address>:<port>". |
| ftp_proxy | In case a cache proxy should be used for the connection to FTP servers when the speed mode is off and ETCP is not used, the _____ Client Proxy can be configured to connect to the proxy instead of the FTP server istself. This entry specifies the address and port of the intermediate proxy that the Client Proxy is connecting to in the format "<address>:<port>".
Please note that the usage of an FTP proxy might also require changes in the browser configuration. E. g. in Microsoft Internet Explorer it is necessary to deactivate ‘Enable folder view for FTP sites’ in the section ‘Tools/Internet Options/Advanced’ in order to use the FTP proxy. |
| local_udp_address | The own IP address that the Client Proxy will report to the Server Proxy. The Server Proxy will direct all UDP packets to this IP destination address when addressing this Client Proxy (speed mode).
As default (when local_udp_address is not specified) the Client Proxy will report it's IP address used for the TCP connection to the Proxy Server. Depending on the IP routing and IP/MAC address mapping (IP/DVB gateway) it may be necessary to send the UDP packets to a different client interface / IP address (e.g. the DVB card). In the latter case you can define the corresponding UDP destination IP address by using local_udp_address. |
| inactivity_timeout | Maximum duration in seconds of an ETCP connection in case no data is transmitted. There is a corresponding entry existing within the Server Configuration File as well – the smaller of both values will be used. (default: 0 = value specified at the server is used.) |
Section [etcp_compression]
The section [etcp_compression] specifies, whether data that is sent from the Client to the Server by ____is compressed.
| html_compression | Specifies, whether HTTP data sent via the HTTP proxy of ____ Client is compressed. Please note that this data is always encrypted, independent from the compression mode chosen. Possible entries are:
1 = HTTP data is compressed. 0 = HTTP dat is not compressed. (default: 0, i. e. HTTP data is not compressed). |
| socks_tcp_compression | Specifies, whether SOCKS TCP traffic is compressed or not compressed. Please note that this data is always encrypted, independent from the compression mode chosen. Possible entries are:
1 = SOCKS TCP traffic is compressed. 0 = SOCKS TCP traffic is not compressed. (default: 0, i. e. SOCKS TCP traffic is not compressed). |
| socks_udp_compression | Specifies, whether SOCKS UDP traffic is compressed or not compressed. Please note that this data is always encrypted, independent from the compression mode chosen. Possible entries are:
1 = SOCKS UDP traffic is compressed. 0 = SOCKS UDP traffic is not compressed. (default: 0, i. e. SOCKS UDP traffic is not compressed). |
| port_forwarding_compression | Specifies, whether port forwarding traffic is compressed or not compressed. Please note that this data is always encrypted, independent from the compression mode chosen. Possible entries are:
1 = port forwarding traffic is compressed. 0 = port forwarding traffic is not compressed. (default: 0, i. e. port forwarding traffic is not compressed). |
Section [etcp_port_forwarding]
The section [etcp_port_forwarding] is used to set up parameters for port_forwarding (e.g. e-mail reception with). In case data is received or sent to multiple different ports, this section has to be repeated for every port number used.
| server_name | Host name of the remote server. |
| server_port | Port used at the remote server (default: 110) |
| local_port | Port provided at the Client Proxy. The local application (e. g. mail client) has to connect to this port to receive or send data. |
Section [etcp_connection_control]
The section [etcp_connection_control] allows to adjust parameters needed for the regulation of ETCP connections.
This section is not mandatory. For all entries there are default values that allow a good regulation of the connections. Therefore it is recommended to leave this section out and use the default values.
Any changes in this section are unnecessary in normal operation mode andshould be made carefully!
| nak_timeout | Retardation of the sending of negative acknowledgements (NAK) in milliseconds (default: 100 milliseconds).
It is possible that packets are delivered in the wrong order. In that case the late coming packet will be regarded as missing and a NAK will be sent out to cause resending before the original packet is delivered. As a result the Client Proxy will receive the packet two times. To avoid this redundant sending, the Client Proxy is configured to wait for a couple of milliseconds to make sure the packet is actually not delivered before sending out the NAK. |
| connect_initial_timeout | Specifies the period of time a Client Proxy is trying to connect to a Server Proxy in milliseconds (default: 2000 milliseconds). If the connection can not be established in the period of time specified with this entry, the Client Proxy is trying to connect to another Server Proxy. |
| connect_additional_timeout | Specifies the period of time a Client Proxy is trying to establish a new TCP connection within an existing ETCP association in milliseconds (default: 6000 milliseconds). If the Client Proxy can not build up the connection in the period of time specified with this entry, the connection will not be established. |
| nr_of_tcp_connections | Specifies the number of TCP connections used for one ETCP association from the Client to the Server (default: 1). |
Section [watchdog]
The section [watchdog] specifies the parameters of an built-in process of ____ that keeps the overall performance of the Client under surveillance.
| activate | Activates the program internal watchdog. Possible entries are:
1 = the watchdog is activated. 0 = the watchdog is not activated. (default: 1, i. e. the watchdog is activated). |
| alive_check_interval | The “working” process has to send an alive message to the watchdog process in the given interval (of minimum 30 seconds) (default: 30 seconds). |
| max_memory_usage | Maximum amount of memory the process is allowed to allocate. In case more memory is allocated the process is restarted (unit: Bytes - default: 300000000 bytes = 300 MByte). |
| max_cpu_usage | In case the CPU usage exceeds the given amount for a period of ‘max_cpu_usage_period’ the process is restarted (unit: percent - default: 75 %).
Please note that it is not possible to control cpu usage under WIN95 or WIN98 due to restrictions in these operating systems. |
| max_cpu_usage_period | Period for max_cpu_usage control (unit: seconds - default 120 seconds). |
| max_nr_of_core_files | Under Unix like operating systems the watchdog will archive the given number of eventually existing core files (default: 10). |
Section [license]
The section [license] is necessary for the program to run. It is normally located in the License File in the working directory of the Client, but can also be part of the Client Configuration File. When a License File with a valid license is available in the working directory of the Client, the license of that file is valid and any license written into the Client Configuration File is inoperative. The [license] section contains the license key and information about the operating system and the product modules that the license is valid for. It has to be entered in exactly the same way (including the order of the lines) as it was given by the distributor. At which place in the file it is written is unimportant, though.
The entries give the following information:
| copyright | Gives copyright information for the software. |
| license_class | The license class of the product, e. g. whether it is a commercial copy or an evaluation license. |
| expire_date | The date until which the license is valid. This entry is only made in licenses with time limit. The format of the time is 'year.month.day'. |
| oem_license | Informs, whether the license is an oem license (product can be used as integrated part of other products). When the company has purchased an oem license, the company name is given with this entry. |
| max_licensed_bandwidth | Specifies the maximum bandwidth allowed for transmission with this Client license. |
| restriction | Any restrictions for the license (e. g. that it can only be used for evaluation purposes). |
| product_license | Specifies a module that can be used with the given license. When the license is valid for more than one module, the entry is repeated for each module. Possible entries are:
|
| operating_system | Specifies the operating system and processor necessary to run the version valid with the given license key. |
| description | A text giving any description or comments. This section is optional. It will not be given by the distributor but can be entered by the operator of the Client according to his demands. |
| http_skin | The web interface design can be adapted to the corporate design of the customer (by including customer logo, colors etc.). These changes in the web interface skin can only be made by the software producer at the request of the customer. This entry specifies the company design that is chosen for the web interface displayed for the licensed product. |
| version | The version of the software. |
| license_key | The license key as given by the distributor. |
Section [activations]
The section [activations] can be included in the License File or the Client Configuration File when the functionality of the Server should be limited to less modules than included in the [license] section. E. g. when a license for FileBroadcast and OfflineMail is available and the Client is only used for Mail Notification, the functionality can be limited to OfflineMail.
The advantage of the deactivation of non used modules is a reduction in the utilisation of processor resources and a better overview, because the web interface only displays the information for the activated modules.
When no section [activations] is existent, all modules are activated.
Each module is activated with an entry in the format:
"Client/<module>=on"
and deactivated with the entry of:
"Client/<module>=off"
The module names are written in the same way as in the [license] section, entry 'product_license'.
Please note that the activation of the single modules is dependent on the activation of the products. E. g. modules of ___, like e. g. FileBroadcast, can only be activated when ___itself is activated.
License File
This file contains the product license.It has to be put in the working directory of the Client program and has to be named as specified in the Client Configuration File, section [locations], with the entry license_file (default: license.ini).
A product license is necessary for the program to run. In addition to the License File it is possible to have a [license] section in the Client Configuration File. Both licenses are valid. That means that no License File has to be available provided that the Client Configuration File contains a valid [license] section. Likewise the software is running without a [license] section in the Client Configuration File when a License File is available. When different licenses are given in the License File and the Client Configuration File, the license of the License File is valid and the license in the Client Configuration File will not be taken into account.
Section [license]
The license section is necessary for the program to run. It contains the license key and information about the operating system and the product modules that the license is valid for. It has to be entered in exactly the same way (including the order of the lines) as it was given by the distributor. At which place in the file it is written is unimportant, though.
The entries give the following information:
| copyright | Gives copyright information for the software. |
| license_class | The license class of the product, e. g. whether it is a commercial copy or an evaluation license. |
| expire_date | The date until which the license is valid. This entry is only made in licenses with time limit. The format of the time is 'year.month.day'. |
| oem_license | Informs, whether the license is an oem license (product can be used as integrated part of other products). When the company has purchased an oem license, the company name is given with this entry. |
| max_licensed_bandwidth | Specifies the maximum bandwidth allowed for transmission with this Client license. |
| restriction | Any restrictions for the license (e. g. that it can only be used for evaluation purposes). |
| product_license | Specifies a module that can be used with the given license. When the license is valid for more than one module, the entry is repeated for each module. Possible entries are:
|
| operating_system | Specifies the operating system and processor necessary to run the version valid with the given license key. |
| description | A text giving any description or comments. This section is optional. It will not be given by the distributor but can be entered by the operator of the Client according to his demands. |
| http_skin | The web interface design can be adapted to the corporate design of the customer (by including customer logo, colors etc.). These changes in the web interface skin can only be made by the software producer at the request of the customer. This entry specifies the company design that is chosen for the web interface displayed for the licensed product. |
| version | The version of the software. |
| license_key | The license key as given by the distributor. |
Section [activations]
The section [activations] can be included in the License File or the Client Configuration File when the functionality of the Server should be limited to less modules than included in the [license] section. E. g. when a license for FileBroadcast and OfflineMail is available and the Client is only used for Mail Notification, the functionality can be limited to OfflineMail.
The advantage of the deactivation of non used modules is a reduction in the utilisation of processor resources and a better overview, because the web interface only displays the information for the activated modules.
When no section [activations] is existent, all modules are activated.
Each module is activated with an entry in the format:
"Client/<module>=on"
and deactivated with the entry of:
"Client/<module>=off"
The module names are written in the same way as in the [license] section, entry 'product_license'.
Please note that the activation of the single modules is dependent on the activation of the products. E. g. modules of , like e. g. FileBroadcast, can only be activated when itself is activated.
[recipient]
user_name=Vitalstatistix
user_name_prefix=provider!
user_key=vitalstatistix-pwd
user_key_crypt=hx4w-4p4l-yjep-teng
[shell]
login=none port=2517
refresh=8
graphic_port=2418
allowed_address=127.1.1.18
interface_address=127.1.1.1
[locations]
log_file=recv.log
channels_file=recv_channels.ini
file_database_directory=receiving
webbroadcast_cache_directory=received/webbroadcast
prefetching_cache_directory=pushed_data
license_file=license.ini
[logging]
log_file_size=1000000
log_file_number=4
log_level=normal
[mail]
mail_server_address=mail.company.de:25
sender_address= user@company.com
default_feedback_mail_recipient=operator@company.com
runtime_error_mail_recipient=operator@company.com
[announcement_channel]
address=224.1.2.3:4711
name=TSL Announcement Channel
bandWIDTH=1000000
[parameters]
interface_address=127.1.1.2
total_bandWIDTH=1000000
acknowledgement_proxy_address=127.0.0.1:9200
packet_naks=0
potential_repetitor=0
repetitor_retransmission_rate=100
allow_execute=0
file_database_size=262144000
temp_directory=incomplete-files
temp_prefix=. temp_suffix=!
[webbroadcast]
min_file_lifetime=0
[news]
server_address=localhost:1400
connection_timeout=30
[etcp_parameters]
server_proxy_host_name=test.company.de
server_proxy_port=9200
http_listen_address=9202
socks_listen_address=9203
max_send_data_rate=1000000
max_receive_data_rate=1000000
multicast_receive_interface=172.1.1.2
allowed_address=127.0.0.1
default_speed_state=0
toggle_speed_listen_port=8560
toggle_speed_allowed_address=127.0.0.1
authentication=0
use_icon=1
use_etcp_when_speed_off=1
use_http_prefetching=auto
http_proxy=samba:8080
ftp_proxy=rumba:8080
local_udp_address=127.1.1.2
inactivity timeout=60
[etcp_compression]
http_compression=0
socks_tcp_compression=0
socks_udp_compression=0
port_forwarding_compression=0
[etcp_port_forwarding]
server_name=mail.company.de
server_port=110
local_port=9595
[etcp_connection_control]
nak_timeout=100
connect_initial_timeout=2000
connect_additional_timeout=6000
nr_of_tcp_connections=1
[license]
copyright=COPYRIGHT (c)
license_class=evaluation copy
expire_date=2001.11.10
oem_license=none
max_licensed_bandWIDTH=5000000
restriction=valid in conjunction with service or evaluation agreement only
product_license=Client/TelliCast
product_license=Client/FileBroadcast
product_license=Client/WebBroadcast
product_license=Client/NewsBroadcast
product_license=Client/OfflineMail
product_license=Client/DataStreams
product_license=Client/TelliNet
product_license= Client/HTTP-Prefetching
product_license= Client/Enhanced-TCP
product_license= Client/Authentication
operating_system=Client/Windows(Intel)
operating_system=Client/Linux(Intel)
operating_system=Client/Irix(Mips)
description=my evaluation copy
http_skin=company
version=3
license_key=
[activations]
Client/TelliCast=on
Client/TelliCast=off
Client/FileBroadcast=on
Client/FileBroadcast=off
Client/WebBroadcast=on
Client/WebBroadcast=off
Client/NewsBroadcast=on
Client/NewsBroadcast=off
Client/OfflineMail=on
Client/OfflineMail=off
Client/DataStreams=on
Client/DataStreams=off
Client/TelliNet=on
Client/TelliNet=off
Client/HTTP-Prefetching=on
Client/HTTP-Prefetching=off
Client/Enhanced-TCP=on
Client/Enhanced-TCP=off
Client/Authentication=on
Client/Authentication=off
[filechannel]
priority=10
target_directory=received
allow_execute=0
packet_naks=1
potential_repetitor=0
repetitor_retransmission_rate=10
temp_directory=incomplete-files
temp_prefix=.
temp_suffix=!
[webchannel]
priority=1
target_directory=received
packet_naks=0
potential_repetitor=0
repetitor_retransmission_rate=10
[mailchannel]
priority=1
packet_naks=1
potential_repetitor=0
repetitor_retransmission_rate=100
[newschannel]
priority=2
packet_naks=1
potential_repetitor=1
repetitor_retransmission_rate=10
[streamchannel]
priority=8
stream_protocol=tcp
stream_address=8405
stream_interface=172.24.24.24
stream_ttl=1
packet_naks=1
potential_repetitor=1
repetitor_retransmission_rate=10
Sat4U - недокументированные возможности
У меня клиент SatSpeed (Sat4U) слетел в кору, ну и я нечаяно у него в "кишках" покопался. Вот например, пропишите у себя в файле licence.ini следующие строчки:
[shell]
login=none
port=2517
refresh=8
И зайдите на http://localhost:2517/
Сами все увидите (там статистика соединений в реальном времени) !!!
Или еще, рабочие ссылки на клиенете/сервере SatSpeed:
- http://localhost:2517/www/html/head.html - основное меню
- http://localhost:2517/www/html/main.html - Status Overview
- http://localhost:2517/www/html/graphics.html - Session Graphics
2002-02-20
Сергей Очкасов aka paganelp
Коломна
| Комментарии? Поправки? Дополнения? dvbnet@msk.gs.ru |
 |
All rights reserved.
Новоладожская, д.4
Тел.: (812) 332-86-68
