I simply cannot get this to work. Back in March I had detailed advice on this forum (arvidjaar) but sadly I coudn’t follow or reproduce the advice and it only ever worked on first attempt, I never had a connection which survived reboot.
Being a simple soul I thought I would start with both machines, my laptop as client running minimwatch with wifi connection to private network and Leap 15.3 machine running minimserver and with copper lan connection to the same subnet connected. Both machines had firewalls set to trusted. In these circumstances minimwatch works and all is good.
I then increased the security level on the laptop from trusted to internal and lost the minimwatch connection. Since the only connection to the laptop is through wifi I checked the interface:-
alastair@localhost:~> firewall-cmd --get-zone-of-interface=wlp3s0
internal
alastair@localhost:~>
Seemed OK so I looked at services and ports and this is what I get:-
alastair@localhost:~> sudo firewall-cmd --list-services
[sudo] password for root:
You're performing an operation over default zone ('public'),
but your connections/interfaces are in zone 'docker,home,internal' (see --get-active-zones)
You most likely need to use --zone=docker option.
alastair@localhost:~> sudo firewall-cmd --list-ports
You're performing an operation over default zone ('public'),
but your connections/interfaces are in zone 'docker,home,internal' (see --get-active-zones)
You most likely need to use --zone=docker option.
9790/tcp 9791/tcp 1900/udp
alastair@localhost:~>
Following the hint I looked;-
alastair@localhost:~> firewall-cmd --get-active-zones
docker
interfaces: docker0
home
interfaces: enp0s25
internal
interfaces: wlp3s0
alastair@localhost:~>
The ports are remnants from earlier attempts following advice from minimserver website but where does docker come from I ask, and why is the problem on the client when I haven’t even touched the server?
No idea what is going on but always grateful for guidance. I just want this to work.