I did get tickit working but am now having another issue with another sbbs node. He is a downlink from me in zone 618. However, tickit is defaulting
all of the outgoing tics from my system to my default zone 1 address.

Tickit on his end sees the zone 1 address in the tic file and gets the
password mis-match error because he does not have (and shouldn't have) my
zone 1 address set up in his sbbsecho.ini file.

How do you tell tickit which zone address to use for each file echo if you
have echos across different zones?

---
þ SLMR 2.1a þ How can I escape this irresistable grasp?
þ Synchronet þ CAPCITY2 * CCO BBS * capcity2.synchro.net

Dumas wrote:

I did get tickit working but am now having another issue with another sbbs node. He is a downlink from me in zone 618. However, tickit is defaulting all of the outgoing tics from my system to my default zone 1 address.

Tickit on his end sees the zone 1 address in the tic file and gets the password mis-match error because he does not have (and shouldn't have) my zone 1 address set up in his sbbsecho.ini file.

How do you tell tickit which zone address to use for each file echo if you have echos across different zones?

Oh yeah, that would be me. I recognize my name anywhere ;)

---
þ Synchronet þ End Of The Line BBS - endofthelinebbs.com

Dumas wrote:

I did get tickit working but am now having another issue with another sbbs node. He is a downlink from me in zone 618. However, tickit is defaulting all of the outgoing tics from my system to my default zone 1 address.

Tickit on his end sees the zone 1 address in the tic file and gets the password mis-match error because he does not have (and shouldn't have) my zone 1 address set up in his sbbsecho.ini file.

How do you tell tickit which zone address to use for each file echo if you have echos across different zones?

Deuce just commited a fix.

You'll want to update your exec directory. Let me know when you've updated
and I'll watch for the next tic file coming down.

Thanks,
Nigel

---
þ Synchronet þ End Of The Line BBS - endofthelinebbs.com

Deuce just commited a fix.

You'll want to update your exec directory. Let me know when you've updated and I'll watch for the next tic file coming down.

thanks, I will try to run an update tonight.

---
þ SLMR 2.1a þ My grubby halo, a vapour trail in the empty air...
þ Synchronet þ CAPCITY2 * CCO BBS * capcity2.synchro.net

Deuce just commited a fix.

You'll want to update your exec directory. Let me know when you've updated and I'll watch for the next tic file coming down.

Updated. Are there any updates, that you know of, that need to be made to any of the config files also?

Thanks.

---
þ Synchronet þ CAPCITY2 * CCO BBS * capcity2.synchro.net

Dumas wrote:

Deuce just commited a fix.

You'll want to update your exec directory. Let me know when you've updated
and I'll watch for the next tic file coming down.

Updated. Are there any updates, that you know of, that need to be made to any
of the config files also?

Nothing was mentioned.

http://cvs.synchro.net/commitlog.ssjs

---
þ Synchronet þ End Of The Line BBS - endofthelinebbs.com

Re: Re: tickit zone mismatching
By: Dumas Walker to Nelgin on Thu Aug 09 2018 06:54 pm

Updated. Are there any updates, that you know of, that need to be made to any of the config files also?

After updating here I tossed an incoming tic and got a password error
so I added @fidonet back to the sending nodes entry in sbbsecho.ini and retossed the tic with exec/jsexec tickit. The file was placed in the directory it should have been but was not imported to the BBS or sent to any links.

Not well tested but that's what I see here at the moment.

Ttyl :-),
Al


... A problem can be found for almost every solution

---
þ Synchronet þ The Rusty MailBox - Penticton, BC Canada

Al wrote:

Re: Re: tickit zone mismatching
By: Dumas Walker to Nelgin on Thu Aug 09 2018 06:54 pm

Updated. Are there any updates, that you know of, that need to be made to
any of the config files also?

After updating here I tossed an incoming tic and got a password error
so I added @fidonet back to the sending nodes entry in sbbsecho.ini and retossed the tic with exec/jsexec tickit. The file was placed in the directory
it should have been but was not imported to the BBS or sent to any links.

Not well tested but that's what I see here at the moment.

I'll forward that on to Deuce.

---
þ Synchronet þ End Of The Line BBS - endofthelinebbs.com

Updated. Are there any updates, that you know of, that need to be made to

y

of the config files also?

Nothing was mentioned.
http://cvs.synchro.net/commitlog.ssjs

Thanks, I looked it up in the echo after I asked and got the same
impression. We will see what happens the next time Andrew or Sean hatch a nodelist or infopack.

---
þ SLMR 2.1a þ Come in Number 51, Your Time Is Up!
þ Synchronet þ CAPCITY2 * CCO BBS * capcity2.synchro.net

Dumas wrote:

Updated. Are there any updates, that you know of, that need to be made to

y

of the config files also?

Nothing was mentioned.
http://cvs.synchro.net/commitlog.ssjs

Thanks, I looked it up in the echo after I asked and got the same impression. We will see what happens the next time Andrew or Sean hatch a nodelist or infopack.

Not successful by the looks of things.

Area MIN_LIST
Origin 618:618/1
Replaces micronet.z15
Magic MIN_LIST
File MICRONET.Z22
Lfile micronet.z22
Size 5949
Desc Micronet Information Network nodelist for Friday, 10 August 2018 (day 222).
Crc 134BA34B
Created by MBSE BBS 1.0.7.6 Copyright (C) 1997-2018 MBSE DevTm
From 1:2320/105
To 618:250/19

---
þ Synchronet þ End Of The Line BBS - endofthelinebbs.com

Not successful by the looks of things.

Hmmm, I am not a tic expert by any means, so this could be a no-no, but I wonder if adding something like this to the tickit.ini file would help:

[MIN_LIST]
Dir=directory
Aka=618:250/1 <== the aka to use in the tic file
Links=618:250/0, [...]

I noticed that deuce said something about not wanting to change
sbbsecho.ini, so something like this might prevent any changes there.


... Direct from the Ministry of Silly Walks
--- MultiMail/??Unknow v0.43
þ Synchronet þ CAPCITY2 * CCO BBS * capcity2.synchro.net

Re: Re: tickit zone mismatching
By: Nelgin to Al on Fri Aug 10 2018 02:55 pm

After updating here I tossed an incoming tic and got a password
error so I added @fidonet back to the sending nodes entry in
sbbsecho.ini and retossed the tic with exec/jsexec tickit. The file
was placed in the directory it should have been but was not
imported to the BBS or sent to any links.

Not well tested but that's what I see here at the moment.

I'll forward that on to Deuce.

It seems to be working here now..

I still see my fido address on the path line but the from address is from the right zone.

It would be a good thing if the path line was written from the other zone as well but I think those tics will pass without any error now.

Ttyl :-),
Al


... It's hard to be serious when you're naked.

---
þ Synchronet þ The Rusty MailBox - Penticton, BC Canada

Re: Re: tickit zone mismatching
By: Al to Nelgin on Fri Aug 17 2018 03:02 pm

It seems to be working here now..

I just got a netmail from one of my links. It seems he got a tic addressed from 1:153/0 instead of 1:153/757.

How do I get tickit to send tic files from 153/757 instead of 153/0? 153/757 is the first node in my AKA list followed by 153/0.

There is a new setting in echocfg called "Local Address (AKA)" that is set to best match and I haven't adjusted it for any nodes. I wonder if I should set that to 1:153/757 and if tickit will read that?

Ttyl :-),
Al


... Junk - stuff we throw away. Stuff - junk we keep.

---
þ Synchronet þ The Rusty MailBox - Penticton, BC Canada

Re: Re: tickit zone mismatching
By: Al to Nelgin on Fri Aug 17 2018 03:41 pm

Re: Re: tickit zone mismatching
By: Al to Nelgin on Fri Aug 17 2018 03:02 pm

It seems to be working here now..

I just got a netmail from one of my links. It seems he got a tic addressed from 1:153/0 instead of 1:153/757.

How do I get tickit to send tic files from 153/757 instead of 153/0? 153/757 is the first node in my AKA list followed by 153/0.

There is a new setting in echocfg called "Local Address (AKA)" that is set to best match and I haven't adjusted it for any nodes. I wonder if I should set that to 1:153/757 and if tickit will read that?

No, Tickit won't (currently at least) use that new setting.

digital man

Synchronet "Real Fact" #30:
The COM I/O routines for Synchronet for DOS were written in ASM by Steve Deppe. Norco, CA WX: 69.0øF, 89.0% humidity, 0 mph S wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: Re: tickit zone mismatching
By: Digital Man to Al on Sat Aug 18 2018 01:38 am

I just got a netmail from one of my links. It seems he got a tic
addressed from 1:153/0 instead of 1:153/757.

No, Tickit won't (currently at least) use that new setting.

OK, I'll leave that setting as is. Here are a few lines from a tic that a link here had trouble with because of the from line.

---- begin ----
File NODEDIFF.A29
Area NODEDIFF
Replaces NODEDIFF.A29
Origin 1:229/426
Size 4675
Crc 68C189A0
From 1:153/0@fidonet
To 1:267/67
Pw
Path 1:229/426@fidonet 1534517074 FRI AUG 17 14:44:34 2018 UTC+0000 53C1F788 Path 1:261/38.0 @180817145002 EDT+5
Path 1:266/404 1534531793 Fri Aug 17 18:49:53 2018 UTC htick/w32-mvcdll 1.9.0-c ur 30-06-15
Path 1:153/757
---- end ----

The path line looks OK. I wonder if tickit could use the same method to get the from line that it uses to get the path line?

Also, the from line has @fidonet attached to it. That is accurate but I wonder if that might be a problem for some nodes when tossing as well?

Ttyl :-),
Al


... Everybody should believe in something - I believe I'll have a beer

---
þ Synchronet þ The Rusty MailBox - Penticton, BC Canada

Re: Re: tickit zone mismatching
By: Al to Digital Man on Sat Aug 18 2018 08:21 pm

Re: Re: tickit zone mismatching
By: Digital Man to Al on Sat Aug 18 2018 01:38 am

I just got a netmail from one of my links. It seems he got a tic
addressed from 1:153/0 instead of 1:153/757.

No, Tickit won't (currently at least) use that new setting.

OK, I'll leave that setting as is. Here are a few lines from a tic that a link here had trouble with because of the from line.

---- begin ----
File NODEDIFF.A29
Area NODEDIFF
Replaces NODEDIFF.A29
Origin 1:229/426
Size 4675
Crc 68C189A0
From 1:153/0@fidonet
To 1:267/67
Pw
Path 1:229/426@fidonet 1534517074 FRI AUG 17 14:44:34 2018 UTC+0000
53C1F788 Path 1:261/38.0 @180817145002 EDT+5
Path 1:266/404 1534531793 Fri Aug 17 18:49:53 2018 UTC htick/w32-mvcdll 1.9.0-c ur 30-06-15
Path 1:153/757
---- end ----

The path line looks OK. I wonder if tickit could use the same method to get the from line that it uses to get the path line?

Also, the from line has @fidonet attached to it. That is accurate but I wonder if that might be a problem for some nodes when tossing as well?

These are all good questions for Deuce in irc.synchro.net. :-)

digital man

Synchronet/BBS Terminology Definition #57:
XON = Transmit On (ASCII 17, Ctrl-Q)
Norco, CA WX: 72.4øF, 76.0% humidity, 0 mph ESE wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net