locked Re: WSJT-X rc2


g4wjs
 

On 15/11/2020 20:25, Thomas Mills wrote:
Just loaded wsjtx rc2 and got a message that the network port was not working.  found this on the wsjtx release notes, so I guess 239.0.0.1 want work anymore?


 Due to  some users using  inappropriate multicast IP  addresses for
   their interoperating  servers the default behaviour now is  to only
   send multicast  UDP datagrams  to the loop-back  network interface.
   Users who  require WSJT-X UDP  Message Protocol datagrams  to reach
   other  hosts will  now  have  to configure  WSJT-X  to  send on  an
   appropriate  network interface,  and  use  an appropriately  scoped
   multicast group address for their  server applications.  If you are
   not sure then  224.0.0.1 (or ff02::1 if IPv6 is  desired) is a safe
   choice.
Thanks Tom WB4JWM
_._,_._,_

Hi Tom,

you appear to be one of the users using an inappropriate multicast address that has caused this change to be made. Until a version of JTAlert is available that will receive multicast traffic on the loop-back network interface, you can restore functionality by choosing your local subnet network interface in WSJT-X "Settings->Reporting->UDP Server->Outgoing interface".

Multicast addresses in the 239.0.0.0/16 block are potentially globally routed, that is not a good choice for getting traffic to a server on the same host or your local subnet.


--
73
Bill
G4WJS.

Join Support@HamApps.groups.io to automatically receive all group messages.