Text 459, 439 rader
Skriven 2006-04-20 01:15:06 av Binkd Team (2:5020/1042)
Ärende: BinkD FAQ [2/2]
=======================
http://www.n451.z2.fidonet.net/binkd/
The latest sources are on the CVS server.
The DOS version has the feature of not supporting a net and every
possible implementation uses one of the IP stacks developed by an
independent producer. The implementation by Victor Pashkevich works with
the drivers of IBM TCP/IP version 2.1 only. One can find them here:
http://www.ibm.com
http://binkd.grumbler.org/tcpdos21.rar
ftp://ftp.grumbler.org/pub/tcpdos/tcpdos21.rar
You may also make a file request for tcpdos21.rar from 2:5080/102.
Besides everybody may port BinkD for the version of IP drivers for DOS
he/she has :-). The sources are in the Internet and in the fileecho (see
"Where Can One Take a Fresh BinkD Version?")
----------------------------------------------------------------------------
21. BinkD Under Windows 3.x
Sergey Zharsky (zharik@usa.net) ported BinkD 0.9.2 and BinkD 0.9.5 for
Windows 3.x. They work using IP stacks Trumpet Winsock ver. 3.0 revision D
and Novell TCP/IP Client for Win 3.11 (see the answer to the question
'BinkD Under DOS', the section "The DOS version has the feature...").
The sources and the binaries:
http://zharik.host.sk/index.php?pages=d&page=d
0.9.2 only:
http://www.doe.carleton.ca/~nsoveiko/fido/binkd/0.9.2/
----------------------------------------------------------------------------
22. Different FTN Domains in BinkD And a Tosser Without 5D Support
Suppose there are two domains (with different zone numbers though it
does not matter). Mail can be successfully sent to the first domain but
not to the second one. This situation may arise if the tosser, the tracker
and the other your FTN programs do not support 5D BSO.
This is a typical BinkD configuration for two FTN domains and 5D
outbound:
domain fidonet c:\\ftn\\outbound\\fidonet 2
domain omeganet c:\\ftn\\outbound\\omeganet 11
address 2:5070/222@fidonet 11:58/6@omeganet
One must configure not the zone of your own address for 'domain'
keyword as one might think but the zone that should not be appended to the
outbound name (i.e. the outbound subdirectory extensions are not processed
for the zone denoted in the 'domain' line).
If your tosser would create bundles for omeganet in the omeganet
directory then you should write as indicated above. But since it does not
work with 5D and it creates the bundles in fidonet.00b then you should
write this way:
domain fidonet c:\\ftn\\outbound\\fidonet 2
domain omeganet c:\\ftn\\outbound\\omeganet 2
address 2:5070/222@fidonet 11:58/6@omeganet
It is obligatory to configure all your addresses with domains. The
outbound directory and the path should be the same everywhere (4D tosser
considers all addresses to belong to one domain).
----------------------------------------------------------------------------
23. How Does "domain ... alias-for ..." In The Configuration File Work?
An alias is taken into consideration when the remote site address is
analyzed.
Example:
domain fidonet.net alias-for fidonet
'fidonet.net' in the remote site address will be changed to 'fidonet' and
address 1:2/3.4@fidonet.net will be dealt with as 1:2/3.4@fidonet.
----------------------------------------------------------------------------
24. What Does "send: TCP/IP error (-10000)" Mean and How To Cure It?
There are two bugs here, one of them had been fixed before a branch for
binkd 0.9.5-stable was created.
1. The fact is that the error number was not stored in a pair of places
in BinkD code but it became apparent nowhere except the Windows version. It
showed there because unlike others the MS Visual C run-time library does
not correspond to the standard. 'errno' and 'h_errno' are macros in MSVC
RTL and they expand to system calls which in the end call GetLastError().
And the variable errno to which the function returns its value is cleared
to zero at every successful system call. Thus errno is cleared at
successful file open (according to the C standard errno should not change
if there were no more errors). The influence of the bug is fixed in BinkD:
2003/04/28 07:30:16 gul
* Bugfix: Log() changes TCPERRNO
2. A Winsock bug: select() always returns successful for a non-blocked
socket. The influence of this and other Winsock bugs is partially fixed:
2003/06/06 16:27:44 gul
* Workaround winsock bug - giveup CPU when sending file
2003/08/11 08:41:55 gul
* workaround winsock bug (patch by Alexander Reznikov)
2003/08/24 00:29:31 hbrew
* win9x-select-workaround fix, thanks to Pavel Gulchouck)
At the high log level many messages of the 'data transfer would block'
type and debug info on select() execution is still logged. It does not
influence a regular work mode. It could be fixed but Pavel decided not to
complicate the code.
----------------------------------------------------------------------------
25. Argus (Radius) and BinkD: Argus Error "Aborting due to carrier
loss"
A session between BinkD and Radius (or Argus, it does not matter) is
aborted "due to carrier loss" when traffic encryption is enabled in Radius.
Moreover the connection at the BinkD side is aborted due to the remote side
initiative ("Connection reset by peer").
Log from the Radius side:
30-Aug-2003 22:24:31 Encrypted (2:463/375) session
30-Aug-2003 22:24:32 Aborting due to carrier loss
30-Aug-2003 22:24:32 Session aborted
30-Aug-2003 22:24:32 End
The reason is that Argus authors implemented an encryption method of
their own which is not implemented in BinkD. It would be OK but Argus (and
Radius together with it) does not keep compatibility with BinkP protocol:
the encryption is enabled unconditionally without checking if the remote
side supports it. Such a glaring contradiction to the specification is
inadmissible but alas... The way out is to disable encryption in Argus for
every link using BinkD.
The correct mailer behaviour should be as follows:
- if encryption is not mandatory then proceed with the nonencrypted
session;
- if encryption is set mandatory in the mailer configuration then it
should inform the remote of aborting the session, for example in such a way:
M_ERR "DES encription required"
----------------------------------------------------------------------------
26. The Outbound Name Has a Comment Char and Binkd Doesn't See It
If BinkD is configured in a working system where Bink/+ is used and the
outbound path contains "#" character which is a comment character for BinkD
the character should be escaped by a backslash in the BinkD configuration
file for BinkD to interpret it correctly.
domain fidonet c:\\fido\\\#out
inbound-nonsecure c:\\fido\\unsec\#in
inbound c:\\fido\\\#in
It is not necessary to escape the character in the version 1.0 starting
with the snapshot 1.0a-317 because the beginning of a comment in the middle
of a line is now the sequence of either a space and the pound character
(" #") or a tab and the pound character. See the examples below.
There is no comment:
temp-inbound c:\\fido\\temp#this_is_not_a_comment_but_a_directory_name
There are comments here:
inbound c:\\fido\\in # this is a comment since there is a space before "#"
# This whole line is a comment.
----------------------------------------------------------------------------
27. Is There a Possibility to Start an Application On an Event From
BinkD?
If time events are discussed then no, there is not and there will never
be. There are diverse schedulers for controlling such events and they are
included in the distribution packages of modern operating systems.
As to an event of receiving a file it is implemented long ago (starting
with the version 0.9). See tokens "exec" and "flag" in the configuration
file.
----------------------------------------------------------------------------
28. What Is the Difference Between BinkD/w32 and BinkD/w9x?
Binkd/w32 is a traditional version of BinkD and a console application.
Binkd/w9x is a GUI Win32 application creating temporary console windows in
case of necessity. If one starts BinkD/w32 in the existing console window
(for example, in the command.com or cmd.exe window) it will work in the
same window. Unlike it BinkD/w9x immediately transfers control to the
calling task.
The development of BinkD/w9x was necessitated by several significant
differencies between Windows 95/98/Me and Windows NT/2000/XP/2003.
In the first place console is implemented differently. The main
difference: Windows 9x console does not react to shutdown and close window
signals thus a working BinkD/w32 cannot stop correctly when the window is
closed or the system shutdown (or reboot) is performed.
In the second place the principles of performing a service differ in
different branches of Windows.
As a result BinkD 1.0a/w32 can work as a service only in Windows
NT/2000/XP/2003 and BinkD 1.0a/w9x as a service only in Windows 95/98/Me.
It is planned to support Windows NT service in BinkD/w9x. A correct support
of working as a service under Windows 9x is impossible for BinkD/w32
because of the described console features in the systems.
----------------------------------------------------------------------------
29. I Miss a Chat in BinkD And I Want To Synchronize Time!
You may use talk, icq or irc (or even Gadu-Gadu) for chatting. If you
can start BinkD then all the programs mentioned here and many other ones
may use the same channel. You may chat as much as you like.
And there are special utilities for synchronizing time via IP, for
example ntpdate. Unlike mailers such utilities take time from the precise
time servers.
----------------------------------------------------------------------------
30. BinkD Receives an Incoming Call Only After an Outgoing One.
Such a behaviour was observed for BinkD/w32 working as a service on a
computer with McAfee Firewall installed. The firewall starts after BinkD
start-up, does not detect any BinkD activity and does not allow to
establish a connection. Thus one must ensure that BinkD starts after
firewall has started.
The possible decisions: give up using BinkD as an independent Windows
NT service and start it from another service or start it as a usual program
or stop using such a firewall.
----------------------------------------------------------------------------
31. "start_file_transfer: ECHO is off.: No such file or directory"
Error.
One may see the following in the log file:
? 10 Sep 20:37:23 [1664] start_file_transfer: ECHO is on.: No such file
or directory
Such a situation may occur when you have created a poll with the command
echo >> 12345678.ilo
The above mentioned line in the log file is the message from the echo
command on its current status of the output to the screen. See question 32
on how to correctly create a poll. See also question 09.
----------------------------------------------------------------------------
32. How to Create a Poll Correctly.
To create a poll in BSO one should create an empty file NNNNMMMM.ilo,
NNNNMMMM.clo, NNNNMMMM.dlo or NNNNMMMM.flo. The filename consists of the
hexadecimal net number (first 4 characters), the hexadecimal node number
(the characters from 5 to 8), the dot, the flavor attribute character
(i = immediate, c = crash, d = direct, f = normal) and two characters "lo".
Certainly you should not create the file, if it already exists. Moreover
you should not overwrite it to avoid losing your mail.
The most universal command (it works under DOS, Windows, OS/2, UNIX
clones, CP/M and many others) is
cd . >>NNNNMMMM.flo
Such a command also works under DOS, Windows, OS/2:
type nul >>NNNNMMMM.flo
You may choose one of the following commands for UNIX clones:
touch NNNNMMMM.flo
echo -n "" >>NNNNMMMM.flo
>>NNNNMMMM.flo
cat /dev/null >>NNNNMMMM.flo
----------------------------------------------------------------------------
33. What Does the Number in Brackets in the Log Mean?
It is either PID (Process ID) in the multiprocess BinkD versions (for
example, in the versions for UNIX-like OS), or TID (Thread ID) in the
multithreaded BinkD versions (for example, in Windows versions).
The process (or the thread) number simplifies the log analysis: it
allows picking out messages from one BinkD process (or thread). In
particular, it allows separating the messages from the different sessions.
----------------------------------------------------------------------------
34. How to Configure BinkD for sending outgoing mail?
You should configure your netmail packer in such a way that your mail
is packed to BSO (Binkley Style Outbound) packets. If you have not used
such a program before then you should install it. In some modem mailers the
possibility of packing netmail to BSO has been provided by their developers
(for example, in T-Mail starting with the version 2500).
See also the answer to question 17.
----------------------------------------------------------------------------
35. What for Does One Need the "share" Directive in the Configuration
File?
Shared AKA is used for sending netmail to one of the alternative routes
and is your protection for the case when your netmail link goes down. In
the sample configuration file
share 2:999/999 2:5020/52 2:5020/238
the uplinks are 2:5020/52 and 2:5020/238 with the shared AKA 2:999/999
added. Then you configure packing netmail to 2:999/999 and BinkD will send
it to those of the two uplinks, the session with which will occur earlier.
If there is no connection to 2:5020/52 the netmail will go to 2:5020/238.
If there is no connection to 2:5020/238 it will go to 2:5020/52. The
package addressee will be replaced by the real one.
P.S. For netmail to be processed correctly at every node, the netmail
processor at the node should be aware of the shared AKA password. In
practice the password should be absent in the PKTs and the netmail tracker
should process PKT from you without a password at every link.
----------------------------------------------------------------------------
36. What for Does One Need the "ftrans" Directive in the Configuration
File?
It is necessary for placing BinkD and your tosser at different computers
in the net, when outbound resides at a net drive and the paths to it are
different. Moreover the tosser may run on a computer with FAT and the paths
of the d:\long\path\to type, and BinkD may run on a UNIX machine with paths
of the /mnt/samba/wincomp1/path/to type.
----------------------------------------------------------------------------
A1. I Have Found a Bug in BinkD!
Try to refresh your BinkD version (it is possible that the bug has
already been fixed). If it did not help please write to developers:
binkd-bugs@happy.kiev.ua
Pavel Gulchouck 2:463/68
Mailing list binkd-dev@happy.kiev.ua
In your message please describe in detail the situation when the error
happens. Please do not forget to mention your BinkD version and to cite a
piece of detailed log (loglevel more than 5).
----------------------------------------------------------------------------
A2. I Want To Talk To Developers
Dmitry Malov who is the author of the first BinkD versions does not
develop it any more now. During the years 2000-2003 the project is
coordinated by Pavel Gulchouck 2:463/68 (Pavel Gulchouck <gul@gul.kiev.ua>).
He also writes the most part of the code.
There is a mailing list for developers and testers:
binkd-dev@happy.kiev.ua.
To subscribe to it write a message:
To: majordomo@happy.kiev.ua
Subject:
subscribe binkd-dev
----------------------------------------------------------------------------
A3. I Want To Get Information About Changes In BinkD Immediately!
Please subscribe to the mailing list binkd-diffs@happy.kiev.ua: the
changes in the sources are sent here (you may also test patches for errors).
You may read how to subscribe in the previous answer.
There are two FIDOnet echomail conferences for discussions on binkd and
for dialogue of the users and the developers: Russian RU.BINKD and
international BINKD (in English). Please look for them at echomail hubs :).
----------------------------------------------------------------------------
A4. And When Will BinkD Do ... ?
Maybe it will do it some time in the future. And maybe not. You may wait
until the feature you wish will be implemented or you may "fix" it yourself:
the source code is open. Please do not forget to send your patch to the
developers, it will be possibly included in the main development branch and
for sure it will be put to the Web site or the FTP archive.
=== The end.
--- hpt/w32 1.4.0-stable
* Origin: Moscow, Russia (2:5020/1042)
|