DOCSLIB.ORG

JNOS-2 “J” Version of Network Operating System This Document Rev:0 Is Matched to Software Rev 2.0 a Software Manual for the Owner / Administrator / User

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
JNOS-2 “J” Version of Network Operating System This Document Rev:0 Is Matched to Software Rev 2.0 a Software Manual for the Owner / Administrator / User Rev: 0.0.4 JNOS OWNERS MANUAL 08/24/06 THIS IS A PREVIEW COPY OF A DOCUMENT UNDER DEVELOPMENT DRAFT - USE WITH CAUTION (REPORT ERRORS) JNOS-2 “J” version of Network Operating System This document rev:0 is matched to software rev 2.0 A software manual for the owner / administrator / user compiled by Skip VerDuin K8RRA [[email protected]] validated against JNOS2.0d [tbd] by Maiko Langelaar VE4KLM LICENCED: in the public domain under [tbd] based on work of MANY OTHERS (based in part on the NOS Reference Manual, by Phil Karn, KA9Q and Gerard van der Grinten, PA0GRI for jnos-1.11) DISCLAIMER ---------------- The authors make no guarantees, explicit or implied, about the functionality or any other aspect of this product. Refer to the manuals provided by the manufacturer of your equipment for installation procedures. This document is a compilation of the documentation of others. Selected documents applicable to JNOS software are included, the content is then validated specifically against the referenced software on the Linux platform, the text is modified as required to be faithful to the application design intent. Variances on other platforms are shown as differences. Permission from original authors is sought, and all inclusions are displayed in the two part bibliography. COPYRIGHTS AND TRADEMARKS; Unix is a Registered Trademark of AT&T. Linux is a Registered Trademark by Linus Torvalds. NET.EXE program (C) Copyright 1992 by Phil R. Karn, KA9Q. JNOS is based on work (C) Copyright 1991 by Phil R. Karn, KA9Q, and other contributors. JNOS (C) Copyright 1994 by Johan K. Reinalda, WG7J NET/ROM software (C) Copyright 1987 Software 2000, Inc. NET/ROM is a trademark of Software 2000, Inc. OS/2 is a registered trademark of International Business Machines,Inc. MS-DOS, Windows 3.0, Windows 3.1, Windows NT, and Microsoft Word are all registered trademarks of Microsoft, Inc. jdoc2.0.0.4.odt Doc ID: DRAFT [JNOS-2.0d] Page 1 of 158 Rev: 0.0.4 JNOS OWNERS MANUAL 08/24/06 Table of Contents INTRODUCTION..........................................................................................................................................................................3 TERMINOLOGY......................................................................................................................................................................................................................4 BBS [MAIL & GATEWAY] USER..............................................................................................................................................5 BBS ACCESS...........................................................................................................................................................................................................................5 BBS [USER] COMMANDS.....................................................................................................................................................................................................6 BBS SERVICES......................................................................................................................................................................................................................13 How to Connect to Another Node....................................................................................................................................................................................13 Manually connect to another station via RF on HF ...............................................................................................................................................................................................................................13 Posting E-Mail..................................................................................................................................................................................................................15 Forward to another BBS.........................................................................................................................................................................................................................................................................16 How to get JNOS to forward to WinLink 2000 (WL2K) systems.........................................................................................................................................................................................................16 Transer of ASCII File Material........................................................................................................................................................................................16 SYSTEM ADMINISTRATION [SYSOP] USER.......................................................................................................................17 STARTING JNOS MANUALLY...........................................................................................................................................................................................17 Environmental Variables..................................................................................................................................................................................................18 CONSOLE: STATUS DISPLAY ..........................................................................................................................................................................................20 SYSTEM [SYSOP] COMMANDS.........................................................................................................................................................................................21 ROUTINE TASKS..................................................................................................................................................................................................................96 User passwords and permissions......................................................................................................................................................................................96 Initiate forwarding (and/or reverse forwarding) .............................................................................................................................................................97 HF server side, accepting connections from REMOTE stations............................................................................................................................................................................................................98 Watching the JNOS log and reporting problems..............................................................................................................................................................98 Trace data management....................................................................................................................................................................................................99 File transfers via FTP ......................................................................................................................................................................................................99 INSTALLATION & CONFIGURATION...................................................................................................................................99 APPLICATION SOFTWARE AND FILE STRUCTURE.....................................................................................................................................................99 THE LINUX INSTALLER............................................................................................................................................................................................100 I/O CONFIGURATION........................................................................................................................................................................................................100 RF Ports..........................................................................................................................................................................................................................101 Configuring the TNC with standard KISS...........................................................................................................................................................................................................................................101 Configuring the Halcomm DXP38 Modem..........................................................................................................................................................................................................................................101 Configuring the SCS PTC II Pro Modem.............................................................................................................................................................................................................................................101 Customized AX25 cross port digipeating rules..............................................................................................................................................................103 Internet Ports..................................................................................................................................................................................................................104 Configuring
Load more

Recommended publications
  • Implementing MACA and Other Useful Improvements to Amateur Packet Radio for Throughput and Capacity
    Implementing MACA and Other Useful Improvements to Amateur Packet Radio for Throughput and Capacity John Bonnett – KK6JRA / NCS820 Steven Gunderson – CMoLR Project Manager TAPR DCC – 15 Sept 2018 1 Contents • Introduction – Communication Methodology of Last Resort (CMoLR) • Speed & Throughput Tests – CONNECT & UNPROTO • UX.25 – UNPROTO AX.25 • Multiple Access with Collision Avoidance (MACA) – Hidden Terminals • Directed Packet Networks • Brevity – Directory Services • Trunked Packet • Conclusion 2 Background • Mission County – Proverbial: – Coastline, Earthquake Faults, Mountains & Hills, and Missions – Frequent Natural Disasters • Wildfires, Earthquakes, Floods, Slides & Tsunamis – Extensive Packet Networks • EOCs – Fire & Police Stations – Hospitals • Legacy 1200 Baud Packet Networks • Outpost and Winlink 2000 Messaging Software 3 Background • Mission County – Proverbial: – Coastline, Earthquake Faults, Mountains & Hills, and Missions – Frequent Natural Disasters • Wildfires, Earthquakes, Floods, Slides & Tsunamis – Extensive Packet Networks • EOCs – Fire & Police Stations – Hospitals • Legacy 1200 Baud Packet Networks • Outpost and Winlink 2000 Messaging Software • Community Emergency Response Teams: – OK Drills – Neighborhood Surveys OK – Triage Information • CERT Form #1 – Transmit CERT Triage Data to Public Safety – Situational Awareness 4 Background & Objectives (cont) • Communication Methodology of Last Resort (CMoLR): – Mission County Project: 2012 – 2016 – Enable Emergency Data Comms from CERT to Public Safety 5 Background &
    [Show full text]
  • X.25: ITU-T Protocol for WAN Communications
    X.25: ITU-T Protocol for WAN Communications X.25, an ITU-T protocol for WAN communications, is a packet switched data network protocol which defines the exchange of data as well as control information between a user device, called Data Terminal Equipment (DTE) and a network node, called Data Circuit Terminating Equipment (DCE). X.25 is designed to operate effectively regardless of the type of systems connected to the network. X.25 is typically used in the packet-switched networks (PSNs) of common carriers, such as the telephone companies. Subscribers are charged based on their use of the network. X.25 utilizes a Connection-Oriented service which insures that packets are transmitted in order. X.25 sessions are established when one DTE device contacts another to request a communication session. The DTE device that receives the request can either accept or refuse the connection. If the request is accepted, the two systems begin full-duplex information transfer. Either DTE device can terminate the connection. After the session is terminated, any further communication requires the establishment of a new session. X.25 uses virtual circuits for packets communications. Both switched and permanent virtual circuits are used. X.75 is the signaling protocol for X.25, which defines the signaling system between two PDNs. X.75 is essentially an Network to Network Interface (NNI). X.25 protocol suite comes with three levels based on the first three layers of the OSI seven layers architecture. The Physical Level: describes the interface with the physical environment. There are three protocols in this group: 1) X.21 interface operates over eight interchange circuits; 2) X.21bis defines the analogue interface to allow access to the digital circuit switched network using an analogue circuit; 3) V.24 provides procedures which enable the DTE to operate over a leased analogue circuit connecting it to a packet switching node or concentrator.
    [Show full text]
  • Virtual-Circuit Networks: Frame Relay Andatm
    CHAPTER 18 Virtual-Circuit Networks: Frame Relay andATM In Chapter 8, we discussed switching techniques. We said that there are three types of switching: circuit switching, packet switching, and message switching. We also men­ tioned that packet switching can use two approaches: the virtual-circuit approach and the datagram approach. In this chapter, we show how the virtual-circuit approach can be used in wide-area networks. Two common WAN technologies use virtual-circuit switching. Frame Relay is a relatively high-speed protocol that can provide some services not available in other WAN technologies such as DSL, cable TV, and T lines. ATM, as a high-speed protocol, can be the superhighway of communication when it deploys physical layer carriers such as SONET. We first discuss Frame Relay. We then discuss ATM in greater detaiL Finally, we show how ATM technology, which was originally designed as a WAN technology, can also be used in LAN technology, ATM LANs. 18.1 FRAME RELAY Frame Relay is a virtual-circuit wide-area network that was designed in response to demands for a new type ofWAN in the late 1980s and early 1990s. 1. Prior to Frame Relay, some organizations were using a virtual-circuit switching network called X.25 that performed switching at the network layer. For example, the Internet, which needs wide-area networks to carry its packets from one place to another, used X.25. And X.25 is still being used by the Internet, but it is being replaced by other WANs. However, X.25 has several drawbacks: a.
    [Show full text]
  • Kenwood TH-D74A/E Operating Tips
    1 Copyrights for this Manual JVCKENWOOD Corporation shall own all copyrights and intellectual properties for the product and the manuals, help texts and relevant documents attached to the product or the optional software. A user is required to obtain approval from JVCKENWOOD Corporation, in writing, prior to redistributing this document on a personal web page or via packet communication. A user is prohibited from assigning, renting, leasing or reselling the document. JVCKENWOOD Corporation does not warrant that quality and functions described in this manual comply with each user’s purpose of use and, unless specifically described in this manual, JVCKENWOOD Corporation shall be free from any responsibility for any defects and indemnities for any damages or losses. Software Copyrights The title to and ownership of copyrights for software, including but not limited to the firmware and optional software that may be distributed individually, are reserved for JVCKENWOOD Corporation. The firmware shall mean the software which can be embedded in KENWOOD product memories for proper operation. Any modifying, reverse engineering, copying, reproducing or disclosing on an Internet website of the software is strictly prohibited. A user is required to obtain approval from JVCKENWOOD Corporation, in writing, prior to redistributing this manual on a personal web page or via packet communication. Furthermore, any reselling, assigning or transferring of the software is also strictly prohibited without embedding the software in KENWOOD product memories. Copyrights for recorded Audio The software embedded in this transceiver consists of a multiple number of and individual software components. Title to and ownership of copyrights for each software component is reserved for JVCKENWOOD Corporation and the respective bona fide holder.
    [Show full text]
  • Examining Ambiguities in the Automatic Packet Reporting System
    Examining Ambiguities in the Automatic Packet Reporting System A Thesis Presented to the Faculty of California Polytechnic State University San Luis Obispo In Partial Fulfillment of the Requirements for the Degree Master of Science in Electrical Engineering by Kenneth W. Finnegan December 2014 © 2014 Kenneth W. Finnegan ALL RIGHTS RESERVED ii COMMITTEE MEMBERSHIP TITLE: Examining Ambiguities in the Automatic Packet Reporting System AUTHOR: Kenneth W. Finnegan DATE SUBMITTED: December 2014 REVISION: 1.2 COMMITTEE CHAIR: Bridget Benson, Ph.D. Assistant Professor, Electrical Engineering COMMITTEE MEMBER: John Bellardo, Ph.D. Associate Professor, Computer Science COMMITTEE MEMBER: Dennis Derickson, Ph.D. Department Chair, Electrical Engineering iii ABSTRACT Examining Ambiguities in the Automatic Packet Reporting System Kenneth W. Finnegan The Automatic Packet Reporting System (APRS) is an amateur radio packet network that has evolved over the last several decades in tandem with, and then arguably beyond, the lifetime of other VHF/UHF amateur packet networks, to the point where it is one of very few packet networks left on the amateur VHF/UHF bands. This is proving to be problematic due to the loss of institutional knowledge as older amateur radio operators who designed and built APRS and other AX.25-based packet networks abandon the hobby or pass away. The purpose of this document is to collect and curate a sufficient body of knowledge to ensure the continued usefulness of the APRS network, and re-examining the engineering decisions made during the network's evolution to look for possible improvements and identify deficiencies in documentation of the existing network. iv TABLE OF CONTENTS List of Figures vii 1 Preface 1 2 Introduction 3 2.1 History of APRS .
    [Show full text]
  • Mind the Uppercase Letters
    Integration of APRS Network with SDI Tomasz Kubik1,2, Wojciech Penar1 1 Wroclaw University of Technology 2 Wroclaw University of Environmental and Life Sciences Abstract. From the point of view of large information systems designers the most important thing is a certain abstraction enabling integration of heterogeneous solutions. Abstraction is associated with the standardization of protocols and interfaces of appropriate services. Behind this façade any device or sensor system may be hidden, even humans recording their measurements. This study presents selected topics and details related to two families of standards developed by OGC: OpenLS and SWE. It also dis- cusses the technical details of a solution built to intercept radio messages broadcast in the APRS network with telemetric information and weather conditions as payload. The basic assumptions and objectives of a prototype system that integrates elements of the APRS network and SWE are given. Keywords: SWE, OpenLS, APRS, SDI, web services 1. Introduction Modern measuring devices are no longer seen as tools for qualitative and quantitative measurements only. They have become parts of highly special- ized solutions, used for data acquisition and post-processing, offering hardware and software interfaces for communication. In the construction of these solutions the latest technologies from various fields are employed, including optics, precision mechanics, satellite and information technolo- gies. Thanks to the Internet and mobile technologies, several architectural and communication barriers caused by the wiring and placement of the sensors have been broken. Only recently the LBS (Location-Based Services) entered the field of IT. These are information services, available from mo- bile devices via mobile networks, giving possibility of utilization of a mobile This work was supported in part by the Polish Ministry of Science and Higher Edu- cation with funds for research for the years 2010-2013.
    [Show full text]
  • Multiprotocol Label Switching
    CHAPTER23 MULTIPROTOCOL LABEL SWITCHING 23.1 The Role of Mpls 23.2 Background Connection-Oriented QoS Support Traffic Engineering Virtual Private Network (VPN) Support Multiprotocol Support 23.3 MPLS Operation 23.4 Labels Label Stacking Label Format Label Placement 23.5 FECs, LSPs, and Labels Route Selection 23.6 Label Distribution Requirements for Label Distribution Label Distribution Protocol LDP Messages LDP Message Format 23.7 Traffic Engineering Elements of MPLS Traffic Engineering Constrained Shortest-Path First Algorithm RSVP-TE 23.8 Virtual Private Networks Layer 2 Virtual Private Network Layer 3 Virtual Private Network 23.9 Recommended Reading 23.10 Key Terms, Review Questions, and Problems 749 750 CHAPTER 23 / MULTIPROTOCOL LABEL SWITCHING LEARNING OBJECTIVES After studying this chapter, you should be able to: ◆ Discuss the role of MPLS in an Internet traffic management strategy. ◆ Explain at a top level how MPLS operates. ◆ Understand the use of labels in MPLS. ◆ Present an overview of how the function of label distribution works. ◆ Present an overview of MPLS traffic engineering. ◆ Understand the difference between layer 2 and layer 3 VPNs. In Chapter 19, we examined a number of IP-based mechanisms designed to improve the performance of IP-based networks and to provide different levels of quality of service (QoS) to different service users. Although the routing protocols discussed in Chapter 19 have as their fundamental purpose dynami- cally finding a route through an internet between any source and any destina- tion, they also provide support for performance goals in two ways: 1. Because these protocols are distributed and dynamic, they can react to congestion by altering routes to avoid pockets of heavy traffic.
    [Show full text]
  • Networking CS 3470, Section 1 Forwarding
    Chapter 3 Part 3 Switching and Bridging Networking CS 3470, Section 1 Forwarding A switching device’s primary job is to receive incoming packets on one of its links and to transmit them on some other link This function is referred as switching and forwarding According to OSI architecture this is the main function of the network layer Forwarding How does the switch decide which output port to place each packet on? It looks at the header of the packet for an identifier that it uses to make the decision Two common approaches Datagram or Connectionless approach Virtual circuit or Connection-oriented approach Forwarding Assumptions Each host has a globally unique address There is some way to identify the input and output ports of each switch We can use numbers We can use names Datagram / Connectionless Approach Key Idea Every packet contains enough information to enable any switch to decide how to get it to destination Every packet contains the complete destination address Datagram / Connectionless Approach An example network To decide how to forward a packet, a switch consults a forwarding table (sometimes called a routing table) Copyright © 2010, Elsevier Inc. All rights Reserved Datagram / Connectionless Approach Destination Port ----------------------------------- A 3 B 0 C 3 D 3 E 2 F 1 G 0 H 0 Forwarding Table for Switch 2 Copyright © 2010, Elsevier Inc. All rights Reserved Datagram Networks: The Internet Model No call setup at network layer Routers: no state about end-to-end connections no network-level concept of “connection” Packets forwarded using destination host address packets between same source-dest pair may take different paths session session transport transport network network 1.
    [Show full text]
  • Future of Asynchronous Transfer Mode Networking
    California State University, San Bernardino CSUSB ScholarWorks Theses Digitization Project John M. Pfau Library 2004 Future of asynchronous transfer mode networking Fakhreddine Mohamed Hachfi Follow this and additional works at: https://scholarworks.lib.csusb.edu/etd-project Part of the Digital Communications and Networking Commons Recommended Citation Hachfi, akhrF eddine Mohamed, "Future of asynchronous transfer mode networking" (2004). Theses Digitization Project. 2639. https://scholarworks.lib.csusb.edu/etd-project/2639 This Thesis is brought to you for free and open access by the John M. Pfau Library at CSUSB ScholarWorks. It has been accepted for inclusion in Theses Digitization Project by an authorized administrator of CSUSB ScholarWorks. For more information, please contact [email protected]. FUTURE OF ASYNCHRONOUS TRANSFER MODE NETWORKING A Thesis Presented to the Faculty of California State University, San Bernardino In Partial Fulfillment of the Requirements for the Degree Master of Business Administration by ' Fakhreddine Mohamed Hachfi June 2004 FUTURE OF ASYNCHRONOUS TRANSFER MODE NETWORKING A Thesis Presented to the Faculty of California State University, San Bernardino by Fakhreddine Mohamed Hachfi June 2004 Approved by: Da^e Frank Lin, Ph.D., Inf ormatTdn—&^-DSsision Sciences „ / Walt Stewart, Jr., Ph.D., Department Chair Information & Decision Sciences © 2004 Fakhreddine Mohamed Hachfi ABSTRACT The growth of Asynchronous Transfer Mode ATM was considered to be the ideal carrier of the high bandwidth applications like video on demand and multimedia e-learning. ATM emerged commercially in the beginning of the 1990's. It was designed to provide a different quality of service at a speed up to 10 Gbps for both real time and non real time application.
    [Show full text]
  • Linux Amateur Radio AX.25 HOWTO
    Linux Amateur Radio AX.25 HOWTO Jeff Tranter, VE3ICH [email protected] v2.0, 19 September 2001 The Linux operating system is perhaps the only operating system in the world that can boast native and standard support for the AX.25 packet radio protocol utilized by Amateur Radio operators worldwide. This document describes how to install and configure this support. Linux Amateur Radio AX.25 HOWTO Table of Contents 1. Introduction.....................................................................................................................................................1 1.1. Changes from the previous version...................................................................................................1 1.2. Where to obtain new versions of this document...............................................................................1 1.3. Other related documentation.............................................................................................................1 2. The Packet Radio Protocols and Linux........................................................................................................3 2.1. How it all fits together......................................................................................................................3 3. The AX.25/NET/ROM/ROSE software components...................................................................................5 3.1. Finding the kernel, tools and utility packages..................................................................................5 3.1.1. The
    [Show full text]
  • Pactor Brochure
    SCS PTC-II Radio Modem HF / VHF / UHF Up to 30 times faster than AMTOR, up to 6 times faster than PACTOR I Send email, transfer files, real-time data links. The PTC-II modem from Special Communications Systems is the data interface between your PC and radio equipment. From the German developers of the PACTOR I protocol comes PACTOR II, the most robust digital mode available. The PTC-II will maintain links in conditions with signal to noise ratios of minus 18 dB. That means data transfer with absolutely inaudible signals. Test proven with a 16 milliwatt link between Europe and Australia! The PTC-II is fully backwards compatible with all known PACTOR I implementations. Powered by a powerful Motorola CPU and DSP (digital signal processing), the PTC-II stands out as superior technology for HF radio data transfers. With optional Packet radio options for VHF/UHF 9600+ baud rates can be employed. backview Simple installation with compatible radios from Icom, Kenwood, Yaesu, SGC, SEA, Furuno, R&S and others. Use the PTC-II with commercial stations WLO, SailMail and others, as well as the international network of amateur radio opetators that support Pactor II. PC software for Windows or DOS. Desktop Or RCU Laptop PC Remote Remote Control controled PTC-II Win95 / 498 devices: Unit (optional) antenna or DOS rotor, lights, contact closures, external sensors, Radio control via Audio in/out, PTT etc! RS-232 (optional) and B+ to PTC-II VHF or UHF VHF or UHF transceiver for use transceiver for use Marine, Commercial or Amateur with Packet AFSK with Packet FSK module (optional) module (optional) HF SSB Transceiver Amateur • Commercial • Industrial • Marine Special Communications Systems GmbH Rontgenstr.
    [Show full text]
  • (Pdf) Download
    1 2 • Winlink programs group: “Official Group to support Winlink Team developed Products, both user and gateway software” • Winlink_for_EmComm: “Supports the discussion and use of the Winlink network and Winlink products for emergency or event support communications. ” 3 4 5 6 7 8 1. Digital voice radio works in exactly the same fashion, except that it deals with audio input, not text. 2. PACKET-1200 uses frequency shift keying (FSK) modulation with a 1000Hz shift and 1200 Bd symbol rate. There are a number of variations for PACKET-1200, including a PSK-based satellite version. PACKET-1200 can be seen in the VHF and UHF bands with indirect FM Modulation. FM bandwidth is 12 kHz. 3. See https://www.sigidwiki.com/wiki/PACKET#PACKET-1200 9 10 11 12 • That’s the packet sound • Each individual packet! • Carrier detect • ”NAK” = “NO ACKNOWLEDGEMENT” – resend • ”ACK” – “ACKNOWLEDGEMENT” – send the next packet • Too many retries, and the sending station stops sending (connection is dropped) • Breaking the message into small packets makes it easier to send a large message. But ALL packets MUST be received in order for the message to be read, 13 • One bye = 8 bits = 1 alphanumeric character • See https://tapr.org/pub_ax25.html • FLAG: start and end of each packet • Address: sender, receiver, and the path in between • Control (CTRL): The control field is responsible for identifying the type of “frame” being sent, and is also used to convey commands and responses from one end of the link to the other in order to maintain proper link control • The length of DATA is ≤ 255, and is set by the use.
    [Show full text]