Skip to content
  • rswindell's avatar
    Packet Type-2e (FSC-39.4) support: · aace645d
    rswindell authored
    For packet creation, the only difference (from Type-2+) is with packets created
    from point nodes: the origNet field won't be set to 0xffff (as is the case with
    FSC-48, Type-2+ packets). The auxNet field is now always set to the originating
    net (ala Squish) when configured for Type-2+ packet generation.
    When importing Type-2e (FSC-39) packets, the detected/logged packet type may be
    reported as "2e" for valid "2+" packets. This is normal and expected when the
    originating node is not a point and the auxNet field is 0.
    The second set of orig/dest zone fields in a type 2e/2+ pkt header will
    now be used when importing if the old/QM orig/dest zone fields are 0.
    Also, the originating point field may now be imported even if the auxNet field
    is not used (origNet != 0xffff).
    
    New umask sbbsecho.ini configuration option (global), maybe used to over-ride
    the default *nix file creation mode mask (077), similar to sbbs.ini.
    aace645d