• Packet Password Issue

    From Robert Wolfe@1:116/18 to All on Fri Dec 28 14:10:53 2018
    Ok, for the following log snippet:

    ----------------- MUTIL v1.12 A42 2018/12/27 Fri, Dec 28 2018 (loglevel 2)
    + Dec 28 14:07:02 Startup using import.ini
    + Dec 28 14:07:02 Process: Toss FDN/TIC Files
    + Dec 28 14:07:02 Scanning Hatches
    + Dec 28 14:07:02 Results: 0 import, 0 toss, 0 hatch, 0 bad in 0.00s
    + Dec 28 14:07:02 Process: Importing EchoMail
    + Dec 28 14:07:02 Waiting for BUSY nodes
    + Dec 28 14:07:02 Importing 28012390.PKT (1:261/20 to 1:116/18)
    ! Dec 28 14:07:02 Invalid PKT password
    + Dec 28 14:07:02 Importing 28027222.PKT (1:261/20 to 1:116/18)
    ! Dec 28 14:07:02 Invalid PKT password
    + Dec 28 14:07:02 Importing 28026279.PKT (1:261/20 to 1:116/18)
    ! Dec 28 14:07:02 Invalid PKT password
    + Dec 28 14:07:02 Results: 0 echo, 0 net, 0 dupes, 0 tossed in 0.05s

    1:116/18 is my main Mystic system.
    1:261/20 is my system running SearchLight and ViaMail/SL 2.0.

    I have verified the same packet password on both setups, but am still getting this error message. I believe this was all working on A39, and nothing has changed configuration wise. Any thoughts?

    --- Mystic BBS v1.12 A42 2018/12/27 (Windows/32)
    * Origin: Omicron Theta * Southaven MS * winserver.org:2300 (1:116/18)
  • From mark lewis@1:3634/12.73 to Robert Wolfe on Fri Dec 28 15:31:20 2018

    On 2018 Dec 28 14:10:52, you wrote to All:

    I have verified the same packet password on both setups, but am still getting this error message. I believe this was all working on A39,
    and nothing has changed configuration wise. Any thoughts?

    have you looked in the raw pkts to see if the password is correct in the pkt header? you can use most any viewer that will show binary... the passwords are easy to spot if they are there... starting with the first byte being zero (as any good coder does), the password is the 26th through 33rd bytes...

    )\/(ark

    Always Mount a Scratch Monkey
    Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
    ... An apple a day keeps the doctor away. So does no medical insurance.
    ---
    * Origin: (1:3634/12.73)
  • From Robert Wolfe@1:116/18 to mark lewis on Fri Dec 28 16:14:10 2018
    On 28 Dec 2018, mark lewis said the following...

    have you looked in the raw pkts to see if the password is correct in the pkt header? you can use most any viewer that will show binary... the passwords are easy to spot if they are there... starting with the first byte being zero (as any good coder does), the password is the 26th
    through 33rd bytes...

    It is correct. Now it seems to be working and I didn't really change
    anything.

    --- Mystic BBS v1.12 A42 2018/12/27 (Windows/32)
    * Origin: Omicron Theta * Southaven MS * winserver.org:2300 (1:116/18)