Default subnet (192.168.65.0/24) may overlap with hosts network
Nobody has claimed this yet.
- Dominant language
- OCaml
- Stars
- 1.2k
- Forks
- 214
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
when running vpnkit in Docker-for-Windows the adresses for the builtin DNS names are chosen from the 192.168.65.0/24 subnet.
As this may overlap with an existing network of the host, other targets within that IP range are not accessible from within the containers.
Is it maybe possible to make the builtin subnet configurable when running vpnkit through docker-for-windows? I know there is a cli option for that, but I am unable to expose this through e.g. dockers daemon.json.
Appreciate any help or tips on this.
Regards,
Holger
Contributor guide
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 tracing vpnkit's existing CLI option for configuring the builtin subnet and how Docker-for-Windows passes settings through daemon.json. Determine where that integration can expose the subnet configuration; done means Docker-for-Windows users can set a non-overlapping builtin subnet.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, ocaml
- Domain
- devops, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100