Dear all
I have searched in the forum to find an answer to my questions but have not found anything.

1. I have connected my SunSDR2Dx directly to my Mac and it was easy to configure and it run out of the box.
2. Then I wanted to connect the SunSDR2Dx to the router to access it within my local network and I even opened the appropriate ports and I was able to access the rig from out side as well. To do so, I have assigned a fixed IP to the rig (192.168.1.199) in the range of my router (192.168.1.1). I have taken care that the DHC of the router does not include this address and so far so good.

I have problems when transmitting on CW and I am not sure if it is an EMI problem or a latency problem. I loose dots on, but on my headphones, connected to the laptop, not when connected to the rig. If power is low then the problems disappear, so I am afraid it is an EMI issue and maybe picked up by the ethernet cables. Therefore I want to make some tests.
First of all I want to directly connect the rig again to the laptop, BUT without changing the IP of the rig back to 192.168.16.200 and keeping the 192.168.1.199.

But I am unable to connect to the rig. EESDR2 sees the rig, I click on Use, but when I ask for info it says it is unreachable.

What am I doing wrong?

Thank you,

Stefan
73 de EA5Q

What is definitely wrong is that you are trying to reach 192.168.1.199/24 from 192.168.2.1/30 when routing between those subnets is not configured.

192.168.2.1/30 certainly discovers 192.168.1.199/24 via supernet broadcast, but when it goes to two way communication, then 192.168.1.199/24 has no idea how to reach 192.168.2.1/30.

For "durect LAN" either place both - PC and Tranceiver into one subnet; or, alternatively, configure routing between existing vlans.

UPD. What you have to do now, to re-establish connectivity - for example, set your PC IP to 192.168.1.50/24 and connect PC with SunSDR via direct cable - then you can change SunSDR IP to .200. Then - contibue with your experiments.

ea5q пишет:
For now, just change the Laptop IP address so the subnet is the same as the now configured Radio.

Simply change the laptop IP address to something like 192.168.1.150

then you should be able to again connect to Radio

without having to redo that IP address

think of it as working backwards you're changing the laptop IP instead of the radio's IP, but you need to place them in the same networking subnet.

Thank you for your prompt replies.

Well, I have changed over to the same subnet (192.168.1.0) but then EESDR2 does not see the rig, whatever IP I assign to my laptop and trying out two different ethernet-to-USB C adaptors. It does not discover it and it does obviously not connect to it.

SOLUTION: disconnect the WiFi.

- I did not know that I could not have several IPs, one for each NIC my computer has.
- As my WiFi connection connects me to this subnet which is controlled by my router, it seems that then it avoids connection via ethernet to avoid conflicts.
- Maybe another explanation I don't know about?

QUESTION: Is it possible to have a workaround and have direct connection with the same subnet as the WiFi connection and my home router?
I would like to test easily, without changing the rig's IP every time, with direct connection and router connection.

EMI problem:
YES, I have an EMI problem. If the ethernet cable is closer than 20 cm to the RF coax, then packets seem to get lost when send to the laptop, and CW sounds crappy (loosing dots and dashes). It is EMI, because it is power dependent. It only happens at full power (~100 W). I hear the proper transmission when plugging the headphones to the rig directly.
I am using the ethernet cable shipped with the rig, which I suppose is well shielded.
I have a bad grounding => have to work on this, but ground here is very bad and dry.
I will need to try some ferrites around the ethernet cables.
ANY suggestion will be very welcome.

Thank you fro your help and quick answers!

ea5q пишет: This is incorrect perception. You can. On many modern mac models you even can have same IP assigend to WiFi and Ehternet (adapter). Same applies to Win and Linux (just performed less user-friendly way)
ea5q пишет: No, it works different way (OS dependent). First: primary LAN connection is defined by interface priority (in case you have multi-interface, i.e. WiFi, Eth1, Eth2) within OS. Second - OS looks on L3-L4 conflicts/missmatches and disables packet forwarding over affected interfaces (note that same process is happening on your router as well). The key point - you current setup has the conflicting config; and if you will fix it - it start working as expected.
ea5q пишет: Yes, but most likely you will not like them

ea5q пишет:
You should change the METRIC of your ethernet adapters.
the True physical cable connection to the radio should have first priority.
that Metric needs to be set LOWER than your Wi-Fi Metric

example Ethernet Lan connection (Metric of 10) Wi-Fi connection used for internet access etc. Metric 100)

Thank you Pavel and CASDR

I am definitely not and network admin or specialist, but I will try to research further.
I will try to change the metric of my connection to see if both are compatible.

And keep you updated .

Kids regards,
Stefan
73 de EA5Q