macos hyperkit NAT mode network (VPN share issue)
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.7k
- Forks
- 336
- PR merge metrics
- No merged PRs in 30d
Description
Hyperkit network is configured in bridged mode and not configured as a NAT mode, which makes an issue with VPN clients which only allow/pass connections from domicile host.
Is it possible to start/configure crc/hyperkit to switch to NAT mode?
The culprit is marked bolded, can not remove it from routing table, and it writes packet to this IP 192.168.64.2, which is dropped by the VPN policy.
default link#26 UCSI bridge1 !
192.168.64 link#26 UC bridge1 !
192.168.64.2 e.f0.e3.c7.4f.be UHLWIi bridge1 1188
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 how Hyperkit configures macOS networking and compare the current bridged setup with the routing table shown in the issue. Done would mean a supported way to use NAT mode so VPN policies accept connections from the host.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, macos
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100