KISS Error on VMAIL notification

Hi. When my modem connects to a station for which there is VMAIL waiting, I get an error in the log. I have previously been able to send VMAILs to an AWAY station. Is this a problem of the software or my machine?

KISS port is set to 8100 on both HF modem (v4.6.4) and VarAS (v6.0.8)

Data Stream pane:

08:31:28 - <SENDING ASYNC MESSAGE> VMAIL RELAY NOTIFICATION: THERE ARE VMAILS WAITING FOR HB9xxx

This results in:

07/11/2022 08:31:18 - Preparing to send a VMail relay notifiaction to HB9xxx

07/11/2022 08:31:28 - Sending Async message: TO:HB9xxx FROM:VK6II Data:<SMP>

07/11/2022 08:31:29 - Error: Unable to send KISS message to VARA modem. Disconnecitng modem.

07/11/2022 08:31:29 - Unable to write data to the transport connection: An established connection was aborted by the software in your host machine.

at System.Net.Sockets.NetworkStream.Write(Byte[] buffer, Int32 offset, Int32 size)

at VarAC.VarAC.command_varahf_kiss(TcpClient conn, Byte[] msg)

07/11/2022 08:31:29 - Restarting VARA modem 1/2

07/11/2022 08:31:29 - Disconnecting VARA modem...

07/11/2022 08:31:29 - Disconnected!

07/11/2022 08:31:30 - Error in mailbox_send_outbox_thread

07/11/2022 08:31:30 - Error: Unable to read data from command stream of VARA modem. Disconnecitng modem command stream.

07/11/2022 08:31:30 - Error: processing Modem data stream: Thread was being aborted.

at System.Net.UnsafeNclNativeMethods.OSSOCK.recv(IntPtr socketHandle, Byte* pinnedBuffer, Int32 len, SocketFlags socketFlags)

at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags, SocketError& errorCode)

at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)

at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)

at VarAC.VarAC.<button_connect_varahf_Click>b__566_2()

07/11/2022 08:31:30 - Thread was being aborted.

at System.Net.UnsafeNclNativeMethods.OSSOCK.recv(IntPtr socketHandle, Byte* pinnedBuffer, Int32 len, SocketFlags socketFlags)

at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags, SocketError& errorCode)

at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)

at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)

at VarAC.VarAC.<button_connect_varahf_Click>b__566_0()

07/11/2022 08:31:30 - Unable to read data from data stream of VARA modem. Disconnecitng modem data stream.

07/11/2022 08:31:30 - Thread was being aborted.

at System.Threading.Thread.SleepInternal(Int32 millisecondsTimeout)

at System.Threading.Thread.Sleep(Int32 millisecondsTimeout)

at VarAC.VarAC.<button_connect_varahf_Click>b__566_4()

07/11/2022 08:31:40 - Connecting VARA Main Modem Command interface...

07/11/2022 08:31:40 - Connecting VARA Main Modem KISS Command interface...

07/11/2022 08:31:40 - Connecting VARA Main Modem data stream...

07/11/2022 08:31:40 - Connected to VARA modem

07/11/2022 08:31:40 - Setting Bandwith to 500Hz

07/11/2022 08:31:40 - Error: Sending relay notification failed: Thread was being aborted.

at VarAC.VarAC.command_varahf_kiss(TcpClient conn, Byte[] msg)

at VarAC.VarAC.<>c__DisplayClass539_0.<Load_configuration>b__1()

07/11/2022 08:31:40 - VARA version: VARA HF v4.6.4

7 Comments

irad d

Nov 11, 2022

Best Answer

Hi All. Jose the creator of VARA (EA5HVK) accidently uploaded a buggy 4.6.4 version that was available for download somewhere between November 1-9th.

That version has a critical bug in the KISS socket.

He uploaded yesterday a fixed version - V4.6.5 that should resolve this.

Please give it a try.

Irad

KI5GBV

Replying to

Just gave it a test, can confirm that updating to V4.6.5 fixes the issue. Thanks so much!

vk6ii

Nov 12, 2022

Hi Irad.

Updated to VARA 4.6.5. today, and can confirm that the error no longer occurs. Thanks for the heads up.

Stephen Shankle

Nov 13, 2022

This fixed my KISS errors, but broke relays. I beacon, other station replies with vmail notification, but i don't decode anything. If i connect to them it will transfer the vmail. Ended up going back to a pre-november version of 4.6.4 and all good.

Nov 08, 2022

I have the exact same problem, I'll add my debug output in case it's helpful. I figured it was a firewall problem, but I've whitelisted both VARA and VarAC, so I doubt it. Will post updates if I find anything.

Nov 09, 2022

Looks like exact same problem to me too. 😀

Further to the above:

The following is relevant output from netstat -aon command, shortly after startup of VARA & VARAC processes.

TCP 127.0.0.1:8100 127.0.0.1:50200 FIN_WAIT_2 9960

TCP 127.0.0.1:8300 127.0.0.1:50199 ESTABLISHED 9960

TCP 127.0.0.1:8301 127.0.0.1:50201 ESTABLISHED 9960

TCP 127.0.0.1:8884 0.0.0.0:0 LISTENING 4

TCP 127.0.0.1:9012 0.0.0.0:0 LISTENING 7116

TCP 127.0.0.1:49704 0.0.0.0:0 LISTENING 2668

TCP 127.0.0.1:50163 0.0.0.0:0 LISTENING 4136

TCP 127.0.0.1:50199 127.0.0.1:8300 ESTABLISHED 1584

TCP 127.0.0.1:50200 127.0.0.1:8100 CLOSE_WAIT 1584

TCP 127.0.0.1:50201 127.0.0.1:8301 ESTABLISHED 1584

It appears that the KISS port network connection is opened on startup of VARA & VARAC, but are not held open.

On the next running of netstat -aon (5mins), the connection and port info has disappeared. Is this the reason for the log output "Error: Unable to send KISS message to VARA modem. Disconnecitng modem." ?