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,032
Reaction score
770
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
Well, the date has now passed, and Windows 10 is no longer supported. Hopefully, the readers of this forum have done one of the many ways this issue can be handled. If not, do a YouTube search and a smorgasbord of solutions will be returned. What I want to mention is that I chose to use a debloated Windows from a debloater. There are many available options, e.g., Chris Titus Utilities (I used a product called Velotic, which also features AI to prevent your computer from overheating etc...
I've been having problems for the past few weeks with the display on my Dell computer. I bought the computer new back in 2019 or so, which makes it about 6 years old. My monitor is a 27" HP monitor that I bought for another computer (an HP Pavilion), recently demised, back in about 2012 or 2013. As far as I can tell, the computer, which is running a 10-core Xeon Scalable processor, is functioning as it should. The first symptom was that the screen would go dark, which I would attempt to...
Back
Top