Page 2 of 2
Re: RUMlogNG - Updates
Posted: Thu 12. Feb 2015, 00:02
by DL2RUM
Can you try to connect the TRX to Fldigi? You have to swap both Fldigi related CAT check boxes
Good trick: tcpdump -nnvi lo0 port 7362 but don't work here. What I have to do?
Code: Select all
tcpdump: lo0: You don't have permission to capture on that device
((cannot open BPF device) /dev/bpf0: Permission denied)
MBA13:~ dl2rum$
Re: RUMlogNG - Updates
Posted: Thu 12. Feb 2015, 19:49
by kf5jra
DL2RUM wrote:Can you try to connect the TRX to Fldigi? You have to swap both Fldigi related CAT check boxes
What is odd is that with RUMlog fldigi follows the VFO. This only happens with RUMlogNG.
Good trick: tcpdump -nnvi lo0 port 7362 but don't work here. What I have to do?
Code: Select all
tcpdump: lo0: You don't have permission to capture on that device
((cannot open BPF device) /dev/bpf0: Permission denied)
MBA13:~ dl2rum$
run that with sudo.
Re: RUMlogNG - Updates
Posted: Thu 12. Feb 2015, 20:49
by DL2RUM
What happens, when you disable all the TRX CAT and uses Fldigi for CAT? You don't to set up Fldigi for CAT, frequency exchange should work in both directions.
Re: RUMlogNG - Updates
Posted: Fri 13. Feb 2015, 16:49
by kf5jra
This did not work with RUMlogNG. I am out of ideas
-Ron
Re: RUMlogNG - Updates
Posted: Fri 13. Feb 2015, 16:57
by DL2RUM
Me too! Anybody else reading here?
Can you check the Console for messages from RUMlogNG?
Re: RUMlogNG - Updates
Posted: Sat 14. Feb 2015, 00:06
by kf5jra
Don't hate me for this but I moved RUMlogNG and Fldigi to a different computer and all is working perfectly. New computer is running 10.10.x where old computer is running 10.9.x.
Go figure. Thank you for the rapid response and guidance.
-Ron
Re: RUMlogNG - Updates
Posted: Sat 14. Feb 2015, 09:29
by DL2RUM