Are the zero and zero2 both running the same release date of the same named release of the OS?
I'm asking because I've seen a related report in the last few days of X11 forwarding not working on the November release of Bookworm. Don't have the link to hand. Sorry.
That post did mention switching from Wayland to X via raspi-config and appeared to blaming that but I suspect that's a red herring as what's running on the local machine/console should have no impact on the remote display.
It's on my to do list to investigate (lack of remote x11 is a deal breaker for me) along with report of rc.local also being removed on that release but I've not yet had time (busy rebuilding my NAS server).
There is an insecure workaround though:
The main issues are that network traffic is not encrypted and that xhosts + will allow anyone on any machine to start programs that display on your X server.
Further firewall configuration may be required but that depends entirely on your setup.
Has been tested with RPiOS Bookworm running the X clients (Windows 11 and VcXsrv on the server end) but not with the latest RPiOS images.
I'm asking because I've seen a related report in the last few days of X11 forwarding not working on the November release of Bookworm. Don't have the link to hand. Sorry.
That post did mention switching from Wayland to X via raspi-config and appeared to blaming that but I suspect that's a red herring as what's running on the local machine/console should have no impact on the remote display.
It's on my to do list to investigate (lack of remote x11 is a deal breaker for me) along with report of rc.local also being removed on that release but I've not yet had time (busy rebuilding my NAS server).
There is an insecure workaround though:
- Configure your X server to listen on TCP. It's off by default as X is unencrypted.
- Add a suitable xhost command to your server machine's autostart. xhosts + opens it to every machine on your network. xhost IPAddress grants access to only the machine with the specified IP address.
- Reboot your X server machine (not the Pi)
- After logging in to the PI
Code:
export DISPLAY=myserver:0
The main issues are that network traffic is not encrypted and that xhosts + will allow anyone on any machine to start programs that display on your X server.
Further firewall configuration may be required but that depends entirely on your setup.
Has been tested with RPiOS Bookworm running the X clients (Windows 11 and VcXsrv on the server end) but not with the latest RPiOS images.
Statistics: Posted by thagrol — Sun Jan 05, 2025 2:09 am