• Bad packets

    From Al@21:4/106 to RickV on Sunday, March 30, 2025 14:44:10
    2 questions. How can you tell why a packet went bad? How can I re-toss a bad packet?

    There are different packet types floating around the net.

    The old standard Type 2. These are fine but they have no support for points unless you use a fakenet method. I don't think you'll see any of these today.

    The most common is Type 2+ and Type 2e. These are the most common these days and they do support points.

    There is also a Type 2.0 (and possibly others!) but these are not well supported. I think Synchronet will toss and produce all of these packet types if configured so but not all tossers can recognize them and will toss them bad.

    --- BBBS/Li6 v4.10 Toy-7
    * Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)
  • From RickV@21:1/206 to Gamgee on Sunday, March 30, 2025 18:22:54
    Hello Gamgee.

    11 Jul 70 14:19, you wrote to Rick V:

    Rick V wrote to Gamgee <=-

    Re: Re: Bad packets
    By: Gamgee to RickV on Sun Mar 30 2025 12:37:36

    Yep, OK... but sure looks like you're posting from SBBS... ^^^

    Well I was, but the question was in a Mystic echo about a Mystic
    packet problem.

    To be fair, you NEVER said a single word about it being a "Mystic"
    packet problem.

    In fact, just a few days ago, you were asking this EXACT same question
    in the SBBS support forums on DoveNet, and specifically told
    Digitalman "that helps" when he explained in good detail how to troubleshoot this problem on SBBS. Let me know if you'd like me to
    quote some messages from there.

    So............. can you see why I was thinking you were asking about Synchronet?

    As a general rule, asking good/detailed/complete questions about
    something will get you good answers. Being vague and leaving out
    helpful information ... will not.



    ... Internal Error: The system has been taken over by sheep at line
    19960
    === MultiMail/Linux v0.52

    I guess we both made assumptions, I was in the Mystic echo and assumed that it would be viewed as a mystic question, and you saw it was a post FROM a SBBS system...

    RickV

    === GoldED+/W64-MSVC 1.1.5-b20240306
    # Origin: The File Cabinet BBS [filecabi.casacam.net:1025] (21:1/206)
    --- SBBSecho 3.24-Win32
    * Origin: The File Cabinet BBS [filecabi.casacam.net:1025] (21:1/206)
  • From RickV@21:1/206 to Gamgee on Sunday, March 30, 2025 18:22:54
    Hello Gamgee.

    11 Jul 70 14:19, you wrote to Rick V:

    Rick V wrote to Gamgee <=-

    Re: Re: Bad packets
    By: Gamgee to RickV on Sun Mar 30 2025 12:37:36

    Yep, OK... but sure looks like you're posting from SBBS... ^^^

    Well I was, but the question was in a Mystic echo about a Mystic
    packet problem.

    To be fair, you NEVER said a single word about it being a "Mystic"
    packet problem.

    In fact, just a few days ago, you were asking this EXACT same question
    in the SBBS support forums on DoveNet, and specifically told
    Digitalman "that helps" when he explained in good detail how to troubleshoot this problem on SBBS. Let me know if you'd like me to
    quote some messages from there.

    So............. can you see why I was thinking you were asking about Synchronet?

    As a general rule, asking good/detailed/complete questions about
    something will get you good answers. Being vague and leaving out
    helpful information ... will not.



    ... Internal Error: The system has been taken over by sheep at line
    19960
    === MultiMail/Linux v0.52

    I guess we both made assumptions, I was in the Mystic echo and assumed that it would be viewed as a mystic question, and you saw it was a post FROM a SBBS system...

    RickV

    === GoldED+/W64-MSVC 1.1.5-b20240306
    # Origin: The File Cabinet BBS [filecabi.casacam.net:1025] (21:1/206)

    --- Mystic BBS v1.12 A49 2024/05/29 (Windows/64)
    * Origin: Altair IV BBS (21:1/206)