Troubleshooting • Running wayvnc server in a network namespace?

Hi All,

Just did a clean install of pi os (bookworm, kernel 6.6, release july 4th 2024) on a pi5 and the wayvnc service works fine.

I then followed the demonstration at https://www.wireguard.com/netns/ to create an isolated network namespace for physical interfaces, with the init namespace isolated to a VPN connection via a wireguard interface.

WAN traffic is working fine over the VPN. LAN traffic works fine in the 'physical' netns. System services are not reachable on the LAN, as expected. For example, while the sshd system service is no longer reachable, but running a new instance in the 'physical' netns allows for SSH access over the LAN: I have been trying to figure how to get a wayvnc server running on the LAN as well (manually running it for testing first, not trying to add a system service yet). I created a copy of /usr/sbin/wayvnc-run.sh (called by the wayvnc service) as wayvnc-run-physical.sh, preceded the wayvncctl and wayvnc commands with and replaced all instances of with Running wayvnc-run-physical.sh seems to set things up alright - i'm able to connect to the pi over the LAN using a vnc client however the display is blank and gray.

I've tried attaching wayland-1 with and get
"ERROR: Failed to execute command: attach: Failed to connect to WAYLAND_DISPLAY="wayland-1"
Ensure wayland is running with that display name"

Running results in a Segmentation fault. While works fine.

Before going any further I just wanted to post and see if I am missing something, or going about getting wayvnc working in the 'physical' namespace the wrong way. Any help is greatly appreciated.

Statistics: Posted by 0nobody0 — Mon Jul 29, 2024 4:48 am

---