Welcome, Guest
Username: Password: Remember me

TOPIC: Couldn't connect on RHEL 9 - First a blocking FW and then port bound by anydesk

Couldn't connect on RHEL 9 - First a blocking FW and then port bound by anydesk 11 Jul 2022 09:36 #1

  • hari
  • hari's Avatar
  • OFFLINE
  • Posts: 26
  • Thank you received: 8
Hello,
just to make you aware, I had to change the firewall on a default RHEL9 install for ExpertSDR2 to work. All good so far, was quite happy that it now does work fine on RHEL9 (libraries were too old on RHEL8). Weird enough, it stopped working a few days later. I completely flushed all firewall tables, checked policies, was wondering about selinux.. couldn't get it to work. On the terminal it did just show:
ControlSunSDR2::Open(  true ): Can't open DevCmd: ( 50001 , QHostAddress("192.168.1.200") )!
ControlSunSDR2::Open(  true ): Can't open DevCmd: ( 50001 , QHostAddress("192.168.1.200") )!
ControlSunSDR2::Open(  true ): Can't open DevCmd: ( 50001 , QHostAddress("192.168.1.200") )!

I hadn't got the nerves to dig further but tried "kappanhang" with my IC-705 the other day on the same computer. Funny enough ICOM also uses port 50001 for communication via network, and "kappanhang" gave a very clear error:
2022-07-10T21:49:22.158+0200	error	main@59: dial udp :50001->192.168.1.125:50001: bind: address already in use

Looking at what the heck binds that port:
$ sudo fuser -a 50001/udp
50001/udp:            1306
$ ps auxw |grep 1306
root        1306  0.0  0.0 573376 22172 ?        Sl   Jul05   0:05 /usr/libexec/anydesk --service

I did install anydesk a few days earlier to help a friend with his printer.. and that kept a background service running even after the GUI was closed, binding to that port. As soon as that process was killed, ExpertSDR2 could connect to the SunSDR2 DX just fine. Ideally ExpertSDR2 would also give a clear error message. Maybe that helps a fellow OM to not pull his hair..
73
vy 73 OE6HKE
Last Edit: 11 Jul 2022 09:41 by hari.
The administrator has disabled public write access.

Couldn't connect on RHEL 9 - First a blocking FW and then port bound by anydesk 11 Jul 2022 10:52 #2

  • Rome
  • Rome's Avatar
  • OFFLINE
  • Quod Licet Jovi Non Licet Bovi
  • Posts: 1076
  • Thank you received: 533
Hello Hari.
Thanks for sharing, this is actually explained in FAQ, section ESSENTIALS, questions#1 and 2.
eesdr.com/en/faq-en
Роман, Roman
Expert Electronics
Last Edit: 11 Jul 2022 10:52 by Rome.
The administrator has disabled public write access.
The following user(s) said Thank You: hari

Couldn't connect on RHEL 9 - First a blocking FW and then port bound by anydesk 11 Jul 2022 13:40 #3

  • hari
  • hari's Avatar
  • OFFLINE
  • Posts: 26
  • Thank you received: 8
see my face blush red... :roll:
I do read documentation usually.. no idea why I've not checked the FAQ this time.. bummer..
vy 73 OE6HKE
The administrator has disabled public write access.
The following user(s) said Thank You: Rome
Time to create page: 0.068 seconds