-b IPv4 not working
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 2.2k
- Forks
- 353
- Avg merge
- 1h 4m
- Merged PRs (30d)
- 1
Description
Hello,
with some big support from outside, microsocks is finally listening on 0.0.0.0. Thx.
Nevertheless I still have the problem to bind target output to an IPv4 address.
Option "-b IPv4" is ignored on my Deb9+ systems and IPv6 addresses are bound/used.
Is there any hint or trick in order to motivate microsocks to use the IPv4 addresses on these systems for target adresses?
I can provide traces if needed. No problem.
Thx in advance
Oliver
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
No source files or tests are named. Start by reproducing the issue on a Debian 9+ system with -b IPv4, then trace how the bind option is parsed and how target address families are selected. Done means target connections consistently use the requested IPv4 address; add or update a regression test if the project provides one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- cli, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100