CLX archive - 1998: Re: Virtual Link

Re: Virtual Link

CLX-User DL6RAI (ybopj@neonramp.com)
Wed, 14 Oct 1998 21:53:12 +0200 (MEST)


Dear Neal,

> I have been up on CLX for over a week now and am really happy with it. The
> passive connectivity capability, along with it being on a modern OS is a
> great advantage. I will try to influence some of my fellow East Coast
> sysops to migrate, but doubt many will as they are not very active in terms
> of maintaining their nodes.

Same here. But we are working on it.

> I think I have encountered a bug (although maybe its a feature?): My node
> call is K3NC. If I start net_user with the call K3NC or K3NC-0, I
> immediately see a PC18 appear on the screen, and it disconnects my link to
> my active cluster partner. Is this normal?

It is normal. You cannot log in with the nodes callsign. That's why we
created the -16 extension by default.

> My question concerns the script to listen to a freq and capture transmitted
> spots without being connected. How should I define this virtual connection
> in cluster_par? I have done a section with the callsign of the node I am
> listening to, and used the connection type as X and using the listening
> script, but it does not work. I get an entry in io.log about a SIGHIGH
> error (or something like that) and it immediately "disconnects". I would
> love to get this to work as I can hear a cluster node on my user access
> frequency that is too far away for me to connect to, but who's signal is
> loud enough for monitoring!

1. Make sure the script is working when you are calling it from the shell
prompt. Take a look at the script kam-monitor, that was used at
TK5NN in 1997 for receiving DX spots from an HF link with a
KAM.

2. Make your virtual link passive, User Mode, without link check with
a type "x". Put the script file in exec/connect and its name should
be given on the conn_path line.

3. re-read the cluster_par file and watch the log for what's happening.

4. If it breaks, try to find out where and if you can't, send me an
excerpt from the log file and your script. Or better yes, post it
to the CLX reflector!

73 Ben

-- 
[] clx - PacketCluster Software for Linux
[] c/o Bernhard ("Ben") Buettner, DL6RAI
[] Internet: egdfqz@roskapostia.tunk.net
[] Packet: DL6RAI @ DB0AAB.#BAY.DEU.EU