Subj : Relay6
To   : Björn Felten
From : Kees van Eeten
Date : Tue Nov 25 2014 20:37:04

Hello Björn!

25 Nov 14 20:27, you wrote to Michiel van der Vlist:

 BF>    But I really hate that textfile config concept. How do you manage, for
 BF> instance, when a node changes URL? You can't rely on the nodelist, because
 BF> if you enter the passwords there they'll all be lost with the next
 BF> nodelist. If you have them in the config, you'll have to manually edit any
 BF> changes.

 That is because you do not know the trics.

 In the main config should contain:

include binkp.inc
..
..
..
include binkp.nl


binkp.nl has the nodes with whom you have exchanged passwords
-----
Node 2:280/5006@fidonet    -   [password]
..
..


In the file binkd.nl you write

Node 2:280/5006@fidonet     fido6.ddutch.nl -


The file binkd.nl, with all the url's can be derived from the nodelist.
Some make that file available.

Some prefer to use DNS, you can forget the binkd.nl file

In the config you declare

root-domain binkp.net

In binkd.inc you write

Node 2:280/5006@fidonet  *  [password]

If you want to override, but it in binkd.inc

 BF>    And there's a lot of more things I think could be done much better
 BF> (beside a GUI for the maintenance of course). But yes, it works very well,
 BF> I have no complaints about that -- but Radius is much more powerful and
 BF> magnitudes more easy to manage.

 After it is setup, there is very little to maintain.

 How many simultainous sessions can Argus handle?

Kees

--- FPD v2.9.040207  GoldED+/LNX 1.1.5
 * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)

.