linuxmint / linuxmint/warpinator

Linux multi user support for Warpinator

Open
#177 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
1.6k
Forks
115
PR merge metrics
No merged PRs in 30d

Description

Hi,
today I've tried Wapinator with user A on a Linux Mint 21.1 and with user B on the same PC. User A work fine, but user B didn't. I expected it to work, but it just showed me that there was some issue with the "protocols".
Actually I had no idea what is meant with that because in the UI there is no mention ( or setting) of a "protocol".
So I ran the debug and it told me that it failed to bind the IP with some GRPC something. At first I couldn't make something out of this either.
It took me quite a while to figure out that this is a multi user issue of concurrently running 2 Linux Mint user at the same time while having Warpinator also opened twice at the same time (once for each user).
In such a configuration one has to change the incoming ports for data transfer. After I've changed the ports to 42002 and 42003, it worked.
So maybe this can be documented and maybe there is a better way to handle this situation. Either by automatically changing the ports or by giving some more meaningful error messages in such situations.

Now that I know this , I'm fine but other Warpinator users may also run into this problem in the future.
Cheers

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing two Linux Mint users running Warpinator concurrently and inspect the debug output for the GRPC bind failure. Compare the current incoming-port settings with the reported workaround using ports 42002 and 42003; done means the multi-user behavior is documented or handled with a more meaningful error or automatic port choice.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, grpc, linux
Domain
networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.