Hello All.
Why is it that Syncrhonet's linux based BinkP always *seems* to drop it's inbound connection, ungracefully at that? Here's a couple of examples from my BinkP log:
-o-o-o-o-o-o-o-o-CUT-o-o-o-o-o-o-o-o-o-
* 20:37:00 (10) Sent to 1:106/633: 0122FDB4.MOB (2151 bytes)
? 20:37:00 (10) BinkP error: remote dropped connection.
Here's an example of a normal close-out of a BinkP session from a couple non-Synchronet Nodes:
-o-o-o-o-o-o-o-o-CUT-o-o-o-o-o-o-o-o-o-
* 00:05:07 (8) Sent to 1:124/5016: 0110EC95.MO0 (15247 bytes)
- 00:05:07 (8) Connection closed.
=-=-=-=
* 01:00:23 (8) Sent to 1:387/20: 00090019.MO0 (848 bytes)
- 01:00:23 (8) Connection closed.
Is this a fault in the Synchronet BinkP daemon or is it a user configuration error?
Sysop: | Tandy |
---|---|
Location: | New York, USA |
Users: | 15 |
Nodes: | 13 (0 / 13) |
Uptime: | 01:01:48 |
Calls: | 335 |
Messages: | 113,798 |