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
  • #279
Closed
Open
Issue created Jun 28, 2021 by John Dovey@BoonDock💬

Feature Request: Add "Route" functionality to PING robot

When doing PING (or trace) to determine routing, it would be handy to be able to specify what route the ping (or trace) should follow. There is an example implementation of this on 2:460/58. Sending that system (ping@2:460/58) a ping request, replies with the correct ping response, but adds the following:

---------- Help ------------------------------------------------------------
  Also, You may use the following commands in the Subject line:
  %RouteTo: <3D_address> - The Ping robot reply will be routed via
                           this node. It MUST be my password-protected link.
  %Links                 - Get the list of my password protected-links.
  -------- Example ---------------------------------------------
  From: BoonDock                        4:920/69
  To  : Ping                            2:460/58
  Subj: %RouteTo: 2:292/854
  --------------------------------------------------------------
   - The answer to this message will be routed via 2:292/854.
----------------------------------------------------------------------------

The addition of the %RouteTo: functionality would be fantastic.

Edited Jun 28, 2021 by John Dovey
Assignee
Assign to
Time tracking