3/30/2023 0 Comments Fldigi setup instructionsL1-cli fundchannel $(l2-cli getinfo | jq. L1-cli proxy-connect $(l2-cli gid ) 55555 # NOTE: the tcp port here MUST match that used above in the "-proxy_out" parameter Upon success, you will note Successful echo over proxy! and server finished in the logs. Sent via fldigi to the listening proxy, and sent back to the test server, which checks that the packets match the test server sends four short binary packets captured from a node handshake in lnproxyĪfter a short delay, packets should start flowing from the test server to the sending proxy.Open a new terminal (Terminal 2) and start the TCP test server.Open a new terminal (Terminal 1) and start second fldigiįldigi -config-dir config_fldigi -arq-server-port 7323 -xmlrpc-server-port 7363.Open a new terminal (Terminal 0) and start first fldigi.NOTE: check which ports are already in use before assigning any here. fldigi_proxy.py -xml 7362 -proxy_in 2288 -modem 'PSK125R ' -rigmode 'CW ' -carrier 1500 TCP proxy test # Make an *outbound* connection to remote TCP port 2288, change some fldigi radio-specific settings on startup # Listen for an *inbound* connection on port 8822, attach to an fldigi instance listening on xml port 7362 # Radio settings are unspecified so default to transceiver mode = USB, carrier = 1500 Hz, modem = PSK125R The nohead, rigmode, carrier, modem settings can be set independently of the other flags that change proxy or test behavior.The default is to make an outbound connection setting proxy_out means the proxy will expect to receive an outbound connection.proxy_out sets the mode for the proxy port between expecting an inbound or outbound connection.fldigi-proxy can also start its own fldigi instance, but this uses the system config dir.by default, fldigi-proxy will attach to an fldigi instance with an XML-RPC interface open.The relevant flags for running in TCP proxy mode are daemon, xml, proxyport, and proxy_out.fldigi-proxy will not run without any flags, and running in TCP proxy mode requires the proxy ports to be listening before start.This LOOPBACK program has been tested and successfully used.You should be able to set up an audio loopback when fldigi is using PortAudio.In pavucontrol, the bars in the Playback and Recording tabs should be in sync.Test the audio loopback by playing some music - you should see output in the waterfall panel at the bottom of the fldigi GUI.PulseAudio settings are persistent, so all future fldigi instances should now use this 'audio loopback' setup.This means fldigi will listen on your default audio output instead of your microphone or other default source in PulseAudio.With fldigi running, open pavucontrol, and under the 'Recording' tab, set the fldigi process to capture from 'Monitor of $SINKNAME sink'.Skip the remaining setup pages fldigi should start, buts needs to be restarted to save the audio settings.On the second page (Audio), select PulseAudio (or PortAudio if not on Linux) leave the server field empty if using PulseAudio.Skip the first page of the initial setup.Even though we don't use the fldigi ARQ interface, we need the two fldigi instances to not collide on those ports. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |