Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Synchronet Synchronet
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 224
    • Issues 224
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

This GitLab instance has migrated as of Nov-5-2022 to a new server: hardware, OS, SSH key

The v3.20a development branch has now been merged to the master branch. Sysops upgrading from earlier versions must run 'jsexec update'

  • MainMain
  • SynchronetSynchronet
  • Issues
  • #278
Closed
Open
Issue created Jun 28, 2021 by John Dovey@BoonDock💬

Feature Request: Add Trace functionality

At the bottom of every nodelist, there is a notice about the PING flag which states:

Nodes flying this flag will adhere to the following functionality:
;S
;S         1) PING-function:
;S         """""""""""""""""
;S             If a message destined to "PING" arrives at its final destination
;S             and this final destination flies the "PING"-flag, then the
;S             receiving node will bounce the message back to the original
;S             sender clearly displaying all the original via-lines.
;S
;S             If a message destined to "PING" arrives at its final destination
;S             but this final destination does _not_ fly the "PING"-flag then the
;S             message may be deleted from the inbound-queue without further
;S             follow-up.
;S
;S         2) TRACE-function:
;S         """"""""""""""""""
;S             If a message destined to "PING" arrives at a node which flies
;S             the PING-flag but is merely passing-through to another destination
;S             then the in-transit node will notify the sender of this occurence
;S             and will forward the original mail unaltered towards its final
;S             destination.

SBBS Supports the PING functionality (around line 4000 of sbbs.c), but doesn't report back when it is a pass-through system (aka TRACE)

There has also been some discussion about separating the TRACE and PING functions. Support for that would be nice.

Assignee
Assign to
Time tracking