Commit Graph

6823 Commits

Author SHA1 Message Date
Bill Somerville
dc169c3a84
Resolve some issues with sequencing of R+rprt and sign-off messages 2020-11-12 13:32:56 +00:00
Bill Somerville
c7f2fdc404
Ensure Tx1 message is used by non-standard callsign holders
The only exception is type 2 prefix/suffix calls in non-77-bit modes.
2020-11-12 13:30:48 +00:00
Bill Somerville
92cdcb1ffe
Helper functions for callsign analysis 2020-11-11 16:22:57 +00:00
Bill Somerville
bc2999499a
Updates Spanish UI translation, tnx to Cédric, EA4AC. 2020-11-11 11:45:22 +00:00
Bill Somerville
61736eb54c
Chinese and Hong Kong UI translation updates, tnx to Sze-To, VR2UPU 2020-11-11 10:35:02 +00:00
Bill Somerville
713a92bce8
Merge branch 'release-2.3.0' into develop 2020-11-10 20:23:49 +00:00
Bill Somerville
742c180967
Allow message_aggregator example to not join on he loopback interface 2020-11-10 20:12:38 +00:00
Bill Somerville
988fcfac5a
Ensure network interfaces validation is run on start up 2020-11-10 20:12:38 +00:00
Bill Somerville
b816875b46
Ensure multicast UDP is sent to at least the loop-back interface
Also send multicast UDP to every selected network interface.
2020-11-10 20:12:38 +00:00
Bill Somerville
bdaf51a074
Comment out diagnostic prints 2020-11-10 20:12:37 +00:00
Bill Somerville
780b1f74ee
Message Client allows sending multicast UDP on multiple interfaces 2020-11-10 20:12:37 +00:00
Bill Somerville
e61a1f969c
UDP multicast TTL default as one
Restricts scope to local subnet.
2020-11-10 20:12:37 +00:00
Bill Somerville
f4db2904a3
Correct Qt version checks 2020-11-10 20:12:36 +00:00
Bill Somerville
50cce43e92
Pre Qt 5.14 compatibility 2020-11-10 20:12:36 +00:00
Bill Somerville
e538ce9294
Disallow sending UDP Message Protocol traffic to broadcast address 2020-11-10 20:12:36 +00:00
Bill Somerville
ff6f01c6b5
Pre Qt v5.11 compatibility 2020-11-10 20:12:35 +00:00
Bill Somerville
ced3b523ea
Add network interface selection combo box widget to message_aggregator 2020-11-10 20:12:35 +00:00
Bill Somerville
1d9dd7df24
Remove unwanted file and directory 2020-11-10 20:12:35 +00:00
Bill Somerville
4e0e23c301
New combo box with a list of checkable items 2020-11-10 20:12:34 +00:00
Bill Somerville
f9aa10f3a5
UDPDaemon command line flag to list network interfaces 2020-11-10 20:12:34 +00:00
Bill Somerville
7b54428a60
Extend UDP MessageServer client mapping key with the host address
The UDP Example reference applications  now work correctly with WSJT-X
instances with duplicate --rig-name= command line arguments so long as
duplicate instances are run on unique hosts.
2020-11-10 20:12:33 +00:00
Bill Somerville
662ed0fa7a
Network interface selection for outgoing UDP multicast datagrams
Default  selection  is  the  loop-back interface.  Users  who  require
interoperation  between  WSJT-X   instances  cooperating  applications
running on different hosts should  select a suitable network interface
and  carefully choose  a multicast  group address,  and TTL,  that has
minimal scope covering the necessary  network(s). Using 224.0.0.1 is a
reasonable    strategy    if   all    hosts    are    on   the    same
subnet. Administratively  scoped multicast group addresses  like those
within 239.255.0.0/16  can cover larger  boundaries, but care  must be
taken if the local subnet has access to a multicast enabled router.

The  IPv4  broadcast  address  (255.255.255.255) may  be  used  as  an
alternative  to multicast  UDP, but  note that  WSJT-X will  only send
broadcast UDP datagrams  on the loop-back interface,  so all recipient
applications must be running on the same host system.

The reference UDP Message protocol  applications are being extended to
be configurable  with a list of  interfaces to join a  multicast group
address on. By default they will only join on the loop-back interface,
which is also  recommended for any applications designed  to take part
in the WSJT-X  UDP Message Protocol. This allows full  user control of
the  scope of  multicast  group membership  with  a very  conservative
default  mode  that will  work  with  all interoperating  applications
running on the same host system.
2020-11-10 20:12:33 +00:00
Bill Somerville
de0af5a2ed
Merge branch 'feat-outgoing-udp-interface' into develop 2020-11-10 20:09:48 +00:00
Bill Somerville
7f5870bdfe
Merge branch 'release-2.3.0' into develop 2020-11-09 13:43:51 +00:00
Bill Somerville
9e71d07075
L10n translation file updates 2020-11-09 13:27:21 +00:00
Bill Somerville
f896532770
Further Chinese and Hong Kong UI translations, tnx Sze-To, VR2UPU 2020-11-09 12:57:48 +00:00
Bill Somerville
e52cd9fb14
Further Chinese and Hong Kong UI translations, tnx Sze-To, VR2UPU 2020-11-09 12:56:32 +00:00
Bill Somerville
9b634c9a2b
Updated Chinese and Hong Kong UI translations, tnx Sze-to, VR2UPU 2020-11-07 13:47:26 +00:00
Bill Somerville
6a1223ce6f
Updated Chinese and Hong Kong UI translations, tnx Sze-to, VR2UPU 2020-11-07 13:42:42 +00:00
Bill Somerville
aa1f0554b0
Merge branch 'develop' of bitbucket.org:k1jt/wsjtx into develop 2020-11-07 13:42:05 +00:00
Bill Somerville
68056ae8fa
Testing options
Two new environment variables to control special testing behaviour:

    * WSJT_TX_BOTH - set to "1" to force transmission on both periods.

    * WSJT_REVERSE_DOPPLER - set to "1" to transpose Tx and Rx Doppler
      corrections. Use this to test Doppler tracking on a terrestrial
      link.
2020-11-06 18:34:02 +00:00
Bill Somerville
ab780a324a
Testing options
Two new environment variables to control special testing behaviour:

    * WSJT_TX_BOTH - set to "1" to force transmission on both periods.

    * WSJT_REVERSE_DOPPLER - set to "1" to transpose Tx and Rx Doppler
      corrections. Use this to test Doppler tracking on a terrestrial
      link.
2020-11-06 18:28:59 +00:00
Steven Franke
e0888eb70c Restore wsprsimf and dependencies. 2020-11-06 09:33:44 -06:00
Bill Somerville
499704d275
Allow message_aggregator example to not join on he loopback interface 2020-11-06 01:28:19 +00:00
Bill Somerville
d953c455fe
Ensure network interfaces validation is run on start up 2020-11-06 01:27:36 +00:00
Bill Somerville
9434c447cd
Ensure multicast UDP is sent to at least the loop-back interface
Also send multicast UDP to every selected network interface.
2020-11-06 00:33:53 +00:00
Bill Somerville
c15f244a09
Comment out diagnostic prints 2020-11-05 11:30:48 +00:00
Bill Somerville
caa23f1101
Message Client allows sending multicast UDP on multiple interfaces 2020-11-05 03:37:01 +00:00
Bill Somerville
3bc3103004
UDP multicast TTL default as one
Restricts scope to local subnet.
2020-11-04 16:02:04 +00:00
Bill Somerville
11497cf0b1
Correct Qt version checks 2020-11-03 23:44:07 +00:00
Bill Somerville
d70cf120b5
Pre Qt 5.14 compatibility 2020-11-03 23:14:26 +00:00
Bill Somerville
698bd23a9c
Disallow sending UDP Message Protocol traffic to broadcast address 2020-11-03 23:08:12 +00:00
Bill Somerville
a6a176bf6e
Pre Qt v5.11 compatibility 2020-11-03 23:07:38 +00:00
Bill Somerville
0df1ce9f64
Add network interface selection combo box widget to message_aggregator 2020-11-03 20:31:11 +00:00
Bill Somerville
1a223f5c45
Remove unwanted file and directory 2020-11-03 20:29:25 +00:00
Bill Somerville
8516a4f538
New combo box with a list of checkable items 2020-11-03 20:28:29 +00:00
Bill Somerville
014812e6c6
UDPDaemon command line flag to list network interfaces 2020-11-02 22:08:37 +00:00
Bill Somerville
93d1e17005
Extend UDP MessageServer client mapping key with the host address
The UDP Example reference applications  now work correctly with WSJT-X
instances with duplicate --rig-name= command line arguments so long as
duplicate instances are run on unique hosts.
2020-11-02 21:35:48 +00:00
Bill Somerville
430d57c1ca
Network interface selection for outgoing UDP multicast datagrams
Default  selection  is  the  loop-back interface.  Users  who  require
interoperation  between  WSJT-X   instances  cooperating  applications
running on different hosts should  select a suitable network interface
and  carefully choose  a multicast  group address,  and TTL,  that has
minimal scope covering the necessary  network(s). Using 224.0.0.1 is a
reasonable    strategy    if   all    hosts    are    on   the    same
subnet. Administratively  scoped multicast group addresses  like those
within 239.255.0.0/16  can cover larger  boundaries, but care  must be
taken if the local subnet has access to a multicast enabled router.

The  IPv4  broadcast  address  (255.255.255.255) may  be  used  as  an
alternative  to multicast  UDP, but  note that  WSJT-X will  only send
broadcast UDP datagrams  on the loop-back interface,  so all recipient
applications must be running on the same host system.

The reference UDP Message protocol  applications are being extended to
be configurable  with a list of  interfaces to join a  multicast group
address on. By default they will only join on the loop-back interface,
which is also  recommended for any applications designed  to take part
in the WSJT-X  UDP Message Protocol. This allows full  user control of
the  scope of  multicast  group membership  with  a very  conservative
default  mode  that will  work  with  all interoperating  applications
running on the same host system.
2020-11-02 15:33:44 +00:00
Bill Somerville
072da278ee
Documentation updates 2020-10-29 22:40:19 +00:00