Hi Mike,

I'm down to a "bare-bone's" binkley.evt, this is gotta fix the dialing out to HOLD nodes, how's it look to you?

; For MDT $ B D N L M F R X C Q A T E1 E2 ;---------------------------------------------------------------------------- Event All 00:00 03:00 B F E1=100
Event All 03:00 04:00 $ N L M A=60 T=2,25 E2=40 Event Sat 10:00 10:00 B F Q=0 E1=98
Event All 04:00 23:59 B L Q=0 E2=40
;

Kevin
klement@shaw.ca
--- Squish/386 v1.11
* Origin: This unit must survive! (1:134/77)

Hello Kevin!

14 May 05 14:36, Kevin Klement wrote to Mike Tripp:

Hi Mike,

I'm down to a "bare-bone's" binkley.evt, this is gotta fix the dialing
out to HOLD nodes, how's it look to you?

Yes...I'm all for trying a pared down version. You're using a lot of flags that I haven't messed with and looks like my doc file is corrupt after ten years on the Netware server and I'm going to need to go scrounge a fresh copy to play in the deep end.<g> I've started to try to duplicate your setup a time
or two to test and am reminded of how much more non-trivial that is than it sounds.

You still have the 10AM Sat zero-length forced event ahead of your everyday 4AM
to midnight event...so resequence to ascending order. The overlap might be causing the Event# confusion.

I still don't think the dialout is Bink's issue...but the fact that the hold node's file is not .HLO is. If you still had the problem with the resorted ROUTE.CFG, then I think it may necessarily Squish either, but perhaps some more
code later in your batch that might be running when you think it isn't. Is it only doing it for this one node, or is it just lucky that this is the guy with something still pending at midnight?

P.S. My equivalent trick to your scripts to keep the analog node from dialing my IP nodes is to assign them my analog number as an override in the analog BINK.CFG. That kept the analog side from trying to CRASH the same node that BINKD was trying to crash, but since it is configurable by address, I could still have the analog node dial Seaborn if nothing was happening on the IP side...due to issues at either end.

.\\ike

--- GoldED 2.50+
* Origin: -=( The TechnoDrome )=- Austin,TX 512-327-8598 33.6k (1:382/61)

Hi Mike,

Saturday May 14 2005, Mike Tripp writes to Kevin Klement:

Yes...I'm all for trying a pared down version. You're using
a lot of flags that I haven't messed with and looks like my
doc file is corrupt after ten years on the Netware server

Yep new binkley.evt, here's hoping.

I have the *.DOC if you want me to send it via binkp.

I still don't think the dialout is Bink's issue...but the
fact that the hold node's file is not .HLO is.

Hmmmm ... Well DARN! It did it again, Just a hobby. :)

Okay, here was the set-up from last night.

binkley.log:
===========================[ BEGINNING OF DAILY LOG ]===========================
! 15 May 00:00:14 NOTE Backing up logs for yesterday took 1 second
! 15 May 00:00:14 NOTE End bbslogs.bat----------------------------------

+ 15 May 00:04:11 BINK begin, BinkleyTerm Version 2.60A -uSoft7.0
* 15 May 00:04:13 BINK Processing node 1:134/11 -- Mike'S Madhouse
: 15 May 00:04:13 BINK Dialing 288-8208
# 15 May 00:04:33 BINK Connect 28800/Arq/V34/Lapm/V42Bis

---cut---
* 15 May 00:09:24 BINK Processing node 1:134/303 -- Ice Zone
: 15 May 00:09:24 BINK Dialing with script 'Dialtmp.Scr'
+ 15 May 00:09:24 BINK Script 'Dialtmp.Scr' failed at line 1
+ 15 May 00:09:27 BINK End of connection attempt
* 15 May 00:10:34 BINK Processing node 1:134/303 -- Ice Zone
: 15 May 00:10:34 BINK Dialing with script 'Dialtmp.Scr'
+ 15 May 00:10:34 BINK Script 'Dialtmp.Scr' failed at line 1
+ 15 May 00:10:37 BINK End of connection attempt
* 15 May 00:13:30 BINK Processing node 1:134/303 -- Ice Zone
: 15 May 00:13:30 BINK Dialing with script 'Dialtmp.Scr'
+ 15 May 00:13:30 BINK Script 'Dialtmp.Scr' failed at line 1
+ 15 May 00:13:33 BINK End of connection attempt
* 15 May 00:15:35 BINK Processing node 1:134/303 -- Ice Zone
: 15 May 00:15:35 BINK Dialing with script 'Dialtmp.Scr'
+ 15 May 00:15:35 BINK Script 'Dialtmp.Scr' failed at line 1
+ 15 May 00:15:38 BINK End of connection attempt
---cut---

binkley.evt:
; For MDT $ B D N L M F R X C Q A T E1 E2 ;---------------------------------------------------------------------------- Event All 00:00 03:00 B F E1=100
Event All 03:00 04:00 $ N L M A=60 T=2,25 E2=40 Event Sat 10:00 10:00 F Q=0 E1=98
Event All 04:00 23:59 B L Q=0 E2=40

And the OUTBOUND looks like so:

Volume in drive Z is PROGRAMS HD
Directory of Z:\OUTBOUND

. <DIR> 05-15-05 1:02p
.. <DIR> 05-15-05 1:02p
0000FED3 FR0 356 05-13-05 6:36p
0000FED3 SA0 3,458 05-14-05 12:34a
0000FED3 SU0 4,053 05-15-05 12:35a
0086012F HLO 81 05-15-05 12:35a
0086012F HUT 72,636 05-14-05 10:10a
7 file(s) 80,584 bytes
2,147,450,880 bytes free


So now I deleted my 10:00 event like so:

My Current set-up:

; For MDT $ B D N L M F R X C Q A T E1 E2 ;---------------------------------------------------------------------------- Event All 00:00 03:00 B F E1=100
Event All 03:00 04:00 $ N L M A=60 T=2,25 E2=40 Event All 04:00 23:59 B L Q=0 E2=40
;

So now I'm hoping again, IT BETTER WORK. <grin>
Kevin
klement@shaw.ca

--- Squish/386 v1.11
* Origin: This unit must survive! (1:134/77)

Hi Mike,

Saturday May 14 2005, Mike Tripp writes to Kevin Klement:

You still have the 10AM Sat zero-length forced event ahead
of your everyday 4AM to midnight event...so resequence to
ascending order. The overlap might be causing the Event#
confusion.

Yes, I've done that now, I guess I shouldn't have never done that, wanted to see
how Binkley would re-act to that, <grin>. Anyway my new even will run to
night. No 10:00 event. :)
Kevin
klement@shaw.ca
--- Squish/386 v1.11
* Origin: This unit must survive! (1:134/77)

Hi Mike,

Saturday May 14 2005, Mike Tripp writes to Kevin Klement:

Is it only doing it for this one node, or is it just
lucky that this is the guy with something still pending at
midnight?

It does it for a few HOLD nodes, but yes, this node was the lucky guy with pending hold mail at midnight, now I've stoped his mail via BINKB tonight to see if binkley try's to dial him.

Time will see.
Kevin

--- Squish/386 v1.11
* Origin: This unit must survive! (1:134/77)

Hi Mike,

Saturday May 14 2005, Mike Tripp writes to Kevin Klement:

P.S. My equivalent trick to your scripts to keep the analog
node from dialing my IP nodes is to assign them my analog
number as an override in the analog BINK.CFG. That kept the
analog side from trying to CRASH the same node that BINKD
was trying to crash, but since it is configurable by
address, I could still have the analog node dial Seaborn if
nothing was happening on the IP side...due to issues at
either end.

Now, how do you do that? Can you show me?
Kevin
klement@shaw.ca

--- Squish/386 v1.11
* Origin: This unit must survive! (1:134/77)

Hi Kevin,

P.S. My equivalent trick to your scripts to keep the analog
node from dialing my IP nodes is to assign them my analog
number as an override in the analog BINK.CFG. That kept the
analog side from trying to CRASH the same node that BINKD
was trying to crash, but since it is configurable by
address, I could still have the analog node dial Seaborn if
nothing was happening on the IP side...due to issues at
either end.

Now, how do you do that? Can you show me?

I use a slightly different approach here, all my mail is handled (IE scanned and packed) for HOLD. At an appropriate SQUISH event, anything that needs to go
via the PSTN gets changed by Squish to either NORMAL or CRASH as required. Mail for my IP nodes is left as HOLD. As I run under OS/2, my background mail processing task (it checks for work every 1 minute) runs a REXX script that checks my outbound areas and if it finds any traffic for any IP node mentioned in my BinkD control file, it then automatically generates a BinkD .ILO file and
that triggers BinkD to make an IP connection to deliver that mail. It works great.

Cheers...............pk.


--- Maximus/2 3.01
* Origin: Another Good Point About OS/2 (3:772/1.10)

Hello Kevin!

15 May 05 17:36, Kevin Klement wrote to Mike Tripp:

address, I could still have the analog node dial Seaborn if
nothing was happening on the IP side...due to issues at
either end.

Now, how do you do that? Can you show me?

Sorry, looks like I misremembered the way I've done this since my node's entry has evolved over time.

You can do a simple DIAL statement with <listed_number> <substitute(your)_number>. In your case, that's going to apply to everyone using the same "generic" IP number, though. My node had a dual listing with a real analog number that made the translation unique to him, though.

Binkley will try to dial the parent host/hub entry for a Pvt/Unpub listing. So
when my node dropped his analog line and switched from a listed node to Unpub, my Bink started trying to dial itself automatically, since I am his host.

My nodelist compiler (QNode) can also assign a number that will override the listed number with one of your choosing...as long as listed number is not -Unpublished-. If yours can do the same/similar, that might be your path to overwriting the generic number with your own for only the specified address.

Overall, it won't have much bearing on your problem. Your logs will fill with just as many attempts to call yourself as it currently does attempts to run your null scripts. Just another technique that might help troubleshooting, and
it recycles on the BUSY fairly quickly, but your script probably is cycling pretty quick now.

Sorry I haven't had much tinker time to assist. My baby girl is graduating from high school on Fri, so the whole household has been tied up in getting the
house ready for invasion by out-of-town family this weekend.

I did manage to clone my current setup to another local drive and comment out my EVT statements and substitute yours. Bink did not try to outdial for any of
the existing HLOs that were in my real outbound and I tried holding something for the same node that is giving you trouble and it didn't/wouldn't try to dial
him either.

.\\ike

--- GoldED 2.50+
* Origin: -=( The TechnoDrome )=- Austin,TX 512-327-8598 33.6k (1:382/61)

Hi Mike,

Monday May 16 2005, Mike Tripp writes to Kevin Klement:

Sorry, looks like I misremembered the way I've done this
since my node's entry has evolved over time.

Okay.

My nodelist compiler (QNode) can also assign a number that

^^^^^^^
I use Qnode also, I like your idea here, so I set it up, but your right my binkley log will still fill up with it trying to call HOLD nodes.

Just another technique that might help troubleshooting, and
it recycles on the BUSY fairly quickly, but your script
probably is cycling pretty quick now.

Yep, now my events in Binkley are running fine, It's running through all three events with a hitch.

Now I've stoped Squish from doing anything during my midnight maintenance event. I've got a node's mail on HOLD right now, and Binkp will NOT try to deliver it tonight after midnight maintenance.

Hoping Binkley doesn't try to call him tonight via modem. :)

Sorry I haven't had much tinker time to assist. My baby
girl is graduating from high school on Fri, so the whole

Congratulations!

Not to worry Mike, thanks for all the help so far, I'll find the problem
sooner or later. :)
Kevin
klement@shaw.ca
--- Squish/386 v1.11
* Origin: This unit must survive! (1:134/77)

Hi Peter,

Monday May 16 2005, Peter Knapper writes to Kevin Klement:

and if it finds any traffic for any IP node mentioned in my
BinkD control file, it then automatically generates a BinkD
.ILO file and that triggers BinkD to make an IP connection
to deliver that mail. It works great.

Okay, question, are you are using IREX?
Kevin
klement@shaw.ca

---
* Origin: This unit must survive! (1:134/77)

Hi Kevin,

Monday May 16 2005, Peter Knapper writes to Kevin Klement:

and if it finds any traffic for any IP node mentioned in my
BinkD control file, it then automatically generates a BinkD
.ILO file and that triggers BinkD to make an IP connection
to deliver that mail. It works great.

Okay, question, are you are using IREX?

Nope, BinkleyTerm/2 (v2.60), Maximus/2, Squish/2, Nef/pk, BinkD/2.

Cheers..............pk.


--- Maximus/2 3.01
* Origin: Another Good Point About OS/2 (3:772/1.10)

Hi Peter,

Tuesday May 17 2005, Peter Knapper writes to Kevin Klement:

Nope, BinkleyTerm/2 (v2.60), Maximus/2, Squish/2, Nef/pk,
BinkD/2.

Okay, just never used/heard of BinkD/2, myself, I use IREX which uses the protocol BinkD for it's internet packet transfers.

Kevin
klement@shaw.ca

--- Squish/386 v1.11
* Origin: This unit must survive! (1:134/77)

Re: binkley.evt
By: Kevin Klement to Peter Knapper on Tue May 17 2005 02:36 pm

Hi Peter,

Tuesday May 17 2005, Peter Knapper writes to Kevin Klement:

Nope, BinkleyTerm/2 (v2.60), Maximus/2, Squish/2, Nef/pk,
BinkD/2.

Okay, just never used/heard of BinkD/2, myself, I use IREX which uses the protocol BinkD for it's internet packet transfers.

BinkP is the name of the protocol.
BinkD is the name of a program. The "/2" just indicates an OS/2 native build of the program.

digital man

Snapple "Real Fact" #169:
The first human-made object to break the sound barrier was a whip.

Hi Rob,

BinkP is the name of the protocol.
BinkD is the name of a program. The "/2" just indicates an
OS/2 native build of the program.

Ops ... that's what I thought. :)
Kevin
--- Squish/386 v1.11
* Origin: This unit must survive! (1:134/77)

Hi Peter,

Monday May 16 2005, Peter Knapper writes to Kevin Klement:

my background mail processing task (it checks for work every
1 minute) runs a REXX script that checks my outbound areas
and if it finds any traffic for any IP node mentioned in my

I've also used this idea, My mail is being processed on a Workstation, so I just got my Server to write flag files for forced events, Binkley on the workstation doesn't run forced events anymore.
Kevin
klement@shaw.ca

--- Squish/386 v1.11
* Origin: This unit must survive! (1:134/77)

Hi Peter,

Is BinkD and IREX two completely different programs?

My assumption is they both use the protocol binkp.
Kevin
klement@shaw.ca

--- Squish/386 v1.11
* Origin: Gypsy BBS -- Gypsy Designs (403) 242-3221 (1:134/77)

Hello, Kevin.

On 24 May 05 at 13:28, Kevin Klement wrote to Peter Knapper:

Is BinkD and IREX two completely different programs?

My assumption is they both use the protocol binkp.

Yes, they're two different programs, however: Internet Rex has a BinkD (daemon)
built into it. BinkD is an actual program also. They both use the BinkP protocol.

Later,
Sean

// hausmaus@darktech.org | http://outpostbbs.net | ICQ: 19965647

--- GoldED+/W32 1.1.5-21011
* Origin: Outpost BBS - Kennesaw, GA - outpostbbs.net (1:18/200)

Hi Kevin,

Is BinkD and IREX two completely different programs?

They are 2 different programs. The TCP/IP communications protocol is known as BinkP. BinkD was the first program to implement the BinkP protocol, and that was followed by others such as Irex, so yes they are different implementations of the same thing.

My assumption is they both use the protocol binkp.

Yep thats it.

Cheers...............pk.


--- Maximus/2 3.01
* Origin: Another Good Point About OS/2 (3:772/1.10)

Hi Peter,

Wednesday May 25 2005, Peter Knapper writes to Kevin Klement:

They are 2 different programs. The TCP/IP communications
protocol is known as BinkP. BinkD was the first program to

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

So, This program BinkD, were is it available?
Kevin
klement@shaw.ca

--- Squish/386 v1.11
* Origin: Gypsy BBS -- Gypsy Designs (403) 242-3221 (1:134/77)

SEAN DENNIS wrote to KEVIN KLEMENT <=-

Yes, they're two different programs, however: Internet Rex has a BinkD (daemon) built into it. BinkD is an actual program also. They both
use the BinkP protocol.

I believe that use different versions of BinkD as well, I think Irex is
BinkD 1.0, where as BinkD (the program) uses BinkD 1.1. Argus/Radius
seem to use BinkD 1.0 or lower.

Kev


... Internal Error: The system has been taken over by sheep at line 19960
--- Telegard/2/QWK v3.09.g2-sp4/mL
* Origin: Razor's Domain BBS (1:397/10)

Hi Kevin,

SEAN DENNIS wrote to KEVIN KLEMENT <=-

Yes, they're two different programs, however:
Internet Rex has a BinkD
(daemon) built into it. BinkD is an actual program also. They both
use the BinkP protocol.

I believe that use different versions of BinkD as well, I think Irex is BinkD 1.0, where as BinkD (the program) uses BinkD 1.1. Argus/Radius
seem to use BinkD 1.0 or lower.

Last time I checked, IREX was BINKP 1.0, BinkD was BINKP 1.1. Its the PROTOCOL version (BINK_P_)that is different between products...

Cheers...........pk.



--- Maximus/2 3.01
* Origin: Another Good Point About OS/2 (3:772/1.10)

Hi Kevin,

They are 2 different programs. The TCP/IP communications
protocol is known as BinkP. BinkD was the first program to

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

So, This program BinkD, were is it available?
Kevin
klement@shaw.ca

Here is the original site, but there are many others as well -
http://www.doe.carleton.ca/~nsoveiko/fido/binkd/

A good mirror is -
ftp://fido.thunderdome.ws/pub/mirror/binkd/

Check out the BINKD echo, an FAQ is posted there weekly, and also try a Google search, that will reveal many more sites...

Cheers.............pk.


--- Maximus/2 3.01
* Origin: Another Good Point About OS/2 (3:772/1.10)

Hello, Kevin.

On 25 May 05 at 22:39, Kevin Nunn wrote to Sean Dennis:

I believe that use different versions of BinkD as well, I think Irex
is BinkD 1.0, where as BinkD (the program) uses BinkD 1.1.
Argus/Radius seem to use BinkD 1.0 or lower.

From my logs:

% 09:22:51 (912) BinkP: VER Internet Rex 2.27 OS/2 (binkp/1.1)
% 08:01:03 (912) BinkP: VER Internet Rex 2.29 Win32 (binkp/1.1)

Internet Rex has always used the latest BinkP, IIRC.

% 09:01:03 (500) BinkP: VER Taurus/5.000/01.05.2005,17:15(Spring)/Win32 binkp/1.1

Looks like Taurus is using the latest.

% 09:01:04 (260) BinkP: VER binkd/0.9.8/Linux binkp/1.1

% 09:01:03 (328) BinkP: VER binkd/0.9.8/OS2 binkp/1.1

So, as far as I can tell, Argus/Radius are still behind. Everyone else seems to be using 1.1.

Later,
Sean

// hausmaus@darktech.org | http://outpostbbs.net | ICQ: 19965647

--- GoldED+/W32 1.1.5-21011
* Origin: Outpost BBS - Kennesaw, GA - outpostbbs.net (1:18/200)

Hello Sean.

26 May 05 10:20, you wrote to Kevin Nunn:

On 25 May 05 at 22:39, Kevin Nunn wrote to Sean Dennis:

I believe that use different versions of BinkD as well, I think
Irex is BinkD 1.0, where as BinkD (the program) uses BinkD 1.1.
Argus/Radius seem to use BinkD 1.0 or lower.

From my logs:

% 09:22:51 (912) BinkP: VER Internet Rex 2.27 OS/2 (binkp/1.1)
% 08:01:03 (912) BinkP: VER Internet Rex 2.29 Win32 (binkp/1.1)

Internet Rex has always used the latest BinkP, IIRC.

% 09:01:03 (500) BinkP: VER
Taurus/5.000/01.05.2005,17:15(Spring)/Win32 binkp/1.1

Looks like Taurus is using the latest.

% 09:01:04 (260) BinkP: VER binkd/0.9.8/Linux binkp/1.1

% 09:01:03 (328) BinkP: VER binkd/0.9.8/OS2 binkp/1.1

So, as far as I can tell, Argus/Radius are still behind. Everyone
else seems to be using 1.1.

I can ay and point on 3 places to grab the binkd mailer.
1. http://sourceforge.net -> http://binkd.sourceforge.net/
2, http://www.kofobbs.dk -> ftp://fileserver.kofobbs.net/pub/2/fido/aftnbnk/ 3. http://www.filegate.net under same fle echo name is comes under aftnbinkd.
and as Binkd mostly is updated of russian people is Filegate (Janis) getting it from me.
if one is running linux and like to compile it to the newest version an there be tryed by cvs to the home of binkd.
My Win32 binkd is complete one and my binkd on my linux is a cvs done and compiled of the sources.
By searching on google.com write then BinkD Mailer Kevin.

I am self now on to try to setting a BTXE up for modem connect and BBS of Maximus on my Win2k pc.


Gert Andersen

--- GoldED+/W32 1.1.5-20050419
* Origin: ===> Next is Using Gentoo Linux for most doing. <===== (2:236/150)

Hi Peter,

Thursday May 26 2005, Peter Knapper writes to Kevin Klement:

Here is the original site, but there are many others as well
- http://www.doe.carleton.ca/~nsoveiko/fido/binkd/

A good mirror is -
ftp://fido.thunderdome.ws/pub/mirror/binkd/

Check out the BINKD echo, an FAQ is posted there weekly, and
also try a Google search, that will reveal many more
sites...

Super!


THX
Kevin
klement@shaw.ca

--- Squish/386 v1.11
* Origin: Gypsy BBS -- Gypsy Designs (403) 242-3221 (1:134/77)

Hi Sean,

Thursday May 26 2005, Sean Dennis writes to Kevin Nunn:

From my logs:

Wich do you like, IREX or BinkD?


Kevin
klement@shaw.ca

--- Squish/386 v1.11
* Origin: Gypsy BBS -- Gypsy Designs (403) 242-3221 (1:134/77)

PETER KNAPPER wrote to KEVIN NUNN <=-

I believe that use different versions of BinkD as well, I think Irex is BinkD 1.0, where as BinkD (the program) uses BinkD 1.1. Argus/Radius
seem to use BinkD 1.0 or lower.

Last time I checked, IREX was BINKP 1.0, BinkD was BINKP 1.1. Its the PROTOCOL version (BINK_P_)that is different between products...

That's what I meant, sorry about that :)

Kev

... DalekDOS v(overflow): (I)Obey (V)ision impaired (E)xterminate
--- Telegard/2/QWK v3.09.g2-sp4/mL
* Origin: Razor's Domain BBS (1:397/10)

SEAN DENNIS wrote to KEVIN NUNN <=-

From my logs:

% 09:22:51 (912) BinkP: VER Internet Rex 2.27 OS/2 (binkp/1.1)
% 08:01:03 (912) BinkP: VER Internet Rex 2.29 Win32 (binkp/1.1)

Internet Rex has always used the latest BinkP, IIRC.

Well, when I was doing research into FREQ using Binkp, Binkp would
handle FREQ's successfully by returning the file during the session.
Where as IREX was not doing that. As I looked further I think I remember reading that it was because IREX did not fully support binkp 1.1, so I
assumed it was binkp 1.0.

And I don't have any nodes using Targus, so could not comment on that. I
know Radius/Argus do not seem to support encrypted passwords.

Kev


... DalekDOS v(overflow): (I)Obey (V)ision impaired (E)xterminate
--- Telegard/2/QWK v3.09.g2-sp4/mL
* Origin: Razor's Domain BBS (1:397/10)