Commit Graph

17 Commits

Author SHA1 Message Date
Bill Somerville 9ea903b259
Merge branch 'develop' into feat-boost-log 2020-11-12 13:36:25 +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 698bd23a9c
Disallow sending UDP Message Protocol traffic to broadcast address 2020-11-03 23:08:12 +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 5a7291b690
Abort incomplete DNS lookup at shut down 2020-10-11 00:02:08 +01:00
Bill Somerville b37e419fc7
Qt 5.15 compatibility 2020-08-19 12:32:27 +01:00
Bill Somerville 7bafb5b71e
Qt5.7 backwards compatibility 2020-08-07 22:40:15 +01:00
Bill Somerville 1f524026f9
Fix merging issue 2020-07-26 15:55:17 +01:00
Bill Somerville 7bb5a8e009
Merge branch 'develop' into feat-psk-reporter-re-work 2020-07-26 15:52:39 +01:00
phl0 6cbc91b653
Include prop mode in ADIF and UDP messages 2020-06-26 23:45:58 +01:00
Bill Somerville a24f402655
Skipping of connection refused net errors on Windows with Qt 5.15
Apparently this is still required.
2020-06-26 17:57:21 +01:00
Bill Somerville b48b23450d
First iteration of optional TCP/IP client for PSK Reporter 2020-06-21 01:36:30 +01:00
Bill Somerville 9c22b5c3ed
Qt v5.15 compatibility 2020-06-13 16:04:41 +01:00
sirhc808 27d4471cde Merge branch 'ft9_refactor' into feat-refactor
# Conflicts:
#	CMakeLists.txt
#	lib/ft4/getcandidates4.f90
#	lib/ft4/sync4d.f90
2019-07-02 12:06:14 -05:00
sirhc808 ee5d5c8ae9 improve physical structure 2019-07-02 10:19:43 -05:00