Any hamlib enabled software (WSJT-X, JS8Call, Flidigi, etc.) that is built with a later version of hamlib allows one to put in "ip:port" in lieu of a COM1, COM2, etc. However, AFAIK, this is an IP port and not a UDP port. Nevertheless, you may wish to try this in order to skip over wfview and go direct to the 705.
If you wish to continue to use wfview, it's a good bet that selecting IC7300 as the rig type and point it at 127.0.0.1:4533 will work.
I realize it can be counterintuitive to type an ip:port where you normally see "COM1", but that's how hamlib works.
View Quote
in the suite of protocols known as "TCP/IP", IP is layer 3 (network layer) and is among other things the address, e.g. 127.0.0.1 or in the case of my 705 192.168.1.30.
Above IP (i.e. the next protocol in the stack, which is encapsulated in the IP packet) is the transport layer 4, which is almost always either TCP or UDP. TCP being connection-oriented with 3way hand shake and flow control and ability to detect and resend lost packets, etc, and UDP being the much lighterweight and faster connectionless option. TCP is usually things like websites (HTTP) etc and UDP is usually media (the voice in VOIP, video streaming, etc).
it wouldn't be completely shocking for CAT to be TCP and the audio to be UDP. But in this case, the 705 only supports UDP for CAT. You can change the port number to something other than 50001, but you can't change it from UDP to TCP.
I would love to skip wfview and go straight from js8call to the 705. What's stopping me there is the security in the icom705. For network control, you have to enter a username and password. WFVIEW supports authentication and js8call hamlib does not. (there's simply no place to enter it in the config)
wfview has the ability to act as a "radio server" which allows you to create a username and password to access wfview server.
wfview also has the simple "external control" which doesn't support authentication. this latter option is what i have to use to communicate with js8call.
(i suspect those are two entirely different protocols, and even if i could turn off authentication in the 705, mixing them wouldn't work)
i'm not sure what you mean by "it's a good bet that selecting IC7300 as the rig type and point it at 127.0.0.1:4533 will work" but once you select ic7300 in js8call, it disables the text box for inputting IP Address and port. That option is only available when you select hamlib. and that's what i'm doing. i configure wfview to listen on 4533, and point hamlib in js8call to talk to the localhost on port 4533, and that's what's working.
if you mean selecting 7300 in wfview, then no, you'd need to put the 705's real address 192.168.1.30 and the 50001 port it's listening on, instead of the laptop's loopback address 127.0.0.1. maybe i'm not following you on that.
the wfview documentation is really helpful. thanks for that link!