packet:xrouter:manpages:examples:xroutercfg
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
packet:xrouter:manpages:examples:xroutercfg [2025/04/20 06:26] – m0mzf | packet:xrouter:manpages:examples:xroutercfg [2025/04/20 06:40] (current) – old revision restored (2025/04/19 19:42) m0mzf | ||
---|---|---|---|
Line 1: | Line 1: | ||
======= Example XROUTER.CFG ======= | ======= Example XROUTER.CFG ======= | ||
- | extracted from xrpi-503a-full-package | + | <file bash XROUTER.CFG> |
- | <file bash XROUTER.CFG># | + | # XROUTER.CFG - Main Configuration file for XRPi / XRLin v501c |
# | # | ||
- | # This file is read only when the program boots. | + | # XRPi reads this file only at bootup. |
# | # | ||
- | # This is a " | + | # !!! This is a non-functional EXAMPLE |
- | # if you like it. It may also come in handy as a known good config, so | + | # It is intended |
- | # you might like to save a copy somewhere before you modify it. | + | # settings, and MUST be edited |
# | # | ||
- | # It has been greatly simplified for clarity. There is an example | + | # You will need to replace MyCall, MyAlias, MyTown, MyLocation etc. |
- | # config | + | # with your own details, then configure |
+ | # suit your hardware. You may remove anything you don't require, but | ||
+ | # it is recommended that you keep an intact copy of this file for | ||
+ | # future reference. | ||
# | # | ||
- | # In order to do anything meaningful, you will need to configure some | + | # Keywords can be in almost any order, |
- | # INTERFACES and PORTS, and set up your own callsigns in place of the | + | # defined before ports. |
- | # examples provided. | + | |
# | # | ||
- | # It is suggested that you copy and paste the required options from | + | # Note some timings are in milliseconds, some are seconds. |
- | # the example file into this one, testing as you go along. Make | + | |
- | # incremental changes, not major ones!! | + | |
# | # | ||
- | #=================================================================== | + | # Lines must not exceed 255 characters in length. |
- | # | + | # Blank lines are allowed. |
- | # Primary Identity for AX25 & NetRom. | + | # Comment lines MUST begin with a semicolon ';' |
- | # | + | # the leftmost column. The recommended convention |
- | NODECALL=G9DUM-1 | + | # section headings and reference material, and ';' |
- | NODEALIAS=DUMMY | + | # keywords and making your own notes. |
- | # | + | |
- | # | + | |
- | # QTH specifies where the node is located. | + | |
- | # | + | |
- | #QTH=MyTown, MyCounty, MyCountry | + | |
# | # | ||
+ | |||
+ | |||
+ | ###################################################################### | ||
+ | # Station Identification | ||
+ | ###################################################################### | ||
# | # | ||
+ | # Node callsign: | ||
+ | # Up to 6 chars plus optional SSID between 1 and 15. | ||
+ | # This is the callsign used for all L3/4 operations, and the | ||
+ | # default for L2 operations on each port. | ||
+ | |||
+ | NODECALL=MyNodeCallsign | ||
+ | |||
+ | # Node alias: | ||
+ | # Up to 6 alphanumeric characters, with no SSID. | ||
+ | # Aliases beginning with "#" | ||
+ | # and are used for " | ||
+ | # You should preferably choose an alias which is geographically | ||
+ | # relevant beyond your own local area, for example BRSTOL, | ||
+ | # LEEDS, or BRUM are good, because users can recognise them in | ||
+ | # node tables, whereas GAB1 and WBA are bad - where on earth | ||
+ | # are they? | ||
+ | |||
+ | NODEALIAS=MyNodeAlias | ||
+ | |||
# Callsign for console operations. | # Callsign for console operations. | ||
# of NODECALL or you may set them the same. You may at any time | # of NODECALL or you may set them the same. You may at any time | ||
# override this callsign using the " | # override this callsign using the " | ||
+ | |||
+ | CONSOLECALL=MyCallsign | ||
+ | |||
+ | # Chat Server Identity: | ||
+ | # Note - the chat server is an integral part of the system and | ||
+ | # cannot be disabled. | ||
+ | # | ||
+ | # setting CHATCALL and CHATALIAS the same as NODECALL and | ||
+ | # | ||
+ | # the " | ||
# | # | ||
- | CONSOLECALL=G9DUM | + | # Chat server callsign. This may be the same as the nodecall, but |
- | # | + | # must use a different SSID, preferably -8. |
- | # | + | |
- | # | + | CHATCALL=MyNodeCallsign-8 |
- | # | + | |
- | # | + | # Alias for chat server (6 chars max). It is suggested that |
- | CHATCALL=MYNODE-8 | + | |
- | # | + | |
- | # | + | |
- | # | + | |
# this should end with " | # this should end with " | ||
# | # | ||
# Leeds etc., so it can be easily identified in node tables. | # Leeds etc., so it can be easily identified in node tables. | ||
+ | |||
+ | CHATALIAS=MyChatAlias | ||
+ | |||
+ | # Chat server quality to broadcast. | ||
+ | # This can be used to limit the NetRom visibility of your server | ||
+ | # to a sensible geographical area, and discourage chat server | ||
+ | # | ||
+ | # distance as nodecall. The value is only meaningful if BOTH | ||
+ | # CHATCALL and CHATALIAS are defined, otherwise nothing is | ||
+ | # | ||
+ | # netrom node if you wish to link it with other servers. | ||
+ | |||
+ | CHATQUAL=150 | ||
+ | |||
+ | # Callsign and alias of the integral Personal Mailbox (PMS): | ||
+ | # If you define NEITHER of these, the PMS will only be | ||
+ | # | ||
+ | # you set a suitable PMSQUAL, the PMS will be visible as a | ||
+ | # NetRom node. | ||
# | # | ||
- | CHATALIAS=DUMCHT | + | # The callsign may be the same as NODECALL, or it may be |
+ | # different (e.g. your own callsign). If you use the NODECALL, | ||
+ | # you must use a different SSID. A long standing convention is | ||
+ | # to use -2 as the SSID for personal mail systems. | ||
+ | |||
+ | PMSCALL=MyNodeCallsign-2 | ||
+ | |||
+ | # The PMS alias should preferably include " | ||
+ | # as a PMS in nodes tables (i.e. if PMSQUAL is non-zero). | ||
+ | |||
+ | PMSALIAS=MyPmsAlias | ||
+ | |||
+ | # PMS quality to include in Netrom nodes broadcast (0-255). | ||
+ | # The default is 0, i.e. no broadcast. You may only use a | ||
+ | # non-zero value if both PMSCALL and PMSALIAS are defined. | ||
+ | # The use of a non-zero value is deprecated unless you are using | ||
+ | # the PMS to provide a public maildrop / BBS. | ||
+ | |||
+ | ; | ||
+ | |||
+ | # Callsign for APRS IGATE (optional). | ||
+ | # This callsign is used by the Igate to identify itself in | ||
+ | # beacons and third party messages. | ||
+ | # the Nodecall. If you are not using the IGATE function, you do | ||
+ | # not need this parameter. | ||
+ | |||
+ | ; | ||
+ | |||
+ | |||
+ | ###################################################################### | ||
+ | # Station Location | ||
+ | ###################################################################### | ||
# | # | ||
+ | # QTH specifies (in words) where the node is located. | ||
+ | |||
+ | QTH=MyTown, MyRegion, MyCountry | ||
+ | |||
# | # | ||
- | # | + | # LOCATOR is your 6 or 8 character Maidenhead QTH locator, |
- | # Please keep it brief but informative. The end of text is marked | + | # e.g. " |
- | # by a line beginning *** | + | |
- | # | + | LOCATOR=CCnnCC |
+ | |||
+ | |||
+ | ###################################################################### | ||
+ | # Texts and Beacons | ||
+ | ###################################################################### | ||
+ | |||
+ | |||
+ | # | ||
+ | # (CTFLAGS controls which callers receive the text.) | ||
+ | # Please keep the text brief but informative. | ||
+ | # The end of text is marked by a line beginning | ||
CTEXT | CTEXT | ||
- | Dummy City AX25/IP Router | + | MyTown |
Type ? for list of commands. | Type ? for list of commands. | ||
*** | *** | ||
+ | |||
+ | # CTFLAGS controls which connects receive CTEXT. | ||
+ | # Add together the following numbers: | ||
# | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
# | # | ||
- | # This text is the response to the ' | + | # Default is 9 (Alias and TCP only). |
- | # | + | |
+ | ; CTFLAGS=1 | ||
+ | |||
+ | # The INFOTEXT | ||
+ | # give as much useful information as possible. Imagine yourself | ||
+ | # as a user who has reached your node from afar, and provide the | ||
+ | # sort of information that you would like to know. | ||
+ | The end of text is marked by a line beginning with *** | ||
INFOTEXT | INFOTEXT | ||
- | XRLin Packet Router, | + | |
+ | XRPi Packet Router, | ||
Sysop: Roger G9DUM @ GB7PZT ([email protected]) | Sysop: Roger G9DUM @ GB7PZT ([email protected]) | ||
To connect to the Dummy BBS, use the command: C GB7DUM | To connect to the Dummy BBS, use the command: C GB7DUM | ||
Line 74: | Line 182: | ||
Website: www.g9dum.com/ | Website: www.g9dum.com/ | ||
*** | *** | ||
- | # | + | |
- | # This ID message | + | # The IDTEXT |
- | # Only the first line is sent. | + | |
# If your APRS-format static position code is included, starting | # If your APRS-format static position code is included, starting | ||
- | # within the first 40 characters, you will be visible on APRS maps | + | # within the first 40 characters, you will be visible on APRS |
- | # and the MHeard function will record distances to heard stations. | + | # maps and the MHeard function will record distances to heard |
- | # The format is " | + | # stations. |
- | # of latitude/longitude and mm.mm represents minutes to two decimal | + | # represents degrees |
- | # places. " | + | # represents minutes to two decimal places. " |
- | # as appropriate. | + | # replaced by " |
- | # | + | |
# | # | ||
+ | # It is highly recommended that you include your position, but | ||
+ | # if you don't know your position, or you don't wish to use | ||
+ | # this facility please delete the position code rather tha | ||
+ | # transmit invalid information. | ||
+ | |||
IDTEXT | IDTEXT | ||
- | !5824.22N/ | + | !5824.22N/ |
*** | *** | ||
+ | |||
+ | ###################################################################### | ||
+ | # | ||
+ | ###################################################################### | ||
+ | |||
+ | # Core IP address for amprnet (44-net) IP routing. | ||
+ | # If you don't already have one, you may obtain one from your | ||
+ | # local amprnet IP co-ordinator. | ||
+ | # If you don't wish to route IP, comment this out or set it to | ||
+ | # 0.0.0.0. | ||
+ | # This IP address is " | ||
+ | # | ||
+ | |||
+ | ; | ||
+ | |||
+ | # Host name for TCP (optional). | ||
+ | # to " | ||
+ | |||
+ | ; | ||
+ | |||
+ | # IP address(es) of " | ||
+ | # This is only required if you don't wish to use Linux' | ||
+ | # You may specify more than one DNS by including more than one | ||
+ | # DNS directive. If you don't specify any servers, domain | ||
+ | # | ||
+ | # there is no connectivity to a suitable DNS, resolution will | ||
+ | # use DOMAIN.SYS only. | ||
+ | |||
+ | ; | ||
+ | |||
+ | # IPTTL overrides the default "Time To Live" (TTL) of 255. This | ||
+ | # is the maximum number of hops an IP datagram can make before | ||
+ | # it is killed. | ||
+ | # | ||
+ | # routed packets may easily make 20 or 30 hops, so don't set it | ||
+ | # too low. Ignore this if you haven' | ||
+ | |||
+ | ; IPTTL=100 | ||
+ | |||
+ | # Max entries in domain cache (default 10) | ||
+ | # This is a hang-over from the days when the XRouter program and | ||
+ | # all its data had to fit into 640kb DOS memory! You may set it | ||
+ | # much larger on XRPi, although a very large cache is probably | ||
+ | # | ||
+ | # hostnames used by your AX*P links. | ||
+ | |||
+ | DCACHE=20 | ||
+ | |||
+ | # Maximum no. of entries in Address Resolution Protocol (ARP) | ||
+ | # table (default 20). | ||
+ | |||
+ | ;MAXARP=20 | ||
+ | |||
+ | # Maximum simultaneous TCP connections. | ||
+ | |||
+ | ;MAXTCP=25 | ||
+ | |||
+ | # UDP port for IP over UDP encapsulation (default=94) | ||
+ | # Use this to reassign the port if another application is using | ||
+ | # port 94. | ||
+ | |||
+ | ; | ||
+ | |||
+ | # Enable IPIP (protocol 94) via Linux IP stack (default=0) | ||
+ | # You only need this if you want to receive IPIP encapsulated | ||
+ | # datagrams from other systems via the Linux stack. IPIP via | ||
+ | # | ||
+ | |||
+ | ;IPIP=1 | ||
+ | |||
+ | # Enable IPENCAP (protocol 4) via Linux IP stack (default=0) | ||
+ | # You only need this if you want to receive IPENCAP encapsulated | ||
+ | # datagrams from other systems via the Linux stack. IPIP via | ||
+ | # | ||
+ | |||
+ | ;IPENCAP=1 | ||
+ | |||
+ | ###################################################################### | ||
+ | # TCP Service Ports # | ||
+ | ###################################################################### | ||
+ | # | ||
+ | # By default, all services are enabled on XRPi's own TCP/IP stack | ||
+ | # (see STACKS manual entry). | ||
+ | # | ||
+ | # If you are NOT using an EXTERNAL interface for connectivity with | ||
+ | # the outside, these services are also enabled on the Linux stack. | ||
+ | # | ||
+ | # But if you ARE using the EXTERNAL interface for that purpose, | ||
+ | # these services will NOT be available via the Linux stack unless | ||
+ | # you explicitly enable them. | ||
+ | # | ||
+ | # You may reassign or disable services using the following | ||
+ | # | ||
+ | # on the Linux stack). A setting of 0 disables a service. It | ||
+ | # is unlikely that you would need to reassign or disable any | ||
+ | # services that use XRPi's own stack, as they do not interfere | ||
+ | # with Linux. | ||
+ | # | ||
+ | # If you supply a single argument, that value is used as follows: | ||
+ | # | ||
+ | # - If you are using the EXTERNAL interface, the argument applies | ||
+ | # only to the XRPi stack. | ||
+ | # | ||
+ | # - If you are not using the EXTERNAL interface, the argument | ||
+ | # applies to BOTH stacks. | ||
+ | # | ||
+ | # If you supply TWO arguments, the first always applies to | ||
+ | # | ||
+ | # supply different numbers for each stack, or disable one and | ||
+ | # not the other. | ||
+ | # NOT commas. See TCP-PORTS manual entry for more information. | ||
+ | # | ||
+ | ###################################################################### | ||
+ | |||
+ | # ECHO Server Port (default=7) | ||
+ | # This server echoes anything it receives back to the sender, | ||
+ | # which is useful for testing. | ||
+ | |||
+ | ECHOPORT=7 0 | ||
+ | |||
+ | # DISCARD Server Port (default=9) | ||
+ | # This is a " | ||
+ | # it, which is useful for testing. | ||
+ | |||
+ | DISCARDPORT=9 0 | ||
+ | |||
+ | # FTP Server Port (default=21) | ||
+ | # File Transfer Protocol server, for use by sysops. | ||
+ | |||
+ | FTPPORT=21 21 | ||
+ | |||
+ | # Telnet Server Port (default=23) | ||
+ | # Allows users to connect to XRPi using a Telnet client. | ||
+ | |||
+ | TELNETPORT=23 23 | ||
+ | |||
+ | # Finger Server Port (default=79) | ||
+ | # Serves files from the FINGER directory. | ||
+ | |||
+ | FINGERPORT=79 79 | ||
+ | |||
+ | # HTTP Server Port (default=80) | ||
+ | # Serves files from the HTTP directory, and runs basic commands. | ||
+ | |||
+ | HTTPPORT=80 80 | ||
+ | |||
+ | # TTYLINK Server Port (default=87) | ||
+ | # This is basically another Telnet server. | ||
+ | |||
+ | TTYLINKPORT=87 87 | ||
+ | |||
+ | # RLogin (Remote Login) Port (default=513) | ||
+ | # This is a telnet server for sysop access only. | ||
+ | |||
+ | RLOGINPORT=513 513 | ||
+ | |||
+ | # SOCKS Proxy Port (default=1080) | ||
+ | # Circuit level proxy, allowing applications to work through a | ||
+ | # firewall. Was used in DOS version when it was used as an | ||
+ | # Internet Connection Sharing router / firewall. Probably not of | ||
+ | # much use in Linux version. | ||
+ | |||
+ | SOCKSPORT=0 | ||
+ | |||
+ | # APRS Server Port (default=1448) | ||
+ | # This server is for use by APRS clients such as UI-View. It | ||
+ | # serves any APRS data sent or received by RF ports and Igate. | ||
+ | |||
+ | APRSPORT=1448 1448 | ||
+ | |||
+ | # Telnet Proxy Server Port (default=2323). | ||
+ | # Allows a TCP/IP application to make a full BINARY (as opposed | ||
+ | # to TELNET) connection to an AX25 or NetRom destination. | ||
+ | |||
+ | TELPROXYPORT=2323 2323 | ||
+ | |||
+ | # Chat Server Port (default=3600) | ||
+ | # Allows Telnet connections to XRPi's chat server. | ||
+ | |||
+ | CHATPORT=3600 3600 | ||
+ | |||
+ | # AGW Emulation Port (default=8000) | ||
+ | # For use by applications that are designed to use AGW Packet | ||
+ | # Engine. | ||
+ | |||
+ | AGWPORT=8000 8000 | ||
+ | |||
+ | # Remote Application Server Port (default=9000) | ||
+ | # There are currently no publicly available RHP applications, | ||
+ | # you may disable this. | ||
+ | |||
+ | RHPPORT=0 | ||
+ | |||
+ | |||
+ | ###################################################################### | ||
+ | # Consoles and display | ||
+ | ###################################################################### | ||
+ | # | ||
+ | # You may have up to 5 " | ||
+ | # may conduct independent sessions. | ||
+ | # using Alt-1 through alt-5, or the left and right arrow keys. | ||
+ | # Setting this to 0 disables all console activity. | ||
+ | |||
+ | NUMCONSOLES=3 | ||
+ | |||
+ | # Console Colour Settings: | ||
+ | # | ||
+ | # Note the default colours have been chosen for their relative | ||
+ | # | ||
+ | # are not legible. Permissible colour names are: | ||
+ | # | ||
+ | # Dark: BLACK, NAVY, GREEN, CYAN, RED, MAGENTA, ORANGE, SILVER | ||
+ | # Light: GREY, BLUE, LIME, TURQUOISE, PINK, CERISE, YELLOW, WHITE | ||
+ | # | ||
+ | # | ||
+ | # Default Settings: | ||
+ | # The following directives specify the colours used for the | ||
+ | # CONSOLES. They may be overridden on a console-by-console | ||
+ | # basis if you want each comsole to look different for instance. | ||
+ | |||
+ | # Top status bar background colour (default = CYAN) | ||
+ | # It is recommended that you avoid SILVER here, otherwise the | ||
+ | # status bar will be inditinguishable from the menu bar above. | ||
+ | |||
+ | ; | ||
+ | |||
+ | # Top status bar text colour (default = WHITE) | ||
+ | |||
+ | ; | ||
+ | |||
+ | # Main window background colour (default = BLACK) | ||
+ | |||
+ | ; | ||
+ | |||
+ | # Main window text colour (default = WHITE) | ||
+ | # This is the colour used to send command responses to you. | ||
+ | |||
+ | ; | ||
+ | |||
+ | # Command line background colour (default = NAVY) | ||
+ | |||
+ | ; | ||
+ | |||
+ | # Command line text colour (default = YELLOW) | ||
+ | |||
+ | ; | ||
+ | |||
+ | # Bottom menu bar background colour (default = CYAN) | ||
+ | |||
+ | ; | ||
+ | |||
+ | # Bottom menu bar text colour (default = WHITE) | ||
+ | |||
+ | ; | ||
+ | |||
+ | # Colour for outgoing (transmitted) data (default = PINK) | ||
+ | |||
+ | ; | ||
+ | |||
+ | # Colour for incoming (received) data (default = LIME) | ||
+ | |||
+ | ; | ||
+ | |||
+ | # Colour used for echoing Sysop' | ||
+ | # (default = YELLOW) | ||
+ | |||
+ | ; | ||
+ | |||
+ | # Monitor Mask: | ||
+ | # Specifies the protocols which are traced (by default) when | ||
+ | # tracing is enabled by <F2> or "MON ON". This can be | ||
+ | # | ||
+ | # time using the MMASK command or the <F4> key. The default | ||
+ | # is 3f8. | ||
+ | # The argument is a HEX number between 0000h and FFFFh, | ||
+ | # which is calculated by adding together the desired values from | ||
+ | # this table: | ||
+ | |||
+ | 0001 - Incoming frames | ||
+ | 0002 - Outgoing frames | ||
+ | 0004 - AX25 layer 2 0400 - KISS | ||
+ | 0008 - AX25 info frames | ||
+ | 0010 - AX25 layer 3 1000 - PASSALL | ||
+ | 0020 - AX25 layer 4 2000 - Hex Dump | ||
+ | 0040 - IP frames | ||
+ | 0080 - ARP frames | ||
+ | |||
+ | ;MMASK=3f8 | ||
+ | |||
+ | # Monitor Ports: | ||
+ | # Specifies which port(s) are monitored (by default) when | ||
+ | # tracing is enabled by <F2> or "MON ON". This can be overridden | ||
+ | # in a CONSOLE definition block, or changed at run time using | ||
+ | # the MPORT command or the <F3> key. The default action is to | ||
+ | # monitor all ports. | ||
+ | # The argument is either the words " | ||
+ | # single port numbers or ranges thereof, without any spaces. | ||
+ | |||
+ | ; | ||
+ | |||
+ | # Console Overrides | ||
+ | # | ||
+ | # The default console settings above may be overridden on a | ||
+ | # | ||
+ | # block as shown in the gaudy example below. | ||
+ | # which differ from the globals defined above need be specified. | ||
+ | # | ||
+ | # console. Consoles are numbered from 1 to 5. | ||
+ | |||
+ | ;CONSOLE=3 | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ;ENDCONSOLE | ||
+ | |||
+ | |||
+ | # | ||
+ | # Set the hours during which the console bells may sound. | ||
+ | # are the two tone connection (low-> | ||
+ | # | ||
+ | # paging sound, and the various bells associated with sysop | ||
+ | # chat. Console bells use the PC speaker, not the soundcard. | ||
+ | # (Not working in XRPi) | ||
+ | |||
+ | ; | ||
+ | |||
+ | |||
+ | ###################################################################### | ||
+ | # Chat Server Parameters | ||
+ | ###################################################################### | ||
+ | |||
+ | # List of chat servers to which our server will link. | ||
+ | # | ||
+ | # must place your CHATCALL in their CHATLINKS list. | ||
+ | # | ||
+ | # | ||
+ | # your users will get poor service. | ||
+ | # | ||
+ | # XRchat links may use TCP/IP or NetRom. NetRom is the norm. | ||
+ | # For NetRom links, you must supply the *callsigns* not the | ||
+ | # aliases, and you may only use partners who exist in your | ||
+ | # NetRom nodes table. | ||
+ | # | ||
+ | # For TCP/IP links, the IP address and TCP " | ||
+ | # be specified, along with the CHATALIAS or server ID of the | ||
+ | # peer server. e.g. CHATLINKS=67.69.96.23: | ||
+ | # | ||
+ | # XRchat servers may also be interconnected with | ||
+ | # | ||
+ | # | ||
+ | # In order to define a link with a RoundTable/ | ||
+ | # the callsign must be prefixed with a ' | ||
+ | # The link will not be allowed unless both callsign and alias | ||
+ | # are in the nodes table. | ||
+ | # | ||
+ | # Links with Tampa Ping Pong Converse servers use TCP/IP as | ||
+ | # outlined above. The only difference between an XRchat TCP link | ||
+ | # and a TPP link is that in the latter the peer ID is prefixed | ||
+ | # with an asterisk, e.g: CHATLINKS=80.195.22.37: | ||
+ | # | ||
+ | # You may specify several servers on one line, separating them | ||
+ | # with commas. Don't include any spaces! Or you may specify each | ||
+ | # server on a separate line. Or any combination of the two. | ||
+ | # You may disable all outgoing and incoming chat linking by | ||
+ | # omitting this directive. | ||
+ | |||
+ | ; | ||
+ | ; | ||
+ | |||
+ | # Chat Server Activity Logging level: | ||
+ | # Add together the values corresponding to the desired options | ||
+ | # from this table: | ||
+ | # | ||
+ | # 1 Local user connect / disconnect event | ||
+ | # 2 Remote user connect / disconnect event | ||
+ | # 4 Peer server connect / disconnect event | ||
+ | # 8 Local channels 1-255 join / leave events | ||
+ | # | ||
+ | # 32 Log channel notifications | ||
+ | # 64 Log the text of conversations | ||
+ | # 128 Use a single logfile, instead of daily ones | ||
+ | # | ||
+ | |||
+ | ; CHATLOG=127 | ||
+ | |||
+ | ###################################################################### | ||
+ | # Miscellaneous Parameters | ||
+ | ###################################################################### | ||
+ | |||
+ | |||
+ | # IGATE controls whether or not the APRS Packet<> | ||
+ | # is started at boot-up. A zero value (default) doesn' | ||
+ | # igate (but it can be started anytime using "start igate" | ||
+ | # a non-zero value starts it immediately. | ||
+ | # Leave this commented out, or set to zero if you aren't running | ||
+ | # a gateway. | ||
+ | |||
+ | ;IGATE=1 | ||
+ | |||
+ | # Optional flags to control the DX heard display (default=0) | ||
+ | # Add together: | ||
+ | # | ||
+ | # Bit Value | ||
+ | # 0 0 - Record directly heard stations only | ||
+ | # 0 1 - Record digipeated and direct stations | ||
+ | # 1 2 - Enable logging of DX exceeding specified distance. | ||
+ | # 2 4 - Log frame contents of qualifying DX. | ||
+ | # | ||
+ | # If logging is enabled Bits 3 - 14 specify the minimum | ||
+ | # distance which will be logged, from 4Km to 32764Km in 8Km | ||
+ | # steps, e.g. DXFLAGS=502 enables DX logging, with a threshold | ||
+ | # of 500Km. If logging is not enabled, bits 3-14 are ignored. | ||
+ | # | ||
+ | # If DX logging is enabled, any received APRS positions which | ||
+ | # exceed the threshold distance are logged to LOG\DXLOG.TXT. | ||
+ | |||
+ | ; DXFLAGS=102 | ||
+ | |||
+ | |||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # Y | ||
+ | # A Only applications may use the command. | ||
+ | # N | ||
+ | |||
+ | ; ENABLE_LINKED=A | ||
+ | |||
+ | |||
+ | # Usage Log: | ||
+ | # Setting LOG=1 will log all connects, disconnects, | ||
+ | # commands and chat server activity. LOG=0 disables this | ||
+ | # function. Can be overridden by LOG command at the command line. | ||
+ | |||
+ | LOG=0 | ||
+ | |||
+ | |||
+ | # Overall limit on no. of concurrent sessions per user, across | ||
+ | # all ports. | ||
+ | # this way! Max setting = default = 255 | ||
+ | |||
+ | ; SESSLIMIT=255 | ||
+ | |||
+ | |||
+ | MAXSESSIONS=30 | ||
+ | |||
+ | # UITRACE and UIFLOOD are two special addresses for APRS use, | ||
+ | # that are suffixed with pseudo-SSID' | ||
+ | # | ||
+ | # The first digit specifies the maximum number of hops, and the | ||
+ | # second is the hop counter, which is decremented each time the | ||
+ | # frame is digipeated. | ||
+ | # | ||
+ | # These two addresses behave slightly differently however. When | ||
+ | # a frame is digipeated on the address specified by UITRACE, | ||
+ | # each digipeater inserts its own callsign in the digipeater | ||
+ | # list and decrements the " | ||
+ | # UIFLOOD address have their SSIDs decremented, | ||
+ | # | ||
+ | # | ||
+ | # For the sake of consistency with UI-View, UITRACE defaults | ||
+ | # to " | ||
+ | # defaults to WIDE, giving WIDEn-n digipeating. | ||
+ | # | ||
+ | # However, according to the APRS "New N-n Paradigm", | ||
+ | # TRACE and WIDE are deprecated, UITRACE should be set to | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # Not everyone agrees with the "New N-n Paradigm, so the choice | ||
+ | # of which features to enable is left to your discretion. | ||
+ | |||
+ | ; | ||
+ | ; | ||
+ | |||
+ | ###################################################################### | ||
+ | # | ||
+ | ###################################################################### | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # No. of seconds between L4 retries and L4 connect/ | ||
+ | # attempts. | ||
+ | |||
+ | L4TIMEOUT=90 | ||
+ | |||
+ | # No. of seconds to delay a L4 ack in case further frames arrive. | ||
+ | # 10 secs is probably OK on normal AX25 links, but is excessive | ||
+ | # on wire links. | ||
+ | # value to cope with prevailing conditions. | ||
+ | |||
+ | L4DELAY=10 | ||
+ | |||
+ | # No. of unacked L4 frames allowed before we stop to await an | ||
+ | # ack. | ||
+ | |||
+ | L4WINDOW=4 | ||
+ | |||
+ | # No. of L4 connect/ | ||
+ | # link is abandoned. | ||
+ | |||
+ | L4RETRIES=3 | ||
+ | |||
+ | # | ||
+ | # Max no. of simultaneous L4 circuits. | ||
+ | |||
+ | MAXCIRCUITS=25 | ||
+ | |||
+ | |||
+ | ###################################################################### | ||
+ | # | ||
+ | ###################################################################### | ||
+ | |||
+ | # | ||
+ | # | ||
+ | |||
+ | OBSINIT=5 | ||
+ | |||
+ | # | ||
+ | # | ||
+ | |||
+ | OBSMIN=3 | ||
+ | |||
+ | # Minutes between nodes broadcasts (0 = disable broadcasts). | ||
+ | # This value is inherited by all ports, but may be overridden on | ||
+ | # a per-port basis by including NODESINTERVAL within a PORT | ||
+ | # | ||
+ | |||
+ | NODESINTERVAL=60 | ||
+ | |||
+ | # Maximum L3 hops (Time To Live). | ||
+ | # This specifies a limit to the number of nodes a L3 packet may | ||
+ | # traverse before it is dumped, and is used to prevent packets | ||
+ | # from looping forever in routing loops. | ||
+ | |||
+ | L3TTL=25 | ||
+ | |||
+ | # If HIDENODES is set to 1, nodes whose alias begins with "#" | ||
+ | # are not displayed by the normal N command. However, whatever | ||
+ | # the setting here, they can always be displayed using "N *". | ||
+ | |||
+ | HIDENODES=1 | ||
+ | |||
+ | # Minimum quality to add to node table. | ||
+ | # value, inherited by all ports unless overridden by a MINQUAL | ||
+ | # directive with a PORT block. If not specified, default is 10. | ||
+ | |||
+ | MINQUAL=10 | ||
+ | |||
+ | # Max no. of nodes to include in table (default=200). | ||
+ | # If you have a large nodes table, the output from the " | ||
+ | # command may be too much for an RF channel to handle. On the | ||
+ | # other hand, if the table size is to small for the number of | ||
+ | # nodes, nodes will keep disappearing from the table as their | ||
+ | # slots are reallocated to " | ||
+ | # You should decide what table size is appropriate for your | ||
+ | # | ||
+ | # expected nodes, and use QUALITY and MINQUAL to control the no. | ||
+ | # of nodes in the table. | ||
+ | |||
+ | MAXNODES=250 | ||
+ | |||
+ | # By default, the plain " | ||
+ | # order. Although the "N C" command can be used to display nodes | ||
+ | # in CALLSIGN order, some sysops prefer this to be the default. | ||
+ | # Setting SORTBYCALL to 1 forces the " | ||
+ | # nodes in callsign order. | ||
+ | |||
+ | SORTBYCALL=0 | ||
+ | |||
+ | # Quality adjustment by callsign. | ||
+ | # This allows you to de-rate the NetRom quality of a node or | ||
+ | # group of nodes based on the NetRom callsign, instead of the | ||
+ | # route on which they were received. Thus you can change the | ||
+ | # relative qualities to favour your local nodes, or (more | ||
+ | # likely) those which share your language. | ||
+ | # This feature is experimental, | ||
+ | # need arises. Note that this only works on netrom " | ||
+ | # nodes which are learned via INP3 have no quality to de-rate. | ||
+ | # The " | ||
+ | # to de-rate all nodes not matched by any other QUALADJUST | ||
+ | # | ||
+ | # 255 gives no de-rate and 0 gives full de-rate (i.e. to block | ||
+ | # a callsign or group of callsigns). If there are no | ||
+ | # | ||
+ | |||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | |||
+ | # | ||
+ | # Maximum simultaneous neighbour node routes. | ||
+ | |||
+ | MAXROUTES=35 | ||
+ | |||
+ | |||
+ | # MAXTT defines the maximum accepted "trip time" (transit time) | ||
+ | # for new nodes table entries received via INP3 unicasts from | ||
+ | # | ||
+ | # figure are not accepted into the nodes table. This value is | ||
+ | # inherited by all PORTS, and all ROUTES learned via those | ||
+ | # ports unless overridden by a MAXTT entry in the PORT or ROUTE. | ||
+ | # The default value is 60000 (600 seconds). | ||
+ | |||
+ | ;MAXTT=5000 | ||
+ | |||
+ | # MAXHOPS defines the maximum accepted "hop count" for new nodes | ||
+ | # table entries received via INP3 unicasts from neighbours. | ||
+ | # Node information with hop counts that exceed this figure are | ||
+ | # not accepted into the nodes table. This value is inherited by | ||
+ | # all PORTS, and all ROUTES learned via those ports unless | ||
+ | # | ||
+ | # The default value is 30 hops. | ||
+ | |||
+ | ;MAXHOPS=2 | ||
+ | |||
+ | |||
+ | # List of callsigns from whom L3 traffic will not be accepted. | ||
+ | # It should be used only in exceptional circumstances. | ||
+ | # Callsigns should be seperated by commas. | ||
+ | # not required. | ||
+ | |||
+ | ; | ||
+ | |||
+ | # | ||
+ | # This allows you to " | ||
+ | # a greater or lesser degree. This has been found to be a more | ||
+ | # effective means of control than blocking them outright, which | ||
+ | # just shifts the troublemaker to another route. The miscreant | ||
+ | # usually assumes the network is slow, and doesn' | ||
+ | # | ||
+ | # A BLEVEL of 0 prevents ALL L3 packets from the budlisted | ||
+ | # stations, and at the other extreme 255 will allow all packets. | ||
+ | # For example 64 will allow on average 1 in 4 L3 packets, which | ||
+ | # should slow things down a bit!! The sysop can vary this | ||
+ | # parameter on the fly. | ||
+ | |||
+ | ;BLEVEL=0 | ||
+ | |||
+ | |||
+ | ###################################################################### | ||
+ | # AX25 Layer 2 Parameters | ||
+ | ###################################################################### | ||
+ | |||
+ | # AX25 " | ||
+ | # AX25 L2 links that are apparently open, but have been idle for | ||
+ | # this length of time are probed to verify that they are still | ||
+ | # alive. | ||
+ | |||
+ | T3=180 | ||
+ | |||
+ | # Idle link shutdown timer in secs (default=900). | ||
+ | # AX25 L2 Links with neighbour nodes are closed down if they | ||
+ | # | ||
+ | # is an outdated idea and shouldn' | ||
+ | # as the links are periodically probed by L3RTT measurements. | ||
+ | |||
+ | IDLETIME=900 | ||
+ | |||
+ | # Minutes between ID broadcasts (default=15). | ||
+ | # This is the time interval between broadcasts of IDTEXT (see | ||
+ | # TEXTS above) on each port. A setting of 0 disables ID beacons. | ||
+ | |||
+ | IDINTERVAL=15 | ||
+ | |||
+ | # Global paclen (default=120). | ||
+ | # This specifies the maximum data field length within an AX25 | ||
+ | # or Netrom packet originated by XRPi. This value is inherited | ||
+ | # by all ports and links, unless overridden in a PORT block. | ||
+ | # Note that we have no control over the paclen of frames | ||
+ | # | ||
+ | |||
+ | PACLEN=120 | ||
+ | |||
+ | # Max. simultaneous AX25 L2 links (default=30) | ||
+ | # You should set this large enough to accommodate the total | ||
+ | # number of AX25 L2 users and internode links that you expect. | ||
+ | |||
+ | ; | ||
+ | |||
+ | |||
+ | ###################################################################### | ||
+ | # Interface definitions - These MUST precede any dependent PORT # | ||
+ | ###################################################################### | ||
+ | # | ||
+ | # WARNING: If you are used to the BPQ paradigm, you must think | ||
+ | # | ||
+ | # | ||
+ | # Unlike BPQ, you first define the INTERFACES with the outside | ||
+ | # world, then you define the PORTS that use those interfaces. | ||
+ | # | ||
+ | # An INTERFACE is the point of interaction between the XRPi | ||
+ | # program and the outside world hardware. Some interfaces (e.g. | ||
+ | # ASYNC) can support several communication " | ||
+ | # the appropriate protocol (e.g. KISS). Other types of interface | ||
+ | # (e.g. SLIP) support only one channel. | ||
+ | # | ||
+ | # A PORT is the point of interaction between the various | ||
+ | # protocol modules and *one channel* of an interface. | ||
+ | # | ||
+ | # Interface definition blocks start with the directive | ||
+ | # | ||
+ | # | ||
+ | # greater than zero and no other interface uses the same number. | ||
+ | # The block ends with ENDINTERFACE. The keywords that may be | ||
+ | # used in interface definition blocks are as follows: | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # This specifies the maximum size for the data portion | ||
+ | # of any IP packet transmitted on the interface. | ||
+ | # | ||
+ | # of the interface on which they are transmitted. | ||
+ | # | ||
+ | # XRPi allows MTU's up to 1500 bytes, but setting MTU | ||
+ | # over 256 is not recommended on AX25 ports, because the | ||
+ | # buffer size on TNC-based nodes is usually only big | ||
+ | # enough for a 256-byte data field. | ||
+ | # | ||
+ | # This is a mandatory keyword, although for some | ||
+ | # | ||
+ | # ignored. If in doubt, use 256. | ||
+ | # | ||
+ | # | ||
+ | # COM Com port number (0 - 32), used by ASYNC and YAM types | ||
+ | # only. COM is mandatory for these interfaces. COM0 is a | ||
+ | # | ||
+ | # | ||
+ | # CHANNELS | ||
+ | # For WA8DED hostmode interfaces only. Specifies the max | ||
+ | # no. of host channels (between 1 and 32) the interface | ||
+ | # will provide. | ||
+ | # | ||
+ | # PROTOCOL | ||
+ | # Protocol to use on the interface: | ||
+ | # | ||
+ | # ASCII - Remote consoles (TTY) via ASYNC ports | ||
+ | # ETHER - Ethernet | ||
+ | # HDLC - For use with YAM modem, and some EXTERNAL | ||
+ | # | ||
+ | # KISS - For driving KISS TNCs or wired links. | ||
+ | # MODEM - Hayes compatible PSTN modem. | ||
+ | # NETROM | ||
+ | # NONE - Use this with type=loopback | ||
+ | # PPP - Point to Point Protocol | ||
+ | # SLIP - Serial Line Interface Protocol | ||
+ | # TNC2 - TNC2 emulation. | ||
+ | # | ||
+ | # | ||
+ | # SPEED The serial port baud rate for ASYNC interfaces only. | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # on the interface TYPE. | ||
+ | # | ||
+ | # FLOW Flow control options (ASYNC interfaces only): | ||
+ | # | ||
+ | # 0 = No flow control | ||
+ | # 1 = Hardware (RTS/CTS) flow control | ||
+ | # 2 = Software (XON/XOFF) flow control (TTY link only) | ||
+ | # 3 = Hardware AND software flow control | ||
+ | # | ||
+ | # If not specified, flow control defaults to NONE. Don't | ||
+ | # use Xon/Xoff with KISS protocol. | ||
+ | # | ||
+ | # | ||
+ | # the TCP port the AXTCP server should listen on, or the | ||
+ | # TCP port used to connect with AGWPE. | ||
+ | # | ||
+ | # | ||
+ | # Options for KISS interfaces only: | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # CHECKSUM - Packets are protected by checksum. | ||
+ | # only use this option if your TNC supports | ||
+ | # it. | ||
+ | # | ||
+ | # | ||
+ | # has been transmitted on air. | ||
+ | # | ||
+ | # | ||
+ | # sending data on serial port only when asked | ||
+ | # to do so. | ||
+ | # | ||
+ | # POLLED and SLAVE are mutually exclusive. BPQKISS | ||
+ | # eproms require POLLED and CHECKSUM, but their use of | ||
+ | # ACKMODE is optional. | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # Example interface for a normal KISS TNC on ttyS0 device: | ||
+ | # KISS interfaces can support up to 16 PORTs, each using a | ||
+ | # different CHANNEL on the interface. | ||
+ | |||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; MTU=256 | ||
+ | ; | ||
+ | |||
+ | |||
+ | # Example interface for BPQKISS TNC on ttyUSB0 device: | ||
+ | # BPQKISS interfaces can support up to 16 PORTs, each using a | ||
+ | # different CHANNEL on the interface. | ||
+ | |||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; MTU=256 | ||
+ | ; | ||
+ | |||
+ | # | ||
+ | # purposes. This type of interface supports one PORT only. | ||
+ | |||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; MTU=576 | ||
+ | ; | ||
+ | |||
+ | |||
+ | # Example interface for Ethernet, sharing " | ||
+ | # Requires CAP_NET_RAW capability, or run from root account. | ||
+ | # Can also be used for a wlan device. | ||
+ | # This type of interface supports one PORT only. | ||
+ | |||
+ | ; | ||
+ | ; | ||
+ | ; ID=eth0 | ||
+ | ; | ||
+ | ; MTU=1064 | ||
+ | ; | ||
+ | |||
+ | |||
+ | # Example of an interface for TTY (remote console). | ||
+ | # connect the com port via a null modem to a dumb terminal or | ||
+ | # computer running a terminal emulator program, such as TELIX. | ||
+ | # This type of interface does NOT have a port attached to it. | ||
+ | |||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; MTU=256 | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | |||
+ | |||
+ | # Example AXIP pseudo-interface. Only TYPE and MTU required, | ||
+ | # all other parameters are ignored (at present). | ||
+ | # At least one AXIP interface is needed if you intend to do AX25 | ||
+ | # over IP. You can attach an unlimited number of ports to one | ||
+ | # AXIP interface, or you can use separate interfaces if you need | ||
+ | # different MTU's. | ||
+ | |||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | |||
+ | |||
+ | # Example AXUDP pseudo-interface. Apart from " | ||
+ | # the comments relating to AXIP interface. | ||
+ | |||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | |||
+ | # Example of an AXTCP server interface, listening for clients on | ||
+ | # TCP port 9393. This type of interface supports one PORT only. | ||
+ | |||
+ | ; | ||
+ | ; | ||
+ | ; MTU=256 | ||
+ | ; | ||
+ | ; | ||
+ | |||
+ | # Example of an AXTCP client interface which connects with the | ||
+ | # KIDDER node, whose address is g8pzt.ath.cx, | ||
+ | # | ||
+ | # The CONFIG directive is used to specify a server to connect, | ||
+ | # thereby activating client mode. The format is as follows: | ||
+ | # | ||
+ | # CONFIG=< | ||
+ | # | ||
+ | # You may specify additional servers, by including a CONFIG for | ||
+ | # each one. There is no limit to the number of CONFIG | ||
+ | # | ||
+ | # This type of interface supports one PORT only. | ||
+ | |||
+ | ; | ||
+ | ; | ||
+ | ; MTU=256 | ||
+ | ; | ||
+ | ; | ||
+ | |||
+ | # Example YAM interface. One of these required for each YAM | ||
+ | # modem. The modem must be initialised with YAMINIT.EXE before | ||
+ | # starting XRPi. In this interface SPEED defines the RADIO baud | ||
+ | # rate. The serial port always runs at 19200 bauds. | ||
+ | # This interface supports a single PORT. | ||
+ | |||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | |||
+ | |||
+ | # Example of a " | ||
+ | # This type of interface supports a single PORT. | ||
+ | |||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; MTU=256 | ||
+ | ; | ||
+ | |||
+ | |||
+ | # Example WA8DED TNC emulation interface. | ||
+ | # No ports are attached to this type of interface. | ||
+ | # | ||
+ | # CHANNELS specifies the max no. of host channels the interface | ||
+ | # will provide (between 1 and 32). | ||
+ | # | ||
+ | # APPLNUM specifies which application will be using this | ||
+ | # | ||
+ | # section below). This directive is not required if the emulator | ||
+ | # is used in " | ||
+ | # | ||
+ | # FLOW must always be set to 0 or 4. Setting FLOW to any value | ||
+ | # other than 0 or 4 may cause the application or XRPi to hang. | ||
+ | # FLOW=4 is a special case which forces the WA8DED emulator to | ||
+ | # start in host mode instead of TNC mode. | ||
+ | |||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; APPLNUM=3 | ||
+ | ; | ||
+ | ; | ||
+ | ; FLOW=0 ; Must be 0 or 4 | ||
+ | ; | ||
+ | ; | ||
+ | |||
+ | |||
+ | # Example of a TNC2 emulation interface. No PORT is required. | ||
+ | # You can have as many TNC emulators as you wish, providing you | ||
+ | # have an RS232 port for each one. You should preferably use a | ||
+ | # different MYCALL or SSID for each one if there is any chance | ||
+ | # of more than one TNC being used on the same radio port. | ||
+ | |||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; MTU=256 | ||
+ | ; | ||
+ | |||
+ | |||
+ | # Example SLIP or PPP interface, used to link XRPi with other IP | ||
+ | # systems via real or virtual COM ports. SLIP and PPP interfaces | ||
+ | # support only one PORT. The interfaces are identical apart from | ||
+ | # the PROTOCOL line - use PROTOCOL=PPP for a PPP interface. | ||
+ | # | ||
+ | # Serial lines used for PPP and SLIP must run at 8 data bits. | ||
+ | # Flow control must be hardware or none, as XON/XOFF flow | ||
+ | # control interferes with the protocol. | ||
+ | # | ||
+ | # If flow control is used, the cable must contain at least 5 | ||
+ | # cores, namely TXD, RXD, RTS, CTS and GND. If flow control is | ||
+ | # not used, only TXD, RXD and GND are required. | ||
+ | # | ||
+ | # In all cases, a NULL MODEM is required. In the case of " | ||
+ | # RS232 this could be an actual null modem device, or a cable | ||
+ | # that is wired such that the TXDs at each end go to the RXDs | ||
+ | # at the other end, and the RTSs at each end go to the CTSs at | ||
+ | # the other. " | ||
+ | # this functionality as standard. | ||
+ | # | ||
+ | # SLIP is a neat way to connect systems without involving the | ||
+ | # Linux TCP/IP stack, allowing XRPi to have its own IP address | ||
+ | # and proper control of the IP stack, including low-level | ||
+ | # protocol tracing. | ||
+ | |||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | |||
+ | |||
+ | # Example AGW interface: | ||
+ | # | ||
+ | # This allows XRPi to use AGW Packet Engine to manage hardware | ||
+ | # which is not directly supported by XRPi, such as soundcards. | ||
+ | # | ||
+ | # Note that IOADDR, INTNUM and CONFIG are all optional, and are | ||
+ | # only needed if you want to change the defaults. | ||
+ | # | ||
+ | # If you don't specify IOADDR, it defaults to 127.0.0.1, which | ||
+ | # is the same computer as XRPi is on. If AGWPE is on a different | ||
+ | # computer to XRPi, you need to enter its IP address here. | ||
+ | # | ||
+ | # If you don't specify INTNUM, it defaults to 8000, which is the | ||
+ | # normal AGWPE port. If AGWPE is on the same PC as XRPi, and it | ||
+ | # is using the default port, you will need to reassign or disable | ||
+ | # | ||
+ | # server and AGWPE itself. | ||
+ | # | ||
+ | # If you don't specify CONFIG, XRPi won't " | ||
+ | # | ||
+ | # AGWPE on the same computer. You can adjust the requirement for | ||
+ | # | ||
+ | # | ||
+ | # the string specified by CONFIG. | ||
+ | # | ||
+ | # The AGWPE interface can support up to 16 PORTs, which are | ||
+ | # declared in the usual way, each PORT using a different CHANNEL | ||
+ | # on the INTERFACE. | ||
+ | |||
+ | ; | ||
+ | ; TYPE=AGW | ||
+ | ; | ||
+ | ; | ||
+ | ; MTU=256 | ||
+ | ; | ||
+ | ; | ||
+ | |||
+ | |||
+ | |||
+ | ###################################################################### | ||
+ | # PORT definitions - MUST follow the Interfaces they attach to # | ||
+ | ###################################################################### | ||
+ | # | ||
+ | # Each definition block begins with PORT=n and ends with ENDPORT | ||
+ | # | ||
+ | # The following is an example port, showing all the options. In | ||
+ | # practice you wouldn' | ||
+ | # | ||
+ | # | ||
+ | # The number following PORT= is the port number as displayed by | ||
+ | # the P[orts] command. They do not need to be sequential. You | ||
+ | # may use any number, but you must define them in the order in | ||
+ | # which they are to appear in the PORTS list. | ||
+ | # | ||
+ | ;PORT=1 | ||
+ | # | ||
+ | # Mandatory text string to identify port on " | ||
+ | # | ||
+ | # Note: You may not append comments to this directive. | ||
+ | # | ||
+ | ;ID=Link to KIDDER | ||
+ | # | ||
+ | # | ||
+ | # port should use. | ||
+ | # | ||
+ | ; | ||
+ | # | ||
+ | # The remainder of the parameters are mostly optional, since | ||
+ | # there are sensible defaults built into the program.... | ||
+ | # | ||
+ | # | ||
+ | # Channel to use on interface (A - P). Default=A. | ||
+ | # This is mandatory for multi-channel interfaces (e.g. KISS), | ||
+ | # but not required for single channel ones. | ||
+ | # | ||
+ | ;CHANNEL=A | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | ; | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | ; | ||
+ | # | ||
+ | # | ||
+ | # Yet another alias, for digipeating only (optional). | ||
+ | # This alias does not accept connections. | ||
+ | # | ||
+ | ; | ||
+ | # | ||
+ | # | ||
+ | # Port override for global chatalias (optional). | ||
+ | # | ||
+ | ; | ||
+ | # | ||
+ | # | ||
+ | # Port override for global chatcall (optional). | ||
+ | # | ||
+ | ; | ||
+ | # | ||
+ | # | ||
+ | # Port override for global PMSALIAS (optional). | ||
+ | # | ||
+ | ; | ||
+ | # | ||
+ | # | ||
+ | # Port override for global PMSCALL (optional). | ||
+ | # | ||
+ | ; | ||
+ | # | ||
+ | # | ||
+ | # Paclen for this port only. Overrides global paclen. | ||
+ | # If set to 0, paclen will adapt to the link conditions. | ||
+ | # | ||
+ | ;PACLEN=160 | ||
+ | # | ||
+ | # | ||
+ | # Max. outstanding AX25 L2 frames (default=3). | ||
+ | # This is the maximum number of frames that are allowed before | ||
+ | # the sender must stop and wait for an acknowledgement. | ||
+ | # | ||
+ | ;MAXFRAME=2 | ||
+ | # | ||
+ | # | ||
+ | # Tx keyup delay in millisecs (default=300). | ||
+ | # This should be adjusted to a suitable value for the baud rate, | ||
+ | # the TX settling time and the other end's squelch opening time. | ||
+ | # | ||
+ | ; | ||
+ | # | ||
+ | # | ||
+ | # TX keydown delay (millisecs). | ||
+ | # | ||
+ | # | ||
+ | ;TXTAIL=100 | ||
+ | # | ||
+ | # | ||
+ | # CSMA interval timer in millisecs (default=100). | ||
+ | # | ||
+ | ; | ||
+ | # | ||
+ | # | ||
+ | # L2 T1 (Frame Acknowledgement) time in ms (default=7000). | ||
+ | # A value of 7000 is recommended for 1200 bauds. (see manual) | ||
+ | # | ||
+ | ;FRACK=7000 | ||
+ | # | ||
+ | # | ||
+ | # L2 delayed ack timer T2 in milliseconds (default=2000). | ||
+ | # Resptime should be *at least* ((paclen * 10000) / RFbauds) | ||
+ | # | ||
+ | # XRPi will send unnecessary poll frames. 1500 is OK for 1200 | ||
+ | # bauds with paclen=120 | ||
+ | # | ||
+ | ; | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # Persist should be set to (255 / (no. of users on frequency)). | ||
+ | # e.g. for a frequency with an average of 10 users on at any one | ||
+ | # time you'd set it to 25. | ||
+ | # | ||
+ | ;PERSIST=64 | ||
+ | # | ||
+ | # | ||
+ | # Maximum retries (default=10). | ||
+ | # There is no point in setting retries more than 10, other than | ||
+ | # for test purposes. | ||
+ | # link and you're just wasting everyone else's airtime. | ||
+ | # higher you set this value, the longer users will have to wait | ||
+ | # to receive a " | ||
+ | # | ||
+ | ;RETRIES=10 | ||
+ | # | ||
+ | # | ||
+ | # Full Duplex (default=0) | ||
+ | # If you set fulldup=1, XRouter will transmit whenever it needs | ||
+ | # to, without waiting for the other end to stop. Used only for | ||
+ | # hardware which is capable of simultaneous transmission and | ||
+ | # | ||
+ | # | ||
+ | ;FULLDUP=0 | ||
+ | # | ||
+ | # | ||
+ | # Softdcd is used only by SCC cards. | ||
+ | # real dcd is ignored, and the driver uses the presence of HDLC | ||
+ | # data as a DCD indication. | ||
+ | # generates a *huge* interrupt loading on the PC, which may | ||
+ | # cause degradation of performance, | ||
+ | # it is not recommended. (Note SCC cards are not currently | ||
+ | # supported by XRPi) | ||
+ | # | ||
+ | ;SOFTDCD=0 | ||
+ | # | ||
+ | # | ||
+ | # Rfbauds defaults to 1200 if not specified. | ||
+ | # use with " | ||
+ | # rate is usually different to the serial baud rate. It simply | ||
+ | # helps the router make better timing decisions. | ||
+ | # | ||
+ | ; | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # specifies how many callsigns to maintain in the list. Set to | ||
+ | # 0 to disable MHEARD, but please be aware that MHeard is very | ||
+ | # useful for diagnosing link problems. | ||
+ | # | ||
+ | ; | ||
+ | # | ||
+ | # | ||
+ | # MHFLAGS controls which callsigns are recorded in the MH list, | ||
+ | # and defaults to 255 (show everything). | ||
+ | # The number is formed by adding the following values: | ||
+ | # | ||
+ | # 1 Show directly heard stations | ||
+ | # 2 Show directly heard digipeaters | ||
+ | # 4 Show digipeated stations | ||
+ | # | ||
+ | ; | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # Add together the required values from this list: | ||
+ | # | ||
+ | # Bit Value Option | ||
+ | # | ||
+ | # 0 1 | ||
+ | # 1 2 | ||
+ | # 2 4 | ||
+ | # 3 8 | ||
+ | # 4 | ||
+ | # 5 | ||
+ | # 6 | ||
+ | # 7 128 Allow digipeating from Internet (IGate). | ||
+ | # 8 256 | ||
+ | # 9 512 | ||
+ | # | ||
+ | # | ||
+ | ; | ||
+ | # | ||
+ | # | ||
+ | # Port to relay digipeated frames on (0=default=this port) | ||
+ | # | ||
+ | ;DIGIPORT=0 | ||
+ | # | ||
+ | # List of destinations for " | ||
+ | # Received non-digipeater UI frames, addressed to one of these | ||
+ | # | ||
+ | # matching address in their BCAST list. This would for example | ||
+ | # be used to broadcast mail beacons from a BBS onto several | ||
+ | # | ||
+ | # | ||
+ | ; | ||
+ | # | ||
+ | # | ||
+ | # List of approved broadcasters. | ||
+ | # If you wish to restrict the broadcast facility to certain | ||
+ | # senders only, list the callsigns here. If no calls are | ||
+ | # | ||
+ | # by commas, and don't include any spaces in the list. | ||
+ | # | ||
+ | ; | ||
+ | # | ||
+ | # | ||
+ | # Default quality for nodes whose broadcasts are received on | ||
+ | # this port. Set to 0 to disable all L3/4 activity on the port. | ||
+ | # If not specified, this defaults to 10. | ||
+ | # | ||
+ | ;QUALITY=10 | ||
+ | # | ||
+ | # | ||
+ | # Minimum quality to add to node table for nodes received via | ||
+ | # this port (default=10). | ||
+ | # global minqual, and can be used to exclude unreachable and | ||
+ | # marginal nodes. | ||
+ | # | ||
+ | ;MINQUAL=10 | ||
+ | # | ||
+ | # | ||
+ | # Port override for global MAXTT (default 60000). | ||
+ | # Inherited by new ROUTES learned via this PORT. | ||
+ | # | ||
+ | ;MAXTT=5000 | ||
+ | # | ||
+ | # | ||
+ | # Port override for global MAXHOPS (default=30). | ||
+ | # Inherited by new ROUTES learned via this PORT. | ||
+ | # | ||
+ | ;MAXHOPS=2 | ||
+ | # | ||
+ | # | ||
+ | # MINTXQUAL specifies the minimum Net/rom node quality to | ||
+ | # transmit on this port (default=0). This would typically be | ||
+ | # used to limit the size of nodes broadcasts on ports which are | ||
+ | # severely bandwidth limited, or when the neighbour nodes have | ||
+ | # limited table capacity. The neighbours could of course limit | ||
+ | # their table size using their MINQUAL, but there is no point in | ||
+ | # | ||
+ | # | ||
+ | ; | ||
+ | # | ||
+ | # | ||
+ | # Minutes between nodes broadcasts on this port (0 = disable). | ||
+ | # Overrides the global value. If not specified, it defaults to | ||
+ | # the global value. | ||
+ | # | ||
+ | ; | ||
+ | # | ||
+ | # | ||
+ | # Port to transmit on (0=default=this port). | ||
+ | # You would typically use this where a single transmitter is | ||
+ | # used in conjunction with several receivers | ||
+ | # | ||
+ | ;TXPORT=0 | ||
+ | # | ||
+ | # Interlock is only used by SCC cards - KISS TNC's make their | ||
+ | # own decisions when to transmit, and XRouter has no control | ||
+ | # over that process. | ||
+ | # ports with the same value will transmit at the same time. | ||
+ | # | ||
+ | ; | ||
+ | # | ||
+ | # | ||
+ | # Maximum no. of simultaneous users on this port. Default is | ||
+ | # 255 which means "no limit" | ||
+ | # | ||
+ | ;USERS=255 | ||
+ | # | ||
+ | # | ||
+ | # Sesslimit specifies the maximum simultaneous connects each | ||
+ | # user is allowed (default=255). | ||
+ | # | ||
+ | ; | ||
+ | # | ||
+ | # | ||
+ | # The following two commands are mutually exclusive... Use one | ||
+ | # or the other, but not both! | ||
+ | # Callsigns should be separated by commas or spaces, and there | ||
+ | # is no limit to the number of calls. You can have multiple | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # is typically used to keep users from connecting to link-only | ||
+ | # ports. | ||
+ | # | ||
+ | ; | ||
+ | # | ||
+ | # | ||
+ | # Exclude allows L2 frames from everyone EXCEPT specified users, | ||
+ | # and would typically be used on a user-access port to prevent | ||
+ | # | ||
+ | # | ||
+ | ; | ||
+ | # | ||
+ | # | ||
+ | # CWID is used only by SCC cards. | ||
+ | # Callsign is sent every 30 mins. | ||
+ | # | ||
+ | ;CWID=G8PZT | ||
+ | # | ||
+ | # | ||
+ | # PIPE allows frames received (and optionally sent) on this port | ||
+ | # to be copied to another port. A typical use might be to allow | ||
+ | # a PMS on one port to see the traffic on another port e.g. | ||
+ | # UNPROTO headers from a local BBS. | ||
+ | # | ||
+ | # Note that this is *not* the same as digipeating. With | ||
+ | # | ||
+ | # but with frame piping the packets are tunneled from one port | ||
+ | # to another with no intervention from the user. | ||
+ | # | ||
+ | # Unless the " | ||
+ | # | ||
+ | # | ||
+ | # opposite port. You may pipe several ports to a single | ||
+ | # | ||
+ | # from any port. | ||
+ | # | ||
+ | # Pipes are capable of generating an immense amount of traffic, | ||
+ | # so use them with care - your target port MUST be capable of | ||
+ | # handling the traffic load. | ||
+ | # | ||
+ | # Pipes can be made " | ||
+ | # callsign list, e.g. " | ||
+ | # the loading on the target port, by piping only the frames with | ||
+ | # the specified calls in the destination field. | ||
+ | # | ||
+ | # Pipes can be made " | ||
+ | # PIPEFLAG value (see below: suggested value = 515). If a frame | ||
+ | # is piped on a bi-directional pipe, the source call is | ||
+ | # | ||
+ | # Thus a reverse pipe is not needed. | ||
+ | # | ||
+ | # This is useful in cases where a BBS has a front end router - | ||
+ | # simply set up bi-directional selective pipes from each user | ||
+ | # port to the BBS port, and set up the BCAST option so that the | ||
+ | # UI mail headers are broadcast on each user port. The BBS will | ||
+ | # then allow direct connect and will respond to resync requests. | ||
+ | # | ||
+ | # To disable piping, set PIPE=0 or just omit the command. | ||
+ | # | ||
+ | ; | ||
+ | # | ||
+ | # | ||
+ | # PIPEFLAG is only used when piping is active, and controls | ||
+ | # which frames are piped. | ||
+ | # The value is made up by adding together the desired options | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | ; | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | ; | ||
+ | # | ||
+ | # | ||
+ | # Optional alternative IP address for use on this port. If this | ||
+ | # is specified, it will be used in addition to the global IP | ||
+ | # address for this port only. | ||
+ | # | ||
+ | ; | ||
+ | # | ||
+ | # | ||
+ | # Subnet mask used with IPADDRESS to specify the range of IP | ||
+ | # addresses that are on the same physical segment as XRPi. | ||
+ | # | ||
+ | ; | ||
+ | # | ||
+ | # | ||
+ | # The DHCP keyword specifies whether or not the port IP address | ||
+ | # will be obtained dynamically using DHCP (DHCP=1) or specified | ||
+ | # | ||
+ | # | ||
+ | ;DHCP=0 | ||
+ | # | ||
+ | # | ||
+ | # If you set SYSOP=1, all users who connect on this port will | ||
+ | # get full sysop status without answering a password challenge. | ||
+ | # This is intended ONLY FOR USE ON SECURE LINKS, such as RS232 | ||
+ | # or Ethernet. | ||
+ | # of gatewaying or digipeating, | ||
+ | # remote system back into this port, thus gaining sysop status. | ||
+ | # The default for this parameter is zero!! | ||
+ | # | ||
+ | ;SYSOP=0 | ||
+ | # | ||
+ | # | ||
+ | # The APPLMASK parameter is used only if you are using XRPi to | ||
+ | # provide network connectivity to other applications. It | ||
+ | # specifies which applications will be directly connectible on | ||
+ | # this port. Default is 255, which allows applications 1-8. | ||
+ | # The value is made up by adding together the desired selection | ||
+ | # from the following numbers: | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # If you want an application to be directly connectible on a | ||
+ | # port it must have a callsign, an alias or both, and the | ||
+ | # | ||
+ | # | ||
+ | ; | ||
+ | # | ||
+ | # | ||
+ | # Optional port-specific ID text, sent every IDINTERVAL in place | ||
+ | # of the global IDTEXT (e.g. for APRS-only ports). | ||
+ | # line may be sent. | ||
+ | # | ||
+ | ; | ||
+ | # | ||
+ | # | ||
+ | # CFLAGS allows level 2 uplinking and/or downlinking to be | ||
+ | # | ||
+ | # Default is 3. Add together the decimal values of the desired | ||
+ | # options from this list: | ||
+ | # | ||
+ | # Bit Dec | ||
+ | # | ||
+ | # 0 | ||
+ | # 1 | ||
+ | # 2 | ||
+ | # 3 | ||
+ | # 4 16 - Allow L2 fragmentation. | ||
+ | # | ||
+ | # The default value is 3, i.e. unconditional use of the port. | ||
+ | # | ||
+ | # | ||
+ | # downlink. | ||
+ | # | ||
+ | # Bit 2 allows APPLICATIONS to downlink unconditionally, | ||
+ | # even if users are prevented from downlinking. | ||
+ | # | ||
+ | # Bit 3 was provided to keep the Luddites happy, but its use is | ||
+ | # strongly deprecated. | ||
+ | # from being originated by the port if it is carrying an | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # Bit 4 allows AX25 layer 2 fragmentation if it is set. This is | ||
+ | # required if Forward Error Correction (FEC) is in use, to allow | ||
+ | # big L3 frames to be sent. | ||
+ | # | ||
+ | ;CFLAGS=3 | ||
+ | # | ||
+ | # | ||
+ | # Remote NET/ROM systems to whom we will tunnel L2 frames. | ||
+ | # (See manual for full explanation) | ||
+ | # | ||
+ | ; | ||
+ | # | ||
+ | # | ||
+ | # Modem Initialisation string (Modem interfaces only) | ||
+ | # | ||
+ | ; | ||
+ | # | ||
+ | # | ||
+ | # Default digipeater path for APRS frames originated by APRS | ||
+ | # messaging shell and Igate. If you omit this, the frames will | ||
+ | # be sent without any digipeaters. Messaging shell users may | ||
+ | # override this path. | ||
+ | # | ||
+ | ; | ||
+ | # | ||
+ | # | ||
+ | # DYNDNS=1 enables the dynamic DNS update client. DYNDNS=0 | ||
+ | # disables the client, as does omitting the directive. Requires | ||
+ | # a suitable configuration in DYNDNS.CFG (see manual). | ||
+ | # Note: you must only use this directive on ONE port, and you | ||
+ | # may crash XRouter if you try to use it on more than one. | ||
+ | # | ||
+ | ;DYNDNS=1 | ||
+ | # | ||
+ | # | ||
+ | # Forward Error Correction enable/ | ||
+ | # In order to make use of FEC, the port needs to be using a | ||
+ | # KISS TNC with the CRC check disabled, or an SCC or YAM card. | ||
+ | # | ||
+ | ;FEC=0 | ||
+ | # | ||
+ | # | ||
+ | # IPLINK is required only by AXIP and AXUDP ports. It specifies | ||
+ | # the IP address or hostname of the link peer. It is more | ||
+ | # efficient to use the IP address if possible. However, the | ||
+ | # | ||
+ | # | ||
+ | ; | ||
+ | # | ||
+ | # | ||
+ | # UDPLOCAL is required only by AXUDP ports (default=93). | ||
+ | # It specifies the UDP service number at the local end of an | ||
+ | # AXUDP link. This number must match the link partner' | ||
+ | # | ||
+ | # from him to you. You may use the same UDPLOCAL for more than | ||
+ | # one PORT. You must not let your link partner dictate this | ||
+ | # | ||
+ | # AXUDP for more details. | ||
+ | # | ||
+ | ; | ||
+ | # | ||
+ | # | ||
+ | # UDPREMOTE is required only by AXUDP ports (default=93). | ||
+ | # It specifies the UDP service number at the remote end of an | ||
+ | # AXUDP link. This number must match the link partner' | ||
+ | # UDPLOCAL, and must be dictated by your link partner, not you. | ||
+ | # | ||
+ | ; | ||
+ | # | ||
+ | # | ||
+ | # ENDPORT ends a PORT definition block (mandatory). | ||
+ | # | ||
+ | ;ENDPORT | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # EXAMPLE PORTS | ||
+ | # | ||
+ | # There are only minor differences between port configurations, | ||
+ | # depending on the underlying INTERFACE type. Therefore detailed | ||
+ | # examples of ports for each interface type are not shown. The | ||
+ | # following examples highlight some of the differences. | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # Example 1200 baud user port, using channel A of a KISS TNC. | ||
+ | # | ||
+ | # Netrom disabled because it is user access only. | ||
+ | # | ||
+ | # beacons from the BBS (callsign GB7PZT) that is wire-linked to | ||
+ | # port 7, plus the use of PIPE and PIPEFLAG to conduct UNPROTO | ||
+ | # requests and responses to/from the BBS. | ||
+ | |||
+ | ;PORT=1 | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; PIPE=7 GB7PZT ; Selective pipe to GB7PZT on port 7 | ||
+ | ; | ||
+ | ;ENDPORT | ||
+ | |||
+ | |||
+ | |||
+ | # | ||
+ | # Example Forward Error Corrected full-duplex linking port. | ||
+ | # | ||
+ | # | ||
+ | # In order to use FEC the TNC *must* be using the KISSFEC EPROM. | ||
+ | |||
+ | ;PORT=2 | ||
+ | ; ID=70cm FDX link to GLOS | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ;ENDPORT | ||
+ | |||
+ | |||
+ | |||
+ | # | ||
+ | # Example Loopback port for test purposes and self-connects. | ||
+ | # | ||
+ | # Use with caution. **ABSOLUTELY FOR TEST PURPOSES ONLY!** | ||
+ | # May cause catastrophic endless loops if IP routing is | ||
+ | # | ||
+ | |||
+ | ;PORT=3 | ||
+ | ; | ||
+ | ; | ||
+ | ;ENDPORT | ||
+ | |||
+ | |||
+ | |||
+ | # | ||
+ | # Example Ethernet port. | ||
+ | # | ||
+ | # | ||
+ | |||
+ | ;PORT=4 | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ;ENDPORT | ||
+ | |||
+ | |||
+ | |||
+ | # | ||
+ | # Example AXIP (AX25 over IP wormhole) port. | ||
+ | # | ||
+ | # You need one of these for each AXIP link | ||
+ | # At least ID, INTERFACENUM, | ||
+ | # The IPLINK address is the remote host's IP address or | ||
+ | # hostname. Parameters such as TXDELAY, TXTAIL, SLOTTIME, | ||
+ | # PERSIST, FULLDUP etc. are meaningless for AXIP, but FRACK, | ||
+ | # RESPTIME, PACLEN, MAXFRAME, QUALITY etc. operate as normal. | ||
+ | |||
+ | |||
+ | ;PORT=5 | ||
+ | ; ID=AXIP link with WA3DXX | ||
+ | ; | ||
+ | ; | ||
+ | ;ENDPORT | ||
+ | |||
+ | |||
+ | |||
+ | # | ||
+ | # Example AXUDP (AX25 over UDP wormhole) port. | ||
+ | # | ||
+ | # You need one of these for each axudp link | ||
+ | # At least ID, INTERFACENUM, | ||
+ | # The IPLINK address is the remote host's IP address or | ||
+ | # hostname. UDPLOCAL and UDPREMOTE are the UDP port numbers for | ||
+ | # each end of the link, and if omitted they default to 93. | ||
+ | # | ||
+ | # FULLDUP etc. are meaningless for AXUDP, but FRACK, RESPTIME, | ||
+ | # PACLEN, MAXFRAME, QUALITY etc. operate as normal. | ||
+ | |||
+ | ;PORT=6 | ||
+ | ; ID=AXUDP link with VK1UDP | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ;ENDPORT | ||
+ | |||
+ | |||
+ | |||
+ | # | ||
+ | # Example AXIP link with XServ BBS (GB7PZT) | ||
+ | # | ||
+ | # | ||
+ | # use of BCAST and BCFROM in conjunction with port 1. Also | ||
+ | # | ||
+ | # and smaller FRACK and RESPTIME befitting a high quality wired | ||
+ | # link. | ||
+ | |||
+ | ;PORT=7 | ||
+ | ; ID=AXIP Link to GB7PZT | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ;ENDPORT | ||
+ | |||
+ | |||
+ | |||
+ | # | ||
+ | # Example APRS-only port. | ||
+ | # | ||
+ | # Note the use of an alternate IDTEXT and IDPATH, and the use of | ||
+ | # CFLAGS to disable connected mode operations, thus MAXFRAME, | ||
+ | # | ||
+ | |||
+ | ;PORT=8 | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
+ | ;ENDPORT | ||
+ | |||
+ | |||
+ | # Define your PORTs here: | ||
+ | |||
+ | |||
+ | ###################################################################### | ||
+ | # APPLICATIONS: | ||
+ | ###################################################################### | ||
+ | # | ||
+ | # In this context " | ||
+ | # provide their connectivity with the outside world. XRPi does | ||
+ | # not currently provide the BPQ Host API, but it does provide | ||
+ | # the following means for supporting applications: | ||
+ | # | ||
+ | # - AGW TCPHOST Interface | ||
+ | # - WA8DED Hostmode Emulation | ||
+ | # - TNC2 Emulation | ||
+ | # - KISS / SLIP / PPP links | ||
+ | # - Remote Host Protocol (RHP) | ||
+ | # - Proxies | ||
+ | # | ||
+ | # | ||
+ | # this section, in order to be able to accept incoming | ||
+ | # | ||
+ | # using KISS, SLIP, PPP, or Proxies. | ||
+ | # | ||
+ | # Each definition block must begin with APPL=< | ||
+ | # end with ENDAPPL. | ||
+ | # | ||
+ | # only a single definition. | ||
+ | # or more of the following keywords: | ||
+ | # | ||
+ | # | ||
+ | # accessed from XRPi's command line. e.g. " | ||
+ | # user types this name at the command prompt, they | ||
+ | # will be connected to the application. | ||
+ | # | ||
+ | # | ||
+ | # use. If specified, the application will accept AX25 | ||
+ | # L2 connects to this callsign, subject to the setting | ||
+ | # of APPLMASK (see below). | ||
+ | # | ||
+ | # APPLALIAS The AX25 layer 2 " | ||
+ | # If specified, the application will accept AX25 L2 | ||
+ | # connects to this callsign, subject to the setting of | ||
+ | # APPLMASK (see below). | ||
+ | # | ||
+ | # | ||
+ | # value is specified here, the APPLCALL will be | ||
+ | # included in Net/Rom nodes broadcasts and the | ||
+ | # application will be connectible at AX25 layer 4. | ||
+ | # The higher the quality, the further the node entry | ||
+ | # will propogate. | ||
+ | # | ||
+ | # APPLFLAGS defaults to 0 if omitted. The flags are as follows: | ||
+ | # | ||
+ | # Bit Value Action | ||
+ | # ------------------ | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # user upon connection to an application. | ||
+ | # This is not required if the application | ||
+ | # sends its own " | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # All fields within an application definition block are optional | ||
+ | # - you may have for instance choose to have an APPLNAME but no | ||
+ | # APPLCALL, meaning the application could only be reached by | ||
+ | # typing the applname at the command prompt. Or you could have | ||
+ | # an APPLCALL but no APPLNAME, in which case the application | ||
+ | # would be directly connectible, | ||
+ | # a command line shortcut. | ||
+ | # | ||
+ | # The choice of application number is arbitrary at present, but | ||
+ | # each application should be assigned a different non-zero | ||
+ | # number between 1 and 8. | ||
+ | # | ||
+ | # Remember to set the APPLMASK in each PORT upon which you want | ||
+ | # the application to be usable. | ||
+ | # | ||
+ | # Example for a Bulletin Board System application using WA8DED | ||
+ | # hostmode. It is accessed by typing " | ||
+ | # or by connecting via AX25 or NetRom to the callsign GB7PZT or | ||
+ | # the alias PZTBBS: | ||
+ | # | ||
+ | # APPL=3 | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # ENDAPPL | ||
+ | # | ||
+ | # In the following example, the application has no callsigns or | ||
+ | # quality, so it can only be reached by issuing the command | ||
+ | # | ||
+ | # | ||
+ | # APPL=2 | ||
+ | # | ||
+ | # ENDAPPL | ||
+ | # | ||
+ | # Define your applications here: | ||
+ | # | ||
+ | |||
+ | |||
+ | |||
+ | ###################################################################### | ||
+ | # Proxies | ||
+ | ###################################################################### | ||
+ | # | ||
+ | # In this context, " | ||
+ | # | ||
+ | # accessed using another protocol. They can also be used | ||
+ | # to give " | ||
+ | # | ||
+ | # Be *very* careful when mixing proxies and pipes, or you | ||
+ | # will end up generating lots of FRMR' | ||
+ | # crashing the system. These are powerful tools and must | ||
+ | # be used carefully. | ||
+ | # | ||
+ | # Proxies are intended for use with your own systems only. | ||
+ | # Do not act as a proxy for someone else's system without | ||
+ | # their permission. | ||
+ | # | ||
+ | # You must *NEVER* set up a proxy to give a NetRom | ||
+ | # presence to a node which already has one!! | ||
+ | # | ||
+ | # For proxies which include < | ||
+ | # the port actually exists (sysops often rearrange ports | ||
+ | # rendering the proxies inactive). | ||
+ | # | ||
+ | # !! IT IS RARE FOR ANYONE TO NEED TO SET UP A PROXY !! | ||
+ | # If you don't understand this concept, please don't use it. | ||
+ | # | ||
+ | # | ||
+ | # AX25 / NetRom -> TCP Proxy: | ||
+ | # | ||
+ | # Allows a remote TCP/IP-only system to have NetRom and AX25 | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # < | ||
+ | # proxied system. | ||
+ | # | ||
+ | # | ||
+ | # system. | ||
+ | # | ||
+ | # | ||
+ | # visibility on the NetRom network. | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # proxied system. | ||
+ | # | ||
+ | # | ||
+ | # system upon connection. This is used to | ||
+ | # verify that the TCP connection originates | ||
+ | # from an approved proxy. | ||
+ | # | ||
+ | # AX25 and NetRom are pure binary channels, whereas standard | ||
+ | # telnet is not. The proxied system must provide a pure | ||
+ | # binary service port in order to make full use of this | ||
+ | # facility for compressed forwarding etc. | ||
+ | # | ||
+ | ; | ||
+ | # | ||
+ | # | ||
+ | # NetRom -> AX25 Proxy: | ||
+ | # | ||
+ | # This is similar to the NetRom -> TCP proxy described | ||
+ | # above, but is intended to allow an AX25-only system to | ||
+ | # have a NetRom presence. | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | # < | ||
+ | # | ||
+ | # | ||
+ | # connected to. | ||
+ | # | ||
+ | ; | ||
+ | # | ||
+ | # | ||
+ | # | ||
+ | ###################################################################### | ||
+ | # Locked-in Routes | ||
+ | ###################################################################### | ||
+ | # | ||
+ | # Routes to lock in - begins with ROUTES and ends with *** | ||
+ | # Syntax of each entry in the block is as follows: | ||
+ | # | ||
+ | # | ||
# | # | ||
+ | # You must specify at least callsign, port and quality. | ||
+ | # include the lock flag ( ! ) the route will be locked in, and | ||
+ | # will only be changed by a replacement entry with the lock flag | ||
+ | # set. If you don't include the lock flag, the route will | ||
+ | # | ||
+ | # | ||
+ | # its contents will override the entries here, subject to the | ||
+ | # locking rules above, and the sysop may also edit routes while | ||
+ | # XRouter is running. | ||
# | # | ||
- | # ======================================================================= | + | # Maxframe, frack and paclen are optional. |
- | # Interface definitions | + | # override port defaults for that route. |
- | # ======================================================================= | + | # Note FRACK is expressed in millisecs, e.g. 7000 = 7 secs. |
+ | # Maxframe > 7 will cause Modulo-128 to be attempted on that | ||
+ | # route. | ||
# | # | ||
- | # Loopback interface | + | ;ROUTES |
- | # Please note: This loopback is internal to XRouter only. It does NOT | + | ; Lock in g6yak on port 1 with quality 100 and maxframe 32 :- |
- | # interface with Linux! It is purely for testing, and you should remove | + | ;g6yak 1 100 ! 32 |
- | # it once you are up and running, otherwise it WILL confuse you. | + | ;*** |
+ | |||
+ | |||
+ | |||
+ | |||
+ | ##################################################################### | ||
+ | # | ||
+ | ###################################################################### | ||
# | # | ||
- | INTERFACE=1 | + | # In this section you may define single-word aliases for |
- | TYPE=LOOPBACK | + | # |
- | MTU=256 | + | # to set up BBS, CONV and DXCLUSTER commands to point to local |
- | ENDINTERFACE | + | # systems. There is no limit to the number of commands you can |
+ | # define. | ||
# | # | ||
- | # ===================================================================== | + | # Each command is defined using a separate " |
- | # Port definitions. Each one begins with PORT and ends with ENDPORT | + | # and the arguments are < |
- | # ===================================================================== | + | |
# | # | ||
- | # Port "attached" | + | # e.g. "COMMAND=BBS C 7 GB7PZT" |
- | PORT=1 | + | # called BBS, which translates to the sequence C 7 GB7PZT" |
- | ID="Loopback port" | + | |
- | INTERFACENUM=1 | + | |
- | ENDPORT | + | |
# | # | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
</ | </ |
packet/xrouter/manpages/examples/xroutercfg.txt · Last modified: 2025/04/20 06:40 by m0mzf