So,
I have a node with a primary node and an aka. It's for my network.
The primary node is what was sent for the packet, but on the client mystic >install when I was trying to import messages I was getting a packet password >error. I had the aka (or second not primary node set as the node in nodes on >the client)
Confused yet?
Anyhow, it rejects with an invalid password because I think it's looking for >a password for the node listed as primary - I know that's the node because >that is the node printed in the mutil log with error.
Is this expected? Or should a system that has dual akas know to use same >password?
It would transfer the packets fine as it read the aka and both node addresses.
Sorry if this is unclear, it's kind of confusing.
--
yrNews Usenet Reader for iOS
http://appstore.com/yrNewsUsenetReader
--- Mystic BBS/NNTP v1.12 A33 (Linux/64)
* Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (21:1/107)
Sysop: | sneaky |
---|---|
Location: | Ashburton,NZ |
Users: | 2 |
Nodes: | 8 (0 / 8) |
Uptime: | 77:18:01 |
Calls: | 2,119 |
Files: | 11,149 |
D/L today: |
26 files (10,016K bytes) |
Messages: | 950,595 |