[0mi am getting this when one of my downlinks connect[B[50D[B[1DBINKP [A[5C 1-No matching AKA to authenticate[B[42DBINKP 1-Cannot authen [A[24Cticate client[B[37D[B[1Dwhen we remove the password it works. a [A[40Cny ideas? [B[50D[B[1D [1;30m.[0;35mú[1mù[37mDr[0me
[A[9C[1;30mam Ma[0mst[1mer[35mù[0;35mú[1;30m.[B[21D øù[0;35mú [A[6C[1mùø[9Cøù[0;35mú[1;30mùø[B[22D [36mDoRE[0;36m![1mACiDiC [A[14C[0;36m![1mDemonic[B[22D[30m[[37mdreamland[34m.[37mdarktech [A[19C[34m.[37morg[30m][B[24D
i am getting this when one of my downlinks connect
BINKP 1-No matching AKA to authenticate
BINKP 1-Cannot authenticate client
[0mi am getting this when one of my downlinks connect[B[50D[B[1DBINKP [A[5C 1-No matching AKA to authenticate[B[42DBINKP 1-Cannot authen [A[24Cticate client[B[37D[B[1Dwhen we remove the password it works. a [A[40Cny ideas? [B[50D[B[1D [1;30m.[0;35mú[1mù[37mDr[0me [A[9C[1;30mam Ma[0mst[1mer[35mù[0;35mú[1;30m.[B[21D øù[0;35mú [A[6C[1mùø[9Cøù[0;35mú[1;30mùø[B[22D [36mDoRE[0;36m![1mACiDiC
I hope you can see what I am replying too!
It sounds like there is no matching AKA to authenticate with.. a typo maybe?
i am getting this when one of my downlinks connect
BINKP 1-No matching AKA to authenticate
BINKP 1-Cannot authenticate client
no it's only when there is a password entered and it is the same we checked.
i am getting this when one of my downlinks connect
BINKP 1-No matching AKA to authenticate
BINKP 1-Cannot authenticate client
when we remove the password it works. any ideas?
BINKP 1-No matching AKA to authenticate
BINKP 1-Cannot authenticate client
Pretty sure most of this is fixed in A39. :)
BINKP 1-No matching AKA to authenticatePretty sure most of this is fixed in A39. :)
BINKP 1-Cannot authenticate client
i am getting this when one of my downlinks connect"No matching AKA to authenticate" means the address they are presenting
BINKP 1-No matching AKA to authenticate
BINKP 1-Cannot authenticate client
when we remove the password it works. any ideas?
is not configured in your Echomail nodes. The logging you're showing doesn't show the address their presenting though, so I can't help
further.
In this case I don't think there is anything to fix. In general thereBINKP 1-No matching AKA to authenticatePretty sure most of this is fixed in A39. :)
BINKP 1-Cannot authenticate client
has been only one change to BINKP in the past (years?) and it was the recent change related to BinkIT.
The message tells you the problem :)
Whatever address the client is presenting is not configured as an
echomail node.
"No matching AKA to authenticate" means the address they are presenti is not configured in your Echomail nodes. The logging you're showing doesn't show the address their presenting though, so I can't help further.
ok i will have to look at what he has because setup.
he informed me he had the domain spelled wrong. he has the right address.he had hide aka off.
It says that exactly,.... but with ANY password any case it won't authenticate, with no password works fine
dream master wrote to All <=-
i am getting this when one of my downlinks
connectBINKP 1-No matching AKA to
authenticateBINKP 1-Cannot authen ticate
clientwhen we remove the password it works. a
ny ideas? .úùDre
am Masterùú.
øùú ùøøùúùø
DoRE!ACiDiC
!Demonic[dreamland.darkte
ch .org]
--- Mystic BBS v1.12 A38 2018/01/01 (Windows/64)
* Origin: |08--[|15!|07dreamland BBS dreamland.darktech.org (21:1/163)
g00r00 wrote to dream master <=-
i am getting this when one of my downlinks connect
BINKP 1-No matching AKA to authenticate
BINKP 1-Cannot authenticate client
when we remove the password it works. any ideas?
"No matching AKA to authenticate" means the address they are presenting
is not configured in your Echomail nodes. The logging you're showing doesn't show the address their presenting though, so I can't help
further.
dream master wrote to g00r00 <=-
he informed me he had the domain spelled wrong. he has the right address.he had hide aka off.
g00r00 wrote to dream master <=-
The address and domain have to match exactly (with the exception of
.org .com .net that sometimes people incorrectly add to their domain, Mystic just strips that).
I would set a password no longer than 7 chars and keep it all uppercase
We figured it out 1) I had 'dornet' as the domain, misspeling! and I hid my aka's.. works like a champ now!
DM, do you _REALLY_ need to use ANSI in a message like this? While I can ANSI, I'm not able to reply with any reasonable quoting (see above). Your of ANSI is actually impeding communication. And the issue you're having i
The address and domain have to match exactly (with the exception of .org .com .net that sometimes people incorrectly add to their domain, Mystic just strips that).
Interesting, binkd requires that you explicitly configure aliases (i.e. incorrectly specified domains). :) There's pros and cons either way I guess.
g00r00 - suggestion might be to populate that field from another setup screen where sysops can load the zone and domain name as a combo then
use a selection tool to choose that base info and finish off by adding
net and node.. dunno... it may be overkill but perhaps something like
that would avoid some of these typo errors we see?
he informed me he had the domain spelled wrong. he has the right address.he had hide aka off.There you go. That will do it! So they can log in now?
This is a tough one but you're onto something... I'm a few adult drinks into the night (more than a few we're celebrating for a not good reason) so this is going to be hard to read. I'm too wordy when I am sober lol
between can be figured out by the software. I want to keep it that way and avoid as much "feature creep/redundancy" as we can. So because of that I am thinking veto on the zone/domain definition as a requirement/configuration editor kinda thing.
Here's my proposal: Lets define a text file that as a zone and domain mapping, and when you're entering an echomail address in Mystic, if the domain is empty, it will auto populate the domain based on the file.
This file would be strictly UI "auto-fill" related and have zero
influence on the echomail system.
Here's the thing though...
This helps to eliminate typos on Mystic ONLY. It does absolutely
nothing for any other BBS setup on the planet. So is it worth this
effort to do all of this?
Yep good catch. I think when this first was posted I had replied and suggested this also. Spelling often catches people out.
g00r00 - suggestion might be to populate that field from another setup screen where sysops can load the zone and domain name as a combo then
use a selection tool to choose that base info and finish off by adding
net and node.. dunno... it may be overkill but perhaps something like
that would avoid some of these typo errors we see?
g00r00 wrote to Vk3jed <=-
DM, do you _REALLY_ need to use ANSI in a message like this? While I can ANSI, I'm not able to reply with any reasonable quoting (see above). Your of ANSI is actually impeding communication. And the issue you're having i
His messages render fine in Mystic so I don't think he's doing it intentionally.
ANSI messages are permitted in this echo and embedded ANSI is fully supported and rendered properly within messages in Mystic (and in file descriptions too).
What likely happens is the message gets saved as a pipe code in his signature, but if he edits it afterwards Mystic will re-save it as
ANSI, assuming he has ANSI enabled for this base (which probably
everyone does because its allowed and I/we occasionally use it)
Mystic will often prefix ANSI messages with [ANSI] in the subject, but
he may have that feature disabled.
g00r00 wrote to Vk3jed <=-
The standard domain for Fidonet is 8 characters, and it cannot be
longer without breaking the BSO standard, because the domain name is
used in the directory structure. Anything over 8 characters would
break compatibility with 5D BSO on an 8.3 file system.
Mystic requires you to do it right, so you can't define more than 8 characters and instead it will strip off .com/.net if a client has that
in their domain name when they try to authenticate.
That would help ensure consistency within the setup of echonodes within the Mystic system. I'd suggest a fresh install of Mystic could ship with
a pre-poulated file much like the spell checking system does with some
about case sensitivity for that field. Does it matter, perhaps lowercase is the accepted convention and if an entry in this txt file were to have
Yep thats what it will be just a file that sits in the DATA directory. It'll serve no purpose but to make entering addresses easier by
suggesting the domain associated to a zone after you type in the numeric
| Sysop: | sneaky |
|---|---|
| Location: | Ashburton,NZ |
| Users: | 31 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 131:53:14 |
| Calls: | 2,073 |
| Files: | 11,136 |
| Messages: | 947,525 |