The next filter line lets through just VHF/UHF spots from EU.
+=== 8^FORWARD/LATLONG <node_call>^Send latitude and longitude information to another cluster
+This command sends all the latitude and longitude information that your
+cluster is holding against callsigns. One advantage of recieving this
+information is that more locator information is held by you. This
+means that more locators are given on the DX line assuming you have
+SET/DXGRID enabled. This could be a LOT of information though, so
+it is not recommended on slow links.
+
=== 1^FORWARD/OPERNAM <call>^Send out information on this <call> to all clusters
This command sends out any information held in the user file which can
be broadcast in PC41 protocol packets. This information is Name, QTH, Location
or
pc G1TLH Try doing that properly!!!
-=== 1^PING <node>^Send a ping command to another cluster
-This command is used to estimate the quality of the link to another cluster.
-The time returned is the length of time taken for a PC51 to go to another
-cluster and be returned.
-
=== 0^KILL <msgno> [<msgno> ...]^Remove or erase a message from the system
You can get rid of any message to or originating from your callsign using
this command. You can remove more than one message at a time.
You can also use in the same way as a talk command to a connected user but
without any processing, added of "from <blah> to <blah" or whatever.
-=== 1^PING <node call>^Find out the delays an a circuit to another node
-This command will enable sysops to determine the speed of an inter-cluster
-node.
-
+=== 1^PING <node call>^Check the link quality between nodes
+This command allows you to send a frame to another cluster node on
+the network and get a return frame. The time it takes to do this
+is a good indication of the quality of the link. The actual time
+it takes is output to the console in seconds.
Any visible cluster node can be PINGed.
=== 1^RCMD <node call> <cmd>^Send a command to another DX Cluster
=== 5^READ-^
As a sysop you may read any message on the system
-=== 0^REJECT/ANNOUNCE [0-9] <pattern>^Set an 'reject' filter line for announce
+=== 0^REJECT/ANNOUNCE [0-9] <pattern>^Set a 'reject' filter line for announce
Create an 'reject this announce' line for a filter.
-An reject filter line means that if the announce matches this filter it is
+A reject filter line means that if the announce matches this filter it is
passed onto the user. See HELP FILTERS for more info. Please read this
to understand how filters work - it will save a lot of grief later on.
reject/ann input node_default by G,M,2
reject/ann user_default by G,M,2
-=== 0^REJECT/SPOTS [0-9] <pattern>^Set an 'reject' filter line for spots
-Create an 'reject this spot' line for a filter.
+=== 0^REJECT/SPOTS [0-9] <pattern>^Set a 'reject' filter line for spots
+Create a 'reject this spot' line for a filter.
-An reject filter line means that if the spot matches this filter it is
+A reject filter line means that if the spot matches this filter it is
dumped (not passed on). See HELP FILTERS for more info. Please read this
to understand how filters work - it will save a lot of grief later on.
reject/spot user_default by G,M,2
-=== 0^REJECT/WCY [0-9] <pattern>^set an 'reject' WCY filter
+=== 0^REJECT/WCY [0-9] <pattern>^set a 'reject' WCY filter
It is unlikely that you will want to do this, but if you do then you can
filter on the following fields:-
reject/wcy gb7djk all
-=== 0^REJECT/WWV [0-9] <pattern>^set an 'reject' WWV filter
+=== 0^REJECT/WWV [0-9] <pattern>^set a 'reject' WWV filter
It is unlikely that you will want to do this, but if you do then you can
filter on the following fields:-
default values, if a node has not responded to a ping within 15 minutes,
it is disconnected.
+You can set this parameter between 1 and 9.
+
+It is STRONGLY recommended that you don't change the default.
+
=== 0^SET/PAGE <lines per page>^Set the lines per page
Tell the system how many lines you wish on a page when the number of line
of output from a command is more than this. The default is 20. Setting it
You can use this command to set a different interval. Please don't.
-But if you do the value you enter is treated as minutes up 60 and seconds
+But if you do the value you enter is treated as minutes up 30 and seconds
for numbers greater than that.
This is used also to help determine when a link is down at the far end
(as certain cluster software doesn't always notice), see SET/OBSCOUNT
for more information.
+If you must change it (and it may be useful for internet connected nodes
+on dynamic IP addresses that go away after a set time of usage) the time
+can be specified as:-
+
+ 5 which if less than 30 is converted to minutes otherwise is
+ taken as the no of seconds between pings.
+ 120s 120 seconds
+ 5m 5 minutes
+ 1h 1 hour
+
+Please be aware that this causes traffic to occur on the link, setting
+this value too low may annoy your neighbours beyond the point of
+endurance!
+
+You can switch this off by setting it to 0.
+
=== 9^SET/PRIVILEGE <n> <call> [<call..]^Set privilege level on a call
Set the privilege level on a callsign. The privilege levels that pertain
to commands are as default:-
and returns any information available for that callsign. This service
is provided for users of this software by http://www.qrz.com
+=== 0^SHOW/ROUTE <callsign> ...^Show the route to the callsign
+This command allows you to see to which node the callsigns specified are
+connected. It is a sort of inverse sh/config.
+
+sh/route n2tly
+
=== 0^SHOW/SATELLITE <name> [<hours> <interval>]^Show tracking data
Show the tracking data from your location to the satellite of your choice
from now on for the next few hours.
projects / spider.git / blobdiff