Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to access network adapter in bridged mode on Steam Deck #1314

Open
t1op opened this issue Dec 30, 2022 · 3 comments
Open

Unable to access network adapter in bridged mode on Steam Deck #1314

t1op opened this issue Dec 30, 2022 · 3 comments
Labels
bug Something isn't working

Comments

@t1op
Copy link

t1op commented Dec 30, 2022

Bug Description

Cannot capture from network adapter

  1. Launch xemu
  2. Select network
  3. Select Bridged mode
  4. Select any network adapter
  5. Initially I received errors about the address. Used flatseal to grant Xemu all available permissions.
  6. New error: "failed to open interface '[network adapter]' for capture; [network adapter]; You don't have permission to capture on that device (socket: Operation not permitted)"

Expected Behavior

No capture error when selecting a network adapter in bridge mode.

xemu Version

0.7.71

System Information

Steam Deck
Steam OS 3.4.4

Additional Context

#Help on discord comments suggest that flatpak on Steam Deck may be missing some necessary libraries and I could not find a /runtime folder for flatpak in /var
This issue was not encountered when running Xemu on Windows 11 laptop.

@t1op t1op added the bug Something isn't working label Dec 30, 2022
@HadetTheUndying
Copy link

This is an issue with flatpak not being able to change the required permissions. Find the binary and give it the permissions outlined here in the documentation.

https://xemu.app/docs/networking/#linux

This is not an issue that can be solved by the xemu devs, this is a Linux permissions issue, those permissions are restricted for security, I believe someone in Discord walked you through where the flatpak binary is located.

@t1op
Copy link
Author

t1op commented Dec 30, 2022

I used this script
sudo setcap cap_net_raw,cap_net_admin=eip which xemu
replacing 'which xemu' with the file path to the binary (I found multiple instances and ran the script for each instance).
This did not resolve the issue.

The files I used the script with were:
/var/lib/flatpak/app/app.xemu.xemu/
current/
[...long numeric string...] or active
x86_64/stable/
[...long numeric string...] or active
then what I expect are relevant files under each:
export/bin/app.xemu.xemu
export/share/applications/app.xemu.xemu.desktop
files/bin/xemu
files/lib/libpcap.so.1.10.1
files/share/applications/app.xemu.xemu.desktop

@HadetTheUndying
Copy link

It appears there's some issues with Flatpak's sandboxing stopping this from working. Locally compiled Binaries don't have this issue, so I don't think this issue will be resolved any time soon without some hacky solutions. It used to work which is strange but doesn't appear to anymore and I think it has to do with some recent flatpak updates. I recommend opening an issue in the flathub repo for xemu here https://github.com/flathub/app.xemu.xemu

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants