All,

Has anyone seen an error like that come up before? I'm now running v1.0.6.8 for
my 1:120/544 hub node and that error is coming up for when just one of my downlinks attempts to connect:

+ 26-Sep-2016 00:14:54 mbcico[24206] Binkp: send "/opt/mbse/var/bso/outbound/0000ffa0.tu3" as "0000ffa0.tu3"
+ 26-Sep-2016 00:14:54 mbcico[24206] Binkp: size 210469 bytes, dated Sep 20 23:34:29, comp No
? 26-Sep-2016 00:14:54 mbcico[24206] tty_write: hanged_up flag
+ 26-Sep-2016 00:14:54 mbcico[24206] Binkp: transmitter failure
+ 26-Sep-2016 00:14:54 mbcico[24206] Binkp: session finished, rc=108
+ 26-Sep-2016 00:14:56 mbcico[24206] Incoming call failed (rc=108)
+ 26-Sep-2016 00:14:56 mbcico[24206] Terminated with error 108


The '0000ffa0.tu3' file itself does not appear to have any permissions issues. That '108' error appears to be a "File Transfer Error"...

The other system uses this (which I'm not familiar with...): BinkIT/1.39,JSBinkP/1.54/Win32 binkp/1.1


Also; depending on the intent of that error message, it may actually be mis-spelled...




Jame


--- BBBS/Li6 v4.10 Dada-1
* Origin: BBBS Info at Rocasa (1:120/546)

Re: Error: "tty_write: hanged_up flag"
By: Rj Clay to All on Mon Sep 26 2016 12:27 pm

The other system uses this (which I'm not familiar with...): BinkIT/1.39,JSBinkP/1.54/Win32 binkp/1.1

I'm not sure what the error is but BinkIT is a JavaScript mailer that duece is working on that works with synchronet. I haven't tried it with MBSE but it works quite well with binkd but may need more work when connecting to other mailers.

... I came, I saw, I had no idea what was going on, I left.
--- SBBSecho 3.00-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.1)

Hello Rj!

Monday September 26 2016 12:27, you wrote to All:

All,

Has anyone seen an error like that come up before? I'm now running
v1.0.6.8 for my 1:120/544 hub node and that error is coming up for
when just one of my downlinks attempts to connect:

+ 26-Sep-2016 00:14:54 mbcico[24206] Binkp: send "/opt/mbse/var/bso/outbound/0000ffa0.tu3" as "0000ffa0.tu3"
+ 26-Sep-2016 00:14:54 mbcico[24206] Binkp: size 210469 bytes, dated
Sep 20
23:34:29, comp No
? 26-Sep-2016 00:14:54 mbcico[24206] tty_write: hanged_up flag
+ 26-Sep-2016 00:14:54 mbcico[24206] Binkp: transmitter failure
+ 26-Sep-2016 00:14:54 mbcico[24206] Binkp: session finished, rc=108
+ 26-Sep-2016 00:14:56 mbcico[24206] Incoming call failed (rc=108)
+ 26-Sep-2016 00:14:56 mbcico[24206] Terminated with error 108

The '0000ffa0.tu3' file itself does not appear to have any permissions issues. That '108' error appears to be a "File Transfer Error"...

The other system uses this (which I'm not familiar with...): BinkIT/1.39,JSBinkP/1.54/Win32 binkp/1.1

Also; depending on the intent of that error message, it may actually
be mis-spelled...

If it is a system defined in your set up try marking it as BINKD v1.0 and see what happens.





Vince

--- Mageia Linux v5/Mbse v1.0.6/GoldED+/LNX 1.1.501-b20150715
* Origin: Air Applewood, The Linux Gateway to the UK (2:250/1)

26 Sep 16 12:27, you wrote to All:

The other system uses this (which I'm not familiar with...): BinkIT/1.39,JSBinkP/1.54/Win32 binkp/1.1

that's the new synchronet bbs binkp protocol mailer written in javascript... it
is still in development...

Also; depending on the intent of that error message, it may actually
be mis-spelled...

i'm not sure which error message you speak of... i didn't notice any misspelling...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDP/IPS yer doin' it wrong...
... "Caught in the Flood" by Noah Zark
---
* Origin: (1:3634/12.73)

Hello Rj!

26 Sep 16 12:27, you wrote to all:

Has anyone seen an error like that come up before? I'm now running v1.0.6.8 for my 1:120/544 hub node and that error is coming up for
when just one of my downlinks attempts to connect:

+ 26-Sep-2016 00:14:54 mbcico[24206] Binkp: send "/opt/mbse/var/bso/outbound/0000ffa0.tu3" as "0000ffa0.tu3"
+ 26-Sep-2016 00:14:54 mbcico[24206] Binkp: size 210469 bytes, dated
Sep 20
23:34:29, comp No
? 26-Sep-2016 00:14:54 mbcico[24206] tty_write: hanged_up flag
+ 26-Sep-2016 00:14:54 mbcico[24206] Binkp: transmitter failure
+ 26-Sep-2016 00:14:54 mbcico[24206] Binkp: session finished, rc=108
+ 26-Sep-2016 00:14:56 mbcico[24206] Incoming call failed (rc=108)
+ 26-Sep-2016 00:14:56 mbcico[24206] Terminated with error 108

The '0000ffa0.tu3' file itself does not appear to have any permissions issues. That '108' error appears to be a "File Transfer Error"...

The other system uses this (which I'm not familiar with...): BinkIT/1.39,JSBinkP/1.54/Win32 binkp/1.1

I've never seen this error connecting to BinkD (for OS/2 or Windows), Argus, Radius, Taurus, and even Fred Riccio's experimental Binkp mailer. I suspect that the issue lies with BinkIT, but will need to test further to confirm that.

Also; depending on the intent of that error message, it may actually
be mis-spelled...

I'll know more after checking out the debug log of a session with a BinkIT node.

Andrew

--- GoldED+/LNX 1.1.5-b20160322
* Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)

Hello Rj!
Monday September 26 2016 12:27, you wrote to All:

All,
Has anyone seen an error like that come up before? I'm now running
v1.0.6.8 for my 1:120/544 hub node and that error is coming up for
when just one of my downlinks attempts to connect:
+ 26-Sep-2016 00:14:54 mbcico[24206] Binkp: send
"/opt/mbse/var/bso/outbound/0000ffa0.tu3" as "0000ffa0.tu3"
+ 26-Sep-2016 00:14:54 mbcico[24206] Binkp: size 210469 bytes, dated
Sep 20
23:34:29, comp No
? 26-Sep-2016 00:14:54 mbcico[24206] tty_write: hanged_up flag
+ 26-Sep-2016 00:14:54 mbcico[24206] Binkp: transmitter failure
+ 26-Sep-2016 00:14:54 mbcico[24206] Binkp: session finished, rc=108
+ 26-Sep-2016 00:14:56 mbcico[24206] Incoming call failed (rc=108)
+ 26-Sep-2016 00:14:56 mbcico[24206] Terminated with error 108

The other system uses this (which I'm not familiar with...):
BinkIT/1.39,JSBinkP/1.54/Win32 binkp/1.1
Also; depending on the intent of that error message, it may actually
be mis-spelled...

If it is a system defined in your set up

He's a downlink, so yes he's in my setup.

try marking it as BINKD v1.0 and see what happens.

Good point. Changed it so that it's *not* 1.1 and then ended up with a different error.

+ 27-Sep-2016 19:28:28 mbcico[18341] Binkp: got M_ERR "Encryption required"
+ 27-Sep-2016 19:28:28 mbcico[18341] Binkp: receiver failure
+ 27-Sep-2016 19:28:28 mbcico[18341] Binkp: session finished, rc=108
+ 27-Sep-2016 19:28:30 mbcico[18341] Incoming call failed (rc=108)


But I can poll his system with no apparent issues...





jame

--- BBBS/Li6 v4.10 Dada-1
* Origin: BBBS Info at Rocasa (1:120/546)

Re: Error: "tty_write: hanged_up flag"
By: Rj Clay to All on Mon Sep 26 2016 12:27 pm

The other system uses this (which I'm not familiar with...):
BinkIT/1.39,JSBinkP/1.54/Win32 binkp/1.1

I'm not sure what the error is but BinkIT is a JavaScript mailer that duece is
working on that works with synchronet. I haven't tried it with MBSE but it works quite well with binkd but may need more work when connecting to other mailers.

Yep, it's looks like it may need more work...





Jame



--- BBBS/Li6 v4.10 Dada-1
* Origin: BBBS Info at Rocasa (1:120/546)

Re: Error: "tty_write: hanged_up flag"
By: Rj Clay to Alan Ianson on Tue Sep 27 2016 07:50 pm

I'm not sure what the error is but BinkIT is a JavaScript mailer that
duece is working on that works with synchronet. I haven't tried it
with MBSE but it works quite well with binkd but may need more work
when connecting to other mailers.

Yep, it's looks like it may need more work...

I think, but I am not certain that the problem is related to the crypt support that it has for binkd but other mailers like Mystics binkp mailer don't get along.

I haven't tested that much but that's the impression I have.

I don't quite understand that crypt support in binkd but I wonder if other mailers like MBSE's and Mystics mailer could/should support it?

... Disclaimer: Advice void where prohibitted by common sense!
--- SBBSecho 3.00-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.1)

Hi Andrew!

Hello Rj!
26 Sep 16 12:27, you wrote to all:

Has anyone seen an error like that come up before? I'm now running
v1.0.6.8 for my 1:120/544 hub node and that error is coming up for
when just one of my downlinks attempts to connect:
+ 26-Sep-2016 00:14:54 mbcico[24206] Binkp: send
"/opt/mbse/var/bso/outbound/0000ffa0.tu3" as "0000ffa0.tu3"
+ 26-Sep-2016 00:14:54 mbcico[24206] Binkp: size 210469 bytes, dated
Sep 20
23:34:29, comp No
? 26-Sep-2016 00:14:54 mbcico[24206] tty_write: hanged_up flag
+ 26-Sep-2016 00:14:54 mbcico[24206] Binkp: transmitter failure
+ 26-Sep-2016 00:14:54 mbcico[24206] Binkp: session finished, rc=108

Also; depending on the intent of that error message, it may actually
be mis-spelled...

I'll know more after checking out the debug log of a session with a BinkIT node.

This is from an inbound session from him today:

30-Sep-2016 22:23:32 mbcico[9173]
30-Sep-2016 22:23:32 mbcico[9173] MBCICO v1.0.6.8
30-Sep-2016 22:23:32 mbcico[9173] Cmd: mbcico -t ibn
? 30-Sep-2016 22:23:32 mbtask[552] TCP/IP session registered (9173), now 1 sessions
+ 30-Sep-2016 22:23:32 mbcico[9173] Options: Call WaZOO EMSI Freqs Zmodem ZedZap Hydra PLZ GZ/BZ2 NoNR CRC
+ 30-Sep-2016 22:23:32 mbcico[9173] Incoming IBN/TCP connection from 24.176.26.218
+ 30-Sep-2016 22:23:32 mbcico[9173] Start inbound Binkp session
+ 30-Sep-2016 22:23:32 mbcico[9173] Binkp: start session
+ 30-Sep-2016 22:23:32 mbcico[9173] Options : CRYPT
+ 30-Sep-2016 22:23:33 mbcico[9173] System : The Twisted Tower
+ 30-Sep-2016 22:23:33 mbcico[9173] Sysop : drakahn99
+ 30-Sep-2016 22:23:33 mbcico[9173] Location: Coldwater, Mi
+ 30-Sep-2016 22:23:33 mbcico[9173] Flags : 115200,TCP,BINKP
+ 30-Sep-2016 22:23:33 mbcico[9173] Time : Fri Sep 30 2016 22:19:58 GMT-0400 (Eastern Daylight Time)
+ 30-Sep-2016 22:23:33 mbcico[9173] Uses : BinkIT/1.39,JSBinkP/1.54/Win32 binkp/1.1
+ 30-Sep-2016 22:23:33 mbcico[9173] address : 1:120/640@fidonet
+ 30-Sep-2016 22:23:33 mbcico[9173] getnlent: 1:120/640@fidonet system name override with twstdt.synchro.net
+ 30-Sep-2016 22:23:33 mbcico[9173] getnlent: 1:120/640@fidonet flags override ICM,IBN
+ 30-Sep-2016 22:23:33 mbcico[9173] Binkp: remote is a listed system
+ 30-Sep-2016 22:23:33 mbcico[9173] Options: Call WaZOO EMSI Freqs Zmodem ZedZap Hydra PLZ GZ/BZ2 NoNR CRC
+ 30-Sep-2016 22:23:33 mbcico[9173] Binkp: MD5 protected session
+ 30-Sep-2016 22:23:33 mbcico[9173] Binkp: mail 0, files 780528 bytes
+ 30-Sep-2016 22:23:33 mbcico[9173] Binkp: send "/opt/mbse/var/bso/outbound/0000ffa0.wem" as "0000ffa0.wem"
+ 30-Sep-2016 22:23:33 mbcico[9173] Binkp: size 213434 bytes, dated Sep 28 23:49:52, comp No
+ 30-Sep-2016 22:23:33 mbcico[9173] Binkp: got M_ERR "Encryption required"
+ 30-Sep-2016 22:23:33 mbcico[9173] Binkp: receiver failure
+ 30-Sep-2016 22:23:33 mbcico[9173] Binkp: session finished, rc=108
+ 30-Sep-2016 22:23:35 mbcico[9173] Incoming call failed (rc=108)
+ 30-Sep-2016 22:23:35 mbcico[9173] Terminated with error 108


Wonder if that "Encryption required" is a setting on his end? Connections to do work if I connect to him, after all...




Jame

--- BBBS/Li6 v4.10 Dada-1
* Origin: BBBS Info at Rocasa (1:120/546)

Re: Error: "tty_write: hanged_up flag"
By: Rj Clay to Alan Ianson on Tue Sep 27 2016 07:50 pm

I'm not sure what the error is but BinkIT is a JavaScript mailer that
duece is working on that works with synchronet. I haven't tried it
with MBSE but it works quite well with binkd but may need more work
when connecting to other mailers.

Yep, it's looks like it may need more work...

I think, but I am not certain that the problem is related to the crypt support
that it has for binkd

That may well be as the error showing in the debug log with his system shows the following:

Binkp: got M_ERR "Encryption required"
Binkp: receiver failure
Binkp: session finished, rc=108

I don't quite understand that crypt support in binkd but I wonder if other mailers like MBSE's and Mystics mailer could/should support it?

That might be a good idea, but is it documented well enough?






Jame

--- BBBS/Li6 v4.10 Dada-1
* Origin: BBBS Info at Rocasa (1:120/546)

30 Sep 16 22:34, you wrote to Andrew Leary:

30-Sep-2016 22:23:33 mbcico[9173] Binkp: size 213434 bytes, dated Sep 28 23:49:52, comp No
+ 30-Sep-2016 22:23:33 mbcico[9173] Binkp: got M_ERR "Encryption required" + 30-Sep-2016 22:23:33 mbcico[9173] Binkp: receiver failure
+ 30-Sep-2016 22:23:33 mbcico[9173] Binkp: session finished, rc=108
+ 30-Sep-2016 22:23:35 mbcico[9173] Incoming call failed (rc=108)
+ 30-Sep-2016 22:23:35 mbcico[9173] Terminated with error 108

Wonder if that "Encryption required" is a setting on his end?
Connections to do work if I connect to him, after all...

yes, i expect so... some operators try to force things like passwords on all sessions even when they don't have passwords set up... some like to try to force encryption and compression... we can see that compression is not in use but apparently they are trying to force encryption... they need to disable it or binkit needs to disregard it if the remote side does not indicate encryption
capabilities being available... we won't even mention the negotiation necessary
to decide which encryption to use ;)

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... We don't get to know people when they come to us; we must go to them.
---
* Origin: (1:3634/12.73)

Re: Error: "tty_write: hanged_up flag"
By: Rj Clay to Alan Ianson on Fri Sep 30 2016 10:39 pm

That may well be as the error showing in the debug log with his system shows the following:

Binkp: got M_ERR "Encryption required"
Binkp: receiver failure
Binkp: session finished, rc=108

My experience with Mystics binkp support is much the same as this. Mystic supports MD5 but doesn't understand crypt.

I don't quite understand that crypt support in binkd but I wonder if
other mailers like MBSE's and Mystics mailer could/should support it?

That might be a good idea, but is it documented well enough?

The source is available but I don't know if there is any documentation of this. I wonder if it is documented in any of the FTSC standards or proposals?

... Proofread carefully to see if you any words out
--- SBBSecho 3.00-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.1)

01 Oct 16 10:30, you wrote to Rj Clay:

That might be a good idea, but is it documented well enough?

The source is available but I don't know if there is any documentation
of this. I wonder if it is documented in any of the FTSC standards or proposals?

the FTSC does have one or two documents concerning the binkp protocol... i think there is also an update in progress but it hasn't seen any activity in a while...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Northerners eat fried chicken with a knife and fork.
---
* Origin: (1:3634/12.73)

Hello Rj!

Friday September 30 2016 22:34, Rj Clay wrote to Andrew Leary:

This is from an inbound session from him today:

30-Sep-2016 22:23:32 mbcico[9173]
30-Sep-2016 22:23:32 mbcico[9173] MBCICO v1.0.6.8
30-Sep-2016 22:23:32 mbcico[9173] Cmd: mbcico -t ibn
? 30-Sep-2016 22:23:32 mbtask[552] TCP/IP session registered (9173),
now 1 sessions + 30-Sep-2016 22:23:32 mbcico[9173] Options: Call WaZOO EMSI Freqs Zmodem ZedZap Hydra PLZ GZ/BZ2 NoNR CRC + 30-Sep-2016
22:23:32 mbcico[9173] Incoming IBN/TCP connection from 24.176.26.218 + 30-Sep-2016 22:23:32 mbcico[9173] Start inbound Binkp session + 30-Sep-2016 22:23:32 mbcico[9173] Binkp: start session + 30-Sep-2016 22:23:32 mbcico[9173] Options : CRYPT + 30-Sep-2016 22:23:33
mbcico[9173] System : The Twisted Tower + 30-Sep-2016 22:23:33 mbcico[9173] Sysop : drakahn99 + 30-Sep-2016 22:23:33 mbcico[9173] Location: Coldwater, Mi + 30-Sep-2016 22:23:33 mbcico[9173] Flags : 115200,TCP,BINKP + 30-Sep-2016 22:23:33 mbcico[9173] Time : Fri Sep
30 2016 22:19:58 GMT-0400 (Eastern Daylight Time) + 30-Sep-2016
22:23:33 mbcico[9173] Uses :
BinkIT/1.39,JSBinkP/1.54/Win32 binkp/1.1 + 30-Sep-2016 22:23:33 mbcico[9173] address : 1:120/640@fidonet + 30-Sep-2016 22:23:33 mbcico[9173] getnlent: 1:120/640@fidonet system name override with twstdt.synchro.net + 30-Sep-2016 22:23:33 mbcico[9173] getnlent: 1:120/640@fidonet flags override ICM,IBN + 30-Sep-2016 22:23:33 mbcico[9173] Binkp: remote is a listed system + 30-Sep-2016 22:23:33 mbcico[9173] Options: Call WaZOO EMSI Freqs Zmodem ZedZap Hydra PLZ
GZ/BZ2 NoNR CRC + 30-Sep-2016 22:23:33 mbcico[9173] Binkp: MD5
protected session + 30-Sep-2016 22:23:33 mbcico[9173] Binkp: mail 0,
files 780528 bytes + 30-Sep-2016 22:23:33 mbcico[9173] Binkp:
send "/opt/mbse/var/bso/outbound/0000ffa0.wem" as "0000ffa0.wem" + 30-Sep-2016 22:23:33 mbcico[9173] Binkp: size 213434 bytes, dated Sep
28
23:49:52, comp No
+ 30-Sep-2016 22:23:33 mbcico[9173] Binkp: got M_ERR "Encryption
required" + 30-Sep-2016 22:23:33 mbcico[9173] Binkp: receiver failure
+ 30-Sep-2016 22:23:33 mbcico[9173] Binkp: session finished, rc=108 + 30-Sep-2016 22:23:35 mbcico[9173] Incoming call failed (rc=108) + 30-Sep-2016 22:23:35 mbcico[9173] Terminated with error 108

Wonder if that "Encryption required" is a setting on his end?

Apparently. His end is sending an M_ERR frame, which indicates a fatal error. Either his end is setup to require encrypted sessions, or there is some sort of
bug in his software.

Connections to do work if I connect to him, after all...

I'm leaning toward a bug in BinkIT. If he had explicitly enabled an encryption
requirement, you would think it would be required for both inbound and outbound
sessions.

I imagine I will need to setup a test node with BinkIT to be sure.

Andrew

---
* Origin: Bits & Bytes BBS * V.Everything! * 860/503-8857 (1:320/119)