Gnome Remote Desktop -- Allow over Ethernet and block over WiFi?

AI Thread Summary
Configuring GNOME Remote Desktop to share the desktop exclusively over the Ethernet interface while blocking WiFi connections is achievable through network-level access control. This can be done by setting up firewall rules or binding the service to the Ethernet interface. The configuration files for GNOME Remote Desktop are typically located in the user's home directory under ~/.config/gnome-remote-desktop, although these files do not support interface-specific settings. To enforce the desired network restrictions, users can utilize tools like ufw or iptables to allow traffic only on the Ethernet interface (commonly eth0) and deny it on the WiFi interface (usually wlan0). After applying these firewall rules, it is essential to restart the GNOME Remote Desktop service to implement the changes effectively.
Swamp Thing
Insights Author
Messages
1,031
Reaction score
769
Is it possible to configure Gnome Remote Desktop to share the desktop over the Ethernet interface but block connections over WiFi? Where is the config file for this daemon?
 
Computer science news on Phys.org
You can try these steps:

Yes, it is possible to configure GNOME Remote Deskto by controlling access at the network level using firewall rules or configuring GNOME Remote Desktop to bind specifically to the Ethernet interface.

NOTE: I've never attempted this.

Find the GNOME Remote Desktop Service Configuration File:

GNOME Remote Desktop is managed by gnome-remote-desktop. Its configuration is typically stored in:

Bash:
~/.config/gnome-remote-desktop

You may find files such as server.conf or similar. However, these files do not typically allow interface-specific configurations.

Configure Firewall Rules:

To limit access to Ethernet:

Bash:
ip link

Typically, Ethernet is eth0 or similar, and WiFi is wlan0.

Use ufw (Uncomplicated Firewall) or iptables to allow traffic only on the Ethernet interface. For example:

Bash:
sudo ufw allow in on eth0

sudo ufw deny in on wlan0

Or, using iptables:

Bash:
sudo iptables -A INPUT -i eth0 -p tcp --dport 3389 -j ACCEPT

sudo iptables -A INPUT -i wlan0 -p tcp --dport 3389 -j DROP

Replace 3389 with the port GNOME Remote Desktop is configured to use (commonly used for RDP or VNC).

Restart GNOME Remote Desktop:

After making changes, restart the GNOME Remote Desktop service:

Bash:
systemctl --user restart gnome-remote-desktop
 
  • Informative
Likes FactChecker, Swamp Thing and berkeman
I came across a video regarding the use of AI/ML to work through complex datasets to determine complicated protein structures. It is a promising and beneficial use of AI/ML. AlphaFold - The Most Useful Thing AI Has Ever Done https://www.ebi.ac.uk/training/online/courses/alphafold/an-introductory-guide-to-its-strengths-and-limitations/what-is-alphafold/ https://en.wikipedia.org/wiki/AlphaFold https://deepmind.google/about/ Edit/update: The AlphaFold article in Nature John Jumper...
Thread 'Urgent: Physically repair - or bypass - power button on Asus laptop'
Asus Vivobook S14 flip. The power button is wrecked. Unable to turn it on AT ALL. We can get into how and why it got wrecked later, but suffice to say a kitchen knife was involved: These buttons do want to NOT come off, not like other lappies, where they can snap in and out. And they sure don't go back on. So, in the absence of a longer-term solution that might involve a replacement, is there any way I can activate the power button, like with a paperclip or wire or something? It looks...
Back
Top