Hello Maxim.

16 Oct 08 11:32, you wrote to me:


 RT>> "config" file appears to be okay, tho ... , except route
 RT>> statement again says to route via Zone 2 ... , should be not just
 RT>> Zone 2 ....

 RT>> Route normal 5:7105/1.0 2:*

 RT>> Should be ...

 MS> ok, no problem - i could take Zone number from yourFTNAddress, first
 MS> digits before symbol:

That would work, yes ...

 RT>> Route normal 5:7105/1.0 1:* 2:* 3:* 4:* 5:*

 RT>> Not to sure about the 5:* on the end, but ....

 MS> could u find out it? I need to know it exactly

If you only have 2:* you are only able to route mail for Zone2 ... , so you 
need to be able to route mail for other Zones, unless you are only 
corresponding to/with persons in Zone 2, what I am not certain about is 
whether your default Zone needs to be specified or not, will try with and 
without and see if "tparser" complains about any one, if no
wisdom is gained 
via that route, I will check what documentation I have here, in this regard 
...

 RT>> Maybe you have a better way to sort this out than a Zone Constant
 RT>> ...

 RT>> Otherwise looks good ...

 MS> if i make modification of unix configurator could u test it and check
 MS> working 'out of box' for zone 5? Here in Russia i have no possabilites
 MS> to test such configuration. or as another variant - could u provide me
 MS> temporary ip-point address to your noda? Then i could test it by
 MS> myself.

I will test what ever changes you make, you do not need to have a working 
connection anywhere, to use other Zone's nodenumbers.

You have no need for a point system for testing, just pick a node number, from 
another Zone, and then examine the config files produced ... , if the correct 
values for that point/node are in the config files produced, then you are 
doing well ...

Just pick a node number at random from outside Zone 2, run the configuration 
and then check that the "problems" I pointed out show the correct
value for 
the Zone you have chosen to use for testing purpose. You need to check the 
values I pointed out to you ...

In BinkD.cfg

domain fidonet /home/fido/outbound 5

This line is correct/valid for nodes in Zone 5,

domain fidonet /home/fido/outbound 1

This line is correct/valid for nodes in Zone 1,

domain fidonet /home/fido/outbound 2

This line is correct/valid for nodes in Zone 2,

That is, the digit at the end of the line, tells BinkD, which Zone it is being 
used in ... , and which outbound is the default outbound for that node ...

In FidoNet, valid values are either  1, 2, 3, 4, or 5 ... , currently ...

Route normal 5:7105/1.0 2:*

This line as it stands, says to route all mail as "normal" versus
"crash" 
"hold" etc. for mail addressed to all nodes in Zone 2 via node 5:7105/1.0.

No routing has been made for Zones 1, 3, 4, or 5 , so it would not be possible 
for this system to route mail to nodes in these Zones, from a node system.

For a point system this may or may not be a problem ... , at this stage, I 
don't know what the situation is for a point ...

Russell

--- GoldED+/LNX 1.1.5