morgan/UxPlay
1
0
Fork 0
mirror of https://github.com/morgan9e/UxPlay synced 2026-04-15 00:34:05 +09:00
Code Issues Packages Projects Releases Wiki Activity

README: add instruction for avahi service on non-systemd systems

Browse Source
This commit is contained in:
F. Duncanh
2023-01-16 01:52:24 -05:00
parent bb5b70305b
commit 105df46772
3 changed files with 21 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
README.html
View File

@@ -370,12 +370,14 @@ client’s drop-down “Screen Mirroring” panel, check that your DNS-SD
server (usually avahi-daemon) is running: do this in a terminal window server (usually avahi-daemon) is running: do this in a terminal window
with <code>systemctl status avahi-daemon</code>. If this shows the with <code>systemctl status avahi-daemon</code>. If this shows the
avahi-daemon is not running, control it with avahi-daemon is not running, control it with
<code>sudo systemctl [start,stop,enable,disable] avahi-daemon</code> (or <code>sudo systemctl [start,stop,enable,disable] avahi-daemon</code> (on
avahi-daemon.service). If UxPlay is seen, but the client fails to non-systemd systems, such as *BSD, use
connect when it is selected, there may be a firewall on the server that <code>sudo service avahi-daemon [status, start, stop, restart, ...]</code>).
prevents UxPlay from receiving client connection requests unless some If UxPlay is seen, but the client fails to connect when it is selected,
network ports are opened: if a firewall is active, also open UDP port there may be a firewall on the server that prevents UxPlay from
5353 (for mDNS queries) needed by Avahi. See <a receiving client connection requests unless some network ports are
opened: if a firewall is active, also open UDP port 5353 (for mDNS
queries) needed by Avahi. See <a
href="#troubleshooting">Troubleshooting</a> below for help with this or href="#troubleshooting">Troubleshooting</a> below for help with this or
other problems.</p> other problems.</p>
<ul> <ul>

7
README.md
View File

@@ -314,9 +314,10 @@ iOS client's drop-down "Screen Mirroring" panel, check that your DNS-SD
server (usually avahi-daemon) is running: do this in a terminal window server (usually avahi-daemon) is running: do this in a terminal window
with ```systemctl status avahi-daemon```. with ```systemctl status avahi-daemon```.
If this shows the avahi-daemon is not running, control it If this shows the avahi-daemon is not running, control it
with ```sudo systemctl [start,stop,enable,disable] avahi-daemon``` (or with ```sudo systemctl [start,stop,enable,disable] avahi-daemon``` (on non-systemd systems, such as \*BSD,
avahi-daemon.service). If UxPlay is seen, but the client fails to connect use ``sudo service avahi-daemon [status, start, stop, restart, ...]``). If UxPlay is
when it is selected, there may be a firewall on the server that prevents seen, but the client fails to connect
when it is selected, there may be a firewall on the server that prevents
UxPlay from receiving client connection requests unless some network ports UxPlay from receiving client connection requests unless some network ports
are opened: if a firewall is active, also open UDP port 5353 (for mDNS queries) are opened: if a firewall is active, also open UDP port 5353 (for mDNS queries)
needed by Avahi. See [Troubleshooting](#troubleshooting) below for needed by Avahi. See [Troubleshooting](#troubleshooting) below for

17
README.txt
View File

@@ -373,14 +373,15 @@ done. If the UxPlay server is not seen by the iOS client's drop-down
avahi-daemon) is running: do this in a terminal window with avahi-daemon) is running: do this in a terminal window with
`systemctl status avahi-daemon`. If this shows the avahi-daemon is not `systemctl status avahi-daemon`. If this shows the avahi-daemon is not
running, control it with running, control it with
`sudo systemctl [start,stop,enable,disable] avahi-daemon` (or `sudo systemctl [start,stop,enable,disable] avahi-daemon` (on
avahi-daemon.service). If UxPlay is seen, but the client fails to non-systemd systems, such as \*BSD, use
connect when it is selected, there may be a firewall on the server that `sudo service avahi-daemon [status, start, stop, restart, ...]`). If
prevents UxPlay from receiving client connection requests unless some UxPlay is seen, but the client fails to connect when it is selected,
network ports are opened: if a firewall is active, also open UDP port there may be a firewall on the server that prevents UxPlay from
5353 (for mDNS queries) needed by Avahi. See receiving client connection requests unless some network ports are
[Troubleshooting](#troubleshooting) below for help with this or other opened: if a firewall is active, also open UDP port 5353 (for mDNS
problems. queries) needed by Avahi. See [Troubleshooting](#troubleshooting) below
for help with this or other problems.
- By default, UxPlay is locked to its current client until that client - By default, UxPlay is locked to its current client until that client
drops the connection; the option `-nohold` modifies this behavior so drops the connection; the option `-nohold` modifies this behavior so