Just playing with stats...
║ 21:1/202 │? 16 0 70 66 4│ 0:03:25│ 1k 118k│3082│597║
binkp/1.1 + 2019.11.26 01:17:02 BINKP 1-Mailer binkd/1.1a-99/Win32 binkp/1.1 + 2019.11.26 01:17:02 BINKP 1-R: ADR 21:1/100@fsxnet 21:1/3@fsxnet 21:1/2@fsxnet 21:1/0@fsxnet 21:0/0@fsxnet
+ 2019.11.26 01:17:02 BINKP 1-R: NUL OPT NDA EXTCMD CRYPT GZ BZ2
+ 2019.11.26 01:17:03 BINKP 1-R: BSY No AKAs in common domains or all AKAs are busy
+ 2019.11.26 01:17:03 BINKP 1-Error receiving data (Msg= Size=0/46)
+ 2019.11.26 01:17:03 BINKP 1-R: BSY No AKAs in common domains or all AKAs are busy
+ 2019.11.26 01:17:03 BINKP 1-Connection lost
Do you know what those BSY errors mean? Clearly we have a domain in
common (fsxnet), and the next minute, another connection is coming in,
and everything is working just as it should:
On 11-27-19 14:05, Avon wrote to Zip <=-
That all said as a mailer BinkD seems to work well as a way of shifting stuff quickly across a bunch of nodes when packets are being tossed.
I'm wondering when I move to Linux is I will notice a performance improvement on the other software I have running on the box. I do
already use it for 21:1/10 and 3:770/1
The move to BinkD has been interesting. Some nodes I was unable to
poll successfully until I made sure the first AKA presented from my
end was 21:1/100. I initially had the system showing another AKA like 21:1/0 but found I needed to change that.
I'm also seeing some issues with CRAM-MD5 on some systems. Others
nodes that I had set to hold I set to crash and in doing so it's
becoming apparent that some nodes domain names are no longer
resolving.
Which mailer program has this problem?
Is this a problem with the domain or binkd?
Can you tell me have you noticed any MIA packets from 1/100 since you started get fed by the new mailer?
Can you tell me have you noticed any MIA packets from 1/100 since you started get fed by the new mailer?
No, I haven't noticed any and I'm trying hard to find one. We need to continue the experiment to collect more data :).
Can you tell me have you noticed any MIA packets from 1/100
since you started get fed by the new mailer?
No, I haven't noticed any and I'm trying hard to find one. We
need to continue the experiment to collect more data :).
I agree. Are you taking your feed exclusively from 1/100 - if not,
can you do this please.
The move to BinkD has been interesting. Some nodes I was unable to poll successfully until I made sure the first AKA presented from my end was 21:1/100. I initially had the system showing another AKA like 21:1/0 but found I needed to change that.
I discovered last night that if you use a node #, rather than the
actual name of the hub...the connection would time out. I use the name...could connect...but the number...couldn't. Is this a thing
with BinkP or is it the same with D'Bridge & Frontdoor?
I'm also seeing some issues with CRAM-MD5 on some systems. Others nodes
that I had set to hold I set to crash and in doing so it's becoming
apparent that some nodes domain names are no longer resolving. So outbound polling to a few is a problem but some are polling in to collect so that's OK.
where the issues are. I can see about 10 nodes I will need to email the sysops of and ask about their domain names etc.
stuff quickly across a bunch of nodes when packets are being tossed. I'm wondering when I move to Linux is I will notice a performance
improvement on the other software I have running on the box. I do
Areas summaryArea In msgs Out msgs Bad Dupe In bytes Out bytes
Areas summaryArea In msgs Out msgs Bad Dupe In bytes Out
Why the difference in "out" messages from 1/100? Would this be expected?
IE: If 1/100 is feeding the other hub's I would expect them to be the same?
Sysop: | echicken |
---|---|
Location: | Toronto, Ontario |
Users: | 2,224 |
Nodes: | 6 (0 / 6) |
Uptime: | 12:30:48 |
Calls: | 14,143 |
Files: | 295 |
Messages: | 551,290 |