virtualsquare / virtualsquare/vuos
socket virtualization is still unstable
Open
Nobody has claimed this yet.
bug
- Dominant language
- C
- Stars
- 49
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
ssh and netcat seem to work properly when accessing the network through unrealsock.
w3m has problems with the name resolution. iceweasel doew not work (and sometimes break the entire umvu hypervisor).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported behavior through unrealsock with w3m and iceweasel, comparing it with the working ssh and netcat cases. Done means name resolution works for w3m, iceweasel works reliably, and neither case breaks the umvu hypervisor.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100