Hello everybody!

Please forgive as I'm more confused the more I read.... which file do I need to
use with binkd to make it call out nodes in the nodelist that I may have netmail for...

Furthermore how to I put it in the binkd.cfg file? Totally lost and confused on this one.

Allen


... Brooklyn is the Dutch name for "broken valley".
--- LiveWire
* Origin: LiveWire BBS -=*=- telnet://livewirebbs.com (1:2320/100)

Hi Allen!

03 Sep 2016 03:25, from Allen Prunty -> All:

Please forgive as I'm more confused the more I read.... which file do
I need to use with binkd to make it call out nodes in the nodelist
that I may have netmail for...

Furthermore how to I put it in the binkd.cfg file? Totally lost and confused on this one.

I thought we already discussed this once ...

You need to convert the nodelist to a format that binkd can use.
I use nl2binkd for that.
Then you include the result in binkd:
include /usr/local/etc/binkd.inc

Then you enter a "-" as the host, and it will take the previous definition that
you included from the nodelist.
I think this is also explained in the default binkd config file.

CU, Ricsi

--- GoldED+/LNX
* Origin: Anyone have any Antivirus spray? (2:310/31)

03 Sep 16 03:25, you wrote to All:

Please forgive as I'm more confused the more I read.... which file do
I need to use with binkd to make it call out nodes in the nodelist
that I may have netmail for...

why are you fiddling with this mess again once you have it working??

in fidonet you simply include binkd.txt from the I-BINKD FDN... othernets may or may not have a distributed binkd contact list... if they do not, you have to
generate one locally and include it...

Furthermore how to I put it in the binkd.cfg file? Totally lost and confused on this one.

at the end of your binkd.cfg file you may have node entries... i keep all my private node entries in a separate file that is easier to update when necessary... i call it myconns.cfg... so with binkd.txt and myconns.cfg, the end of my binkd.cfg looks like

----- snip -----
exec "allfix RP -SRIF *S" *.[Rr][Ee][Qq]
flag mail-in.sem *.[STFWMstfwm][ouaherOUAHER][0-9A-Za-z] *.[pP][kK][tT] ################################################################
# set default node options & include myconns.cfg and binkd.txt # ################################################################
# defnode -4 *
include binkd.txt
include myconns.cfg
#EOF#
----- snip -----

)\/(ark

Always Mount a Scratch Monkey

... Thank you Mother government for looking after us, for we are incapable.
---
* Origin: (1:3634/12.73)

Richard Menedetter wrote to Allen Prunty on Saturday September 03 2016 at 10:42:

Please forgive as I'm more confused the more I read.... which file do
I need to use with binkd to make it call out nodes in the nodelist
that I may have netmail for...

Furthermore how to I put it in the binkd.cfg file? Totally lost and
confused on this one.

I thought we already discussed this once ...

You need to convert the nodelist to a format that binkd can use. I use nl2binkd for that. Then you include the result in binkd: include /usr/local/etc/binkd.inc

That is NOT enough. I also use a nodelist converter, but the result does NOT include passwords.

In my binkd.cfg, I have a line reading:

include \\fido\\bin\\binkd\\binkdnod.txt

I do not use drive letters, as you see, but this works fine on my OS/2 machine.
Note the double backslashes. These are required to produce a single backslash, as binkd was ported from a *nix system.

And binkdnod.txt is the binkd nodelist derived from the current nodelist. It includes entries such as:

Node 1:138/393@fidonet bbs.ezvsn.com -

Note the dash at the end of the line. That's where the password should be. And actually, the line should read:

Node 1:138/393@fidonet bbs.ezvsn.com - -

The final (optional) dash in this case specifies the "flavour" with which messages should be sent. I only rarely use this, since messages are sent "normal" by default and this means binkd will automatically send them as soon as they are in the outbound.

The above line is located BEFORE my private entries in binkd.cfg which include passwqords, since ther LATER entries in binkd.cfg overwrite any earlier entries.

An example of a line at the END of binkd.cfg (with with word "PASSWORD" instead
of the real password) is:

# Fred Riccio
node 1:132/174 asok.dtdns.net PASSWORD -

which corresponds to the entry in binkdnod.txt:

Node 1:132/174@fidonet asok.dtdns.net -

and overwrites that entry with the entry containing the password. The ORDER of the entries is important: later entries always overwrite earlier ones. Sorry to
Fred if using him as an example irritates him, but I haven't included anything that isn't in the nodelist.

If you have NO passworded links, you can naturally use the binkd nodelist derived from the regular nodelist just as it is. Just use the INCLUDE statement
to make sure binkd sees the list.

But make sure you either define links at the END of binkd.cfg OR (if you use no
passwords) use an include file with the binkd nodelist. Otherweise binkd will do nothing at all. It will just sit there, waiting to be told what to do.

One further thing: you start binkd and allow it to run continuously. I start it
(under OS/2) with a CMD file:

binkd.cmd:
/* Call BinkD */

/* define paths for REXX script */

bd='\fido\bin\binkd'

curdir=directory() /* save current directory */

newdir=directory(bd) /* go to binkd directory */
/* binkd '\fido\bin\binkd\binkd.cfg' */
binkd '\fido\bin\binkd\binkd.cfg'

call directory curdir /* return to original directory */

This REXX script works fine under OS/2, and could probably also be used under Windows if you install Regina REXX (freeware: just Google for it), which I also
use when calling REXX functions from a networked Windows computer. Some small modifications are sometimes necessary when converting OS/2 REXX scripts into Regina REXX scripts, but that may not be necessary in your case.

Hopes this helps. Just for the record, I had trouble setting up binkd the first
time, too.

Cheers, Bob

--- GoldED+/W32 1.1.5-0613
* Origin: Jabberwocky System - 02363-56073 ISDN/V34 (2:2448/44)

Hello Robert!

03 Sep 16 13:39, Robert Bashe wrote to Richard Menedetter:

That is NOT enough. I also use a nodelist converter, but the result
does NOT include passwords.

Or you can hook into the I-BINKD file area, and Binkd.Txt will be delivered to your door weekly. No need for a full nodelist unless you run both POTS and BinkP.

An example of a line at the END of binkd.cfg (with with word
"PASSWORD" instead of the real password) is:

# Fred Riccio
node 1:132/174 asok.dtdns.net PASSWORD -

You can get rid of that line. I removed the password from my end when we finished testing that SRIF program.

--- Msged/NT 6.0.1
* Origin: Somewhere in New Hampshire's White Mountains (1:132/174)

Hi Robert!

03 Sep 2016 13:39, from Robert Bashe -> Richard Menedetter:

That is NOT enough.

That is why this part was in the original message:
"Then you enter a "-" as the host, and it will take the previous definition that you included from the nodelist."

CU, Ricsi

--- GoldED+/LNX
* Origin: RAM = Rarely Adequate Memory (2:310/31)

03 Sep 16 13:39, you wrote to Richard Menedetter:

Please forgive as I'm more confused the more I read.... which file
do I need to use with binkd to make it call out nodes in the
nodelist that I may have netmail for...

Furthermore how to I put it in the binkd.cfg file? Totally lost and
confused on this one.

I thought we already discussed this once ...

You need to convert the nodelist to a format that binkd can use. I
use nl2binkd for that. Then you include the result in binkd: include
/usr/local/etc/binkd.inc

That is NOT enough. I also use a nodelist converter, but the result
does NOT include passwords.

it isn't supposed to... it is only to provide a connection line for unsecure connections... if you have a secure connection with a specific system then you add a separate node line for that specific system and you place your password in there... it is called "overriding"... but that's not what was being asked for... what was being asked for was how to include the list of all nodes so that a system may connect with any other system using binkd...

aside from that, your explanation was spot on :)

)\/(ark

Always Mount a Scratch Monkey

... He who hesitates is not only lost but miles from the next exit.
---
* Origin: (1:3634/12.73)

Fred Riccio wrote to Robert Bashe on Saturday September 03 2016 at 09:07:

03 Sep 16 13:39, Robert Bashe wrote to Richard Menedetter:

That is NOT enough. I also use a nodelist converter, but the result
does NOT include passwords.

Or you can hook into the I-BINKD file area, and Binkd.Txt will be
delivered to your door weekly.

Which still does not address the problem of passwords. I explaind this in my message. If you want to communicate with a passworded system, binkd.cfg must have the final lines I mentioned, which include the password. Any binkd nodelists generated on site or downloaded as you mention are only valid for communication with systems not requiring a password.

An example of a line at the END of binkd.cfg (with with word
"PASSWORD" instead of the real password) is:

# Fred Riccio
node 1:132/174 asok.dtdns.net PASSWORD -

You can get rid of that line. I removed the password from my end when
we finished testing that SRIF program.

;-) Actually, the line had no password to begin with. I just used it as an example.

Perhaps I should add the information that I had a "super-GAU" (both motherboard
AND HDD became defective at the same time) a couple of weeks ago, and had to jury rig a replacement based on a backup from April 2014. I've meanwhile adjusted the configuration to work properly, but anything between April 2014 and July 2016 is not necessarily included. So any password we might have agreed
on during the meanwhile has been lost.

Cheers, Bob

--- GoldED+/W32 1.1.5-0613
* Origin: Jabberwocky System - 02363-56073 ISDN/V34 (2:2448/44)

04 Sep 16 09:46, you wrote to Fred Riccio:

Which still does not address the problem of passwords. I explaind this in my message. If you want to communicate with a passworded system, binkd.cfg must have the final lines I mentioned, which include the password. Any binkd nodelists generated on site or downloaded as you mention are only valid for communication with systems not requiring a password.

You can use a separate password file.

=== cut ===
# Format of the password file:
# [password] <FTN address> <inpwd>[,[<pktpwd>][,<outpwd>]]
# where:
# [password] optional "password" token;
# <FTN address> address of a link in the form 1:2/3.4@domain
# or 1:2/3@domain or 1:2/3 or 1:2/3.4;
# <inpwd> password for incoming sessions;
# <pktpwd> packet password, used when "share" token
# is handled;
# <outpwd> password for outgoing sessions.
# Any password is one word without spaces or tabs. If <pktpwd> or <outpwd>
# is omitted, it will be assumed equal to <inpwd>. If a password is defined for # a node by the "node" token, then the passwords for the node in the password
# file will be ignored.
#
passwords ~/ftn/binkd/passwords
=== cut ===

'Tommi

---
* Origin: ====================================== (2:221/1.1)

* Originally from Tommi Koivula to Robert Bashe :

passwords ~/ftn/binkd/passwords

And if you are not sure in which order the included files are interpreted,
you can run binkd -d to check. ;)

'Tommi

--- Concord/2 001B30d (Reg.)
* Origin: - rbb - telnet://rbb.homeip.net - (2:221/360)

Tommi Koivula wrote to Robert Bashe on Sunday September 04 2016 at 12:18:

passwords ~/ftn/binkd/passwords

And if you are not sure in which order the included files are
interpreted, you can run binkd -d to check. ;)

My understanding is that binkd.cfg is read from top (beginning) to bottom (end), and that entries at the bottom overwrite any before them.

So I would assume any include files are read in the same order: the last one listed in binkd.cfg takes prescedence over any include file listed previous to it.

Please correct me if this is not the case.

Cheers, Bob

--- GoldED+/W32 1.1.5-0613
* Origin: Jabberwocky System - 02363-56073 ISDN/V34 (2:2448/44)

Hi Robert.

04 Sep 16 13:28, you wrote to me:

Tommi Koivula wrote to Robert Bashe on Sunday September 04 2016 at 12:18:

passwords ~/ftn/binkd/passwords

And if you are not sure in which order the included files are
interpreted, you can run binkd -d to check. ;)

My understanding is that binkd.cfg is read from top (beginning) to bottom (end), and that entries at the bottom overwrite any before them.

So I would assume any include files are read in the same order: the last one listed in binkd.cfg takes prescedence over any include file listed previous to it.

My understanding was that the later setting will replace the previous setting if it was not set when reading the conf from top to bottom. So that if any of the setting is "-" it may be replaced. Also my understanding was that the password in passwords.lst has the top priority, but I'm not sure anymore.

I made a little test:

=== binkd.cfg: ===
passwords passwords.lst
node 2:2448/44 ip1.localnet pass1 h
node 2:2448/44 ip2.localnet pass2 c
node 2:2448/44 ip3.localnet pass3 i
=== binkd.cfg: ===

=== passwords.lst ===
password 2:2448/44 pass4
=== passwords.lst ===

And the result of 'binkd -d binkd.cfg':

2:2448/44@fidonet ip3.localnet pass1 i - -

Pretty weird...

'Tommi

---
* Origin: ====================================== (2:221/1.1)

Re: Questions about nodelist and Binkd...
By: Robert Bashe to Fred Riccio on Sun Sep 04 2016 09:46:00

;-) Actually, the line had no password to begin with. I just used it as an example.

Perhaps I should add the information that I had a "super-GAU" (both motherboard
AND HDD became defective at the same time) a couple of weeks ago, and had to jury rig a replacement based on a backup from April 2014. I've meanwhile adjusted the configuration to work properly, but anything between April 2014 and July 2016 is not necessarily included. So any password we might have agreed on during the meanwhile has been lost.

I am trying to send you a netmail with the password we had, but the connection is timing out.
--- SBBSecho 3.00-Win32
* Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)

04 Sep 16 09:46, you wrote to Fred Riccio:

That is NOT enough. I also use a nodelist converter, but the result
does NOT include passwords.

Or you can hook into the I-BINKD file area, and Binkd.Txt will be
delivered to your door weekly.

Which still does not address the problem of passwords.

there is no problem with passwords...

I explaind this in my message. If you want to communicate with a passworded system, binkd.cfg must have the final lines I mentioned,
which include the password. Any binkd nodelists generated on site or downloaded as you mention are only valid for communication with
systems not requiring a password.

yes, exactly... that's how it is supposed to be... it is working as per design and implementation :)

)\/(ark

Always Mount a Scratch Monkey

... We don't consider even one life petty. - Riker
---
* Origin: (1:3634/12.73)

Re: Questions about nodelist and Binkd...
By: Joe Delahaye to Robert Bashe on Sun Sep 04 2016 10:06:03

I am trying to send you a netmail with the password we had, but the connection is timing out.

I received the netmail you sent me, however after changing my your entry to what you gave me, and trying to send a reply, I get the following.

getaddrinfo failed: No such host is known (11001)

I checked 3 times to make sure I copied it correctly.
--- SBBSecho 3.00-Win32
* Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)

Tommi Koivula wrote to Robert Bashe on Sunday September 04 2016 at 15:46:

I made a little test:

=== binkd.cfg: ===
passwords passwords.lst
node 2:2448/44 ip1.localnet pass1 h
node 2:2448/44 ip2.localnet pass2 c
node 2:2448/44 ip3.localnet pass3 i
=== binkd.cfg: ===

=== passwords.lst ===
password 2:2448/44 pass4
=== passwords.lst ===

And the result of 'binkd -d binkd.cfg':

2:2448/44@fidonet ip3.localnet pass1 i - -

Pretty weird...

Indeed. I've never run into such things since I enter my "include" file above the final node entries with passwords. Never have used an include file for passwords alone.

Cheers, Bob

--- GoldED+/W32 1.1.5-0613
* Origin: Jabberwocky System - 02363-56073 ISDN/V34 (2:2448/44)

Joe Delahaye wrote to Robert Bashe on Sunday September 04 2016 at 10:06:

I am trying to send you a netmail with the password we had, but the connection is timing out.

I think I have the answer: my subdomain has changed, and is now:

abel.spdns.eu

But my crashmail to you, using your old subdomain (lionsden.darktech.org) and our password, was accepted, whereas I get a password error when I use your new subdomain (lionsden.ddutch.nl) and our ols, original password.

Not sure what's going wrong here.

Cheers, Bob

--- GoldED+/W32 1.1.5-0613
* Origin: Jabberwocky System - 02363-56073 ISDN/V34 (2:2448/44)

Joe Delahaye wrote to Robert Bashe on Sunday September 04 2016 at 11:38:

I am trying to send you a netmail with the password we had, but the
connection is timing out.

I received the netmail you sent me, however after changing my your
entry to what you gave me, and trying to send a reply, I get the
following.

getaddrinfo failed: No such host is known (11001)

I checked 3 times to make sure I copied it correctly.

Whatever you did, it works now. You can send me crashmails, and I can send them
to you. So don't touch anything, and I won't either :-)

Cheers, Bob

--- GoldED+/W32 1.1.5-0613
* Origin: Jabberwocky System - 02363-56073 ISDN/V34 (2:2448/44)

Re: Questions about nodelist and Binkd...
By: Robert Bashe to Joe Delahaye on Sun Sep 04 2016 17:27:46

I am trying to send you a netmail with the password we had, but the
connection is timing out.

I think I have the answer: my subdomain has changed, and is now:

abel.spdns.eu

That is different then the change you sent me in the netmail <G> Have changed it again.

But my crashmail to you, using your old subdomain (lionsden.darktech.org) and our password, was accepted, whereas I get a password error when I use your new subdomain (lionsden.ddutch.nl) and our ols, original password.

Not sure what's going wrong here.

Both should work, as my static IPv4 address has not changed, and is linked to the ddutch.nl address as well.
--- SBBSecho 3.00-Win32
* Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)

Re: Questions about nodelist and Binkd...
By: Robert Bashe to Joe Delahaye on Sun Sep 04 2016 17:52:24

getaddrinfo failed: No such host is known (11001)

I checked 3 times to make sure I copied it correctly.

Whatever you did, it works now. You can send me crashmails, and I can send them
to you. So don't touch anything, and I won't either :-)

Perhaps when you polled me? We shall see what happens now <G>
--- SBBSecho 3.00-Win32
* Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)

Hello mark!

03 Sep 16 05:52, you wrote to me:

why are you fiddling with this mess again once you have it working??

I want to have the capability of sending netmail and etc crash to nodes that I don't have listed in my bink-d config. It's a pain to have to go in and list a
node every time I want to send a crash mail to it. Frontdoor used to do it all
"automagically".

at the end of your binkd.cfg file you may have node entries... i keep
all my private node entries in a separate file that is easier to
update when necessary... i call it myconns.cfg... so with binkd.txt
and myconns.cfg, the end of my binkd.cfg looks like

Now that's an idea I did not know we can do as my binkd.cfg is becoming monsterous.

Always Mount a Scratch Monkey

Thanks for your help and insight it is always appreciate... remember I am recovering from major head trauma... sometimes the most complex things are the simplest things for me and the simplest things are the most complex.

I don't think we touched the inclue files. I get tons of them just wasn't sure
which one to use.

Allen


... Being a pain in the ass is a perogative of the creative mind.
--- LiveWire
* Origin: LiveWire BBS -=*=- telnet://livewirebbs.com (1:2320/100)

Hello Robert!

03 Sep 16 13:39, you wrote to Richard Menedetter:

Hopes this helps. Just for the record, I had trouble setting up binkd
the first time, too.

Cheers, Bob

I'm running windows for now. Cobbling an old system together to instal Linux... toying with ubuntu or one called mint not sure too many flavors. Will
be asking for help on that one too.

So what everyone is saying so far is no matter what I include I am still going to have to enter a line for every node I want to crash mail to :-( no wildcards
here???

Allen


... By my weirdness, you shall know me...
--- LiveWire
* Origin: LiveWire BBS -=*=- telnet://livewirebbs.com (1:2320/100)

Re: Questions about nodelist and Binkd...
By: Allen Prunty to Robert Bashe on Sun Sep 04 2016 15:58:22

So what everyone is saying so far is no matter what I include I am still going to have to enter a line for every node I want to crash mail to :-( no wildcards here???

I think if you have one of the include files, you can crash, even without a PW.
Binkd treats that like the nodelist.
--- SBBSecho 3.00-Win32
* Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)

Allen Prunty wrote to Robert Bashe on Sunday September 04 2016 at 15:58:

So what everyone is saying so far is no matter what I include I am
still going to have to enter a line for every node I want to crash
mail to :-( no wildcards here???

I don't think so. I have a line for every passworded node. But this is not really a big deal. I have maybe 20 nodes in total, and most are only used occasionally. Start with including your normal up- and downlinks, and just add as necessary.

Cheers, Bob

--- GoldED+/W32 1.1.5-0613
* Origin: Jabberwocky System - 02363-56073 ISDN/V34 (2:2448/44)

Joe Delahaye wrote to Allen Prunty on Sunday September 04 2016 at 16:33:

I think if you have one of the include files, you can crash, even
without a PW. Binkd treats that like the nodelist.

As long as no password was agreed on, you can send and receive from any binkd-capable node.

Cheers, Bob

--- GoldED+/W32 1.1.5-0613
* Origin: Jabberwocky System - 02363-56073 ISDN/V34 (2:2448/44)

Hi Allen!

04 Sep 2016 15:58, from Allen Prunty -> Robert Bashe:

So what everyone is saying so far is no matter what I include I am
still going to have to enter a line for every node I want to crash
mail to :-( no wildcards here???

No you don't!
You need a line for each secure (password protected) node.
And you either need to send direct/crash attributes on the nermail, or you need
to advise your tosser to crash netmails generally.

CU, Ricsi

--- GoldED+/LNX
* Origin: Divorce is not an effective deterrent to marriage (2:310/31)

Re: Questions about nodelist and Binkd...
By: Robert Bashe to Joe Delahaye on Mon Sep 05 2016 09:38:00

I think if you have one of the include files, you can crash, even
without a PW. Binkd treats that like the nodelist.

As long as no password was agreed on, you can send and receive from any binkd-capable node.

Yes, but it may end up in the unsecure directory <G>
--- SBBSecho 3.00-Win32
* Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)

05 Sep 16 09:30, you wrote to Robert Bashe:

I think if you have one of the include files, you can crash,
even without a PW. Binkd treats that like the nodelist.

As long as no password was agreed on, you can send and receive
from any binkd-capable node.

Yes, but it may end up in the unsecure directory <G>

Well, thats exactly the place where it should go, and from where every system should process _netmail_. ;)

'Tommi

--- GoldED+/W32-MINGW 1.1.5-b20150715
* Origin: ================================== (2:221/360.8110)

Re: Questions about nodelist and Binkd...
By: Tommi Koivula to Joe Delahaye on Mon Sep 05 2016 17:12:00

Yes, but it may end up in the unsecure directory <G>

Well, thats exactly the place where it should go, and from where every system should process _netmail_. ;)

Only if you set it to Secure. My system processes netmail from the regular inbound. Not much shows up in the insecure area.
--- SBBSecho 3.00-Win32
* Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)