1. Forum
  2. FidoNet
  3. SYNC SYSOPS

  • PACKET ISSUES

    From Daryl Stout@1:103/705 to ALL on Thu Apr 23 12:50:00 2020
    While I finally got the BBS back up (I'm still dodging severe weather
    in the midst of our spring tornado season), I've run into a problem with
    some of the FTN Networks.

    I'm getting a ton of errors with SBBS Tossing some packets, saying it
    "can't determine packet type".

    2020-04-21 14:38:14 ERROR determining type of archive: c:\irex229\secure\0ccbb6ce.mo0
    2020-04-21 14:38:14
    !Unpack failure: c:\irex229\secure\0ccbb6ce.mo0
    2020-04-21 14:38:14 Unpacking bundle: c:\irex229\secure\5e54cac3.mo0
    (3.6KB)

    I have each one set to type 2+ and the archive at ZIP. All the bad
    packets have been renamed with a .bad suffix.

    Is there a way to view what type of packet it is, or are they lost??

    2020-04-15 09:24:52 FIDONET-RBERRYPI: Unrecognized internal code,
    assumed pass thru

    I may end up redoing the AREAFIX data and Message Area deals in SCFG,
    as I've got a lot of errors like this one.

    Daryl

    ---
    * OLX 1.53 * If you put root beer in a square mug, is it now beer??
    * Synchronet * The Thunderbolt BBS - tbolt.synchro.net
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Daryl Stout on Thu Apr 23 22:39:35 2020
    Re: PACKET ISSUES
    By: Daryl Stout to ALL on Thu Apr 23 2020 12:50 pm

    While I finally got the BBS back up (I'm still dodging severe weather
    in the midst of our spring tornado season), I've run into a problem with some of the FTN Networks.

    I'm getting a ton of errors with SBBS Tossing some packets, saying it "can't determine packet type".

    2020-04-21 14:38:14 ERROR determining type of archive:

    "type of archive" is different than "packet type".

    c:\irex229\secure\0ccbb6ce.mo0
    2020-04-21 14:38:14
    !Unpack failure: c:\irex229\secure\0ccbb6ce.mo0
    2020-04-21 14:38:14 Unpacking bundle: c:\irex229\secure\5e54cac3.mo0
    (3.6KB)

    I have each one set to type 2+ and the archive at ZIP. All the bad
    packets have been renamed with a .bad suffix.

    That's a bundle, not a packet. If you use a hex viewer and look at the few several bytes of the file, that's how you determine what kind of archive type it is. This is a ZIP archive:
    00000000 50 4b 03 04 14 00 00 00 08 00 cd b9 fe 3e 73 17 |PK...........>s.|

    Is there a way to view what type of packet it is, or are they lost??

    Likely recoverable. Just got to determine what type of archive it is and make sure you have that achive type configured in sbbsecho.cfg/echocfg. Or just extract the packets within into your inbound and SBBSecho will toss them.

    2020-04-15 09:24:52 FIDONET-RBERRYPI: Unrecognized internal code,
    assumed pass thru

    I may end up redoing the AREAFIX data and Message Area deals in SCFG,
    as I've got a lot of errors like this one.

    Look at your internal codes in SCFG->Message Areas. Sounds like you've got a mismatch or you removed that sub from SCFG.

    digital man

    Synchronet "Real Fact" #26:
    The Synchronet Web Server was written predominantly by Stephen Hurd (Deuce). Norco, CA WX: 71.4oF, 53.0% humidity, 0 mph W wind, 0.00 inches rain/24hrs
    --- SBBSecho 3.10-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)