• 1:14/0

    From Wilfred van Velzen@2:280/464 to All on Wed Dec 1 12:12:46 2021
    Hello All,

    I have been trying to connect to 1:14/0 for a couple of days now, and constantly getting this result:

    + 01 Dec 01:15:26 [3848] call to 1:14/0@fidonet
    ? 01 Dec 01:15:27 [3848] called 1:14/0@fidonet, but remote has no such AKA
    + 01 Dec 01:15:27 [3848] done (to 1:14/0@fidonet, failed, S/R: 0/0 (0/0 bytes))

    But last night this behaviour changed:

    + 01 Dec 02:15:29 [10843] call to 1:14/0@fidonet
    ? 01 Dec 02:15:45 [10843] connection to 1:14/0@fidonet failed: Connection refused

    Can anyone confirm this?


    Regards, NPC.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: NPC Station (2:280/464)
  • From Michiel van der Vlist@2:280/5555 to Wilfred van Velzen on Wed Dec 1 12:35:39 2021
    Hello Wilfred,

    On Wednesday December 01 2021 12:12, you wrote to All:

    But last night this behaviour changed:

    + 01 Dec 02:15:29 [10843] call to 1:14/0@fidonet
    ? 01 Dec 02:15:45 [10843] connection to 1:14/0@fidonet failed:
    Connection refused

    Can anyone confirm this?

    + 12:35 [3260] call to 1:14/0@fidonet
    12:35 [3260] trying vintagebbsing.com [66.175.233.147]...
    + 12:35 [3260] bind -- getaddrinfo: Der angegebene Host ist unbekannt. (11001) ? 12:35 [3260] connection to 1:14/0@fidonet failed: {W32 API error
    10061} Connection refused


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: Nodelist Police Station (2:280/5555)
  • From Nodelist Police Commissioner@2:280/464 to Michiel van der Vlist on Wed Dec 1 18:06:04 2021
    Hello Michiel,

    On 2021-12-01 12:35:39, you wrote to me:

    But last night this behaviour changed:

    + 01 Dec 02:15:29 [10843] call to 1:14/0@fidonet
    ? 01 Dec 02:15:45 [10843] connection to 1:14/0@fidonet failed:
    Connection refused

    Can anyone confirm this?

    MvdV> + 12:35 [3260] call to 1:14/0@fidonet
    MvdV> 12:35 [3260] trying vintagebbsing.com [66.175.233.147]...
    MvdV> + 12:35 [3260] bind -- getaddrinfo: Der angegebene Host ist unbekannt.
    MvdV> (11001) ? 12:35 [3260] connection to 1:14/0@fidonet failed: {W32 API error
    MvdV> 10061} Connection refused

    Ok then it's not just me... ;-)


    Regards, NPC.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: NPC Station (2:280/464)
  • From Richard Menedetter@2:310/31 to Wilfred van Velzen on Wed Dec 1 19:27:22 2021
    Hi Wilfred!

    01 Dec 2021 12:12, from Wilfred van Velzen -> All:

    + 01 Dec 02:15:29 [10843] call to 1:14/0@fidonet
    ? 01 Dec 02:15:45 [10843] connection to 1:14/0@fidonet failed:
    Connection refused
    Can anyone confirm this?

    Yes

    CU, Ricsi

    ... 42? - 7 and a half million years and all you can come up with is 42?!
    --- GoldED+/LNX
    * Origin: I work harder than an ugly stripper! (2:310/31)
  • From Tommi Koivula@2:221/360 to Wilfred van Velzen on Thu Dec 2 16:07:24 2021
    Hi Wilfred.

    01 Dec 21 12:12:46, you wrote to All:

    Hello All,

    I have been trying to connect to 1:14/0 for a couple of days now, and constantly getting this result:

    + 01 Dec 01:15:26 [3848] call to 1:14/0@fidonet
    ? 01 Dec 01:15:27 [3848] called 1:14/0@fidonet, but remote has no such AKA + 01 Dec 01:15:27 [3848] done (to 1:14/0@fidonet, failed, S/R: 0/0 (0/0 bytes))

    But last night this behaviour changed:

    + 01 Dec 02:15:29 [10843] call to 1:14/0@fidonet
    ? 01 Dec 02:15:45 [10843] connection to 1:14/0@fidonet failed: Connection refused


    === Cut ===
    16:06 [4300] BEGIN standalone, binkd/1.1a-113/Win64 -p -P 1:14/0 binkd_perl.cfg
    + 16:06 [4300] No Autoloader in perl
    - 16:06 [4300] Nodelist \bbs\nodelist/NODELIST.NDL parsed, 1068 IP-nodes processed (0 sec)
    16:06 [4300] creating a poll for 1:14/0@fidonet (`d' flavour)
    16:06 [4300] clientmgr started
    16:06 [7720] Substituted * to vintagebbsing.com:24554. for 1:14/0@fidonet by nodelist
    + 16:06 [7720] call to 1:14/0@fidonet
    ? 16:06 [7720] 24554.: incorrect port (getaddrinfo: The specified class was not found. )
    ? 16:06 [7720] vintagebbsing.com:24554.: 1: error parsing host list
    16:06 [4300] the queue is empty, quitting...
    === Cut ===

    Nodelist.PL error.. Caused by the incorrect INA flag:

    Region,14,Mid_West_USA,IA_KS_MN_MO_NE_ND_SD,Jon_Justvig,-Unpublished-,300,CM,XX,ITN,IFT,INA:vintagebbsing.com:24554,IBN

    Can anyone confirm this?

    === Cut ===
    + 16:14 [8252] call to 1:14/0@fidonet
    16:14 [8252] trying vintagebbsing.com [47.49.255.14]...
    16:14 [8252] connected
    + 16:14 [8252] outgoing session with vintagebbsing.com:24554 [47.49.255.14]
    - 16:14 [8252] OPT CRAM-MD5-9a8af839b21601c8939828581c4bb0ee
    + 16:14 [8252] Remote requests MD mode
    - 16:14 [8252] SYS Raiders Inc BBS
    - 16:14 [8252] ZYZ Jon Justvig
    - 16:14 [8252] LOC Wichita, KS. USA
    - 16:14 [8252] NDL 115200,TCP,BINKP
    - 16:14 [8252] TIME Thu, 2 Dec 2021 14:13:44 +0000
    - 16:14 [8252] VER binkd/1.1a-99/Linux binkp/1.1
    + 16:14 [8252] addr: 1:298/26@fidonet
    + 16:14 [8252] addr: 316:36/1@whispnet (n/a or busy)
    + 16:14 [8252] addr: 10:5/3@league10 (n/a or busy)
    + 16:14 [8252] addr: 601:100/6@rebelnet (n/a or busy)
    + 16:14 [8252] addr: 701:1/3@fishnet (n/a or busy)
    + 16:14 [8252] addr: 700:100/40@spooknet (n/a or busy)
    + 16:14 [8252] addr: 21:1/154@fsxnet (n/a or busy)
    + 16:14 [8252] addr: 77:1/112@scinet (n/a or busy)
    + 16:14 [8252] addr: 46:1/154@agoranet (n/a or busy)
    + 16:14 [8252] addr: 1337:3/113@tqwnet (n/a or busy)
    + 16:14 [8252] addr: 10:101/19@araknet (n/a or busy)
    + 16:14 [8252] addr: 314:314/205@pinet (n/a or busy)
    + 16:14 [8252] addr: 169:1/164@battlnet (n/a or busy)
    + 16:14 [8252] addr: 57:58/3@gatornet (n/a or busy)
    + 16:14 [8252] addr: 719:509/1@cscnet (n/a or busy)
    + 16:14 [8252] addr: 54:1/9999@sfnet (n/a or busy)
    ? 16:14 [8252] called 1:14/0@fidonet, but remote has no such AKA
    + 16:14 [8252] done (to 1:14/0@fidonet, failed, S/R: 0/0 (0/0 bytes))
    16:14 [8252] session closed, quitting...
    === Cut ===

    Regards, NPC.

    'Tommi

    ---
    * Origin: rbb.fidonet.fi (2:221/360)
  • From Wilfred van Velzen@2:280/464 to Tommi Koivula on Thu Dec 2 17:41:21 2021
    Hello Tommi,

    On 2021-12-02 16:07:24, you wrote to me:

    Nodelist.PL error.. Caused by the incorrect INA flag:

    Region,14,Mid_West_USA,IA_KS_MN_MO_NE_ND_SD,Jon_Justvig,-Unpublished-,300,C
    M,XX,ITN,IFT,INA:vintagebbsing.com:24554,IBN

    I'm using a php script that "compiles" the nodelist for binkd usage. It seems to ignore the port on the INA...

    Can anyone confirm this?

    === Cut ===
    + 16:14 [8252] call to 1:14/0@fidonet
    16:14 [8252] trying vintagebbsing.com [47.49.255.14]...
    16:14 [8252] connected
    + 16:14 [8252] outgoing session with vintagebbsing.com:24554 [47.49.255.14]
    - 16:14 [8252] OPT CRAM-MD5-9a8af839b21601c8939828581c4bb0ee
    + 16:14 [8252] Remote requests MD mode
    - 16:14 [8252] SYS Raiders Inc BBS
    - 16:14 [8252] ZYZ Jon Justvig
    - 16:14 [8252] LOC Wichita, KS. USA
    - 16:14 [8252] NDL 115200,TCP,BINKP
    - 16:14 [8252] TIME Thu, 2 Dec 2021 14:13:44 +0000
    - 16:14 [8252] VER binkd/1.1a-99/Linux binkp/1.1
    + 16:14 [8252] addr: 1:298/26@fidonet
    + 16:14 [8252] addr: 316:36/1@whispnet (n/a or busy)
    + 16:14 [8252] addr: 10:5/3@league10 (n/a or busy)
    + 16:14 [8252] addr: 601:100/6@rebelnet (n/a or busy)
    + 16:14 [8252] addr: 701:1/3@fishnet (n/a or busy)
    + 16:14 [8252] addr: 700:100/40@spooknet (n/a or busy)
    + 16:14 [8252] addr: 21:1/154@fsxnet (n/a or busy)
    + 16:14 [8252] addr: 77:1/112@scinet (n/a or busy)
    + 16:14 [8252] addr: 46:1/154@agoranet (n/a or busy)
    + 16:14 [8252] addr: 1337:3/113@tqwnet (n/a or busy)
    + 16:14 [8252] addr: 10:101/19@araknet (n/a or busy)
    + 16:14 [8252] addr: 314:314/205@pinet (n/a or busy)
    + 16:14 [8252] addr: 169:1/164@battlnet (n/a or busy)
    + 16:14 [8252] addr: 57:58/3@gatornet (n/a or busy)
    + 16:14 [8252] addr: 719:509/1@cscnet (n/a or busy)
    + 16:14 [8252] addr: 54:1/9999@sfnet (n/a or busy)
    ? 16:14 [8252] called 1:14/0@fidonet, but remote has no such AKA
    + 16:14 [8252] done (to 1:14/0@fidonet, failed, S/R: 0/0 (0/0 bytes))
    16:14 [8252] session closed, quitting...
    === Cut ===

    I'm getting the same result now... At least the system is back online... :-(

    Regards, NPC.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: NPC Station (2:280/464)
  • From Andrew Leary@1:320/219 to Wilfred van Velzen on Fri Dec 3 02:23:22 2021
    Hello Wilfred!

    02 Dec 21 17:41, you wrote to Tommi Koivula:

    I'm getting the same result now... At least the system is back
    online... :-(

    I also get a connection, but Jon's system doesn't present the 1:14/0@fidonet AKA.

    Andrew

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)
  • From Wilfred van Velzen@2:280/464 to Andrew Leary on Fri Dec 3 10:36:57 2021
    Hello Andrew,

    On 2021-12-03 02:23:22, you wrote to me:

    I'm getting the same result now... At least the system is back
    online... :-(

    I also get a connection, but Jon's system doesn't present the 1:14/0@fidonet AKA.

    Thanks for checking this, and confirming our results...

    Regards, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: NPC Station (2:280/464)
  • From Tommi Koivula@2:221/1 to Wilfred van Velzen on Fri Dec 17 13:42:28 2021

    Wilfred van Velzen wrote:

    + 01 Dec 02:15:29 [10843] call to 1:14/0@fidonet

    grep vintagebbsing.com NODELIST.351

    Region,14,Mid_West_USA,IA_KS_MN_MO_NE_ND_SD,Jon_Justvig,-Unpublished-,300,CM,XX,ITN,IFT,INA:vintagebbsing.com:24555,IBN
    ,1,Sunflower_Region_14_BBS,Wichita_KS,Jon_Justvig,-Unpublished-,300,CM,XX,ITN,IFT,INA:vintagebbsing.com:24555,IBN
    Host,298,Raiders_Inc_BBS,Wichita_Kansas,Jon_Justvig,-Unpublished-,300,CM,INA:vintagebbsing.com,CM,ITN,IBN
    ,25,Raiders_Inc_BBS,Wichita_Kansas,Jon_Justvig,-Unpublished-,300,CM,INA:vintagebbsing.com,CM,ITN,IBN
    ,26,Sunflower_Region_14_BBS,Wichita_Kansas,Jon_Justvig,-Unpublished-,300,CM,INA:vintagebbsing.com:24555:24555,CM,ITN,IBN
    ,27,Nightfall_Ordain,Wichita_Kansas,Jon_Justvig,-Unpublished-,300,CM,INA:vintagebbsing.com:24556,CM,ITN,IBN
    ,33,ChristNet_HUB,Wichita_KS,Jon_Justvig,-Unpublished-,300,CM,INA:vintagebbsing.com:24557,ITN,IBN

    INA for 1:14/0 still not fixed. Cannot deliver mail. :(

    INA for 1:298/26 looks interesting.

    'Tommi

    --- Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32)
    * Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/1.0)
  • From Nodelist Police Commissioner@2:280/464 to Tommi Koivula on Fri Dec 17 12:58:10 2021
    Hello Tommi,

    On 2021-12-17 13:42:28, you wrote to me:

    + 01 Dec 02:15:29 [10843] call to 1:14/0@fidonet

    grep vintagebbsing.com NODELIST.351

    Region,14,Mid_West_USA,IA_KS_MN_MO_NE_ND_SD,Jon_Justvig,-Unpublished-,300,C
    ...

    INA for 1:14/0 still not fixed. Cannot deliver mail. :(

    Do you want my binkd_nodelister.php script? ;-)

    INA for 1:298/26 looks interesting.

    There were no changes at all in the R14 section this week... :-(


    Regards, NPC.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: NPC Station (2:280/464)
  • From Tommi Koivula@2:221/1 to Nodelist Police Commissioner on Fri Dec 17 14:12:16 2021
    Nodelist Police Commissioner wrote:

    INA for 1:14/0 still not fixed. Cannot deliver mail. :(

    Do you want my binkd_nodelister.php script? ;-)

    It doesn't fix the INA errors in the nodelist... :(

    'Tommi

    ---
    * Origin: rbb.fidonet.fi - Lake Ylo - Finland (2:221/1.0)
  • From Nodelist Police Commissioner@2:280/464 to Tommi Koivula on Fri Dec 17 14:18:02 2021
    Hello Tommi,

    On 2021-12-17 14:12:16, you wrote to me:

    INA for 1:14/0 still not fixed. Cannot deliver mail. :(

    Do you want my binkd_nodelister.php script? ;-)

    It doesn't fix the INA errors in the nodelist... :(

    No but it makes it so, you can still deliver mail...

    Regards, NPC.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: NPC Station (2:280/464)
  • From Michiel van der Vlist@2:280/5555 to Tommi Koivula on Fri Dec 17 16:25:21 2021
    Hello Tommi,

    On Friday December 17 2021 13:42, you wrote to Wilfred van Velzen:

    INA for 1:14/0 still not fixed. Cannot deliver mail. :(

    INA for 1:298/26 looks interesting.

    So it is still a mess....


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: Nodelist Police Station (2:280/5555)
  • From Michiel van der Vlist@2:280/5555 to Nodelist Police Commissioner on Fri Dec 17 16:32:13 2021
    Hello Nodelist,

    On Friday December 17 2021 14:18, you wrote to Tommi Koivula:

    Do you want my binkd_nodelister.php script? ;-)

    It doesn't fix the INA errors in the nodelist... :(

    No but it makes it so, you can still deliver mail...

    That amounts to rewarding bad behaviour. I say it is better to dump the undeliverable mail for R14 into the Z1C's inbound. Thereby droppng the problem on the plate of the one responsible for having an incompetent Z1 RC.


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: Nodelist Police Station (2:280/5555)
  • From Nodelist Police Commissioner@2:280/464 to Michiel van der Vlist on Fri Dec 17 17:09:21 2021
    Hello Michiel,

    On 2021-12-17 16:32:13, you wrote to me:

    Do you want my binkd_nodelister.php script? ;-)

    It doesn't fix the INA errors in the nodelist... :(

    No but it makes it so, you can still deliver mail...

    MvdV> That amounts to rewarding bad behaviour. I say it is better to dump the
    MvdV> undeliverable mail for R14 into the Z1C's inbound. Thereby droppng the
    MvdV> problem on the plate of the one responsible for having an incompetent Z1
    MvdV> RC.

    I have little hope that will help. It won't get noticed that way. It will probably just get delivered when the R14 system polls the Z1 system. Or the Z1 doesn't use the nodelist for polling R14, because he has him setup in his config...

    Regards, NPC.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: NPC Station (2:280/464)
  • From Michiel van der Vlist@2:280/5555 to Nodelist Police Commissioner on Sat Dec 18 11:38:51 2021
    Hello Nodelist,

    On Friday December 17 2021 17:09, you wrote to me:

    MvdV>> That amounts to rewarding bad behaviour. I say it is better to
    MvdV>> dump the undeliverable mail for R14 into the Z1C's inbound.
    MvdV>> Thereby droppng the problem on the plate of the one responsible
    MvdV>> for having an incompetent Z1 RC.

    I have little hope that will help. It won't get noticed that way. It
    will probably just get delivered when the R14 system polls the Z1
    system. Or the Z1 doesn't use the nodelist for polling R14, because he
    has him setup in his config...

    I am afraid you are right. It is unlikely that it will trigger action. It is very unlikely that ZC1 is unaware of the problem and if he were inclined to do something about it, he would have done it long ago.

    OTOH, creating work arounds on the sender side, as you do, is certainly not going the solve the problem.

    How about bouncing the 'undeliverable' mail back to the originator of the message? (With an explanation.)


    Cheers, Michiel

    --- GoldED+/W32-MSVC 1.1.5-b20170303
    * Origin: Nodelist Police Station (2:280/5555)
  • From Nodelist Police Commissioner@2:280/464 to Michiel van der Vlist on Sat Dec 18 12:41:11 2021
    Hello Michiel,

    On 2021-12-18 11:38:51, you wrote to me:

    MvdV>>> That amounts to rewarding bad behaviour. I say it is better to
    MvdV>>> dump the undeliverable mail for R14 into the Z1C's inbound.
    MvdV>>> Thereby droppng the problem on the plate of the one responsible
    MvdV>>> for having an incompetent Z1 RC.

    I have little hope that will help. It won't get noticed that way. It
    will probably just get delivered when the R14 system polls the Z1
    system. Or the Z1 doesn't use the nodelist for polling R14, because he
    has him setup in his config...

    MvdV> I am afraid you are right. It is unlikely that it will trigger action. It
    MvdV> is very unlikely that ZC1 is unaware of the problem and if he were inclined
    MvdV> to do something about it, he would have done it long ago.

    Maybe "Educating and helping other *C's" and being responsible for the complete content of your segment should be added to the job description of any *C...

    Maybe the IC can/should intervene? ;-)

    MvdV> OTOH, creating work arounds on the sender side, as you do, is
    MvdV> certainly not going the solve the problem.

    I think we should separate these things:

    1) The (automatic) reporting on technical nodelist issues should be as strict as possible.
    2) The processing of the nodelist, should be as flexible and auto-correcting as possible.

    I think we need 2 because of the declining knowledge, skills and numbers to keep this network going.

    MvdV> How about bouncing the 'undeliverable' mail back to the originator
    MvdV> of the message? (With an explanation.)

    It's a good thing in general to bounce undeliverable mail, but it's a different matter. Besides this discussion started because some can't crash 1:14/0. Bouncing is more a routing thing...

    What can be done is what we are doing right now, trying to make the responsible people aware of the problems. This can be done in escalating steps. First in private, second in public, repeat until fixed... The private and public steps have already been taken in this case... :-(

    Regards, NPC.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: NPC Station (2:280/464)
  • From Tommi Koivula@2:221/1 to Nodelist Police Commissioner on Sat Dec 18 14:21:46 2021
    On 17.12.2021 15:18, Nodelist Police Commissioner wrote:

    Do you want my binkd_nodelister.php script? ;-)

    It doesn't fix the INA errors in the nodelist... :(

    No but it makes it so, you can still deliver mail...

    Well.. In the nodelist there is:

    CM,XX,ITN,IFT,INA:vintagebbsing.com:24555,IBN

    The good guess is that the port 24555 is for IBN, but as well it could
    be for ITN or IFT. You don't know.

    'Tommi

    --- Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:4.8) Goanna/20210817 Interlink/52.9.7899
    * Origin: nntp://rbb.fidonet.fi - Lake Ylo - Finland (2:221/1.0)
  • From Nodelist Police Commissioner@2:280/464 to Tommi Koivula on Sat Dec 18 13:33:30 2021
    Hello Tommi,

    On 2021-12-18 14:21:46, you wrote to me:

    Do you want my binkd_nodelister.php script? ;-)

    It doesn't fix the INA errors in the nodelist... :(

    No but it makes it so, you can still deliver mail...

    Well.. In the nodelist there is:

    CM,XX,ITN,IFT,INA:vintagebbsing.com:24555,IBN

    The good guess is that the port 24555 is for IBN, but as well it could
    be for ITN or IFT. You don't know.

    Indeed you don't. But the binkd_nodelist "compiler" script doesn't care about the ITN and IFT flags. And it guesses/asumes the port on the INA flag is for IBN. That guess was correct in this case. If it wasn't you still couldn't connect, the same as you coudn't when you would be using the strict interpretation...

    Regards, NPC.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: NPC Station (2:280/464)
  • From Stas Mishchenkov@2:460/5858 to Nodelist Police Commissioner on Fri Jan 28 09:28:58 2022
    Hi, Nodelist!

    17 дек 21 12:58, Nodelist Police Commissioner -> Tommi Koivula:

    Do you want my binkd_nodelister.php script? ;-)

    Or try https://brorabbit.g0x.ru/files/perl/callip.pl

    Have nice nights.
    Stas Mishchenkov.

    --- Мужики, они как куры - двадцать метров от дома и уже ничьи.
    * Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)
  • From Tommi Koivula@2:221/1 to Stas Mishchenkov on Fri Jan 28 09:46:06 2022
    Hi Stas.

    28 Jan 22 09:28, you wrote to Nodelist Police Commissioner:

    Or try https://brorabbit.g0x.ru/files/perl/callip.pl


    === Cut ===

    tommi@pin:/bbs$ ./callip.pl -l /tmp/loki -f 2:460/5858 nodelist/nodelist.ndl You have actual version.
    Parsing nodelist file nodelist/nodelist.ndl

    Nodelist for Friday, January 28, 2022 -- Day number 028 parsed, 1060 IP-nodes processed (0 sec)
    burrow.g0x.ru, 24554
    Calling 2:460/5858 (2001:470:dcd0:0:f1d0:2:460:5858:24554)
    OPT CRAM-MD5-f175869cc2b7f3a74e2f60d1c9d1f9ee
    SYS For_Technical_Perposes
    ZYZ Brother Rabbit
    LOC Simferopol, Crimea.
    NDL MO,CM,IBN,INA:[2001:470:dcd0:1000:f1d0:2:460:5858],INO4
    TIME Fri, 28 Jan 2022 10:45:44 +0300
    VER binkd/1.1a-99/Win64 binkp/1.1
    address: 2:460/5858@fidonet
    TRF 0 0
    OPT EXTCMD GZ BZ2
    2001:470:dcd0:0:f1d0:2:460:5858 - Ok.
    Session with 2:460/5858 done.

    === Cut ===

    'Tommi

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: rbb.fidonet.fi (2:221/1)
  • From Stas Mishchenkov@2:460/5858 to Tommi Koivula on Fri Jan 28 13:03:40 2022
    Hi, Tommi!

    28 янв 22 09:46, Tommi Koivula -> Stas Mishchenkov:

    Or try https://brorabbit.g0x.ru/files/perl/callip.pl


    === Cut ===

    tommi@pin:/bbs$ ./callip.pl -l /tmp/loki -f 2:460/5858 nodelist/nodelist.ndl You have actual version. Parsing nodelist file nodelist/nodelist.ndl

    Nodelist for Friday, January 28, 2022 -- Day number 028 parsed, 1060 IP-nodes processed (0 sec) burrow.g0x.ru, 24554 Calling 2:460/5858 (2001:470:dcd0:0:f1d0:2:460:5858:24554) OPT CRAM-MD5-f175869cc2b7f3a74e2f60d1c9d1f9ee SYS For_Technical_Perposes ZYZ Brother Rabbit LOC Simferopol, Crimea. NDL MO,CM,IBN,INA:[2001:470:dcd0:1000:f1d0:2:460:5858],INO4 TIME Fri, 28 Jan 2022
    10:45:44 +0300 VER binkd/1.1a-99/Win64 binkp/1.1
    address: 2:460/5858@fidonet
    TRF 0 0
    OPT EXTCMD GZ BZ2
    2001:470:dcd0:0:f1d0:2:460:5858 - Ok.
    Session with 2:460/5858 done.

    === Cut ===

    Is it Ok? ;)
    Have you any suggestions?

    Have nice nights.
    Stas Mishchenkov.

    --- Женщины ревнуют, потому что знают, на что способны женщины.
    * Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)
  • From Nodelist Police Commissioner@2:280/464 to Stas Mishchenkov on Fri Jan 28 11:13:19 2022
    Hello Stas,

    On 2022-01-28 13:03:40, you wrote to Tommi Koivula:

    Or try https://brorabbit.g0x.ru/files/perl/callip.pl

    Is it Ok? ;)
    Have you any suggestions?

    Rewrite it in python! ;-)

    Regards, NPC.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: NPC Station (2:280/464)
  • From Nodelist Police Commissioner@2:280/464 to Stas Mishchenkov on Fri Jan 28 13:24:42 2022
    Hello Stas,

    On 2022-01-28 09:28:58, you wrote to me:

    Do you want my binkd_nodelister.php script? ;-)

    Or try https://brorabbit.g0x.ru/files/perl/callip.pl

    I get:

    # ./callip.pl -f 2:280/464 NODELIST.028
    Can't locate Parallel/ForkManager.pm in @INC (you may need to install the Parallel::ForkManager module) (@INC contains: /usr/lib/perl5/site_perl/5.18.2/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.18.2 /usr/lib/perl5/vendor_perl/5.18.2/x86_64-linux-thread-multi /usr/lib/perl5/vendor_perl/5.18.2 /usr/lib/perl5/5.18.2/x86_64-linux-thread-multi /usr/lib/perl5/5.18.2 /usr/lib/perl5/site_perl .) at ../bin/callip.pl line 6.
    BEGIN failed--compilation aborted at ../bin/callip.pl line 6.

    And I can't find a package for my linux distribution that supplies: Parallel::ForkManager :-(


    Regards, NPC.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: NPC Station (2:280/464)
  • From Stas Mishchenkov@2:460/5858 to Nodelist Police Commissioner on Fri Jan 28 15:50:28 2022

    *** Ответ на сообщение из _Carbon.Mail (Carbon.Mail).

    Hi, Nodelist!

    28 янв 22 11:13, Nodelist Police Commissioner -> Stas Mishchenkov:

    Or try https://brorabbit.g0x.ru/files/perl/callip.pl

    Is it Ok? ;)
    Have you any suggestions?

    Rewrite it in python! ;-)

    What for? It works well as well. ;)

    Have nice nights.
    Stas Mishchenkov.

    --- Мне бесполезно что-либо запрещать, я и так не собираюсь ничего делать.
    * Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)
  • From Stas Mishchenkov@2:460/5858 to Nodelist Police Commissioner on Fri Jan 28 15:54:34 2022

    *** Ответ на сообщение из _Carbon.Mail (Carbon.Mail).

    Hi, Nodelist!

    28 янв 22 13:24, Nodelist Police Commissioner -> Stas Mishchenkov:

    Do you want my binkd_nodelister.php script? ;-)

    Or try https://brorabbit.g0x.ru/files/perl/callip.pl

    I get:

    # ./callip.pl -f 2:280/464 NODELIST.028
    Can't locate Parallel/ForkManager.pm in @INC (you may need to install the Parallel::ForkManager module) (@INC contains:

    [...skipped...]

    And I can't find a package for my linux distribution that supplies: Parallel::ForkManager :-(

    Did you try the command "cpan Parallel::ForkManager"?

    https://metacpan.org/pod/Parallel::ForkManager https://cpan.metacpan.org/authors/id/Y/YA/YANICK/Parallel-ForkManager-2.02.tar. gz

    Have nice nights.
    Stas Mishchenkov.

    --- Мне бесполезно что-либо запрещать, я и так не собираюсь ничего делать.
    * Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)
  • From Nodelist Police Commissioner@2:280/464 to Stas Mishchenkov on Fri Jan 28 14:05:39 2022
    Hello Stas,

    On 2022-01-28 15:54:34, you wrote to me:

    Do you want my binkd_nodelister.php script? ;-)

    Or try https://brorabbit.g0x.ru/files/perl/callip.pl

    I get:

    # ./callip.pl -f 2:280/464 NODELIST.028
    Can't locate Parallel/ForkManager.pm in @INC (you may need to install
    the
    Parallel::ForkManager module) (@INC contains:

    [...skipped...]

    And I can't find a package for my linux distribution that supplies:
    Parallel::ForkManager :-(

    Did you try the command "cpan Parallel::ForkManager"?

    I have no clue how these things work in perl! ;-)

    But this seems to do something, and I had to repeat it for: Time::TZOffset

    Now:

    # ./callip.pl -f 2:280/464 NODELIST.028
    You have actual version.
    Parsing nodelist file NODELIST.028

    Nodelist for Friday, January 28, 2022 -- Day number 028 parsed, 1060 IP-nodes processed (0 sec)
    fido.vlzn.nl, 24554
    Calling 2:280/464 (2001:981:8a54:1:f1d0:2:280:464:24554)
    OPT CRAM-MD5-67f4e1097f9bc8323358005a9e9306ee
    SYS FMail dev HQ, FKA Amiga O(n|ff)line BBS Lisse (AOBL)
    ZYZ Wilfred van Velzen
    LOC Lisse, Netherlands
    NDL CM,MO,IBN,PING,TRACE,ENC
    TIME Fri, 28 Jan 2022 14:04:50 +0100
    VER binkd/1.1a-113/Linux binkp/1.1
    address: 2:280/464@fidonet
    address: 39:39/0@AmigaNet
    OPT EXTCMD GZ BZ2
    2001:981:8a54:1:f1d0:2:280:464 - Ok.
    Session with 2:280/464 done.
    Calling 2:280/464 (80.101.186.126:24554)
    OPT CRAM-MD5-79bc32f768c15eb6123fcdb4222437ee
    SYS FMail dev HQ, FKA Amiga O(n|ff)line BBS Lisse (AOBL)
    ZYZ Wilfred van Velzen
    LOC Lisse, Netherlands
    NDL CM,MO,IBN,PING,TRACE,ENC
    TIME Fri, 28 Jan 2022 14:04:50 +0100
    VER binkd/1.1a-113/Linux binkp/1.1
    address: 2:280/464@fidonet
    address: 39:39/0@AmigaNet
    OPT EXTCMD GZ BZ2
    80.101.186.126 - Ok.
    Session with 2:280/464 done.

    And in my binkd.log:

    + 28 Jan 14:04:50 [29080] incoming session with 2001:981:8a54:1:f1d0:2:280:464 - 28 Jan 14:04:50 [29080] SYS linux
    - 28 Jan 14:04:50 [29080] ZYZ Evil Robot
    - 28 Jan 14:04:50 [29080] LOC Sinferopol, Crimea
    - 28 Jan 14:04:50 [29080] NDL 300 MO
    - 28 Jan 14:04:50 [29080] TIME Fri Jan 28 14:04:50 2022 0100
    - 28 Jan 14:04:50 [29080] VER Call_Robot/v.0.4/linux binkp/1.0
    + 28 Jan 14:04:50 [29080] addr: 2:9999/9999.9999@fidonet
    - 28 Jan 14:04:50 [29080] TRF 0 0
    + 28 Jan 14:04:50 [29080] Remote has 0b of mail and 0b of files for us
    + 28 Jan 14:04:50 [29080] done (from 2:9999/9999.9999@fidonet, OK, S/R: 0/0 (0/0 bytes))
    28 Jan 14:04:50 [29080] session closed, quitting...

    + 28 Jan 14:04:50 [29081] incoming session with vlzn.xs4all.nl [80.101.186.126] - 28 Jan 14:04:50 [29081] SYS linux
    - 28 Jan 14:04:50 [29081] ZYZ Evil Robot
    - 28 Jan 14:04:50 [29081] LOC Sinferopol, Crimea
    - 28 Jan 14:04:50 [29081] NDL 300 MO
    - 28 Jan 14:04:50 [29081] TIME Fri Jan 28 14:04:50 2022 0100
    - 28 Jan 14:04:50 [29081] VER Call_Robot/v.0.4/linux binkp/1.0
    + 28 Jan 14:04:50 [29081] addr: 2:9999/9999.9999@fidonet
    - 28 Jan 14:04:50 [29081] TRF 0 0
    + 28 Jan 14:04:50 [29081] Remote has 0b of mail and 0b of files for us
    + 28 Jan 14:04:50 [29081] done (from 2:9999/9999.9999@fidonet, OK, S/R: 0/0 (0/0 bytes))
    28 Jan 14:04:50 [29081] session closed, quitting...

    Succes! :-)


    Regards, NPC.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: NPC Station (2:280/464)
  • From Nodelist Police Commissioner@2:280/464 to Stas Mishchenkov on Fri Jan 28 14:29:20 2022
    Hello Stas,

    On 2022-01-28 14:05:39, I wrote to you:

    Or try https://brorabbit.g0x.ru/files/perl/callip.pl

    I did some testing in AmigaNet, the log is a bit confusing:

    For instance when I tested a net:

    2022-01-28 14:16:17 Calling 39:170/0
    2022-01-28 14:16:17 datenbahn.dd-dns.de:24554
    2022-01-28 14:16:17 31.19.183.44 - Error Connection timed out
    2022-01-28 14:16:17No such AKA.
    2022-01-28 14:16:17
    2022-01-28 14:16:17 Calling 39:170/5834
    2022-01-28 14:16:17 datenbahn.dd-dns.de:24554
    2022-01-28 14:16:17No such AKA.
    2022-01-28 14:16:17 31.19.183.44 - Error Connection timed out

    Sometimes when there is a "connection timed out", there is also a "No such AKA", but not for all the timeouts? And why is the order for the 2 nodes different?
    Also there should be a space character before 'No such AKA.".

    What I would like is milliseconds in the log. ;)
    And also the system and sysop name, for the tested systems. Or maybe even what is reported back in the SYS and ZYZ fields.


    Regards, NPC.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: NPC Station (2:280/464)
  • From Stas Mishchenkov@2:460/5858 to Nodelist Police Commissioner on Fri Jan 28 19:13:58 2022

    *** Ответ на сообщение из _Carbon.Mail (Carbon.Mail).

    Hi, Nodelist!

    28 янв 22 14:05, Nodelist Police Commissioner -> Stas Mishchenkov:

    And I can't find a package for my linux distribution that supplies:
    Parallel::ForkManager :-(

    Did you try the command "cpan Parallel::ForkManager"?

    I have no clue how these things work in perl! ;-)

    This is the standard way to install the required perl modules for any operating system.

    But this seems to do something, and I had to repeat it for: Time::TZOffset

    Good.

    Now:

    # ./callip.pl -f 2:280/464 NODELIST.028
    You have actual version.

    Pay attention. This script is equipped with an automatic update system, leaving the decision to apply updates to the sysop.

    -u,--update - Automatic update. Optional. By default, it
    checks for a new version and downloads the
    update to a new file.

    Calling 2:280/464 (2001:981:8a54:1:f1d0:2:280:464:24554)

    [...skipped...]

    2001:981:8a54:1:f1d0:2:280:464 - Ok.
    Session with 2:280/464 done.
    Calling 2:280/464 (80.101.186.126:24554)

    [...skipped...]

    80.101.186.126 - Ok.
    Session with 2:280/464 done.

    All known IP addresses for the specified node are checked.

    And in my binkd.log:

    [...skipped...]

    Succes! :-)

    I'm glad. I hope this script will be useful for you.

    Have nice nights.
    Stas Mishchenkov.

    --- Мне бесполезно что-либо запрещать, я и так не собираюсь ничего делать.
    * Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)
  • From Nodelist Police Commissioner@2:280/464 to Stas Mishchenkov on Fri Jan 28 17:18:29 2022
    Hello Stas,

    On 2022-01-28 19:13:58, you wrote to me:

    # ./callip.pl -f 2:280/464 NODELIST.028
    You have actual version.

    Pay attention. This script is equipped with an automatic update system, leaving the decision to apply updates to the sysop.

    Yes, I noticed...

    2001:981:8a54:1:f1d0:2:280:464 - Ok.
    Session with 2:280/464 done.
    Calling 2:280/464 (80.101.186.126:24554)

    [...skipped...]

    80.101.186.126 - Ok.
    Session with 2:280/464 done.

    All known IP addresses for the specified node are checked.

    That's good: Check everything!

    Succes! :-)

    I'm glad. I hope this script will be useful for you.

    Maybe/probably. It's definitly usefull when you want to check a complete net for instance! But the loging can be improved (See my other mail)...

    Regards, NPC.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: NPC Station (2:280/464)
  • From Tommi Koivula@2:221/1 to Stas Mishchenkov on Fri Jan 28 22:32:30 2022

    28 Jan 22 13:03, Stas Mishchenkov wrote to Tommi Koivula:

    Hi, Tommi!

    28 ??? 22 09:46, Tommi Koivula -> Stas Mishchenkov:

    Or try https://brorabbit.g0x.ru/files/perl/callip.pl


    === Cut ===

    tommi@pin:/bbs$ ./callip.pl -l /tmp/loki -f 2:460/5858
    nodelist/nodelist.ndl You have actual version. Parsing nodelist
    file nodelist/nodelist.ndl

    Nodelist for Friday, January 28, 2022 -- Day number 028 parsed,
    1060 IP-nodes processed (0 sec) burrow.g0x.ru, 24554 Calling
    2:460/5858 (2001:470:dcd0:0:f1d0:2:460:5858:24554) OPT
    CRAM-MD5-f175869cc2b7f3a74e2f60d1c9d1f9ee SYS
    For_Technical_Perposes ZYZ Brother Rabbit LOC Simferopol, Crimea.
    NDL MO,CM,IBN,INA:[2001:470:dcd0:1000:f1d0:2:460:5858],INO4 TIME
    Fri, 28 Jan 2022
    10:45:44 +0300 VER binkd/1.1a-99/Win64 binkp/1.1
    address: 2:460/5858@fidonet
    TRF 0 0
    OPT EXTCMD GZ BZ2
    2001:470:dcd0:0:f1d0:2:460:5858 - Ok.
    Session with 2:460/5858 done.

    === Cut ===

    Is it Ok? ;)

    It is Ok. :)

    Have you any suggestions?

    No.

    'Tommi

    ---
    * Origin: =========================>>>> (2:221/1)
  • From Stas Mishchenkov@2:460/5858 to Nodelist Police Commissioner on Sat Jan 29 12:02:08 2022
    Hi, Nodelist!

    28 янв 22 14:29, Nodelist Police Commissioner -> Stas Mishchenkov:

    Or try https://brorabbit.g0x.ru/files/perl/callip.pl

    I did some testing in AmigaNet, the log is a bit confusing:

    For instance when I tested a net:

    2022-01-28 14:16:17 Calling 39:170/0
    2022-01-28 14:16:17 datenbahn.dd-dns.de:24554
    2022-01-28 14:16:17 31.19.183.44 - Error Connection timed out
    2022-01-28 14:16:17No such AKA.
    2022-01-28 14:16:17
    2022-01-28 14:16:17 Calling 39:170/5834
    2022-01-28 14:16:17 datenbahn.dd-dns.de:24554
    2022-01-28 14:16:17No such AKA.
    2022-01-28 14:16:17 31.19.183.44 - Error Connection timed out

    Sometimes when there is a "connection timed out", there is also a "No such AKA", but not for all the timeouts?

    That's why:
    [fido@brorabbit bin]$ host datenbahn.dd-dns.de
    datenbahn.dd-dns.de has address 31.17.199.89
    datenbahn.dd-dns.de has address 31.19.183.44

    And why is the order for the 2 nodes different?

    That's why:
    [fido@brorabbit bin]$ host datenbahn.dd-dns.de
    datenbahn.dd-dns.de has address 31.17.199.89
    datenbahn.dd-dns.de has address 31.19.183.44
    [fido@brorabbit bin]$ host datenbahn.dd-dns.de
    datenbahn.dd-dns.de has address 31.19.183.44
    datenbahn.dd-dns.de has address 31.17.199.89
    [fido@brorabbit bin]$ host datenbahn.dd-dns.de
    datenbahn.dd-dns.de has address 31.17.199.89
    datenbahn.dd-dns.de has address 31.19.183.44
    [fido@brorabbit bin]$ host datenbahn.dd-dns.de
    datenbahn.dd-dns.de has address 31.19.183.44
    datenbahn.dd-dns.de has address 31.17.199.89

    Also there should be a space character before 'No such AKA.".

    I'll try to fix it.

    What I would like is milliseconds in the log. ;)

    I will made it, but it doesn't make much sense. The script is multi-threaded and each session writes the entire result to the log at once, and not in stages, like mailers.

    And also the system and sysop name, for the tested systems. Or maybe
    even what is reported back in the SYS and ZYZ fields.

    I will made it.

    Have nice nights.
    Stas Mishchenkov.

    --- На кашу в голове хорошо бегут тараканы.
    * Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)
  • From Stas Mishchenkov@2:460/5858 to Nodelist Police Commissioner on Sat Jan 29 12:28:10 2022
    Hi, Nodelist!

    28 янв 22 17:18, Nodelist Police Commissioner -> Stas Mishchenkov:

    That's good: Check everything!

    Yes!

    [fido@brorabbit ip]$ cat ./1042.log
    2022-01-29 12:26:35.151 Nodelist for Saturday, January 29, 2022 -- Day number 029 parsed, 1060 IP-nodes processed (0 sec)
    2022-01-29 12:26:37.136 Calling 2:5020/1042
    2022-01-29 12:26:37.136 f1042.ru:24554
    2022-01-29 12:26:37.136 (2a00:6d41:10:1987:f1d0:2:5020:1042:24554) 2022-01-29 12:26:37.136 OPT CRAM-MD5-8d8eabc6e3f6831bb8c052153c167bee 2022-01-29 12:26:37.136 SYS f1042.ru
    2022-01-29 12:26:37.136 ZYZ Michael Dukelsky, node@f1042.ru
    2022-01-29 12:26:37.136 LOC Moscow, Russia
    2022-01-29 12:26:37.136 NDL 1Gbit,TCP,BINKP
    2022-01-29 12:26:37.136 TIME Sat, 29 Jan 2022 12:26:35 +0300
    2022-01-29 12:26:37.136 VER binkd/1.1a-112/Linux binkp/1.1
    2022-01-29 12:26:37.136 OPT EXTCMD GZ BZ2
    2022-01-29 12:26:37.136 2a00:6d41:10:1987:f1d0:2:5020:1042 - Ok.
    2022-01-29 12:26:37.136 Session with 2:5020/1042 done.
    2022-01-29 12:26:37.136 (89.46.79.135:24554)
    2022-01-29 12:26:37.136 OPT CRAM-MD5-b1e3a5d460e4cb9a376fa14438ee6fee 2022-01-29 12:26:37.136 SYS f1042.ru
    2022-01-29 12:26:37.136 ZYZ Michael Dukelsky, node@f1042.ru
    2022-01-29 12:26:37.136 LOC Moscow, Russia
    2022-01-29 12:26:37.136 NDL 1Gbit,TCP,BINKP
    2022-01-29 12:26:37.136 TIME Sat, 29 Jan 2022 12:26:35 +0300
    2022-01-29 12:26:37.136 VER binkd/1.1a-112/Linux binkp/1.1
    2022-01-29 12:26:37.136 OPT EXTCMD GZ BZ2
    2022-01-29 12:26:37.136 89.46.79.135 - Ok.
    2022-01-29 12:26:37.136 Session with 2:5020/1042 done.
    2022-01-29 12:26:37.136 fido.delin.ru:24554
    2022-01-29 12:26:37.136 (2a00:6d41:10:1987:f1d0:2:5020:1042:24554) 2022-01-29 12:26:37.136 OPT CRAM-MD5-1a93053cfe647fd06dc33bc40fb583ee 2022-01-29 12:26:37.136 SYS f1042.ru
    2022-01-29 12:26:37.136 ZYZ Michael Dukelsky, node@f1042.ru
    2022-01-29 12:26:37.136 LOC Moscow, Russia
    2022-01-29 12:26:37.136 NDL 1Gbit,TCP,BINKP
    2022-01-29 12:26:37.136 TIME Sat, 29 Jan 2022 12:26:35 +0300
    2022-01-29 12:26:37.136 VER binkd/1.1a-112/Linux binkp/1.1
    2022-01-29 12:26:37.136 OPT EXTCMD GZ BZ2
    2022-01-29 12:26:37.136 2a00:6d41:10:1987:f1d0:2:5020:1042 - Ok.
    2022-01-29 12:26:37.136 Session with 2:5020/1042 done.
    2022-01-29 12:26:37.136 (89.46.79.135:24554)
    2022-01-29 12:26:37.136 OPT CRAM-MD5-fab4fdb4cbf1e3668f1bfa277af5e3ee 2022-01-29 12:26:37.136 SYS f1042.ru
    2022-01-29 12:26:37.136 ZYZ Michael Dukelsky, node@f1042.ru
    2022-01-29 12:26:37.136 LOC Moscow, Russia
    2022-01-29 12:26:37.136 NDL 1Gbit,TCP,BINKP
    2022-01-29 12:26:37.136 TIME Sat, 29 Jan 2022 12:26:36 +0300
    2022-01-29 12:26:37.136 VER binkd/1.1a-112/Linux binkp/1.1
    2022-01-29 12:26:37.136 OPT EXTCMD GZ BZ2
    2022-01-29 12:26:37.136 89.46.79.135 - Ok.
    2022-01-29 12:26:37.136 Session with 2:5020/1042 done.
    2022-01-29 12:26:37.136 f1042.n5020.z2.binkp.net:24554
    2022-01-29 12:26:37.136 (89.46.79.135:24554)
    2022-01-29 12:26:37.136 OPT CRAM-MD5-e774b3c0e99f013335e7f783b2d8c6ee 2022-01-29 12:26:37.136 SYS f1042.ru
    2022-01-29 12:26:37.136 ZYZ Michael Dukelsky, node@f1042.ru
    2022-01-29 12:26:37.136 LOC Moscow, Russia
    2022-01-29 12:26:37.136 NDL 1Gbit,TCP,BINKP
    2022-01-29 12:26:37.136 TIME Sat, 29 Jan 2022 12:26:36 +0300
    2022-01-29 12:26:37.136 VER binkd/1.1a-112/Linux binkp/1.1
    2022-01-29 12:26:37.136 OPT EXTCMD GZ BZ2
    2022-01-29 12:26:37.136 89.46.79.135 - Ok.
    2022-01-29 12:26:37.136 Session with 2:5020/1042 done.
    2022-01-29 12:26:37.136

    Succes! :-)

    I'm glad. I hope this script will be useful for you.

    Maybe/probably. It's definitly usefull when you want to check a complete net for instance!

    Yes.

    [fido@brorabbit ip]$ ./callip.pl Usage: ./callip.pl [options] nodelist_file_name
    ~~~~~
    -l,--log log_file_name - file name of log file
    -f,--fnode address - address of node to call. Optional.
    -z,--zone number - number of zone to test all nodes. Optional. ----------------------------------------------------^^^^^^^^^^^^^^^
    -r,--region number - number of region to test all nodes. Optional. ------------------------------------------------------^^^^^^^^^^^^^^^
    -n,--net network - number of network to test all nodes, -------------------------------------------------------^^^^^^^^^^^^^^^
    i.e. 460. Optional.

    If you do not specify anything, then the check will pass through the entire nodelist.

    But the loging can be improved (See my other mail)...

    I'll try.

    Have nice nights.
    Stas Mishchenkov.

    --- Людeй, пeрeживших лeто в Симферополе, будут выгoнять из ада за смeх в кoтле
    * Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)
  • From Nodelist Police Commissioner@2:280/464 to Stas Mishchenkov on Sat Jan 29 12:20:40 2022
    Hello Stas,

    On 2022-01-29 12:02:08, you wrote to me:

    For instance when I tested a net:

    2022-01-28 14:16:17 Calling 39:170/0
    2022-01-28 14:16:17 datenbahn.dd-dns.de:24554
    2022-01-28 14:16:17 31.19.183.44 - Error Connection timed out
    2022-01-28 14:16:17No such AKA.
    2022-01-28 14:16:17
    2022-01-28 14:16:17 Calling 39:170/5834
    2022-01-28 14:16:17 datenbahn.dd-dns.de:24554
    2022-01-28 14:16:17No such AKA.
    2022-01-28 14:16:17 31.19.183.44 - Error Connection timed out

    Sometimes when there is a "connection timed out", there is also a "No
    such AKA", but not for all the timeouts?

    That's why:
    [fido@brorabbit bin]$ host datenbahn.dd-dns.de
    datenbahn.dd-dns.de has address 31.17.199.89
    datenbahn.dd-dns.de has address 31.19.183.44

    Ok, understood. But it should be made more clear in the logs.

    What I would like is milliseconds in the log. ;)

    I will made it,

    Thanks! ;)

    but it doesn't make much sense.

    Sometimes it is usefull information.

    The script is multi-threaded and each session writes the entire result
    to the log at once, and not in stages, like mailers.

    But it could still be possible that they get mixed up, when two threads start writing at exactly the same time? If so maybe you start each logline with the nodenumber?

    And also the system and sysop name, for the tested systems. Or maybe
    even what is reported back in the SYS and ZYZ fields.

    I will made it.

    Thanks!

    Regards, NPC.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: NPC Station (2:280/464)
  • From Nodelist Police Commissioner@2:280/464 to Stas Mishchenkov on Sat Jan 29 12:32:33 2022
    Hello Stas,

    On 2022-01-28 19:13:58, you wrote to me:

    # ./callip.pl -f 2:280/464 NODELIST.028
    You have actual version.

    Pay attention. This script is equipped with an automatic update system, leaving the decision to apply updates to the sysop.

    -u,--update - Automatic update. Optional. By default, it
    checks for a new version and downloads the
    update to a new file.

    # callip -u -f 2:460/5858 -a 2:280/464 NODELIST.028
    callip.pl will be updated to v.0.5!
    /usr/local/sbin/callip.pl saved.

    This didn't work for me, because /usr/local/sbin/callip is a symlink to /home/fido/bin/callip.pl on my system... :-/ ;-)


    Btw: If you use '-a node' maybe the script could use the values from the nodelist for the SYS, ZYZ, and LOC info sent? Now it still says:

    - 29 Jan 12:28:15 [17842] SYS linux
    - 29 Jan 12:28:15 [17842] ZYZ Evil Robot
    - 29 Jan 12:28:15 [17842] LOC Sinferopol, Crimea

    Or maybe these values could be given on the command line too? Like: -a 2:280/464,system,sysop,location

    Regards, NPC.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: NPC Station (2:280/464)
  • From Stas Mishchenkov@2:460/5858 to Nodelist Police Commissioner on Wed Feb 2 10:04:54 2022
    Hi, Nodelist!

    29 янв 22 12:32, Nodelist Police Commissioner -> Stas Mishchenkov:

    # callip -u -f 2:460/5858 -a 2:280/464 NODELIST.028
    callip.pl will be updated to v.0.5!
    /usr/local/sbin/callip.pl saved.

    This didn't work for me, because /usr/local/sbin/callip is a symlink to /home/fido/bin/callip.pl on my system... :-/ ;-)

    Fixed.

    Btw: If you use '-a node' maybe the script could use the values from the nodelist for the SYS, ZYZ, and LOC info sent? Now it still says:

    - 29 Jan 12:28:15 [17842] SYS linux
    - 29 Jan 12:28:15 [17842] ZYZ Evil Robot
    - 29 Jan 12:28:15 [17842] LOC Sinferopol, Crimea

    Or maybe these values could be given on the command line too? Like: -a 2:280/464,system,sysop,location

    It turns out too much to write on the command line. I did better - an optional config file. This greatly shortens the command line.
    Try new version, please.

    Have nice nights.
    Stas Mishchenkov.

    --- Слабые люди мстят. Сильные люди прощают. Умные люди игнорируют.
    * Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)
  • From Nodelist Police Commissioner@2:280/464 to Stas Mishchenkov on Wed Feb 2 13:16:31 2022
    Hello Stas,

    On 2022-02-02 10:04:54, you wrote to me:

    # callip -u -f 2:460/5858 -a 2:280/464 NODELIST.028
    callip.pl will be updated to v.0.5!
    /usr/local/sbin/callip.pl saved.

    This didn't work for me, because /usr/local/sbin/callip is a symlink
    to /home/fido/bin/callip.pl on my system... :-/ ;-)

    Fixed.

    I've had some time to think about this. I don't like the fact it "calls home" on every invocation! It shouldn't act like spyware where the user has no control over it. Maybe you could replace it with an option like for instance youtube-dl has:

    -U, --update Update this program to latest version. Make sure that you have sufficient permissions (run with sudo if needed)

    Which can be used on it's own, without doing anything else. And only checks for updates when this option is specificly used!

    Btw: If you use '-a node' maybe the script could use the values from
    the nodelist for the SYS, ZYZ, and LOC info sent? Now it still says:

    - 29 Jan 12:28:15 [17842] SYS linux
    - 29 Jan 12:28:15 [17842] ZYZ Evil Robot
    - 29 Jan 12:28:15 [17842] LOC Sinferopol, Crimea

    Btw: Does the binkp protocol require that you send these, or can a valid connection be made without them?

    Or maybe these values could be given on the command line too? Like:
    -a 2:280/464,system,sysop,location

    It turns out too much to write on the command line. I did better - an optional config file. This greatly shortens the command line. Try new version, please.

    I was already thinking in the same direction for a future update! ;-)

    Regards, NPC.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: NPC Station (2:280/464)
  • From Stas Mishchenkov@2:460/5858 to Nodelist Police Commissioner on Fri Feb 4 20:44:36 2022
    Hi, Nodelist!

    02 фев 22 13:16, Nodelist Police Commissioner -> Stas Mishchenkov:

    I've had some time to think about this. I don't like the fact it
    "calls home" on every invocation! It shouldn't act like spyware where
    the user has no control over it.

    How can we talk about spyware in case of open source? ;)

    Maybe you could replace it with an option like for instance
    youtube-dl has:

    -U, --update Update this program to latest version. Make sure that you have sufficient permissions (run with sudo if needed)

    Which can be used on it's own, without doing anything else. And only checks for updates when this option is specificly used!

    Changed to:

    [fido@brorabbit perl]$ ./callip.pl

    Calls the specified nodes by the binkp protocol, using connect information
    from the nodelist.

    Usage: ./callip.pl [options] nodelist_file_name
    ~~~~~
    -f,--fnode address - address of node to call. Optional.
    -z,--zone number - number of zone to test all nodes. Optional.
    -r,--region number - number of region to test all nodes. Optional.
    -n,--net network - number of network to test all nodes,
    i.e. 460. Optional.
    If you do not specify anything, then the check will pass through the entire nodelist.
    -l,--log log_file_name - file name of log file
    -a,--aka address - the fido address from which to make calls.
    Optional. default is '2:9999/9999.9999'.
    -c,--config - Configuration file name. Command line options
    owerrides it. Optional. Not needed by default.
    Use command callip.pl -e > callip.conf to
    create a new one
    -e,--export - export configuration end exit.
    -u,--update - How to update programm. Optional.
    =a - auto. Check for a new version, download
    and update.
    =d - download. Checks for a new version and
    download the update to a new file.
    =w - warn. Checks for a new version and warn
    the sysop. Default.
    =n - no. Do nothing.


    Btw: If you use '-a node' maybe the script could use the values
    from the nodelist for the SYS, ZYZ, and LOC info sent? Now it still
    says:

    Now it may be configured.

    - 29 Jan 12:28:15 [17842] SYS linux
    - 29 Jan 12:28:15 [17842] ZYZ Evil Robot
    - 29 Jan 12:28:15 [17842] LOC Sinferopol, Crimea

    Btw: Does the binkp protocol require that you send these, or can a valid connection be made without them?

    A valid connection may be made without them.

    Or maybe these values could be given on the command line too? Like:
    -a 2:280/464,system,sysop,location

    It turns out too much to write on the command line. I did better - an
    optional config file. This greatly shortens the command line. Try new
    version, please.

    I was already thinking in the same direction for a future update! ;-)

    Is it works now?

    Have nice nights.
    Stas Mishchenkov.

    --- Мудрость - это когда ты всё понимаешь, но уже не огорчаешься.
    * Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)
  • From Nodelist Police Commissioner@2:280/464 to Stas Mishchenkov on Sat Feb 5 18:36:27 2022
    Hello Stas,

    On 2022-02-04 20:44:36, you wrote to me:

    I've had some time to think about this. I don't like the fact it
    "calls home" on every invocation! It shouldn't act like spyware
    where the user has no control over it.

    How can we talk about spyware in case of open source? ;)

    I said "act like spyware"! ;-)

    Maybe you could replace it with an option like for instance
    youtube-dl has:

    -U, --update Update this program to latest version. Make sure that
    you have sufficient permissions (run with sudo if needed)

    Which can be used on it's own, without doing anything else. And only
    checks for updates when this option is specificly used!

    Changed to:

    [fido@brorabbit perl]$ ./callip.pl

    Calls the specified nodes by the binkp protocol, using connect information from the nodelist.

    Usage: ./callip.pl [options] nodelist_file_name
    ~~~~~
    -f,--fnode address - address of node to call. Optional.
    -z,--zone number - number of zone to test all nodes. Optional.
    -r,--region number - number of region to test all nodes. Optional.
    -n,--net network - number of network to test all nodes,
    i.e. 460. Optional.
    If you do not specify anything, then the check will pass through the entire nodelist.
    -l,--log log_file_name - file name of log file
    -a,--aka address - the fido address from which to make calls.
    Optional. default is '2:9999/9999.9999'.
    -c,--config - Configuration file name. Command line options
    owerrides it. Optional. Not needed by default.
    Use command callip.pl -e > callip.conf to
    create a new one
    -e,--export - export configuration end exit.
    -u,--update - How to update programm. Optional.
    =a - auto. Check for a new version, download
    and update.
    =d - download. Checks for a new version and
    download the update to a new file.
    =w - warn. Checks for a new version and warn
    the sysop. Default.
    =n - no. Do nothing.

    The last (-u=n) should be the default!

    And you can't do just an update on it's own:

    # callip -u=a

    Calls the specified nodes by the binkp protocol, using connect information
    from the nodelist.

    Usage: /usr/local/sbin/callip [options] nodelist_file_name
    ~~~~~
    [...]

    :-(

    Btw: If you use '-a node' maybe the script could use the values
    from the nodelist for the SYS, ZYZ, and LOC info sent? Now it
    still
    says:

    Now it may be configured.

    Cool! ;-)

    - 29 Jan 12:28:15 [17842] SYS linux
    - 29 Jan 12:28:15 [17842] ZYZ Evil Robot
    - 29 Jan 12:28:15 [17842] LOC Sinferopol, Crimea

    Btw: Does the binkp protocol require that you send these, or can a
    valid connection be made without them?

    A valid connection may be made without them.

    Can callip.pl made to do that?


    Regards, NPC.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: NPC Station (2:280/464)
  • From Stas Mishchenkov@2:460/5858 to Nodelist Police Commissioner on Sun Feb 6 12:45:22 2022
    Hi, Nodelist!

    05 фев 22 18:36, Nodelist Police Commissioner -> Stas Mishchenkov:

    How can we talk about spyware in case of open source? ;)

    I said "act like spyware"! ;-)

    Ok. ;)

    -u,--update - How to update programm. Optional.
    =a - auto. Check for a new version,
    download
    and update.
    =d - download. Checks for a new version
    and
    download the update to a new file.
    =w - warn. Checks for a new version and
    warn
    the sysop. Default.
    =n - no. Do nothing.

    The last (-u=n) should be the default!

    I think otherwise. Strictly speaking, with such a wide range of configurability, the default value can be any convenient for the author. ;)

    And you can't do just an update on it's own:

    # callip -u=a

    And this is a really important note.

    - 29 Jan 12:28:15 [17842] SYS linux
    - 29 Jan 12:28:15 [17842] ZYZ Evil Robot
    - 29 Jan 12:28:15 [17842] LOC Sinferopol, Crimea

    Btw: Does the binkp protocol require that you send these, or can a
    valid connection be made without them?

    A valid connection may be made without them.

    Can callip.pl made to do that?

    What do you mean?
    Do you consider it necessary to be able to disable the sending of this information? It seems to me that such an insignificant saving of traffic can only cause annoyance of the called sysop with the anonymous call.

    Have nice nights.
    Stas Mishchenkov.

    --- Люди, вы когда своей головой начнете думать, а не телевизором?
    * Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)
  • From Nodelist Police Commissioner@2:280/464 to Stas Mishchenkov on Sun Feb 6 13:31:46 2022
    Hello Stas,

    On 2022-02-06 12:45:22, you wrote to me:

    How can we talk about spyware in case of open source? ;)

    I said "act like spyware"! ;-)

    Ok. ;)

    -u,--update - How to update programm. Optional.
    =a - auto. Check for a new version,
    download
    and update.
    =d - download. Checks for a new
    version and
    download the update to a new
    file.
    =w - warn. Checks for a new version
    and warn
    the sysop. Default.
    =n - no. Do nothing.

    The last (-u=n) should be the default!

    I think otherwise. Strictly speaking, with such a wide range of configurability, the default value can be any convenient for the author. ;)

    If you want to do it like spyware does it... :-(

    Btw: If I put 'update no' in a configuration file, it ignores it. :-(

    - 29 Jan 12:28:15 [17842] SYS linux
    - 29 Jan 12:28:15 [17842] ZYZ Evil Robot
    - 29 Jan 12:28:15 [17842] LOC Sinferopol, Crimea

    Btw: Does the binkp protocol require that you send these, or can a
    valid connection be made without them?

    A valid connection may be made without them.

    Can callip.pl made to do that?

    What do you mean?
    Do you consider it necessary to be able to disable the sending of this information? It seems to me that such an insignificant saving of traffic can only cause annoyance of the called sysop with the anonymous call.

    I don't consider it necessary. But you could leave it up to the user of the script, to send this information or not?


    Requests:

    I would like to specify something like below in the config file:

    nodelist /home/fido/nodelist/NODELIST.*

    So I don't have to change the config file every time there is a nodelist update.


    Also, flags, should be something like:
    # busy flags dir name.
    flags /home/fido/outbound 2

    Like the domain line in binkd.conf. So it automatically uses the right outbound[.XXX] directory where binkd also does this. Otherwise 'flags' is not useful for fidonet...


    Regards, NPC.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: NPC Station (2:280/464)
  • From Nodelist Police Commissioner@2:280/464 to Stas Mishchenkov on Sun Feb 6 14:05:40 2022
    Hello Stas,

    On 2022-02-06 13:31:46, I wrote to you:

    -u,--update - How to update programm. Optional.
    =a - auto. Check for a new
    version, download
    and update.

    # callip -u=a -c callip_fido.cfg -f 2:460/5858
    callip.pl will be updated to v.0.8!
    /home/fido/bin/callip.plcallip.pl saved.
    ^^^^^^^^^^^^^^^^^^

    Bug in v.0.7, already fixed in v.0.8 ?

    Regards, NPC.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: NPC Station (2:280/464)
  • From Stas Mishchenkov@2:460/5858 to Nodelist Police Commissioner on Sun Feb 6 16:15:08 2022

    *** Ответ на сообщение из _Carbon.Mail (Carbon.Mail).

    Hi, Nodelist!

    05 фев 22 18:36, Nodelist Police Commissioner -> Stas Mishchenkov:

    And you can't do just an update on it's own:

    # callip -u=a

    Fixed and new option added:
    -u,--update - How to update programm. Optional.

    [...skipped...]
    =f - Force download callip.pl end exit even
    if no new version is found.

    The extended use of busy flags has also been applied. Now should not appear the log entries "all AKA are busy".

    Have nice nights.
    Stas Mishchenkov.

    --- Если вам не везет на любовном фронте, возвращайтесь к мирной жизни.
    * Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)
  • From Stas Mishchenkov@2:460/5858 to Nodelist Police Commissioner on Sun Feb 6 16:54:02 2022
    Hi, Nodelist!

    06 фев 22 13:31, Nodelist Police Commissioner -> Stas Mishchenkov:

    The last (-u=n) should be the default!

    I think otherwise. Strictly speaking, with such a wide range of
    configurability, the default value can be any convenient for the author.
    ;)

    If you want to do it like spyware does it... :-(

    Well, why immediately "like spayware"? The code is open and there are several ways to disable this action? On the other hand, if the user does not have the latest version, it seems reasonable to me to warn him about this at the first start. Am I right?

    Btw: If I put 'update no' in a configuration file, it ignores it. :-(

    Thank you. Fixed.

    What do you mean?
    Do you consider it necessary to be able to disable the sending of
    this information? It seems to me that such an insignificant saving of
    traffic can only cause annoyance of the called sysop with the
    anonymous call.

    I don't consider it necessary. But you could leave it up to the user of the script, to send this information or not?

    I'll think about this option. Although, I don't want some particularly irritable sysops to accuse me of making anonymous calls. ;)

    Requests:

    I would like to specify something like below in the config file:

    nodelist /home/fido/nodelist/NODELIST.*
    So I don't have to change the config file every time there is a
    nodelist update.

    Yes. This is a useful and convenient feature. I will definitely implement this.

    For such cases, I simply execute the "cp $1 ~/nodelist/nodelist.367" command when a fresh nodelist arrives.


    Also, flags, should be something like:
    # busy flags dir name.
    flags /home/fido/outbound 2

    Like the domain line in binkd.conf. So it automatically uses the right outbound[.XXX] directory where binkd also does this.

    It seems to me that it is risky to tell to this script the path to the actual outbound. It is much safer not to specify your known AKA in the script settings, but to use something like 2:460/58.1, i.e. an address with which definitely cannot be the session at the current moment. I need to remember to write it in HELP.

    Otherwise 'flags' is not useful for fidonet...

    They were not intended to be used with Fidonet mailers. These are exclusively internal flags that allow the script not to call the same system in different threads. Moreover, they have their own format, somewhat similar to ASO.

    Have nice nights.
    Stas Mishchenkov.

    --- Мне бесполезно что-либо запрещать, я и так не собираюсь ничего делать.
    * Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)
  • From Stas Mishchenkov@2:460/5858 to Nodelist Police Commissioner on Sun Feb 6 17:33:28 2022
    Hi, Nodelist!

    06 фев 22 14:05, Nodelist Police Commissioner -> Stas Mishchenkov:

    On 2022-02-06 13:31:46, I wrote to you:

    -u,--update - How to update programm. Optional.
    =a - auto. Check for a new
    version, download
    and update.

    # callip -u=a -c callip_fido.cfg -f 2:460/5858
    callip.pl will be updated to v.0.8!
    /home/fido/bin/callip.plcallip.pl saved.
    ^^^^^^^^^^^^^^^^^^

    Bug in v.0.7, already fixed in v.0.8 ?

    Hope so. ;)

    [fido@brorabbit ip]$ ./callip.pl -c ./callip.conf -f 2:460/5858 -u a

    callip.pl will be updated to v.0.9!
    /home/fido/perl/devel/ip/callip.pl saved.

    Now you can use 'callip -u=f' to use own update system.

    Have nice nights.
    Stas Mishchenkov.

    --- - А вы по национальности...? - Таки-да. А вы? - Нет. - А шо так?
    * Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)
  • From Stas Mishchenkov@2:460/5858 to Nodelist Police Commissioner on Sun Feb 6 18:31:46 2022

    *** Ответ на сообщение из _Carbon.Mail (Carbon.Mail).

    Hi, Nodelist!

    06 фев 22 13:31, Nodelist Police Commissioner -> Stas Mishchenkov:

    Requests:

    I would like to specify something like below in the config file:

    nodelist /home/fido/nodelist/NODELIST.*

    So I don't have to change the config file every time there is a nodelist update.

    I did it. Now you can update and check it.

    Have nice nights.
    Stas Mishchenkov.

    --- Умные мысли приходят лишь тогда, когда херня уже сделана.
    * Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)
  • From Nodelist Police Commissioner@2:280/464 to Stas Mishchenkov on Sun Feb 6 17:18:19 2022
    Hello Stas,

    On 2022-02-06 16:15:08, you wrote to me:

    And you can't do just an update on it's own:

    # callip -u=a

    Fixed and new option added:
    -u,--update - How to update programm. Optional.

    [...skipped...]
    =f - Force download callip.pl end exit even
    if no new version is found.

    Great! ;)


    Regards, NPC.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: NPC Station (2:280/464)
  • From Nodelist Police Commissioner@2:280/464 to Stas Mishchenkov on Sun Feb 6 17:19:16 2022
    Hello Stas,

    On 2022-02-06 16:54:02, you wrote to me:

    The last (-u=n) should be the default!

    I think otherwise. Strictly speaking, with such a wide range of
    configurability, the default value can be any convenient for the
    author. ;)

    If you want to do it like spyware does it... :-(

    Well, why immediately "like spayware"? The code is open and there are several ways to disable this action? On the other hand, if the user does not have the latest version, it seems reasonable to me to warn him about this at the first start. Am I right?

    It seems reasonable. And now the user has the option to put 'update no' or use the -u=n option, so it's ok...

    What do you mean?
    Do you consider it necessary to be able to disable the sending of
    this information? It seems to me that such an insignificant saving of
    traffic can only cause annoyance of the called sysop with the
    anonymous call.

    I don't consider it necessary. But you could leave it up to the user
    of the script, to send this information or not?

    I'll think about this option. Although, I don't want some particularly irritable sysops to accuse me of making anonymous calls. ;)

    You are not responsible for what the users of the script do with it!
    They could even change the script if they wanted to, to not send these...

    Requests:

    I would like to specify something like below in the config file:

    nodelist /home/fido/nodelist/NODELIST.*
    So I don't have to change the config file every time there is a
    nodelist update.

    Yes. This is a useful and convenient feature. I will definitely implement this.

    Great!

    Also, flags, should be something like:
    # busy flags dir name.
    flags /home/fido/outbound 2

    Like the domain line in binkd.conf. So it automatically uses the
    right outbound[.XXX] directory where binkd also does this.

    It seems to me that it is risky to tell to this script the path to the actual outbound. It is much safer not to specify your known AKA in the script settings, but to use something like 2:460/58.1, i.e. an address with
    which definitely cannot be the session at the current moment. I need to remember to write it in HELP.

    Good point!

    Otherwise 'flags' is not useful for fidonet...

    They were not intended to be used with Fidonet mailers. These are exclusively internal flags that allow the script not to call the same system in different threads. Moreover, they have their own format, somewhat
    similar to ASO.

    Ok understood!

    Regards, NPC.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: NPC Station (2:280/464)
  • From Nodelist Police Commissioner@2:280/464 to Stas Mishchenkov on Sun Feb 6 17:25:37 2022
    Hello Stas,

    On 2022-02-06 18:31:46, you wrote to me:

    Requests:

    I would like to specify something like below in the config file:

    nodelist /home/fido/nodelist/NODELIST.*

    So I don't have to change the config file every time there is a
    nodelist update.

    I did it. Now you can update and check it.

    Thanks! Got v.0.9.1, tested it and it works!

    Btw:
    # callip -c callip_fido.cfg -f 2:460/5858
    Parsing nodelist file /home/fido/nodelist/NODELIST.035
    Nodelist for Friday, February 4, 2022 -- Day number 035 parsed, 1060 IP-nodes processed (0.013 sec)
    burrow.g0x.ru, 24554
    Calling 2:460/5858 (2001:470:dcd0:0:f1d0:2:460:5858:24554)
    OPT CRAM-MD5-de0316997b7a66a8f5eca4a8474ac6ee
    SYS For_Technical_Perposes
    ^
    = "Purposes"


    Regards, NPC.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: NPC Station (2:280/464)
  • From Stas Mishchenkov@2:460/5858 to Nodelist Police Commissioner on Sun Feb 6 20:52:20 2022

    *** Ответ на сообщение из _Carbon.Mail (Carbon.Mail).

    Hi, Nodelist!

    06 фев 22 17:18, Nodelist Police Commissioner -> Stas Mishchenkov:

    And you can't do just an update on it's own:

    # callip -u=a

    Fixed and new option added:
    -u,--update - How to update programm. Optional.

    [...skipped...]
    =f - Force download callip.pl end exit even
    if no new version is found.

    Great! ;)

    I'm glad you liked it. ;)

    Have nice nights.
    Stas Mishchenkov.

    --- Нa opужейнoм зaвoдe заpплату дают дeнь в день, cекунда в секунду
    * Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)
  • From Stas Mishchenkov@2:460/5858 to Nodelist Police Commissioner on Sun Feb 6 21:08:42 2022

    Hi, Nodelist!

    06 фев 22 17:19, Nodelist Police Commissioner -> Stas Mishchenkov:

    Well, why immediately "like spayware"? The code is open and there are
    several ways to disable this action? On the other hand, if the user
    does
    not have the latest version, it seems reasonable to me to warn him
    about
    this at the first start. Am I right?

    It seems reasonable. And now the user has the option to put 'update
    no'
    or use the -u=n option, so it's ok...

    Well, thanks the God, we agreed. ;)

    I don't consider it necessary. But you could leave it up to the
    user of the script, to send this information or not?

    I'll think about this option. Although, I don't want some
    particularly
    irritable sysops to accuse me of making anonymous calls. ;)

    You are not responsible for what the users of the script do with it!
    They could even change the script if they wanted to, to not send
    these...

    Some sysops believe that it is not the one who is naughty who is to blame, but the one who gave him such an opportunity. ;)

    Requests:

    I would like to specify something like below in the config file:

    nodelist /home/fido/nodelist/NODELIST.*
    So I don't have to change the config file every time there is a
    nodelist update.

    Yes. This is a useful and convenient feature. I will definitely
    implement
    this.

    Great!

    I hope I got it right.

    Have nice nights.
    Stas Mishchenkov.

    --- Кто не рискует, - тот пьёт водку на поминках того, кто рисковал.
    * Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)
  • From Stas Mishchenkov@2:460/5858 to Nodelist Police Commissioner on Sun Feb 6 21:13:04 2022

    *** Ответ на сообщение из _Carbon.Mail (Carbon.Mail).

    Hi, Nodelist!

    06 фев 22 17:25, Nodelist Police Commissioner -> Stas Mishchenkov:

    Requests:

    I would like to specify something like below in the config file:

    nodelist /home/fido/nodelist/NODELIST.*

    So I don't have to change the config file every time there is a
    nodelist update.

    I did it. Now you can update and check it.

    Thanks! Got v.0.9.1, tested it and it works!

    I'm glad.

    Btw:
    # callip -c callip_fido.cfg -f 2:460/5858
    Parsing nodelist file /home/fido/nodelist/NODELIST.035
    Nodelist for Friday, February 4, 2022 -- Day number 035 parsed, 1060 IP-nodes processed (0.013 sec) burrow.g0x.ru, 24554 Calling 2:460/5858 (2001:470:dcd0:0:f1d0:2:460:5858:24554) OPT CRAM-MD5-de0316997b7a66a8f5eca4a8474ac6ee SYS For_Technical_Perposes
    ^
    = "Purposes"

    Oh my God! Thank you. My English is sometimes lame on all four feet. ;)

    Have nice nights.
    Stas Mishchenkov.

    --- Мудрость - это когда ты всё понимаешь, но уже не огорчаешься.
    * Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/5858)
  • From Nodelist Police Commissioner@2:280/464 to Stas Mishchenkov on Sun Feb 6 20:26:23 2022
    Hello Stas,

    On 2022-02-06 21:08:42, you wrote to me:

    Well, why immediately "like spayware"? The code is open and there
    are several ways to disable this action? On the other hand, if the
    user does not have the latest version, it seems reasonable to me to
    warn him about this at the first start. Am I right?

    It seems reasonable. And now the user has the option to put 'update
    no' or use the -u=n option, so it's ok...

    Well, thanks the God, we agreed. ;)

    "the (?) God" has nothing to do with it. ;)

    Regards, NPC.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: NPC Station (2:280/464)