Odd behavior connecting SmartSDR for Mac 4.9.5 to 6400 running 3.8.20

m5kvk

To avoid unnecessary questions, let me be clear about the environment.

My 6400 is located approx 20 miles from home in a remote shack. I have a Zerotier L3 VPN connection between the two. At home, I have a Macmini. At the remote shack, I have a Windows 11 mini-pc. I also have windows 11 and Mac laptops and an iPad. All have the appropriate version of SmartSDR installed on them. Prior to this week, everything worked 100%.

I needed to rebuild the remote shack PC and installed SmartSDR 3.8.20 on it. This resulted in a firmware upgrade on the 6400; which was applied this morning. After the upgrade, I checked that the remote shack PC could access the 6400, and my MacBook (running SmartSDR for Mac 4.9.5) could also access the radio.

Back home, I checked again that the MacBook could access the 6400 (directly via the VPN and via SmartLink). I also checked that the Windows 11 laptop could access the 6400 from home (via SmartLink). BUT, when I tried to access the 6400 from the Mac mini using Smartlink, I got this:

Note the existence of "1: 14.100 A" in the top bar. As far as SmartLink and the Radio are concerned, there is a connection to slice A. If I hit connect again, this is confirmed by the connection dialogue showing that there is a client connected to the radio. I get this whether I connect directly or via SmartLink.

To be absolutely sure, I tried:

• resetting the settings back to factory defaults
• deleting and reinstalling SmartSDR for Mac.

Nothing made any difference. So, what's going on? How can I debug this.

Before people start taking about network etc - this worked 100% yesterday, and nothing has changed on the Mac mini. The only change (as far as the Mac side is concerned) is that the radio's firmware has been upgraded from 3.5.9 (I think) to 3.8.20.

Gareth - M5KVK

ct1drb

Hello,

it is same behaviour that I have with my actual setup, Mac Mini M4 with latest SmartSDR version.

Did a downgrad to 3.8.19 version but it does not work as well.

My flex6600 is local, no remote.

Best 73 and have a nice weekend.

CT1DRB/OK8RB

David Quental

m5kvk

Thanks, David

If I find a solution, I'll be sure to report back.

ct1drb

Hello Gareth,

ok, fine, thanks for your words, lets see if we have a solution to solve problem.

Best 73.

CT1DRB/OK8RB

David Quental

K3SF

I run 6600m with ssdr 3.8.20 installed

Current version of mac smartsdr is 2.9.45… **makes sure to update to this version **

I run it in macbookair M1 with macos 15.2 (sequioa)

and

on mac minis ( intel and M1) running Sonoma

** also be sure to do data update *

Paul K3SF

ct1drb

Hello Paul and Gareth,

how are you doing?

Thanks Paul for your help but even so it does not work here, take a look:

As you can see I have the 2.9.45 SmartSDR version, I did the Data Update and it does nothing because it is updated but even so software does not work at all, I guess that Gareth still has the same problem.

I have a Flex6600 but it seems does not matter.

In Windows, iPhone and iPad it works well but not in my Mac mini m4.

Best 73 es tks for help.

CT1DRB/OK8RB

David Quental

m5kvk

No, I'm still not at the bottom of this. On the basis that everything works OK on Windows and from another Mac on the same home network, I'm pointing the finger at the Mac Mini.

It's running version 2.9.45 and its data is up to date. I've tried re-installing (with and without deleting all the user data), and I've tried running from a different user account (to be sure there is no user data). Nothing works.

I've now got Wireshark running in an attempt to see who is taking to whom.

I'll update the thread as and when I make progress.

m5kvk

OK, I got to the bottom of this once I started running Wireshark.

I noticed that - even if SmartSDR was not running, in fact even if it was uninstalled - that something was attempting to connect to TCP port 4992 on the Flex. Once I did a sudo lsof -nP -i4TCP:4992 I could see that dotnetwas running on my Mac and trying to connect.

This was a hang over from when I installed the Mac version of frstackwebapi on my Mac. I quit the dotnet process and then SmartSDR for Mac connected OK to a Fixed IP address. It also connected using SmartLink (though I don't use this from home).

I cannot promise that will also be the solution to David's problem; neither do I understand why this problem only emerged once I upgraded the firmware on the Flex. I also don't understand why dotnet was trying to connect to port 4992 rather than 4993, or why dotnet was even running, but that's irrelevant as I've deleted dotnet now. However, I would start by running Wireshark to see who is talking to whom.

ct1drb

Hello all,

in fact there is a process named dotnet when I start SmartSDR app and when I killed it SmartSDR works well, min tks for your work Gareth, it seems that you discovered the culprit.

Lets see if the problem will be solved in future.

Best 73 es tks agn.

CT1DRB/OK8RB

David Quental

ct1drb

Hello all,

I think I have already solved problem, I erased dotnet following suggestion from this site:

https://gist.github.com/maximgorbatyuk/e4afb2d8ae6ac85fe32c05964931290f

Now when I start SmartSDR app, after a switch on computer, dotnet does not start and flex works quite well now, mni tks for all your work Gareth and hoping that our problem can help others.

Best 73 es tks.

CT1DRB/OK8RB

David Quental

K3SF

OK…great find about dotnet….

now my question " where did dotnet orignated from"??…

best i can find is it seems maybe a microsoft pkg for visual studio

Paul K3SF